Hi Eric,
 
In the end what I have done is to blow away the old version and re-entered everything on a new installation. I'm sorry as that doesn't help you in the debugging.
 
I finally got SVN installed on the server and did try as you suggest. The problem seemed to be that it was unable to update the ZOPE database. Right at the beginning of the script I was getting an error about not being able to move or delete something. I couldn't quite work that out. My guess is that this was why something wasn't being upgraded.
 
At first I dumped the MYSQL table and used the script to re-create it. zenxevent then started, but there were still holes in the ZOPE. It got to the point were I was probably introducing more problems than solving, but I now have a clearer understanding of how it all works.
 
In the end re-entering the data on a new install was the quickest way to get back on line. It seems to be working well at this point. I've seen a few errors when reading SNMP from devices, I'll post these once I get a few more things bedded down.
 
Regards
Eric.

>>> Eric Newton <[EMAIL PROTECTED]> 5/09/2006 11:22 pm >>>
Eric,

I fixed a logic error in the migration code (v. 2248).  Svn update and
try it again.

-Eric

Eric Belcher wrote:
> Hi Eric,

> Here is the errors from the migrate function.

> [EMAIL PROTECTED]:/usr/local/Zope-2.8.6-final/bin> ./zenmigrate run
> INFO:zen.migrate:Installing HoistPerfData
> INFO:zen.migrate:Installing InterfaceNameConvert
> INFO:zen.migrate:Database going to version 22.0
> INFO:zen.migrate:Installing Processes
> Recovering
> Traceback (most recent call last):
>   File "/usr/local/zenoss/Products/ZenModel/migrate/zenmigrate.py",
> line 9, in ?
>     main()
>   File "/usr/local/zenoss/Products/ZenModel/migrate/zenmigrate.py",
> line 6, in main
>     m. main()
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/Migrate.py", line
> 215, in main
>     self.cutover()
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/Migrate.py", line
> 116, in cutover
>     self.migrate()
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/Migrate.py", line
> 104, in migrate
>     m.cutover(self.dmd)
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/processes.py",
> line 23, in cutover
>     if not dmd.Processes.hasProperty('zFailSeverity'):
> AttributeError: Processes
> [EMAIL PROTECTED]:/usr/local/Zope-2.8.6-final/bin>

> This is the same as what is found in the zenbuild.log

> INFO:zen.migrate:Installing HoistPerfData< BR>> INFO:zen.migrate:Installing InterfaceNameConvert
> INFO:zen.migrate:Database going to version 22.0
> INFO:zen.migrate:Installing Processes
> Recovering
> Traceback (most recent call last):
>   File "/usr/local/zenoss/Products/ZenModel/migrate/zenmigrate.py",
> line 9, in ?
>     main()
>   File "/usr/local/zenoss/Products/ZenModel/migrate/zenmigrate.py",
> line 6, in main
>     m.main()
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/Migrate.py", line
> 215, in main
>     self.cutover()
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/Migrate.py", line
> 116, in cutover
>     self.migrate()
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/Migrate.py", line
> 104, i n migrate
>     m.cutover(self.dmd)
>   File
> "/usr/local/Zope-2.8.6-final/Products/ZenModel/migrate/processes.py",
> line 23, in cutover
>     if not dmd.Processes.hasProperty('zFailSeverity'):
> AttributeError: Processes

> Thanks
> Eric Belcher
>
>  
>>>> Eric Newton <[EMAIL PROTECTED]> 1/09/2006 10:24 pm >>>
>>>>        
> Oops... that should be
>
>     $ zenmigrate run --commit
>
> -Eric
>
> Eric Newton wrote:
>  
>> The migration script has to be run successfully to proceed.
>>
>>    $ zenmigrate run
>>
>>    $ zenmigrate run commit
>>
>> If it fails, send some details so we can wo rk that out.
>>
>> -Eric
>>
>> Eric Belcher wrote:
>>    
>>> Hi Eric,
>>> 
>>> It would appear that the mysql DB hasn't been updated. The error is
>>> about a missing field. See Below. The migration fails also. It
>>>      
> maybe
>  
>>> related, but I was leaving that until I solved the first part. I'm
>>>      
> not
>  
>>> seeing any errors in the build regarding mysql. 
>>> EBL-005:/usr/local/zenoss/bin # ./zenxevent run -v 10 --cycle
>>> DEBUG:zen.Events:EventClassInst=Start
>>> DEBUG:zen.Events:update status set clearid =
>>>      
> '0a67b4bf344d1410dfffffff'
>  
>>> where de vice='EBL-005.iacgs.qld.edu.au' and component='zenxevent'
>>>      
> and
>  
>>> eventKey='' and (eventClass='/App/Stop' or eventClass='/App/Start')
>>> ERROR:zen.Events:(1054, "Unknown column 'clearid' in 'field list'")
>>> Traceback (most recent call last):
>>>   File
>>> "/usr/local/Zope-2.8.6-final/Products/ZenEvents/MySqlSendEvent.py",
>>>      
> line
>  
>>> 19, in execute
>>>     result = cursor.execute(statement)
>>>   File "/usr/local/zenoss/lib/python/MySQLdb/cursors.py", line 137,
>>>      
> in
>  
>>> execute
>>>     self.errorhandler(self, exc, value)
>>>   File "/us r/local/zenoss/lib/python/MySQLdb/connections.py", line
>>>      
> 33,
>  
>>> in defaulterrorhandler
>>>     raise errorclass, errorvalue
>>> OperationalError: (1054, "Unknown column 'clearid' in 'field
>>>      
> list'")
>  
>>> ERROR:zen.Events:(1054, "Unknown column 'clearid' in 'field list'")
>>> Traceback (most recent call last):
>>>   File
>>> "/usr/local/Zope-2.8.6-final/Products/ZenEvents/MySqlSendEvent.py",
>>>      
> line
>  
>>> 87, in sendEvent
>>>     self.doSendEvent(event, db)
>>>   File
>>> "/usr/local/Zope-2.8.6-final/Products/ZenEvents/MySqlSendEvent.py",
>>>       
> line
>  
>>> 107, in doSendEvent
>>>     execute(curs, self.buildClearUpdate(event, clearcls))
>>>   File
>>> "/usr/local/Zope-2.8.6-final/Products/ZenEvents/MySqlSendEvent.py",
>>>      
> line
>  
>>> 24, in execute
>>>     raise ex
>>> OperationalError: (1054, "Unknown column 'clearid' in 'field
>>>      
> list'")
>  
>>> Traceback (most recent call last):
>>>   File "/usr/local/zenoss/Products/ZenEvents/zenxevent.py", line 87,
>>>      
> in
>  
>>> ?
>>>     z = ZenXEvent()
>>>   Fil e "/usr/local/zenoss/Products/ZenEvents/zenxevent.py", line 37,
>>>      
> in
>  
>>> __init__
>>>     EventServer.__init__(self)
>>>   File
>>>      
> "/usr/local/Zope-2.8.6-final/Products/ZenEvents/EventServer.py",
>  
>>> line 69, in __init__
>>>     component=self.name))
>>>   File
>>>      
> "/usr/local/Zope-2.8.6-final/Products/ZenEvents/EventServer.py",
>  
>>> line 96, in sendEvent
>>>     self.zem.sendEvent(evt)
>>>   File
>>> "/usr/local/Zope-2.8.6-final/Products/ZenEvents/MySqlSendEvent.py",
>>>      
> line
& gt;  
>>> 92, in sendEvent
>>>     raise ZenBackendFailure(str(e))
>>> Products.ZenEvents.Exceptions.ZenBackendFailure: (1054, "Unknown
>>>      
> column
>  
>>> 'clearid' in 'field list'")
>>> 
>>> Eric Belcher
>>> Manager - Technology Services
>>> Anglican Church Grammar School
>>> Oaklands Parade, East Brisbane
>>> [EMAIL PROTECTED] Phone 617 3896 2186
>>> Fax 617 3891 5976
>>>
>>>
>>> 
>>>      
>>>>>> Eric Newton <[EMAIL PROTECTED]> 29/08/2006 10:44 pm >>>
>>>>>>        
>>>>>>        &n bsp;   
>>> Run zenxevent with debugging turned on:
>>>
>>>     zenxevent run -v 10 --cycle
>>>
>>> Ignore the warning about the config, or just make one:
>>>
>>>     touch $ZENHOME/etc/zenxevent.conf
>>>
>>> You should be able to connect to zenxevent on port 8081:
>>>
>>>     http://localhost:8081 ( http://localhost:8081/ ) (
>>>      
> http://localhost:8081/ )
>  
>>> -Eric
>>>
>>> Eric Belcher wrote:
>>> 
>>>      
>>>> Hi,
>>>> 
>>>> Just tried to upgrade to 0.22.1. My main problem seems to be that
>>>> zenxevent doesn't start. Could I have a few things to check?
>>>> 
>>>> For example the config file is empty (zenxevent.conf). Is this
>>>> correct?
>>>> 
>>>> Thanks
>>>> Eric.
>>>> 
>>>> 
>>>>    
>>>>        
>>> _______________________________________________
>>> zenoss-users mailing list
>>> [email protected]
>>> http://lists.zenoss.org/mailman/listinfo/zenoss-users
>>>
>>> Disclaimer
>>> --------------------------------------------
>>> This email is intended  for the  use of the
>>> ; named individual or entity and may  contain
>>> confidential and privileged information.
>>> Any dissemination  distribution or  copying
>>> by anyone other than the intended recipient
>>> of this email is strictly prohibited.
>>>
>>> If this email has been received in error,
>>> please send an email in response, or telephone us immediately on +61
>>>      
>
>  
>>> 7 38962200,
>>> and destroy the original message. Any views
>>> expressed in  this message are those of the
>>> individual sender,  except where the sender specifically states them
>>>      
>
>  
>>> to be the views of
>>> the Corporation of the Synod of the Diocese
>>> of Brisbane or Churc hie.
>>>
>>>  
>>>
>>>      

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Disclaimer

This email is intended for the use of the named individual or entity and may contain confidential and privileged information. Any dissemination distribution or copying by anyone other than the intended recipient of this email is strictly prohibited. If this email has been received in error, please send an email in response, or telephone us immediately on +61 7 38962200, and destroy the original message. Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of the Corporation of the Synod of the Diocese of Brisbane or Churchie.

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to