After upgrading ISPConfig to newest version (3.0.1.3 -> 3.0.1.4), all logs under "Server state" has stop updating.
Updating version 3.0.1.4 works fine. Update usualy is depending of something that needs to be updated. use apt-get update and apt-get upgrade. on debian based distros. and whait a couple of minutes to see the monitor green. Im just tring to help. im not a guru. By.
Install Manualy You can change internal version to make ispconfig think the version is outdated. and then update again. Or Manualy i think but use old db, first delete ispconfig from tmp folder. To install ISPConfig 3 from the latest released version, do this: cd /tmp wget http://downloads.sourceforge.net/ispconfig/ISPConfig-3.0.1.tar.gz?use_mirror= tar xvfz ISPConfig-3.0.1.tar.gz cd ispconfig3_install/install/ The next step is to run php -q install.php This will start the ISPConfig 3 installer:
I think it's a bit weird, since all crontabs is running.. but it still says: Data from: 2009-09-06 02:00
The problem occurres because of server.php is freezed. I solved it by killing the process. Read more about the problem at http://www.howtoforge.com/forums/showthread.php?t=39280&page=2
You mix up the server.php file and the cron_daily.file. webalizer, which reports the error "Warning: Truncating oversized request field [141903]" is executed by cron_daily.php and not server.php. The cron_daily is a different cronjob then the server cronjob. You should enable debugging on your server and see what causes your server.php file to hang. Might be something like apt that hangs if you run debian or ubuntu.
Yes i know that, the problem is in apt-get update and is coursed by a lock file not being deleted. What can i do about it?
As a first workaround you can comment out the line 120 ($this->monitorSystemUpdate() in the file /usr/local/ispconfig/server/mods-available/monitor_core_module.inc.php. Do you know the name of the apt lock file that does not get deleted? Maybe we can add a check for that file and dont run apt when it is there.
Okay. The lock file is: /var/lib/apt/lists/lock But i think it a bug in apt-get or something, since i can't use apt-get update before i delete the lock file manually. It's not happening all the time, and i can't reconstruct the error, right now it works fine because i have deleted the lock file.
