Bug#367341: [Fwd: Re: Bug#367341: monit failed to restart after upgrade]
Hi, monit-4.8.1 was released yesterday ... Martin Stefan Alfredsson wrote: (forwarding for reference. In summary - monit needs to be compiled on amd64 for the patch to be effective. It fails when started from initscripts but works with manual start -- I'll await 4.8.1 before doing further investigations) //Stefan Original Message Subject: Re: Bug#367341: monit failed to restart after upgrade From:"ngb" <[EMAIL PROTECTED]> Date:Wed, May 17, 2006 10:12 To: "Stefan Alfredsson" <[EMAIL PROTECTED]> -- Stefan, thanks for that. I have build the source without any trouble (although it did ask me to install byacc and cdbs which monit didn't need before). However when installing it I got the following: ruby:/home/ngb/monit# dpkg -i monit_4.8-2_amd64.deb (Reading database ... 163511 files and directories currently installed.) Preparing to replace monit 1:4.7-1 (using monit_4.8-2_amd64.deb) ... Stopping daemon monitor: monit. Unpacking replacement monit ... Setting up monit (4.8-2) ... Starting daemon monitor: monitinvoke-rc.d: initscript monit, action "start" failed. dpkg: error processing monit (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: monit However running "monit -d 240" from the command line started it with no problems. ruby:/home/ngb/monit# monit -d 240 Starting monit daemon with http interface at [*:2812] and I can log onto the web page and see that everything is working. thanks again for your help. cheers, Neil -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367341: [Fwd: Re: Bug#367341: monit failed to restart after upgrade]
(forwarding for reference. In summary - monit needs to be compiled on amd64 for the patch to be effective. It fails when started from initscripts but works with manual start -- I'll await 4.8.1 before doing further investigations) //Stefan Original Message Subject: Re: Bug#367341: monit failed to restart after upgrade From:"ngb" <[EMAIL PROTECTED]> Date:Wed, May 17, 2006 10:12 To: "Stefan Alfredsson" <[EMAIL PROTECTED]> -- Stefan, thanks for that. I have build the source without any trouble (although it did ask me to install byacc and cdbs which monit didn't need before). However when installing it I got the following: ruby:/home/ngb/monit# dpkg -i monit_4.8-2_amd64.deb (Reading database ... 163511 files and directories currently installed.) Preparing to replace monit 1:4.7-1 (using monit_4.8-2_amd64.deb) ... Stopping daemon monitor: monit. Unpacking replacement monit ... Setting up monit (4.8-2) ... Starting daemon monitor: monitinvoke-rc.d: initscript monit, action "start" failed. dpkg: error processing monit (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: monit However running "monit -d 240" from the command line started it with no problems. ruby:/home/ngb/monit# monit -d 240 Starting monit daemon with http interface at [*:2812] and I can log onto the web page and see that everything is working. thanks again for your help. cheers, Neil
Bug#367341: monit failed to restart after upgrade
Hello, Martin Pala wrote: > this is AMD64 only related bug which is addressed by this patch for > monit-4.8: > > http://www.tildeslash.com/monit/dist/monit-4.8-patch01 > > Neil Broderick wrote: >> Also trying to start monit manually results in: >> >> ruby:/home/ngb# monit >> Starting monit daemon with http interface at [*:2812] >> Segmentation fault I've applied the patch and just uploaded 4.8-2. As I don't have AMD64 myself, I would be grateful if you can try it out and report how it works. Thanks, Stefan
Bug#367341: monit failed to restart after upgrade
Hi, this is AMD64 only related bug which is addressed by this patch for monit-4.8: http://www.tildeslash.com/monit/dist/monit-4.8-patch01 We will release monit-4.8.1 soon which will contain the fix. Martin Neil Broderick wrote: Package: monit Version: 1:4.8-1 Severity: grave Justification: renders package unusable Hi, I upgraded to the latest version of monit on the weekend with the following result: 1 not fully installed or removed. Need to get 0B of archives. After unpacking 0B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up monit (4.8-1) ... Starting daemon monitor: monit/etc/init.d/monit: line 83: 13082 Segmentation fault start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null 2>&1 invoke-rc.d: initscript monit, action "start" failed. dpkg: error processing monit (--configure): subprocess post-installation script returned error exit status 139 Errors were encountered while processing: monit E: Sub-process /usr/bin/dpkg returned an error code (1) Also trying to start monit manually results in: ruby:/home/ngb# monit Starting monit daemon with http interface at [*:2812] Segmentation fault or ruby:/home/ngb# /etc/init.d/monit start Starting daemon monitor: monit/etc/init.d/monit: line 83: 13088 Segmentation fault start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null 2>&1 thanks, Neil -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-11-amd64-k8-smp Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages monit depends on: ii libc6 2.3.6-5GNU C Library: Shared libraries an ii libssl0.9.8 0.9.8a-8 SSL shared libraries monit recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367341: monit failed to restart after upgrade
Package: monit Version: 1:4.8-1 Severity: grave Justification: renders package unusable Hi, I upgraded to the latest version of monit on the weekend with the following result: >1 not fully installed or removed. >Need to get 0B of archives. >After unpacking 0B of additional disk space will be used. >Do you want to continue [Y/n]? y >Setting up monit (4.8-1) ... >Starting daemon monitor: monit/etc/init.d/monit: line 83: 13082 Segmentation >fault start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid >--exec $DAEMON -- $ARGS >/dev/null 2>&1 >invoke-rc.d: initscript monit, action "start" failed. >dpkg: error processing monit (--configure): > subprocess post-installation script returned error exit status 139 >Errors were encountered while processing: > monit >E: Sub-process /usr/bin/dpkg returned an error code (1) > Also trying to start monit manually results in: ruby:/home/ngb# monit Starting monit daemon with http interface at [*:2812] Segmentation fault or ruby:/home/ngb# /etc/init.d/monit start Starting daemon monitor: monit/etc/init.d/monit: line 83: 13088 Segmentation fault start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null 2>&1 thanks, Neil -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-11-amd64-k8-smp Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Versions of packages monit depends on: ii libc6 2.3.6-5GNU C Library: Shared libraries an ii libssl0.9.8 0.9.8a-8 SSL shared libraries monit recommends no packages. -- debconf-show failed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
