Go Back   HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials > ISPConfig 3 > General

Do you like HowtoForge? Please consider supporting us by becoming a subscriber.
Reply
 
Thread Tools Display Modes
  #21  
Old 7th March 2012, 15:58
drapsag drapsag is offline
Junior Member
 
Join Date: Apr 2011
Posts: 21
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Sorry, my fault. The cron.log is very long and that's from the beginning of the file which is probably from long ago.

I'll post more recent stuff in a bit.
Reply With Quote
Sponsored Links
  #22  
Old 7th March 2012, 18:42
drapsag drapsag is offline
Junior Member
 
Join Date: Apr 2011
Posts: 21
Thanks: 0
Thanked 0 Times in 0 Posts
Default

There are no errors in cron.log

I went through the whole log. There are a bunch of repeated messages about mailq being empty and others, but nothing about errors. The Warnings I posted earlier are at the top of the file which is from when the server was first installed a year ago so they won't apply any more. Sorry for the confusion earlier.
Reply With Quote
  #23  
Old 8th March 2012, 14:51
drapsag drapsag is offline
Junior Member
 
Join Date: Apr 2011
Posts: 21
Thanks: 0
Thanked 0 Times in 0 Posts
 
Default

Just as an FYI, since we couldn't find a resolution to this problem, I decided to try adding a new entry in cron to rm the lock file manually after the server.sh script was run.

This seems to work. My system updates properly, everything works and my System Monitor is showing correct information.

I'm sure this is not the right way to fix this issue, but just having the issue in the first place was causing major headaches over here, so I had to do something.
Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 05:02.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.