Forums

RE: All Monitored Components Report not running

shakespear — Sun, 12 Jul 2009 17:22:04 GMT

Using .../manage and editing/storing the atttribute serial number doesn't lead to the conflict.

The traceback of the conflict:

Traceback (most recent call last): File "/opt/zenoss/lib/python/Zope2/App/startup.py", line 167, in zpublisher_exception_hook v.reraise() File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 120, in publish transactions_manager.commit() File "/opt/zenoss/lib/python/Zope2/App/startup.py", line 233, in commit transaction.commit() File "/opt/zenoss/lib/python/transaction/_manager.py", line 84, in commit self.get().commit(sub) File "/opt/zenoss/lib/python/transaction/_transaction.py", line 381, in commit self._saveCommitishError() # This raises! File "/opt/zenoss/lib/python/transaction/_transaction.py", line 379, in commit self._commitResources() File "/opt/zenoss/lib/python/transaction/_transaction.py", line 427, in _commitResources rm.tpc_vote(self) File "/opt/zenoss/lib/python/ZODB/Connection.py", line 637, in tpc_vote s = vote(transaction) File "/opt/zenoss/lib/python/ZEO/ClientStorage.py", line 893, in tpc_vote return self._check_serials() File "/opt/zenoss/lib/python/ZEO/ClientStorage.py", line 877, in _check_serials raise s ConflictError: database conflict error (oid 0x2ca84d, class BTrees._IOBTree.IOBucket, serial this txn started with 0x037f4aad83073777 2009-07-12 17:17:30.709732, serial currently committed 0x037f4aad956c4f22 2009-07-12 17:17:35.021035)

Hmm - doesn't help me

Is it normal that location and group are set several times with the same value? =>

2009-07-12 19:17:12 INFO zen.Device setting location to xxxx
2009-07-12 19:17:12 INFO zen.Device setting group ['yyyy']
2009-07-12 19:17:16 INFO zen.Device setting location to xxx
2009-07-12 19:17:16 INFO zen.Device setting group ['yyyy']
2009-07-12 19:17:23 INFO zen.Device setting location to xxx
2009-07-12 19:17:23 INFO zen.Device setting group ['yyy']
2009-07-12 19:17:31 INFO zen.Device setting location to xxx
2009-07-12 19:17:31 INFO zen.Device setting group ['yyyy']
2009-07-12 19:17:35 ERROR Zope.SiteErrorLog /zport/dmd/Devices/Server/Linux/devices/yxyx/editDevice

christian

RE: Monitoring using telnet (Command?)

djmuk — Sun, 12 Jul 2009 17:21:47 GMT

Yep that should help...

I have a one liner command that does the job & have spent a little ( ) time trying to run it as a command type data collector... I have FINALLY discovered that

1; setting ssh to false means that the command is run on the LOCAL system not on the remote system (so it should be called run locally...??)

2; That there is NO WAY to run a command on the remote system without using ssh despite the existence of hopeful looking zProperties variables like TelnetEnable...

I do find it frustrating that often the only way to really find out how it works is either to debug the deamons or look at the scripts (EG it was only when I saw local shell variables in the debug output that I realised that the SSH option switched to local execution...)

Ho hum now to borrow your expect script, I wonder if I can make the second part a one liner rather than a script.....

RE: All Monitored Components Report not running

shakespear — Sun, 12 Jul 2009 17:11:44 GMT

shakespear wrote:

After editing the serialnumber of an device I got:

A concurrent access to this object has been detected

This can happen under normal operations, where a Zenoss daemon is updating a device at the same time you edit it from the user interface. Try resubmitting your request (reload your browser) to see if the conflict is now resolved or navigate back to the object

... and the snmpperf collection stopped for this device.

I fear 2.4.2 seems broken seriously.

bye,
christian

Restarting zenoss doesn't solve this issue.

RE: All Monitored Components Report not running

shakespear — Sun, 12 Jul 2009 17:07:00 GMT

RE: 2.4.1 zenmodeler not using builtin snmp plugins

shakespear — Sun, 12 Jul 2009 15:59:25 GMT

I am having a similar symptom here - but some built in plugins are run. I was upgrading from 2.1.3. After upgrade everything seems ok. After changing CpuMap.py and deleting the .pyc it stopped working. Also after restarting zenoss and restoring the original CpuMap.py => the .pyc is not being generated.

I have no ideas what to.

christian