From: Dick M. <di...@fo...> - 2008-04-27 17:51:42
|
I had logrotate fail last night on several files, for example: error: failed to compress log /var/log/apache2/access.log.1 I've no idea why and I'm not sure how repeatable that is - it works OK manually. I was going to leave it another night then I noticed: #man passwd sh: /bin/gunzip: No such file or directory fgets: No such file or directory Error reading man page /usr/share/man/man1/passwd.1.gz sh: /bin/gunzip: No such file or directory fgets: No such file or directory Error reading man page /usr/man/man1/passwd.1.gz No manual entry for passwd I'm just wondering if these are related. My path looks like: /bin:/usr/bin:/sbin:/usr/sbin Version is 1.3.5-2008-04-23-i586 Any suggestions? Dick |
From: Serge L. <fi...@in...> - 2008-04-27 19:28:27
|
Hi, Bruce moved gzip package to /usr/bin/. Not sure about logrotate, but "man" doesn't work due to wrong path in /etc/man.conf. -- Serge Dick Middleton wrote: > I had logrotate fail last night on several files, for example: > > error: failed to compress log /var/log/apache2/access.log.1 > > I've no idea why and I'm not sure how repeatable that is - it works OK manually. > I was going to leave it another night then I noticed: > > #man passwd > sh: /bin/gunzip: No such file or directory > fgets: No such file or directory > Error reading man page /usr/share/man/man1/passwd.1.gz > sh: /bin/gunzip: No such file or directory > fgets: No such file or directory > Error reading man page /usr/man/man1/passwd.1.gz > No manual entry for passwd > > I'm just wondering if these are related. > > My path looks like: /bin:/usr/bin:/sbin:/usr/sbin > > Version is 1.3.5-2008-04-23-i586 > > Any suggestions? > > Dick |
From: Dick M. <di...@fo...> - 2008-04-27 19:47:49
|
Serge, > Bruce moved gzip package to /usr/bin/. Not sure about logrotate, but "man" > doesn't work due to wrong path in /etc/man.conf. Easy when you know how! All these years and I never new that existed. Thanks Dick |
From: Bruce S. <bw...@ar...> - 2008-04-28 02:07:23
|
> > Bruce moved gzip package to /usr/bin/. Not sure about logrotate, but "man" > > doesn't work due to wrong path in /etc/man.conf. > > Easy when you know how! All these years and I never new that existed. Thanks for reporting the error. It's fixed in CVS. - BS |
From: Dick M. <di...@fo...> - 2008-04-28 09:00:02
|
Dick Middleton wrote: > Version is 1.3.5-2008-04-23-i586 > I had logrotate fail last night on several files, for example: > > error: failed to compress log /var/log/apache2/access.log.1 > > I've no idea why and I'm not sure how repeatable that is - it works OK manually. This has done it again. There's something wrong. It's even more curious because I have delaycompress set so it shouldn't be trying to compress these files anyway. It's also true that I'm using copytruncate for all the files that failed. I wonder what's changed to provoke this? Dick |
From: Serge L. <fi...@in...> - 2008-04-28 09:49:32
|
Hi Dick, Dick Middleton wrote: > Dick Middleton wrote: > > > Version is 1.3.5-2008-04-23-i586 > >> I had logrotate fail last night on several files, for example: >> >> error: failed to compress log /var/log/apache2/access.log.1 >> >> I've no idea why and I'm not sure how repeatable that is - it works OK manually. > > This has done it again. There's something wrong. It's even more curious > because I have delaycompress set so it shouldn't be trying to compress these > files anyway. I'm sorry in advance, I cannot allocate time to investigate the problem properly. Instead I may only suggest you to do several actions to minimize/avoid "the harm": - modify logrotate section and add "compresscmd". - I have no idea why but looks like the problem with environment, so please don't use for 'compresscmd' a command which is a bash wrapper, use exactly the binary (with necessary options). I think it helps. -- Serge > > It's also true that I'm using copytruncate for all the files that failed. > > I wonder what's changed to provoke this? > > Dick |
From: Dick M. <di...@fo...> - 2008-04-28 10:56:37
|
Serge, >>> I had logrotate fail last night on several files, for example: >>> >>> error: failed to compress log /var/log/apache2/access.log.1 > > - modify logrotate section and add "compresscmd". > - I have no idea why but looks like the problem with environment, so please > don't use for 'compresscmd' a command which is a bash wrapper, use exactly the > binary (with necessary options). I'll try that, thanks for suggestion. I'll let you know what happens. Dick |
From: Dick M. <di...@fo...> - 2008-04-29 16:47:35
|
Serge, > Well, I'm happy to know your system is OK. :-) > May I ask to share modified config lines? We'll add it to default logrotate > config to avoid such problem in future... In /etc/logrotate.conf compresscmd /usr/bin/gzip Dick |
From: Bruce S. <bw...@ar...> - 2008-04-29 17:28:43
|
> > Well, I'm happy to know your system is OK. :-) > > May I ask to share modified config lines? We'll add it to default logrotate > > config to avoid such problem in future... > > In /etc/logrotate.conf > > compresscmd /usr/bin/gzip Since I'm mucking around in the source code now, I added it to CVS. - BS |
From: Dick M. <di...@fo...> - 2008-04-29 07:02:43
|
Serge, > - modify logrotate section and add "compresscmd". > - I have no idea why but looks like the problem with environment, so please > don't use for 'compresscmd' a command which is a bash wrapper, use exactly the > binary (with necessary options). > > I think it helps. I have to say I'm surprised :-) but that worked OK last night. Have some extra kudos from me. Dick |
From: Serge L. <fi...@in...> - 2008-04-29 16:05:49
|
Hi Dick, Dick Middleton wrote: > Serge, > >> - modify logrotate section and add "compresscmd". >> - I have no idea why but looks like the problem with environment, so please >> don't use for 'compresscmd' a command which is a bash wrapper, use exactly the >> binary (with necessary options). >> >> I think it helps. > > I have to say I'm surprised :-) but that worked OK last night. Have > some extra kudos from me. Well, I'm happy to know your system is OK. :-) May I ask to share modified config lines? We'll add it to default logrotate config to avoid such problem in future... -- Serge |