Scheduler has been stopped
1997-05-20 07:46:18
Hi all,
1. Affected systems:
====================
3 out of 15 HP-clients V2.1.06 running on HP-UX 9.05 with
SCHEDMOD=Prompted
started by: nohup /usr/adsm/dsmc sched -quiet &
The server-system is an AIX-server V2.1.0.12
2. Tail of DSMSCHED.LOG
=======================
# tail -30 rzhp735b/dsmsched.log
19.05.1997 12:58:00 Schedule Name: RZHP735B
19.05.1997 12:58:00 Action: Incremental
19.05.1997 12:58:00 Objects: /
19.05.1997 12:58:00 Options:
19.05.1997 12:58:00 Server Window Start: 17:15:00 on 19.05.1997
19.05.1997 12:58:00
------------------------------------------------------------
19.05.1997 12:58:00 Waiting to be contacted by the server.
19.05.1997 12:58:00 Waiting to be contacted by the server.
19.05.1997 17:15:01 Querying server for next scheduled event.
19.05.1997 17:15:01 Next operation scheduled:
19.05.1997 17:15:01
------------------------------------------------------------
19.05.1997 17:15:01 Schedule Name: RZHP735B
19.05.1997 17:15:01 Schedule Name: RZHP735B
19.05.1997 17:15:01 Action: Incremental
19.05.1997 17:15:01 Objects: /
19.05.1997 17:15:01 Options:
19.05.1997 17:15:02 Server Window Start: 17:15:00 on 19.05.1997
19.05.1997 17:15:02
------------------------------------------------------------
19.05.1997 17:15:02
19.05.1997 17:15:02
Executing scheduled command now.
19.05.1997 17:15:02 Scheduler has been stopped.
3. The output of "nohup.out"
============================
# cat nohup.out
ADSTAR Distributed Storage Manager
Command Line Backup Client Interface - Version 2, Release 1, Level 0.6
(C) Copyright IBM Corporation, 1990, 1996, All Rights Reserved.
Querying server for next scheduled event.
Next operation scheduled:
------------------------------------------------------------
Schedule Name: RZHP735B
Schedule Name: RZHP735B
Action: Incremental
Objects: /
Options:
Server Window Start: 17:15:00 on 19.05.1997
------------------------------------------------------------
Waiting to be contacted by the server.
Waiting to be contacted by the server.
TCP/IP accepted connection from server.
Querying server for next scheduled event.
Next operation scheduled:
------------------------------------------------------------
Schedule Name: RZHP735B
Schedule Name: RZHP735B
Action: Incremental
Objects: /
Options:
Server Window Start: 17:15:00 on 19.05.1997
------------------------------------------------------------
Executing scheduled command now.
Executing scheduled command now.
Scheduler has been stopped.
4. Comments:
===========
1. In the above log I did a restart of the dsmc-client at 12:58 due to
"Scheduler has been stopped"
on the day before
2. At 17:15 the same day again the:
"Scheduler has been stopped"
3. A "core"-file has been produced as:
-r-------- 1 root sys 418652 Mai 19 17:15 core
4. running "xdb" with this core, delivers no useable info ( dsmc is
4. running "xdb" with this core, delivers no useable info ( dsmc is
"stripped" ? )
5. No further evidence in any of the system-log-files.
6. If I run this scheduled backup manually, all works well.
5. Questions:
=============
1. Is this failure known to ADSM'ers / IBM ?
2. Is there a workaround ?
3. Any further idea ?
--
MfG / Ciao - - - - - - - - - - - - - - - - - - - - - - - - - - - -
MfG / Ciao - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Peter Dümpert Email: p.duempert AT tu-bs DOT
de
Rechenzentrum der Technischen Universität Fax : ++49/531/391-5549
D 38092 Braunschweig Tel : ++49/531/391-5535
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Scheduler has been stopped,
Peter Duempert <=
|
|
|