Hi,
We have two servers running WHM latest CURRENT version. The backups are configured to backup and ftp to a remote off site server and it used to work flawlessly.
Now both servers are not performing the scheduled backups at all and I can not find out why.
When I try to manually run cpbackup, It starts the backup process for a few accounts, compresses them and actually sucessfully ftp's them to the remote server, then all of the sudden, the load gets really high and we get the following error:
"Can't call method "login" on an undefined value at /scripts/cpbackup line 399, <PWCACHEENT> line 33."
Looking at the daily cron email regarding cpbackup, this error message also occurs
"Waiting for load to go down to continue
Waiting for load to go down to continue
Waiting for load to go down to continue
Waiting for load to go down to continue
Waiting for load to go down to continue
Can't call method "login" on an undefined value at /scripts/cpbackup line 399, <PWCACHEENT> line 33."
This happens on both of our servers running WHM.
Any ideas on how to fix.
We have two servers running WHM latest CURRENT version. The backups are configured to backup and ftp to a remote off site server and it used to work flawlessly.
Now both servers are not performing the scheduled backups at all and I can not find out why.
When I try to manually run cpbackup, It starts the backup process for a few accounts, compresses them and actually sucessfully ftp's them to the remote server, then all of the sudden, the load gets really high and we get the following error:
"Can't call method "login" on an undefined value at /scripts/cpbackup line 399, <PWCACHEENT> line 33."
Looking at the daily cron email regarding cpbackup, this error message also occurs
"Waiting for load to go down to continue
Waiting for load to go down to continue
Waiting for load to go down to continue
Waiting for load to go down to continue
Waiting for load to go down to continue
Can't call method "login" on an undefined value at /scripts/cpbackup line 399, <PWCACHEENT> line 33."
This happens on both of our servers running WHM.
Any ideas on how to fix.