LMS 3.2 / a lot of Java processes + some unamed

Answered Question
Dec 17th, 2009

Hello,

I have been connected on the LMS Portal/ System in a version LMS 3.2.

I saw that there is some process down with no names attached, under the Critical Message Window.

11 processes down but we don't know how to find them under the system., neither in RME nor CS.

What are theses processes ?

I have attached the snapshot of what we can see. I have made doing a PDSHOW and what we can see is that

theses processes are "shut down by administrator " , but the administrator told me that they didn't launched anything.

I have this problem too.
0 votes
Correct Answer by Michel Hegeraat about 6 years 11 months ago

I don't think so.

I think it's only a flag in the database that remains, indicating the job did not finnish..

It is then up to you to relaunch or delete the job.

Cheers,

Michel

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Michel Hegeraat Thu, 12/17/2009 - 03:13

Nothing really alarming here

The numerical processes:

   1536, 1019, 1590, 1843, 1013 42, 1017, 1020,1420, 1430, 1864, 1693

are jobs that may have been running when the ciscoworks proccesses where shut down.

You can find these jobs under Common services -> admin -> server -> job browser

UTMajorAcquisition is process that runs twice a day by default

DCRDevicePoll is running from time to time if you or someone else have turned it on

Cheers,

Michel

Michel Hegeraat Thu, 12/17/2009 - 03:24

Tiens...., normaly when I change the filter to JobID and enter the job Id it shows me the job.....

Not sure why this doesn't work for you

Cheers,

Michel

richard.tetu Wed, 12/30/2009 - 01:44

In fact, it 's not so important under our GUI .

Is someone has try to kill them , as for me, they use , for sure, memory allocation which rearrange hierarchy of processes ?

Richard

Correct Answer
Michel Hegeraat Wed, 12/30/2009 - 03:39

I don't think so.

I think it's only a flag in the database that remains, indicating the job did not finnish..

It is then up to you to relaunch or delete the job.

Cheers,

Michel

Michel Hegeraat Wed, 12/30/2009 - 07:31

I'm not following what you are trying to do here

PSKILL works on process id's

There is no relation between the process id and the jobid in ciscoworks

Cheers,

Michel

richard.tetu Wed, 12/30/2009 - 08:43

I used to check processes under Unix and UNix-like system.

I never used PSKILL but we could imagine that theses jobs could be seen like in UNis system, so that they could be killed in the same maner.

(Jobs are processus with depencies )

As PSKILL is relatively new ( 1rst December on Microsoft technet), for me too

I will try under lab machine and i will send a post.

Thanks a lot anyway. Michel

richard.tetu Mon, 05/17/2010 - 07:29

I have tried with the PSKILL Tool: it works .

I have made the test with a LMS 2.6 in Lab.I have done it with the Process Proxy list in the PdShow command.

After that the command has been executed, the RC is set to 0.

In the other side, the GUI don't remove from the list of the processus list the PID, but the RC is set to 0 equally to the PDSHOW.

Richard

Actions

This Discussion