Job archive doesn't work. It use to work before.
We have this message:
CM0051 Unable to connect to ConfigMgmtSever process Cause: URN_NOT_FOUND : urn "Archive Mgmt" : Not found !! Action: Please restart ConfigMgmtSever process."
pdshow seems to be ok. But, I am afraid because there are few files on log folder:
2 drwxrwxr-x 5 casuser casusers 512 Apr 10 2008 .
2 drwxrwxr-x 29 casuser casusers 1024 Sep 23 12:44 ..
2 drwxr-x--- 2 casuser casusers 512 Dec 7 2006 conf
1360 -rw-r----- 1 casuser casusers 687588 Sep 21 12:48 ctm.log
2016 -rw-r----- 1 casuser casusers 1024000 Apr 10 2008 ctm.log.1
2 drwxrwxr-x 17 casuser casusers 512 Dec 5 2006 dfmLogs
2 drwxr-xr-x 2 root other 512 Dec 5 2006 dfmdb
2 -rw-r--r-- 1 root other 50 Dec 7 2006 schema.log
0 -rw-r----- 1 casuser casusers 0 Dec 5 2006 socketmessages.log
Operating system is solaris 5.8.
Cu has reboot, no change.
I don't see any errors here that would account for ConfigMgmtServer going down. As of 14:30 local time, it was working. Where are you seeing the error?
Yes. The job in question ran 12 days ago. The problem is no longer present now. If it happens again, you need to capture the logs immediately.
The daily job has stopped since 09/20. In fact the job is hang since 09/20 see screenshot3.jpg.
How can we stop this job ?
There is no screenshot attached. However, if the job is really running, pdshow should show a process with the job ID as its name. If you pdterm that process, the job will stop.
4303.1 and 4303.2 are successfull.
But, 4303.3, 4303.4 and 4303.5 failed and took more than one day.
If the customer stop and restart LMS, then jobs work for 2 or 3 days and then fail.
It happens manytime on Sunday, maybe there are a lot of jobs ?
What are the details of the failure? Yes, the job failed, but why? If you click on the job ID, why does it say the devices within the job failed?
I see a huge gap in the dcmaservice.log when this job should have run. It makes me think the server is crashing, but I see no other indications of that. The next time the job fails, before doing anything else with RME, open a TAC service request so this problem can be looked at in real time. A thread dump of ConfigMgmtServer may be required to figure out why it is not running the job.