| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1065.1 | Sounds like the default server is not pointing to a correct server? | MRBASS::PUISHYS | Project Leader Scheduler V3.0 for Digital UNIX | Fri Apr 12 1996 12:37 | 27 |
| HI Stephen,
In the cli do:
show server
what does it say?
show server servername
what does it say?
do a printenv
what does SCHED_DEFAULT_SERVER point to?
if sched_default_server is not defined are you executing the
/var/sched/sched_init for the shell you are in?
The way the server defaults is first: what sched_default_server is pointing to,
next to the node you are on.
All this can be overriden in the cli and gui. to override in gui it is done
at startup time:
xschedule servername
This is all in the user docs.
Now if the cli command show server servername does not work, than we have
some king of install/environment problem.
bob
|
| 1065.2 | Ok.... | DECWET::WHITE | Surfin' with the Alien | Fri Apr 12 1996 14:01 | 27 |
| # ps auxxww | grep sch
root 1047 0.0 0.4 10.5M 1.9M ?? S 07:55:56 2:26.93 /var/sche
d/sched_agent
root 7696 0.0 0.0 248K 72K ttypa S + 09:58:39 0:00.02 grep sch
root 1065 0.0 0.4 9.93M 1.9M ?? S 07:56:02 0:00.80 /var/sche
d/sched_listener
root 1089 0.0 0.1 5.49M 760K ?? I 07:56:12 0:02.56 sqlexec s
ched_db slugbt.zso.dec.com
root 1083 0.0 0.7 13.6M 3.6M ?? S 07:56:03 0:01.94 /var/sche
d/sched_engine
SCHEDULE> sho server
SCHED-E-NET_SRVNOTLISTEN, Server or Agent component is not available
SCHED-E-CMDFAIL, Command failure
SCHEDULE> sho server slugbt
SCHED-E-NET_SRVNOTLISTEN, Server or Agent component is not available
SCHED-E-CMDFAIL, Command failure
SCHEDULE>
SCHED_DEFAULT_SERVER=slugbt.zso.dec.com
This all worked before, I even created the sample jobs...
-Stephen
|
| 1065.3 | | MRBASS::PUISHYS | Project Leader Scheduler V3.0 for Digital UNIX | Fri Apr 12 1996 17:05 | 5 |
| Looks like you do not have part of the server running, The TXM is missing,
This is the transation manager that takes all the user request.Just do a
sched_startup as root and it should start. (txm never crashes.. this is starnge)
bob
|
| 1065.4 | hmmm.... | DECWET::WHITE | Surfin' with the Alien | Fri Apr 12 1996 18:32 | 30 |
| # sh scheduler_startup.sh
***
*** POLYCENTER Scheduler has STARTED all requested processes
*** Startup script procedure exiting with success.
***
# more slugbt_txm.log
SchedTrace::OpenSchedulerLog: Opened log file /var/sched/slugbt_txm.log
SchedTrace::OpenSchedulerLog: Start of Trace Information /var/sched/slugbt_txm.l
og
SchedTrace::CloseLog: closing log file...
# ps auxxww | sch
sch: Command not found.
# ps auxww | grep sch
root 1047 6.0 0.4 10.5M 1.9M ?? S 07:55:56 7:52.29 /var/sche
d/sched_agent
root 20776 0.0 0.0 248K 72K ttypa S + 14:30:12 0:00.01 grep sch
root 1065 0.0 0.4 9.93M 1.9M ?? S 07:56:02 0:01.21 /var/sche
d/sched_listener
root 1083 0.0 0.7 13.6M 3.6M ?? S 07:56:03 0:02.78 /var/sche
d/sched_engine
root 1089 0.0 0.1 5.49M 760K ?? I 07:56:12 0:02.56 sqlexec s
ched_db slugbt.zso.dec.com
# xschedule
Could not open server
#
Should I reinstall the product??
-Stephen
|
| 1065.5 | More stuff... | DECWET::WHITE | Surfin' with the Alien | Mon Apr 15 1996 20:12 | 22 |
| oleum.zso.dec.com> printenv
HOME=/usr/staff4/white
SHELL=/bin/csh
PATH=/usr/staff4/white/bin:.:/usr/staff4/white/bin:/usr/bin/mh:/usr/ucb:/bin:/us
r/bin:/usr/new:/usr/OV/bin:/usr/dec/bin.alpha:/var/sched
USER=white
TZ=
LOGNAME=white
MAIL=/usr/spool/mail/white
NNTPSERVER=ninja.zso.dec.com
LD_LIBRARY_PATH=/usr/shlib:/usr/ccs/lib:/usr/lib/cmplrs/cc:/usr/lib:/usr/local/l
ib:/usr/lib/cmplrs/cxx
OLDPATH=.:/usr/staff4/white/bin:/usr/bin/mh:/usr/ucb:/bin:/usr/bin:/usr/new:/usr
/OV/bin:/usr/dec/bin.alpha
SCHEDPATH=.:/usr/staff4/white/bin:/usr/bin/mh:/usr/ucb:/bin:/usr/bin:/usr/new:/u
sr/OV/bin:/usr/dec/bin.alpha:/var/sched
SCHED_DEFAULT_SERVER=slugbt.zso.dec.com
DISPLAY=16.64.0.210:0.0
oleum.zso.dec.com> xschedule
Could not open server
|
| 1065.6 | Please follow these steps and report back | MUZICK::MORIARTY | | Tue Apr 16 1996 19:33 | 22 |
|
Please check there is a database created /var/sched/sched.dbs.
There should be a directory /var/sched/schedule, there needs
to be a user "schedule" in the /etc/passwd file, and a "schedule"
group in the /etc/group file. The user and group "schedule" needs
to be user id and group id above 100.
Also, run the ivp for the server "setld -v SCHSRVR300" if this
is successful, then be sure you are properly configured by using
the command "#/var/sched/scheduler_startup.sh menu" and be sure
answer the questions for menu option 8 (be sure and give it a
full node name including the domain).
If the above does not work execute the startup as follows to
generate debug information about the TXM:
# /var/sched/scheduler_startup.sh 'TXM 1'
Then let us know what is in the lengthly txm log file (named
<nodename>_txm.log). This is the best process to follow.
|