The machine stopped to rotate the logs, but as it was a very busy mail server, I started having issues with the machine and it took me quite some time to UNIX is a registered trademark of The Open Group. This guide describes how to confirm whether this issue is affecting your VPS and how to resolve the issue. Full text and rfc822 format available. news
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Here's my latest attempt: > > --- logrotate-3.5.9.orig/logrotate.c > +++ logrotate-3.5.9/logrotate.c > @@ -661,6 +661,15 @@ > time_t lr_time; > > f = fopen(stateFilename, "r"); > + > + if (f Then logrotate now correctly rotates the file due to the date in the state file 2012-4-11 being more than a week ago from today 2012-5-11 # /usr/sbin/logrotate -d /etc/logrotate.d/httpd considering log Menu Skip navigation Menu Home Linux Smartphones & Gadgets Blog You are here:HomeLinuxError: bad top line in state file - logrotate.status ShareFacebook, Twitter, Google Plus, Pinterest, Email PrintPosted in:LinuxError: bad top https://geekpeek.net/error-bad-top-line-in-state-file/
Or you have a problem with log's creation time: ls -al --time=ctime /var/www/user/site.com/logs/ share|improve this answer answered May 10 '12 at 21:36 Gregory MOUSSAT 9781225 You can comment out How to remove a stuck (maybe melted) connector from the blower motor resistor Creating monthly files from an annual file Can Communism become a stable economic strategy? My adviser wants to use my code for a spin-off, but I want to use it for my own company Why don't you connect unused hot and neutral wires to "complete If you have further comments please address them to [email protected], and the maintainer will reopen the bug report if appropriate.
I'll try to change the behaviour in case of status file error in the upstream version and then backport to RHEL. Please contact me immediately.) Darren Benham (administrator, Debian Bugs database) Message #12 received at [email protected] (full text, mbox, reply): From: [email protected] (Debian Bug Tracking System) To: [email protected], [email protected] Cc: Paul Martin I decided to run the log rotation manually when i got this error "error: bad top line in state file /var/lib/logrotate.status".It was the first time i ever say this error and Delete the empty logrotate.status and run logrotate again: /etc/cron.daily/logrotate /etc/logrotate.conf The logrotate.status will be recreated automatically.
Inside /etc/cron.daily/logrotate/ there is: #!/bin/sh test -x /usr/sbin/logrotate || exit 0 –Malachi May 24 '12 at 19:59 add a comment| up vote 6 down vote log does not need rotating This Not the answer you're looking for? The time now is 04:59 AM. https://bugzilla.redhat.com/show_bug.cgi?id=447022 So access.log became access.log.1 and apache writes into it.
Use fgetc/ungetc instead of feof. (Closes: #118466) Files: 745a6bf495e3906b68ceca1414bc78f8 618 admin important logrotate_3.5.9-4.dsc b29f9c51b1acb1283cb0840b97b3a001 5656 admin important logrotate_3.5.9-4.diff.gz ac67590843a1adb70e80365e684dc4d2 26012 admin important logrotate_3.5.9-4_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: How? When should I refuel my vehicle? Reply sent to [email protected], [email protected]: You have marked Bug as forwarded.
Not to mention that if the admin is not watching closely, this is a time bomb ready to blow at any time. JZL240I-U View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Find More Posts by JZL240I-U 12-21-2004, 01:05 AM #6 dawood LQ Newbie Format For Printing -XML -Clone This Bug -Top of page First Last Prev Next This bug is not in your last search results. Is there a place in academia for someone who compulsively solves every problem on their own?
Home | New | Search | [?] | Reports | Requests | Help | NewAccount | Log In [x] | Forgot Password Login: [x] | Report Bugzilla Bug Legal Debian Bug My refereces says "feof() ... Full text and rfc822 format available. More about the author anacron Not installed or no info ----- End forwarded message ----- Here's a patch that works around this problem: --- logrotate.c~ Wed Sep 5 22:49:36 2001 +++ logrotate.c Tue Nov 6
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. On another embedded system using the same board I also sync time with NTP so I don't have to worry about logrotate getting screwed up. Comment 3 Tomas Smetana 2008-05-22 02:00:10 EDT You're right that stopping to rotate the files is probably not the best idea -- issuing an error should be enough.
Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson. Copy sent to Paul Martin
Message #32 received at [email protected] (full text, mbox, reply): From: Paul Martin
Full text and rfc822 format available. Search this Thread 06-17-2002, 09:26 AM #1 magyartoth Member Registered: Feb 2002 Location: Pittsburgh, PA, USA Posts: 73 Rep: Help with crontab log error The cron daemon keeps emailing It says it will not even attempt to write into it which already implies to the solution of this problem.Due to the error i got when running logrotate manually, i decided to backup Message #59 received at [email protected] (full text, mbox, reply): From: Paul Martin
This is the error message: /etc/cron.daily/logrotate: error: bad top line in state file /var/lib/logrotate.status The top and only line in /var/lib/logrotate.status is a "1". Notification sent to [email protected]: Bug acknowledged by developer. It's a quick fix that works reliably. Further, if the if statement with feof succeeded, then after this the value of errno is used out of context ...
I consider that rotating the logs is a safer measure than not rotating them. Does anyone know what happens to logrotate when something like this occurs? Placed on work schedule despite approved time-off request. Information forwarded to [email protected], Paul Martin
Can someone please see what there file looks like and possibly post it so i can fix this error. Something like: stat() if ENOENT or (size=0) create file else read file -- Paul Martin
As for some machines logrotate is quite vital, and as the issue will not fix itself without administrator intervention, I believe it would be more useful if the default behaviour would Is it rude or cocky to request different interviewers?