Re: rsyslog init script breaks after package upgrade
Hi, > In which case I'm inclined to say this is a bogus kernel, which > prepends “ (deleted)” instead of appending it. You should report this > to the server provider. And I'm in principle going to just close this > bug report (instead of adding a workaround to s-s-d), as this might > break other userspace programs and should be fixed in the kernel side. One more note: To be honest, the behaviour of OpenVZ seems to make more sense than upstream Linux. I mean, what if a file called "/usr/sbin/rsyslogd (deleted)" actually exists? There is no way to distinguish whether this program was executed from a deleted version of "/usr/sbin/rsyslogd", or the current version of "/usr/sbin/rsyslogd (deleted)". The way OpenVZ makes it, however, these cases are easy to distinguish: If the link does not start with "/", it does not refer to an actually eixsting file. Kind regards Ralf -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532ab085.6060...@ralfj.de
Re: rsyslog init script breaks after package upgrade
Hi, > This seems also suspiciously similar to Chris' kernel: > > ,--- > Kernel: Linux 2.6.32-042stab081.5 (SMP w/20 CPU cores) > `--- > > In which case I'm inclined to say this is a bogus kernel, which > prepends “ (deleted)” instead of appending it. You should report this > to the server provider. And I'm in principle going to just close this > bug report (instead of adding a workaround to s-s-d), as this might > break other userspace programs and should be fixed in the kernel side. I will contact support, but my experience is that this does not reach people who even understand what I am talking about... :-/ I'd probably have to know someone in their tech team to actually get this fixed^^ (or use the magic password [0]) [0]: https://xkcd.com/806/ Kind regards Ralf -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532a2001@ralfj.de
Re: rsyslog init script breaks after package upgrade
Hi Guillem, > If --exec is supposedly broken then this would affect any daemon using > it, which I find a bit perplexing, and I'd have expected a ton of bug > reports on dpkg due to broken upgrades. I've rechecked it on current > unstable, and it still works here. That's surprising me, too. It works fine on my laptop, which uses testing. > Going over the original bug report I see this very suspicious line: > > ,--- > chrisb@massmail:~$ sudo ls /proc/427/exe -l > lrwxrwxrwx 1 root root 0 Dec 6 01:33 /proc/427/exe -> > (deleted)/usr/sbin/rsyslogd > `--- > > If this is really the contents of the exe symlink, then that's the reason > s-s-d cannot find the process. The expected contents of the symlink > when the inode has been unlinked should be «/pathname (deleted)». I can however confirm this observation. On my server, it says: > # ls -lah /proc/$(pidof rsyslogd)/exe > lrwxrwxrwx 1 root root 0 Mar 19 19:38 /proc/30211/exe -> > (deleted)/usr/sbin/rsyslogd > Chris, Ralf, what kind of kernel are you guys using? Is that a custom > one? Perhaps heavily patched? The system is running on a virtual server provided by Stato. I do not have access to the kernel - as in, I cannot (un)load modules or even choose my own. As far as I know, they are using OpenVZ for visualisation. At least, the root FS has type "vzfs". uname says: > # uname -srvmpo > Linux 2.6.32-042stab078.27 #1 SMP Mon Jul 1 20:48:07 MSK 2013 i686 unknown > GNU/Linux I hope this is helpful. Kind regards Ralf -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5329e52f.20...@ralfj.de
rsyslog init script breaks after package upgrade
severity 731530 important reassign 731530 dpkg 1.16.12 thanks Hi, this issue is still present in current wheezy, including the backports package. Without taking manual steps, it results in rsyslog filling up the disk as log rotation is completely broken - so I'd argue it should have a severity of important, at least (it may even be RC, as it should affect many packages - but only in rsyslog I see this problem, so far). I fixed this now on my system by replacing "--exec $DAEMON" in do_stop with "--name $RSYSLOGD". But that still leaves --exec rather useless for "stop", so I am also re-assigning the bug to dpkg (start-stop-daemon). Kind regards Ralf PS: I'm really looking forward to systemd solving all these issues at once... -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/532954a8.6060...@ralfj.de
