Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Blue

LMS 2.6 backup schedule issue

I got "Cannot read schedule info. Please look into the log files." when trying to change the backup location in LMS 2.6 Common Service. I don't see any pertinent log file getting updated in /var/adm/CSCOpx/log/. Is LMS having trouble reading the crontab?

1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: LMS 2.6 backup schedule issue

Correct, this error indicates a problem accessing the crontab file for casuser. The backup code will try to run crontab -l as casuser. If that fails, but the crontab file actually exists, then you will see this error.

6 REPLIES
Cisco Employee

Re: LMS 2.6 backup schedule issue

Correct, this error indicates a problem accessing the crontab file for casuser. The backup code will try to run crontab -l as casuser. If that fails, but the crontab file actually exists, then you will see this error.

Blue

Re: LMS 2.6 backup schedule issue

I got "crontab: you are not authorized to use cron. Sorry." when issuing "crontab -l" as a user with the same uid as casuser, who's in neither cron.allow nor cron.deny. Does that jive with everything happened so far? Can the backup mechanism from the GUI be tweaked to work with any other schedular than cron on Solaris?

Cisco Employee

Re: LMS 2.6 backup schedule issue

Chances are the perms on crontab have been changed. crontab must be:

-r-sr-xr-x 1 root bin 20336 Jan 22 2005 /bin/crontab

Note the setuid bit. As for using a different scheduler, this is not possible.

Blue

Re: LMS 2.6 backup schedule issue

The permissions look ok.

-r-sr-xr-x 1 root bin 17224 Nov 16 2006 crontab

After getting casuser added to cron.allow, I was able to modify the backup schedule from the GUI.

Would it make sense for the LMS install script to always append "casuser" to cron.allow on Solaris?

Cisco Employee

Re: LMS 2.6 backup schedule issue

cron.allow doesn't exist by default on Solaris. All that is required by default is for casuser NOT to exist in cron.deny. If a cron.allow does exist, then yes, casuser needs to be in there. We do check these things at installation time, but we do not modify these files. Instead, we will throw up a warning. If you check your installation log, the warning should be there provided the cron.allow file existed at installation time.

Blue

Re: LMS 2.6 backup schedule issue

That makes sense. The cron.allow/deny are recent additions.

179
Views
0
Helpful
6
Replies
CreatePlease to create content