TECHZEN Zenoss User Community ARCHIVE  

Zenoss Updated time, can't login now!!!

Subject: Zenoss Updated time, can't login now!!!
Author: [Not Specified]
Posted: 2014-06-05 11:11

ype:
Value: 1401984100
Traceback (most recent call last): File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 126, in publish request, bind=1) File "/opt/zenoss/lib/python/ZPublisher/mapply.py", line 77, in mapply if debug is not None: return debug(object,args,context) File "/opt/zenoss/lib/python/ZPublisher/Publish.py", line 46, in call_object result=apply(object,args) # Type s to step into published object. File "/opt/zenoss/Products/ZenUtils/patches/pasmonkey.py", line 153, in login pas_instance.updateCredentials(request, response, login, password) File "/opt/zenoss/lib/python/Products/PluggableAuthService/PluggableAuthService.py", line 1100, in updateCredentials updater.updateCredentials(request, response, login, new_password) File "/opt/zenoss/lib/python/Products/PluggableAuthService/plugins/SessionAuthHelper.py", line 102, in updateCredentials request.SESSION.set('__ac_name', login) File "/opt/zenoss/lib/python/ZPublisher/HTTPRequest.py", line 1379, in __getattr__ v = self.get(key, default, returnTaints=returnTaints) File "/opt/zenoss/lib/python/ZPublisher/HTTPRequest.py", line 1336, in get v = v() File "/opt/zenoss/lib/python/Products/Sessions/SessionDataManager.py", line 101, in getSessionData return self._getSessionDataObject(key) File "/opt/zenoss/lib/python/Products/Sessions/SessionDataManager.py", line 188, in _getSessionDataObject ob = container.new_or_existing(key) File "/opt/zenoss/lib/python/Products/Transience/Transience.py", line 842, in new_or_existing self[key] = item File "/opt/zenoss/lib/python/Products/Transience/Transience.py", line 454, in __setitem__ current_bucket = self._data[current_ts] KeyError: 1401984100



Subject: Take a look at this older
Author: [Not Specified]
Posted: 2014-06-05 12:26

Take a look at this older post: http://www.zenoss.org/forum/1306

Hydruid



Subject: Yep, read that and waited
Author: [Not Specified]
Posted: 2014-06-05 12:58

Yep, read that and waited didn't work, not sure why changing the time breaks the entire system. I just said screw it and had to revert to a back up file and will try to change the time again. Which it will probably break again.



Subject: Make sure to stop zenoss and
Author: [Not Specified]
Posted: 2014-06-05 13:57

Make sure to stop zenoss and then change the time....

Hydruid



Subject: Not sure, but I reloaded from
Author: [Not Specified]
Posted: 2014-06-09 09:23

Not sure, but I reloaded from a back up which it fixed the time by it's self.



< Previous
DNS FQDN not resetting IP addresses.
  Next
Data Migration from 3.1.7 to 4.2.5
>