Bug#367341: [Fwd: Re: Bug#367341: monit failed to restart after upgrade]

2006-05-17 Thread Martin Pala
rther 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 Alf

Bug#367341: [Fwd: Re: Bug#367341: monit failed to restart after upgrade]

2006-05-17 Thread Stefan Alfredsson
ssage 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]> --

Bug#367341: monit failed to restart after upgrade

2006-05-15 Thread Stefan Alfredsson
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

Bug#367341: monit failed to restart after upgrade

2006-05-15 Thread Martin Pala
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 Justificatio

Bug#367341: monit failed to restart after upgrade

2006-05-15 Thread Neil Broderick
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 use