Debian/rpm package upgrades fail when Kibana is running

[seidler2547]

When installing Kibana via the Debian repository, the upgrade process fails because it wants to delete and re-create the user, which fails if Kibana is running. Hence the Kibana service should be stopped before the upgrade and restarted if it was running before. Most Debian package upgrades do this anyway to immediately make use of the new version.

[marcinkubica]

Same on Centos.

Sent from Gmail Mobile

[gebi]

The debian package of kibana is completely broken regarding user creation.
Please take a look at how it is done in the elasticsearch package.

[jaddison]

After manually stopping the kibana service and doing the apt upgrade of kibana, it fails to start due to permissions problems as well.

[gebi]

@jaddison yea here as well, that's because the debian package removes the system user on package upgrade and re-adds it shortly after.

If you have added any system user after first installing the kibana package all autogenerated files from kibana now have the wrong user and group.

[haizaar]

There is a workaround: #6310 (comment)

[LeeDr]

From a user on irc;

Preparing to unpack .../kibana_4.4.1_amd64.deb ...
Unpacking kibana (4.4.1) over (4.4.0) ...
userdel: user kibana is currently used by process 11323
dpkg: warning: subprocess old post-removal script returned error exit status 8
dpkg: trying script from the new package instead ...
userdel: user kibana is currently used by process 11323
dpkg: error processing archive /var/cache/apt/archives/kibana_4.4.1_amd64.deb (--unpack):
 subprocess new post-removal script returned error exit status 8
userdel: user kibana is currently used by process 11323
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 8
Processing triggers for systemd (215-17+deb8u3) ...
Errors were encountered while processing:
 /var/cache/apt/archives/kibana_4.4.1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
# 

[haizaar]

I wonder why it was not fixed in 4.5. The fix trivial and causes such a mess.

[stefws]

Still not fixed in rpm 4.5.1 :/ ... Maybe jbudz has a fix, seems he wants to pull...

[jbudz]

Fixed in #7308

[thers]

Not fixed for ubuntu 16.04 and kibana 4.5.3.

Still needs to stop kibana first.

[UPD]: event if i disabled it first, it won't install using apt, only running dpkg -i manually did the trick.

[haizaar]

Not fixed indeed. Had to manually stop kibana before upgrade.

On 24 Jul 2016 16:48, "Alexander Kuhta" notifications@github.com wrote:

Not fixed for ubuntu 16.04 and kibana 4.5.3

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6262 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADjWRgduC6VklZl38KEItrtI-FWOwXPks5qY21GgaJpZM4Ha76O
.

[splitice]

Confirmed still not fixed and causing a large mess.

userdel: user kibana is currently used by process with 2.5.3