Can you copy the process information from the GUI and put it in here like this?

I have a similar issue with corruptions in the process table after a 2.4.x -> 2.5.x upgrade.  Navigating to /Processes/Zenoss (where Zenoss is my suborganizer for defining Zenoss process monitors), I see that some processes have a count greater than 1.  They should all be 1 except for zenhub (which matches both zenhub and zenhubworker).  All those with counts greater than 1 are broken.

Using zendmd to look at the Zope database I get:

The broken ones, zeneventlog, and zenwin have 3 identical entries.  zenprocess has 3 entries, including a weird view.

I have tried doing:

reindex()

commit()

and this doesn't resolve the errors; however it DID resolve the problem whereby zenprocess wouldn't start at all.  It also looks like process data IS now being collected for all processes, including those processes that seem to have corrupt instances.  I just can't see / modify the definition of the process.

Any good Zenoss gurus suggest commands / procedures to clean up the database non-destructively?

BTW, I suspect that similar reported errors with zenstatus after upgrade can be attributed to similar instance corruptions in Zope.

Cheers,

Jane

Are you working in a test environment, cpp-zen??  Mine is production and I am a bit loath to experiment until I have a quiet slot, but I did get a command to remove a particular instance of a process which did seem to work but, for me, the problem just moved to another instance.  I can't currently go back and try removing each instance.

To get all the instances of a Process, use:

for d in dmd.Processes.Zenoss.osProcessClasses.zenhub.instances():

     print d.id

where Zenoss is my process SubOrganizer - just omit this if all your process definitions are directly under /Processes,

and zenhub is the process you want to find instances for.

If you have a corruption, I think you will see more instances than actually exist, probably with identical hex number identifiers.  From this output, the first line is index 0, the second is index 1, and so on.

To delete an instance, (say the third line), use:

dmd.Processes.Zenoss.osProcessClasses.zenhub.instances._remove(dmd.Processes.Zenoss.osProcessClasses.zenhub.instances._objects[2])

If anyone who has this problem can safely try removing spurious / all instances and feedback here, that would be great.

You will also need to reindex() and commit() again or things certainly will be messed-up and you may go back to zenprocess not starting again.

I guess the other thing to try is going back to the earlier append here and trying the little script with the d.manage_delObjects(d.id).

Cheers,

Jane

Perhaps we should wait and see if anyone from development can expand a little on what these hex numbers are??  On my test system (which doesn't have messed up processes), when I use zendmd to list process instances for devices then some have a hex number after the name and some don't and I can't see any pattern as to whether they have the hex or not.

Any gurus out there who can divulge more about the internals of the process table?

Cheers,

Jane

Brilliant!  I hoped that might work but couldn't really try it out currently on my production system.  At an appropriate time, I will follow what you have done.

Still be nice to hear from someone about the internals of the process table though

Cheers,

Jane