Dear Sukhvir,
thanks for your bug report.
sukhvir wrote:
> I was trying to install xymon on ubuntu 18.4 lts, I am getting following
> error.
> chgrp: cannot access 'critical.cfg': No such file or directory
> chgrp: cannot access 'critical.cfg.bak': No such file or directory
> dpkg: error processing package xymon (--configure):
> installed xymon package post-installation script subprocess returned error
> exit status 1
[...]
> modified.conffile..etc.xymon.alerts.cfg: [deleted]
> modified.conffile..etc.xymon.analysis.cfg: [deleted]
> modified.conffile..etc.xymon.cgioptions.cfg: [deleted]
> modified.conffile..etc.xymon.client-local.cfg: [deleted]
> modified.conffile..etc.xymon.columndoc.csv: [deleted]
> modified.conffile..etc.xymon.combo.cfg: [deleted]
> modified.conffile..etc.xymon.critical.cfg: [deleted]
> modified.conffile..etc.xymon.critical.cfg.bak: [deleted]
> modified.conffile..etc.xymon.graphs.cfg: [deleted]
This is caused by the following (IMHO rather uncommon) case that
* the package xymon had been installed beforehand (not explicitly
mentioned, but obvious due to the deleted conffiles),
* has been removed again (but not purged, otherwise dpkg wouldn't know
about the conffiles),
* then someone deleted /etc/xymon/ manually (otherwise not all
conffiles would have been deleted),
* and tried to install xymon again.
Removing /etc/xymon/ (or any other conffile of any other package)
without purging ("apt-get purge" or "apt-get remove --purge") a
package makes dpkg think that the system administrator on purpose
remove these conffiles and hence respects this decision and doesn't
unpack them again.
While having removed _all_ conffiles manually without purging the
package, too, is theoretically a valid setup, it's nevertheless a
broken setup and breakage has to be expected then IMHO with most
packages.
So I'm not sure if I really should add support to the xymon package
for such a broken environment.
This breakage is btw. easily fixed: Do an "apt-get purge xymon" before
installing the package again. Be aware that this may also remove
monitoring data previously collected with xymon.
Thomas wrote:
> coping critical.cfg to critical.cfg.bak bypassed the error.
I think Thomas' case is slightly different, alone because in the above
case critical.cfg had been deleted, too. I actually expect further
breakage in the above case even if critical.cfg and critical.cfg.bak
are restored.
But Back to Thomas' case:
I though must admit that the file "critical.cfg.bak" (and _only_ that
file) doesn't really look like being relevant and might be deleted by
a local admin.
And this is actually a case we definitely need to handle better. I've
filed https://bugs.debian.org/924665 in Debian for that.
P.S.: Thanks to Thomas' variant of this issue, I became aware of the
fact that this issue might also happen if you just tried to clean up
your /etc/ from seemingly unnecessary backup files.
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
** Bug watch added: Debian Bug tracker #924665
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924665
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819378
Title:
package xymon 4.3.28-3build1 failed to install/upgrade: installed
xymon package post-installation script subprocess returned error exit
status 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xymon/+bug/1819378/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
