| Title: | SCHEDULER |
| Notice: | Welcome to the Scheduler Conference on node HUMANE ril |
| Moderator: | RUMOR::FALEK |
| Created: | Sat Mar 20 1993 |
| Last Modified: | Tue Jun 03 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 1240 |
| Total number of notes: | 5017 |
Our Operator called me this weekend and said that the scheduler engine sent an error to the console on startup stating the scheduler did not startup properly, and to notify the system administrator... I've looked through the docs quickly, do not see a section on trouble-shooting startup issues... I have not touched it since the reboot this weekend, in case you people want me to post logs or something... what's the recommended trouble-shooting procudure here? I want to make sure this thing is going to start up on a reboot before I start creating jobs and stuff. -Stephen
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1076.1 | hello? | DECWET::WHITE | Surfin' with the Alien | Tue Apr 23 1996 17:55 | 0 |
| 1076.2 | Trace information at startup time | MUZICK::MORIARTY | Tue Apr 23 1996 21:46 | 29 | |
Stephen,
The best approach is similar note 1065.6 for the engine
startup:
# /var/sched/scheduler_startup.sh 'ENGINE -1 -1 -1 3'
or with V2.1 agent support use:
# /var/sched/scheduler_startup.sh 'ENGINE -1 -1 -1 3 -1 -1 -1 1'
Then let us know what is in the lengthly engine log file (named
<nodename>_engine.log). This is the best process to follow.
In general there is a file called trace_parameter.dat in the
directory /var/sched/tmp. I tell people to rename that file
to sched_parameter.dat and place it in the /var/sched directory.
Then use the "#/var/sched/scheduler_startup.sh menu" and pick
menu option "4) Startup file". Or just execute the command
after moving the file (please save old sched_parameter.dat).
# /var/sched/scheduler_startup.sh file
Please do this and let us know what the log is telling you.
| |||||
| 1076.3 | hold on a sec. | DECWET::WHITE | Surfin' with the Alien | Wed Apr 24 1996 16:24 | 23 |
I don't think the problem is with starting up the product on the running system, I think the problem is with starting up the product when the system boots... Thus the concern, if the system crashes late at night and we have a job schedule running, the product won't start and our jobs won't run. What I was looking for is some kind of startup log that would give us a clue as to why the product would not start on boot up. Also, since we have installed scheduler, the UNIX host has started crashing every couple of hours...we are not sure what the cause is, but one thing we do know is that since we have not started it...the system stays up. So I guess I need to chase down this problem first. Is there indeed a startup log for scheduler for when a system is coming up from a reboot? -Stephen | |||||