LMS 2.6 backup schedule issue

Answered Question
Nov 15th, 2007

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?

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 9 years 2 weeks ago

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.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Joe Clarke Thu, 11/15/2007 - 08:24

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.

yjdabear Thu, 11/15/2007 - 08:39

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?

Joe Clarke Thu, 11/15/2007 - 08:43

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.

yjdabear Thu, 11/15/2007 - 08:54

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?

Joe Clarke Thu, 11/15/2007 - 09:02

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.

yjdabear Thu, 11/15/2007 - 09:54

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

Actions

This Discussion