[solved] cronjob not running clean, unable to debug

Hi!

Please ignore my post. Problem solved, the SQL root login was not correct.

Matthias

Hi!

I have copied an existing test-installation of froxlor on a new system and made an upgrade to 0.9.19. Unfortunatly the cronjob seems not to be running clean. I get an error and the creation of awstats statistics is not working at all.

The lock-file did not get deleted, as the cronjob is not exiting correctly, but I am unable to see, why I get an error, and the point where the error occured.

The error, when starting the cron-job manually:

Establishing connection failed, exiting<br />
mysql error number: 0<br />
mysql error desc: <br />
Time/date: 04/04/2011 01:47 PM<br />
Script: <br />
Referer: <br />

new directories or customers get created correctly, so sql connection seems to work.

lock-File of above run:

Setting Lockfile to /var/run/froxlor_froxlor_master_cronjob.lock-27190
Setting Froxlor installation path to /var/shared/var/www/froxlor
Previous cronjob didn't exit clean. PID: 22668
Removing lockfile: /var/run/froxlor_froxlor_master_cronjob.lock-22668
Userdatas included
Table definitions included
Database Class has been loaded
Database-connection established
Froxlor settings have been loaded from the database
Checking froxlor file permissionsFroxlor version and database version are correct
Logger has been included
 cron_tasks: Searching for tasks to do

Another lock-File (after enabling debugging):

Setting Lockfile to /var/run/froxlor_froxlor_master_cronjob.lock-22668
Setting Froxlor installation path to /var/shared/var/www/froxlor
Userdatas included
Table definitions included
Database Class has been loaded
Database-connection established
Froxlor settings have been loaded from the database
Checking froxlor file permissionsFroxlor version and database version are correct
Logger has been included
 cron_tasks: Searching for tasks to do
 apache::createIpPort: creating ip/port settings for  *:80
 apache::createVirtualHosts: creating vhost container for domain 6, customer web1
 apache::createVirtualHosts: creating vhost container for domain 3, customer web1
 apache::createVirtualHosts: creating vhost container for domain 7, customer Alex
 apache::createVirtualHosts: creating vhost container for domain 4, customer web1
 apache::createVirtualHosts: creating vhost container for domain 2, customer web1
 apache::createVirtualHosts: creating vhost container for domain 9, customer web2
 apache::createVirtualHosts: creating vhost container for domain 10, customer web2
 apache::createVirtualHosts: creating vhost container for domain 1, customer web1
 apache::createVirtualHosts: creating vhost container for domain 8, customer web2
 apache::createVirtualHosts: creating vhost container for domain 5, customer web1
 apache::writeConfigs: rebuilding /var/shared/etc/apache2/sites-enabled/
 apache::wipeOutOldDiroptionConfigs: cleaning /var/shared/etc/apache2/sites-enabled/
 apache::writeConfigs: rebuilding /var/shared/etc/apache2/froxlor-htpasswd/
 apache::wipeOutOldHtpasswdConfigs: cleaning /var/shared/etc/apache2/froxlor-htpasswd/
 apache::writeConfigs: rebuilding /var/shared/etc/apache2/sites-enabled/
 apache::wipeOutOldVhostConfigs: cleaning /var/shared/etc/apache2/sites-enabled/
  apache::reload: reloading apache
 cron_tasks: Task4 started - Rebuilding froxlor_bind.conf
 cron_tasks: Task4 - Writing 4::xxxx.de
 cron_tasks: Task4 - `/var/shared/etc/bind/domains/xxxx.de.zone` zone written
 cron_tasks: Task4 - Writing 2::test123.de
 cron_tasks: Task4 - `/var/shared/etc/bind/domains/test123.de.zone` zone written
 cron_tasks: Task4 - Writing 9::test1234.de
 cron_tasks: Task4 - `/var/shared/etc/bind/domains/test1234.de.zone` zone written
 cron_tasks: Task4 - Writing 10::test12345.de
 cron_tasks: Task4 - `/var/shared/etc/bind/domains/test12345.de.zone` zone written
 cron_tasks: Task4 - Writing 5::xxxx.net
 cron_tasks: Task4 - `/var/shared/etc/bind/domains/xxxx.net.zone` zone written
 cron_tasks: Task4 - froxlor_bind.conf written
 cron_tasks: Task4 - Bind9 reloaded

Is there any way to see, where the cronjob stops?

Regards,

Matthias