Richard,
Unfortunately that error message just says that zope encountered an
error when it was trying to render the standard error message page.
No info on the initial error.
You might get a bit more information out of zope by running in non-
daemon mode. Try this:
> zopectl stop
> runzope
This will run zope in the foreground and spit out messages to the
terminal. Try hitting zenoss in your browser and see if anything
interesting gets reported in the terminal. You can usually break out
of runzope with a ctl-c, though if that doesn't work you might need
to kill -9 from another terminal.
Also, what url are you hitting that seems to kill zope? And does it
die after you've gone through the login screen or before?
-jason
On Feb 1, 2007, at 7:08 AM, R J Thompson wrote:
I have found that zope is actually running, although when I connect
to the instance it dies and refuses new connections, event.log as
follows:
------
2007-01-30T17:41:58 ERROR root Exception while rendering an error
message
Traceback (most recent call last):
File "usr/local/zenoss/lib/python/OFS/SimpleItem.py", line 209,
in raise_standardErrorMessage
File "usr/local/zenoss/lib/python/OFS/DTMLMethod.py", line 144,
in __call__
File "usr/local/zenoss/lib/python/DocumentTemplate/DT_String.py",
line 476, in __call__
File "usr/local/zenoss/lib/python/DocumentTemplate/DT_Util.py",
line 196, in eval
File "<string>", line 1, in <expression>
Unauthorized: You are not allowed to access 'zenoss_error_message'
in this context
------
2007-01-30T18:07:52 INFO Z2 Caught signal SIGTERM
------
2007-01-30T18:07:53 INFO Z2 Shutting down fast
------
2007-01-30T18:07:53 INFO ZServer closing HTTP to new connections
Thanks
Richard
R J Thompson wrote:
Hi Ian
The migration was successful after doing that, thanks.
For some reason though I am unable to connect to Zope, the
logfiles show that Zenoss itself is running, with monitoring
information being logged, Z2.log has not updated since the
problem occured.
How would I check for any errors in this area?
Cheers
Richard
Ian McCracken wrote:
Richard,
That's essentially correct, although I'd probably check your
Python version /before/ blowing away your Five directory. Also, a
fresh install obviates the need for a zenmigrate, so you don't
have to do that step.
If, in the future, you do have to run zenmigrate, don't forget
that without the --commit option, none of the changes will be
permanent.
Ian
R J Thompson wrote:
Hi Ian
Thanks, so to perform an upgrade to the Trunk from my 1.0.2/1.1
broken install I would do the following :-
1. Remove $ZENHOME/Products/Five
2. Check Python version
3. run install.sh (I had errors here initially when the script
started checking out the svn source with overriding existing
files in $ZENHOME/bin)
4. zenmigrate run
Cheers
Richard
Ian McCracken wrote:
Richard,
Looks like a breakpoint accidentally got left in there...by me.
Thanks for the catch. I've just fixed it, so an install should
proceed normally now.
If you're upgrading to the trunk, make sure that:
a) You first get rid of the directory $ZENHOME/Products/Five
(.pyc files left over could prevent subversion from removing it)
b) You've got Python 2.4.3+. It's required by Zope 2.10.1, to
which we just migrated.
Ian
Ian
R J Thompson wrote:
Incidentally, it seems some of Zenoss is running from the
logfiles, but I cannot connect to the web interface,
zenactions.log for example is showing these errors -
2007-01-31 13:09:22 ERROR zen.ZenActions: unexpected exception
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenEvents/zenactions.py",
line 365, in runCycle
self.mainbody()
File "/usr/local/zenoss/Products/ZenEvents/zenactions.py",
line 353, in mainbody
self.eventCommands(db, zem)
File "/usr/local/zenoss/Products/ZenEvents/zenactions.py",
line 340, in eventCommands
for command in zem.commands():
AttributeError: commands
Thanks
Richard
R J Thompson wrote:
Hi Marc
Have tried a zenmigrate run with the following results...
INFO:zen.migrate:Installing BetterStandardErrorMessage
INFO:zen.migrate:Installing ChangeEventClasses
INFO:zen.migrate:Installing DefaultCommandTimeout
INFO:zen.migrate:Installing DevicePriority
INFO:zen.migrate:Installing EventCommands
INFO:zen.migrate:Installing EventNewClasses
INFO:zen.migrate:Installing EvtProps
INFO:zen.migrate:Installing KeyPath
INFO:zen.migrate:Installing MaxOIDPerRequest
INFO:zen.migrate:Installing ProcParams
INFO:zen.migrate:Installing RRDCpuType
INFO:zen.migrate:Installing RRDMinValue2
INFO:zen.migrate:Installing ReportServer
INFO:zen.migrate:Installing StatusConnectTimeout
INFO:zen.migrate:Installing UserCommands
INFO:zen.migrate:Database going to version Zenoss 1.2.0
INFO:zen.migrate:Installing EventClassMapping
INFO:zen.migrate:Database going to version Zenoss 1.2.0
INFO:zen.migrate:Installing ZenUILayer
> /usr/local/zenoss/Products/ZenWidgets/ZenTableManager.py
(328)initTableManagerSkins()
-> path = map(string.strip, string.split(path,','))
(Pdb)
Do I need to run this before or after attempting an upgrade?
Thanks
Richard
Marc Irlandez wrote:
Richard,
A migrate script for EventClassMapping was added this
morning. Make sure you download and install the latest
build. Then execute a zenmigrate:
zenmigrate run
Regards,
Marc Irlandez
On Jan 30, 2007, at 2:35 PM, R J Thompson wrote:
Hello
Trying to upgrade from 1.0.2 to 1.1 but seem to be having a
few problems, have included the following from zenbuild.log:
make[1]: Leaving directory `/usr/local/zenoss-1.1.0/build/
winexe-0.7/source'
make[1]: Entering directory `/usr/local/zenoss-1.1.0/build/
winexe-0.7/source'
==============================================================
========
The binaries are installed. You may restore the old
binaries (if there
were any) using the command "make revert". You may
uninstall the binaries
using the command "make uninstallbin" or "make uninstall"
to uninstall
binaries, man pages and shell scripts.
==============================================================
========
Installing bin/winexe as //usr/local/zenoss/bin/winexe
==============================================================
========
The binaries are installed. You may restore the old
binaries (if there
were any) using the command "make revert". You may
uninstall the binaries
using the command "make uninstallbin" or "make uninstall"
to uninstall
binaries, man pages and shell scripts.
==============================================================
========
make[1]: Leaving directory `/usr/local/zenoss-1.1.0/build/
winexe-0.7/source'
creating events database using zenevent build...
creating database
loading schema
ERROR 1235 (42000) at line 80: This version of MySQL
doesn't yet support 'multiple triggers with the same action
time and event for one table'
loading stored procedures
events database created and loaded
WARNING:OFS.Application:Duplicate Product name
After loading Product 'Five' from '/usr/local/zenoss/
Products',
I skipped the one in '/usr/local/zenoss/lib/python/Products'.
2007-01-30 19:28:33 WARNING OFS.Application Duplicate
Product name
After loading Product 'Five' from '/usr/local/zenoss/
Products',
I skipped the one in '/usr/local/zenoss/lib/python/Products'.
Traceback (most recent call last):
File "/usr/local/zenoss/Products/ZenModel/zenbuild.py",
line 129, in ?
zb = zenbuild()
File "/usr/local/zenoss/Products/ZenModel/zenbuild.py",
line 44, in __init__
self.app = Zope2.app()
File "/usr/local/zenoss/Products/ZenModel/__init__.py",
line 51, in app
"IpInterface",
File "/usr/local/zenoss/Products/ZenModel/__init__.py",
line 47, in startup
"HardDisk",
File "usr/local/zenoss/lib/python/Zope2/App/startup.py",
line 57, in startup
File "usr/local/zenoss/lib/python/DBTab/DBTab.py", line
96, in getDatabase
File "usr/local/zenoss/lib/python/DBTab/DBTab.py", line
113, in _createDatabase
File "usr/local/zenoss/lib/python/Zope2/Startup/
datatypes.py", line 163, in open
File "usr/local/zenoss/lib/python/Zope2/Startup/
datatypes.py", line 160, in createDB
File "usr/local/zenoss/lib/python/ZODB/config.py", line
97, in open
File "usr/local/zenoss/lib/python/ZODB/config.py", line
153, in open
File "usr/local/zenoss/lib/python/ZEO/ClientStorage.py",
line 314, in __init__
File "usr/local/zenoss/lib/python/ZEO/cache.py", line
112, in open
File "usr/local/zenoss/lib/python/ZEO/cache.py", line
835, in scan
File "usr/local/zenoss/lib/python/ZEO/cache.py", line
121, in install
File "usr/local/zenoss/lib/python/ZEO/cache.py", line
630, in fromFile
ValueError: corrupted record, oid
Do I need to run some database migration tools first?
Thanks
Richard
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
--------------------------------------------------------------------
----
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
