I have tried this on both the integration instance and an brand new test instance.
Version info after upgrade:
$ sudo bin/kibana --version --allow-root
7.15.1
$ sudo bin/elasticsearch --version
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Version: 7.15.1, Build: default/tar/83c34f456ae29d60e94d886e455e6a3409bba9ed/2021-10-07T21:56:19.031608185Z, JVM: 11.0.12
It's not the full file; however, you are correct that the message does not appear in the log - it only appears on the console when I run kibana in the foreground.
The log is the associated log data from the time when I ran the command. Otherwise, the message is not logged.
Do you mean that Kibana crashes silently or does it function normally?
Right now it sounds like a potential bug. Would you mind creating a bug report and providing steps to reproduce the problem? Sign in to GitHub · GitHub
It crashes silently from my POV when I try and systemctl start kibana - journalctl indicates it starts successfully and then it must either hang or stop but systemctl doesn't indicate running if I check it's status. In that case (running as service), nothing at all is even logged in kibana.log.
Note: everything works just fine if I perform a rollback
If I run in the foreground it gives me the cannot read property error.
Issue is solved. It appears files from the old install may have been causing the issue. Moving the old install, copying back the appropriate folders, and setting the permissions corrected the issue.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.