Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade stops running service #9863

Closed
hundredacres opened this issue Jan 13, 2017 · 7 comments · Fixed by #82049
Closed

Upgrade stops running service #9863

hundredacres opened this issue Jan 13, 2017 · 7 comments · Fixed by #82049
Labels
Team:Operations Team label for Operations Team

Comments

@hundredacres
Copy link

Kibana version: 5.1.2

Elasticsearch version: 5.1.2

Server OS version: CentOS release 6.8

Browser version: n/a

Browser OS version: n/a

Original install method (e.g. download page, yum, from source, etc.): Yum

Description of the problem including expected versus actual behavior:

Yum update breaks a running service. The preinstall script stops the service, but the postinstall script doesn't start it up again. Either you stop managing the service, or you start it up again after upgrade.

Provide logs and/or server output (if relevant):

/var/log/messages:Jan 13 04:06:36 is04 /etc/init.d/kibana: Attempting 'stop' on kibana
/var/log/messages:Jan 13 04:06:36 is04 /etc/init.d/kibana: Killing kibana (pid 14082) with SIGTERM
/var/log/messages:Jan 13 04:06:36 is04 /etc/init.d/kibana: Waiting kibana (pid 14082) to die...
/var/log/messages:Jan 13 04:06:36 is04 /etc/init.d/kibana: kibana stopped.
/var/log/messages:Jan 13 04:06:41 is04 yum[11721]: Updated: kibana-5.1.2-1.x86_64
/var/log/messages:Jan 13 04:06:51 is04 /etc/init.d/kibana: Attempting 'stop' on kibana

My engineer had to manually start the process here -

/var/log/messages:Jan 13 04:23:08 is04 /etc/init.d/kibana: kibana is not running
/var/log/messages:Jan 13 04:23:14 is04 /etc/init.d/kibana: Attempting 'start' on kibana
/var/log/messages:Jan 13 04:23:14 is04 /etc/init.d/kibana: kibana started

@jbudz jbudz added Team:Operations Team label for Operations Team release_note:enhancement labels Jan 16, 2017
@sebunger
Copy link

The same happens on Ubuntu using the PPA provided packages. Is there a chance to get this fixed?

@Rittsel
Copy link

Rittsel commented Jul 14, 2017

This is still the case upgrading from 5.4.3 to 5.5 with RPM (yum on CentOS 7) with elastic repositories.

@sebunger
Copy link

I think this is mislabelled. It is not an enhancement request. It is a bug that really needs fixing.

@sebunger
Copy link

Happened again today when upgrading to 5.5.1.

@sebunger
Copy link

@jbudz could you check the labelling on this issue. I don't think "enhancement" is the correct label here.

@Diftraku
Copy link

This is also present in the Debian package when upgrading to 5.6.1 from the Elastic APT repo. Running Ubuntu 16.04

@jbudz jbudz changed the title RPM upgrade stops running service Upgrade stops running service Dec 7, 2017
jsoref added a commit to jsoref/kibana that referenced this issue Jul 4, 2018
jbudz added a commit to jbudz/kibana that referenced this issue Oct 29, 2020
This adds a new environment variable KBN_RESTART_ON_UPGRADE with a
default value of true.  In an upgrade scenario Kibana will automatically
restart.

Closes elastic#9863
@jxadams
Copy link

jxadams commented Jul 26, 2023

I am experiencing this on 7.17:

Scriptlet output:
1 Using bundled JDK: /usr/share/logstash/jdk
2 Using provided startup.options file: /etc/logstash/startup.options
3 OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
4 /usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/pleaserun-0.0.32/lib/pleaserun/platform/base.rb:112: warning: constant ::Fixnum is deprecated
5 Successfully created system startup script for Logstash
6 Stopping kibana service...Stopping kibana (via systemctl): [ OK ]
7 OK
8 Created elasticsearch keystore in /etc/elasticsearch/elasticsearch.keystore

Note that step 6 stops kibana rather than restarts it, and there is no later start of the service to compensate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Operations Team label for Operations Team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants