11-04-2009 06:01 AM
LMS imdediate backup works but cannot schedule. Got message 'Cannot read schedule info. Please look into the log files' which log I should check?
It did not work in 3.1 now upgraded to 3.2
11-04-2009 06:10 AM
It's "dbbackup.log" in NMSROOT\CSCOpx\log\ (on Windows) or /var/adm/CSCOpx/log/ (on Solaris). The "casuser" must have cron access on Solaris to be able to utilize the scheduled backup feature.
11-04-2009 06:18 AM
Tks for reply, no update to that file, it only got my last manual backup sucess info. and Casuer has full rights. any more idea?
11-04-2009 07:37 AM
Try to login as casuser and access
crontab -l
1) su casuser
2) crontab -l
11-04-2009 07:39 AM
It sounds like your LMS is on Windows? Does casuser have access to Windows AT service/facility? That appears to be the only prerequisite to schedule the backup. You may want to check Windows' Event Viewer for any security warning when your attempt fails.
11-05-2009 03:49 AM
yes, it on Windows.
Casuser is in the local admin group, there is no log in security event.
11-05-2009 05:35 AM
Another thread with the similar issue to yours just got bumped up. I think the hints and tips sprinkled throughout there may be useful to resolving your issue, such as checking stdout.log for errors, particularly concerning casuser access to cmd.exe:
11-05-2009 05:41 AM
thanks for the info.
I read that one, he cannot run immediate backup, in the screen dump. I can but just can't schedule it.
11-05-2009 05:47 AM
Hmmm, I thought two posters there said they couldn't schedule. Oh well, could you post your NMSROOT/MDC/tomcat/logs/stdout.log after a failed scheduling of backup, anyway?
11-05-2009 06:05 AM
11-06-2009 02:11 AM
according to the return code (retVal=143) I would say your schedule fails while executing the following command :
cmd.exe /c crontab.cmd
with crontab.cmd being lokated in NMSROOT\bin
and cmd.exe should be set in %ComSpec% variable of the OS;
open a DOS box and run it from there, - it should just tell that it is looking for the at command and return the table with the scheduled jobs, like this:
=====================
E:\PROGRA~1\CSCOpx>cmd.exe /c crontab.cmd
E:\PROGRA~1\CSCOpx>set atcommand=at
E:\PROGRA~1\CSCOpx>IF EXIST E:\WINDOWS\System32\at.exe set atcommand=E:\WINDOWS\System32\at.exe
E:\PROGRA~1\CSCOpx>E:\WINDOWS\System32\at.exe
Status ID Day Time Command Line
-------------------------------------------------------------------------------
1 Each Su 12:00 AM E:\PROGRA~1\CSCOpx\conf\backupsch.bat
====================
if it fails have a look if at.exe exists in the system32 folder and casuser has full access to it:
%SystemRoot%\System32\at.exe
(this is tested in crontab.cmd)
@jclarke or anybody who is interested in it... (NMSROT\cgi-bin\dbadmin\pdbadmin\schCommon.pl)
- in "schCommon.pl" the line 46 is a match like this :
until ($line =~ /---/ || $line == "");
It seems that they just want to get the array of scheduled tasks in @lines and get rid of the command lines (see output above). But because there is a blank line after each line there is a match with the first item in @lines (a blank line). So @lines contains the same as before just not the first blank line...
Can this also cause any problems when scheduling backups?
11-06-2009 02:52 AM
Thanks, found the root cause is window task schuder is disabled.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide