Bug 10625 - error: cannot stat /etc/logrotate.d: No such file or directory
Summary: error: cannot stat /etc/logrotate.d: No such file or directory
Status: CLOSED FIXED
Alias: None
Product: IPFire
Classification: Unclassified
Component: logrotate (show other bugs)
Version: 2
Hardware: unspecified Unspecified
: - Unknown - Major Usability
Assignee: Michael Tremer
QA Contact:
URL:
Keywords:
: 10531 10762 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-09-19 15:12 UTC by M.A.
Modified: 2015-04-21 21:28 UTC (History)
6 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description M.A. 2014-09-19 15:12:20 UTC 
Hello! :)

The logrotation is not possible.
it ends up with 
error: cannot stat /etc/logrotate.d: No such file or directory

to solve the problem, just create the folder /etc/logrotate.d or otherwise remove the corresponding line in /etc/lograte.conf :

<<< snip
# packages drop log rotation information into this directory
include /etc/logrotate.d
snap >>>

example: one consequence of not logrotating is a veeeeeery long time of waiting for the perl script proxylog.dat to function properly and getting results, because the access.log was getting very big (1,6 GB)

It would be nice to optimize this perl script although: 
Suggestion: because the log is filled in chronologic order, it is NOT necessary to analyse each line fully! Just check the date first and stop analyzing when the date is older than the searched one. Everything older than 1 year can be ignored

regards and thank you for the great product!

Markus
Comment 1 M.A. 2014-09-19 15:18:39 UTC 
addition to perl script: 
/srv/web/ipfire/cgi-bin/logs.cgi/proxylog.dat

if you press "Update/Aktualisieren" more than once you can fire more than one perl process which can lead into hanging ipfire machine, if the access.log is too big.
Comment 2 saco 2014-12-19 10:24:00 UTC 
Hello, 

with core 85, there is still this problem.

To solve the problem, just create the folder /etc/logrotate.d manually or otherwise remove the corresponding line in /etc/lograte.conf

One customer of us, had 46 GB logfiles yesterday. I hope it will be solved in the next ipfire version. 

It does not make sense to fix the problem after each new installation manually.

thanks
Andreas
Comment 3 Michael Tremer 2014-12-19 16:55:11 UTC 
Just to confirm this, logrotate doesn't rotate any logs at all if the directory does not exist?

I don't suppose that we will be able to do any performance improvements on that perl code in the next time.
Comment 4 M.A. 2014-12-19 17:25:52 UTC 
Hi,
i can confirm your suspicion. Just create the folder and everything is functioning properly. (you can check this in your normal update routine and / or create it at new installations)
Regards 
Markus
Comment 6 Arne.F 2015-02-23 13:00:46 UTC 
*** Bug 10531 has been marked as a duplicate of this bug. ***
Comment 7 Arne.F 2015-03-02 16:25:19 UTC 
*** Bug 10762 has been marked as a duplicate of this bug. ***
Comment 9 Stefan Schantl 2015-04-21 21:28:00 UTC 
Fix shipped with Core Update 89.