ISPC Cron-Log shows errors

[tilman]

Monitor -> Logfiles -> Show ISCP Cron-Log always shows: E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?
E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another process using it?

OS: Fresh ISPconfig 3 install on Debian Lenny 5.0.2

[falko]

Is another apt process running?

[tilman]

"Is another apt process running? " -> No, definitely not.

Just for testing purpose: I opened an aptitude instance -> worked fine.
Tried to open a second aptitude instance: Error because of the first aptitude instance running. This is the correct behavior.

[till]

Maybe you run a apt command manually at the time were this happened. This is uncritical, just keep an eye on it if this happens more often.

[tilman]

I did not run an apt command the time it happend. Might be this is an automatic scheduled apt command during startup of the server.
The server is for testing purpose only and started when it is needed.
The time of the errors shown in the log are always directly after booting the server.

[tilman]

Ok, let's come back on this issue.
I did some more investigation:
The error messages seem to be outdated. The content of the file: /var/log/ispconfig/cron.log is from the time of the server install and has never been updated.
If i run the crontab scripts manually, always "finished" is the output.

[till]

Thene verything is perfect. The cron log file contains only error messages, so you will never get the finished message there and if it does not contain new lines, then there vare no errors.

[tilman]

Seems to be a bit confusing if outdated errors are pending in a logfile. The logfile should be updated and show the actual status of the cron jobs. There is no information that the errors shown do not need any action.

[till]

If you want to see the current status, look into the ispconfig monitor. You just looked into the wrong file! The file you checked is only for errors and why shall old errors be deleted if vthe file shall contain the history of errors like nay error log file.

[tilman]

Ok, i can follow you, but each error line in the logfile should contain a timestamp.