[Resolved] Automated backups not working correctly via cron (Linux-VServer)

Since about a month ago, the automated cPanel/WHM backups haven't been working correctly. They used to work perfectly, but suddenly stopped working one day. My set up is as follows:
Backup interval = Weekly
Backup retention = Weekly and Monthly
Days to run backup = Wednesday
Backup type = Remote FTP

In the "Configure cPanel Cron Times" plugin I have cpbackup set to run every day at midnight. If I run /scripts/cpbackup manually, it works and I get an email about the backup being successful. The only log file in /usr/local/cpanel/logs/cpbackup is the log from when I ran the backup manually.

Any ideas on how to diagnose this issue?

 

It's configured like this:

 

Thanks for your reply, cPanelDon. Here's the output of those commands:

 

It stopped working at the end of July, and there's no records for the cronjob since then.

 

Yes:

Code:

root@quimby [/]# /etc/init.d/crond status
crond (pid  2030) is running...
root@quimby [/]# chkconfig --list crond
crond           0: off   1: off   2: on    3: on    4: on    5: on    6: off

I did notice the following in /var/log/cron, which is a bit odd:

Code:

2010-09-08T16:00:01.424856+10:00 quimby crond[12575]: Cannot make/remove an entry for the specified session
2010-09-08T16:00:01.424995+10:00 quimby crond[12575]: CRON (root) ERROR: failed to open PAM security session: Success
2010-09-08T16:00:01.425004+10:00 quimby crond[12575]: CRON (root) ERROR: cannot set security context
2010-09-08T16:01:01.427069+10:00 quimby crond[14658]: Cannot make/remove an entry for the specified session
2010-09-08T16:01:01.427246+10:00 quimby crond[14658]: CRON (root) ERROR: failed to open PAM security session: Success
2010-09-08T16:01:01.427254+10:00 quimby crond[14658]: CRON (root) ERROR: cannot set security context

Tried searching around but couldn't find any definite explanations on what's causing this. SELinux is disabled.

Edit: Trying the fix at 0002191: pam_loginuid fails with message: set_loginuid failed opening loginuid - CentOS Bug Tracker and seeing if that fixes it.
Edit 2: That appears to have fixed it. I edited the cpbackup cron to run now, and it ran correctly!
Also see: http://linux-vserver.org/Frequently_Asked_Questions#Why_do_neither_sshd_nor_crond_.28vixie-cron.29_work_correctly_in_my_CentOS_.2F_Fedora_guest.3F_I_get_.27pam_loginuid.28crond:session.29:_set_loginuid_failed_opening_loginuid.27_and_similar_lines_in_my_logs. (I'm using Linux-Vserver)

 

No worries, I thought it might be helpful to others. Now I just have to figure out what caused this issue. I'm using Linux-VServer and several vservers but actually own the server myself. I restarted the host server around the time it stopped working for kernel updates, so I might try and work out if an update was the cause.

Too bad I didn't notice it until now!