Re: Zenoss Port Web-UI seems incomplete
[...] If there is no issue after this, please send us a unified diff of the zone.conf files. The reason I ask to do this, is that I changed nothing and it worked out-of-the-box. Thanks, Jason -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 Here is the diff of the zope.conf and zope.conf.in file: # diff zope.conf zope.conf.in 0a1,2 # This is the proposed version for SC / Zope 2.12.1 25c27,31 %define INSTANCE /usr/local/zenoss --- %define INSTANCE INSTANCE_HOME # this needs to match the encoding in the sitecustomize.py file # in $ZENHOME/lib/python default-zpublisher-encoding utf-8 148c154 #effective-user chrism --- effective-user zenoss 929a936 conflict-error-log-level debug 1019,1027c1026,1034 zodb_db main # Main FileStorage database filestorage # See .../ZODB/component.xml for directives (sectiontype # filestorage). path $INSTANCE/var/Data.fs /filestorage mount-point / /zodb_db --- #zodb_db main ## Main FileStorage database #filestorage # # See .../ZODB/component.xml for directives (sectiontype # # filestorage). # path $INSTANCE/var/Data.fs #/filestorage #mount-point / #/zodb_db 1042,1065c1049,1063 # zodb_db main # # The full mount-point syntax is: # # # # mount-point localpath[:remotepath] # # # # localpath - the path where the storage is mounted in this instance # # remotepath - is the path to the object in the storage where it is mounted # # from. This defaults to whatever is supplied for localpath. # mount-point / # # ZODB cache, in number of objects # cache-size 5000 # zeoclient # # See .../ZODB/component.xml for directives (sectiontype # # zeoclient). # server localhost:8100 # storage 1 # name zeostorage # var $INSTANCE/var # # ZEO client cache, in bytes # cache-size 20MB # # Uncomment to have a persistent disk cache # #client zeo1 # /zeoclient # /zodb_db --- zodb_db main mount-point / # ZODB cache, in number of objects cache-size 5000 zeoclient server localhost:8100 storage 1 name zeostorage var $INSTANCE/var # ZEO client cache, in bytes cache-size 20MB # Uncomment to have a persistent disk cache #client zeo1 /zeoclient /zodb_db Regards, Kaya ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Zenoss Port Web-UI seems incomplete
On Wed, Jun 6, 2012 at 12:22 PM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Kaya Saman wrote on 06.06.2012 15:02: On Wed, Jun 6, 2012 at 11:53 AM, Ruslan Mahmatkhanovcvs-...@yandex.ru wrote: Hi Kaya, Kaya Saman wrote on 06.06.2012 14:30: Can someone suggest anything or am I stuck with Linux for Zenoss? Would you disclose some details like what the exact problem is, which error messages you are seeing, what isn't works as expected? From which version you are migrating (which version you have installed on a Linux boxes)? FreeBSD port of Zenoss seems slightly outdated. -- Regards, Ruslan Tinderboxing kills... the drives. Sorry for the non-existant information.. FreeBSD version is 3.1.0 built fresh from ports - clean install CentOS 6.2 version is 3.2.1 - I think I got directly from zenoss homepage though can't quite remember now! Again clean install Unfortunatley the version in FreeBSD seems to be missing a few bits I am unable to get the Web-UI (Zope) running. Changing the /usr/local/zenoss/etc/zope.conf file was the easy part but there are many inconsistancies This is what the tty gives on a restart: Daemon: zopectl exec: /usr/local/zenoss/python/bin/zopectl: not found Daemon: zeoctl Error: no program specified; use -p or -C For help, use /usr/local/zenoss/bin/zeoctl -h Daemon: zeoctl Error: no program specified; use -p or -C For help, use /usr/local/zenoss/bin/zeoctl -h Daemon: zopectl exec: /usr/local/zenoss/python/bin/zopectl: not found This error is after I copied over zopectl from the Linux version! I didn't find zopectl on the system at all, unless I looked in the wrong place? Regards, Kaya Did you initialize zenoss instance? zopectl should be copied after that. [rm@smeshariki3 ~] cat /usr/ports/net-mgmt/zenoss/pkg-message Add the following line to /etc/rc.conf to enable zenoss: zenoss_enable=YES To initialize zenoss, you can run the following (as root): service zenoss init = After this will be done, just do `service zenoss start` and it should start. -- Regards, Ruslan Tinderboxing kills... the drives. Ah thanks :-) Now that we've got a handle on the setup here's an error: mv: /usr/local/zenoss/etc/zope.conf: set owner/group (was: 949/0): Operation not permitted mv: /usr/local/zenoss/etc/zope.conf: set owner/group (was: 949/0): Operation not permitted mv: /usr/local/zenoss/etc/zeo.conf: set owner/group (was: 949/0): Operation not permitted Starting Zope Object Database . daemon process started, pid=91120 Loading initial Zenoss objects into the Zeo database (this can take a few minutes) Unable to create the initial Zenoss object database is the Zenoss objects database within MySQL? The user is root with no password for now as this system is a simple throw-away sandbox for testing. Regards, Kaya ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Zenoss Port Web-UI seems incomplete
On Wed, Jun 6, 2012 at 1:13 PM, Kaya Saman kayasa...@gmail.com wrote: On Wed, Jun 6, 2012 at 1:06 PM, Robert Huff roberth...@rcn.com wrote: Kaya Saman writes: FreeBSD version is 3.1.0 built fresh from ports - clean install Are you sure that's the correct version? 3.* has been unsupported for, like, ten years. (Not that some people won't try to help, but there's not many these days who remember the details.) Robert Huff Sorry if I was unclear or if what I meant was unclear The FreeBSD version is 8.3 RELEASE x64 and the version of Zenoss is 3.1.0. My fault for trying to 'shorthand' - I should have known better! Regards, Kaya Ok I did this: rm -rf /usr/local/zenoss then on the port: make deinstall make install clean then ran the commands suggested: service zenoss init Everything went through fine and am up online! Would I be able to make one slight request here though? If the port could be updated from version 3.1.0 to 3.2.x (the latest)?? I'd really appreciate that! Regards, Kaya ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Zenoss Port Web-UI seems incomplete
On Wed, Jun 6, 2012 at 1:59 PM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Kaya Saman wrote on 06.06.2012 16:54: Everything went through fine and am up online! Glad to see. Whoops spoke too soon! The web-ui won't launch?? I don't see anything in the event.log however, here is the output: -- 2012-06-06T13:37:35 INFO ZServer HTTP server started at Wed Jun 6 13:37:35 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T13:37:36 WARNING ZODB.FileStorage Ignoring index for /usr/local/zenoss/var/Data.fs -- 2012-06-06T13:37:39 INFO Zope Ready to handle requests -- 2012-06-06T13:47:40 INFO ZPublisher.Conflict ConflictError at /zport/dmd/network_router: database conflict error (oid 0x0a8d, class Products.ZenModel.IpNetwork.IpNetwork) (1 conflicts (0 unresolved) since startup at Wed Jun 6 13:37:39 2012) -- 2012-06-06T15:16:14 INFO zen.ZenossInfo Telling zenjobs to start -- 2012-06-06T15:22:23 INFO zen.ZenossInfo Telling zeoctl to start -- 2012-06-06T15:41:04 INFO ZServer HTTP server started at Wed Jun 6 15:41:04 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:05 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:14 INFO ZServer HTTP server started at Wed Jun 6 15:41:14 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:14 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:16 INFO ZServer HTTP server started at Wed Jun 6 15:41:16 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:17 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:19 INFO ZServer HTTP server started at Wed Jun 6 15:41:19 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:20 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:24 INFO ZServer HTTP server started at Wed Jun 6 15:41:24 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:24 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:29 INFO ZServer HTTP server started at Wed Jun 6 15:41:29 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:30 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:36 INFO ZServer HTTP server started at Wed Jun 6 15:41:36 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:36 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock
Re: Zenoss Port Web-UI seems incomplete
On Wed, Jun 06, 2012 at 04:59:16PM +0400, Ruslan Mahmatkhanov thus spake:
Kaya Saman wrote on 06.06.2012 16:54:
Everything went through fine and am up online!
Glad to see.
Would I be able to make one slight request here though?
If the port could be updated from version 3.1.0 to 3.2.x (the latest)??
I'd really appreciate that!
I added zenoss port maintainer to discussion. He is a right person to
asking questions like this :).
--
Regards,
Ruslan
Glad to hear this is working out for you! I just verified myself here that
it did work.
Attached is a patch for the upgrade to 3.2.0. As I understand it, 4.0 is
coming out, and having any preliminary results would be great for moving to
this release.
There was an issue internally that was preventing the port from being
updated that we were researching. A pr enlightening us, and we are
now testing the upgrade procedure, but if you would like to try this
preliminary patch, you are more then welcome to. If you are able to, we
would be very interested, as well, in any issues or success you may have with
zenoss, or any zenpacks in the portstree.
Keep in mind, the upgrade for Zenoss is really unsafe, at the moment.
We are working with upstream in achieving a safe make process.
The port does make/install as part of the building process.
I am also going to discuss with Phil moving the maintainership to
zen...@experts-exchange.com, which I am a part of, as well.
We've already discussed setting up an online group for community involvement,
as well. If anyone has any thoughts on this, we would love to hear them.
Very excited that we have a growing FreeBSD Zenoss community!
cc: zenoss, myself
Thanks!
-jgh
--
Jason Helfman
System Administrator
experts-exchange.com
http://www.experts-exchange.com/M_4830110.html
E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5
Index: Makefile
===
RCS file: /home/pcvs/ports/net-mgmt/zenoss/Makefile,v
retrieving revision 1.2
diff -u -r1.2 Makefile
--- Makefile16 May 2012 17:24:23 - 1.2
+++ Makefile6 Jun 2012 17:07:45 -
@@ -6,10 +6,9 @@
#
PORTNAME= zenoss
-PORTVERSION= 3.1.0
-PORTREVISION= 1
+PORTVERSION= 3.2.0
CATEGORIES=net-mgmt java
-MASTER_SITES=
SF/${PORTNAME}/${PORTNAME}-3.1/${PORTNAME}-${PORTVERSION}:source1 \
+MASTER_SITES=
SF/${PORTNAME}/${PORTNAME}-${PORTVERSION:R}/${PORTNAME}-${PORTVERSION}:source1 \
http://dev.sencha.com/deploy/:source2
DISTFILES= ${PORTNAME}-${PORTVERSION}.tar.gz:source1 \
JSBuilder2.zip:source2
Index: distinfo
===
RCS file: /home/pcvs/ports/net-mgmt/zenoss/distinfo,v
retrieving revision 1.1
diff -u -r1.1 distinfo
--- distinfo21 Jul 2011 16:55:07 - 1.1
+++ distinfo6 Jun 2012 17:07:45 -
@@ -1,4 +1,4 @@
-SHA256 (zenoss-3.1.0.tar.gz) =
a37b6b3acb820e420e863657cd14eca87ef3f23a10ee9b51e2563537aadd4662
-SIZE (zenoss-3.1.0.tar.gz) = 105896128
+SHA256 (zenoss-3.2.0.tar.gz) =
5a2843d9ff23024e75aaf07ed2e023a174873a048560f83115fc338eadaab51e
+SIZE (zenoss-3.2.0.tar.gz) = 106156572
SHA256 (JSBuilder2.zip) =
71948305d1d89a7952fdd43a5f59bdc99c2acca785b5636f4eae6d76e8dcd07a
SIZE (JSBuilder2.zip) = 870364
Index: pkg-plist
===
RCS file: /home/pcvs/ports/net-mgmt/zenoss/pkg-plist,v
retrieving revision 1.1
diff -u -r1.1 pkg-plist
--- pkg-plist 21 Jul 2011 16:55:07 - 1.1
+++ pkg-plist 6 Jun 2012 17:07:45 -
@@ -130,6 +130,7 @@
%%ZENHOME%%/Products/Jobber/zenjobs.py
%%ZENHOME%%/Products/LICENSE.txt
%%ZENHOME%%/Products/ZenCollector/__init__.py
+%%ZENHOME%%/Products/ZenCollector/DeviceConfigCache.py
%%ZENHOME%%/Products/ZenCollector/config.py
%%ZENHOME%%/Products/ZenCollector/daemon.py
%%ZENHOME%%/Products/ZenCollector/interfaces.py
@@ -267,6 +268,8 @@
%%ZENHOME%%/Products/ZenHub/PBDaemon.py
%%ZENHOME%%/Products/ZenHub/XmlRpcService.py
%%ZENHOME%%/Products/ZenHub/__init__.py
+%%ZENHOME%%/Products/ZenHub/ServiceTester.py
+%%ZENHOME%%/Products/ZenHub/notify.py
%%ZENHOME%%/Products/ZenHub/services/Beat.py
%%ZENHOME%%/Products/ZenHub/services/CommandConfig.py
%%ZENHOME%%/Products/ZenHub/services/DiscoverService.py
@@ -279,15 +282,16 @@
%%ZENHOME%%/Products/ZenHub/services/RRDImpl.py
%%ZENHOME%%/Products/ZenHub/services/RRDService.py
%%ZENHOME%%/Products/ZenHub/services/SnmpPerfConfig.py
+%%ZENHOME%%/Products/ZenHub/services/SnmpTrapConfig.py
%%ZENHOME%%/Products/ZenHub/services/StatusConfig.py
%%ZENHOME%%/Products/ZenHub/services/ThresholdMixin.py
-%%ZENHOME%%/Products/ZenHub/services/TrapService.py
%%ZENHOME%%/Products/ZenHub/services/ZenRender.py
%%ZENHOME%%/Products/ZenHub/services/__init__.py
%%ZENHOME%%/Products/ZenHub/tests/TestService.py
%%ZENHOME%%/Products/ZenHub/tests/__init__.py
%%ZENHOME%%/Products/ZenHub/tests/testRRDImpl.py
%%ZENHOME%%/Products/ZenHub/tests/testZenHub.py
Re: Zenoss Port Web-UI seems incomplete
On Wed, Jun 06, 2012 at 04:12:12PM +0100, Kaya Saman thus spake: On Wed, Jun 6, 2012 at 1:59 PM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Kaya Saman wrote on 06.06.2012 16:54: Everything went through fine and am up online! Glad to see. Whoops spoke too soon! The web-ui won't launch?? I don't see anything in the event.log however, here is the output: -- 2012-06-06T13:37:35 INFO ZServer HTTP server started at Wed Jun 6 13:37:35 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T13:37:36 WARNING ZODB.FileStorage Ignoring index for /usr/local/zenoss/var/Data.fs -- 2012-06-06T13:37:39 INFO Zope Ready to handle requests -- 2012-06-06T13:47:40 INFO ZPublisher.Conflict ConflictError at /zport/dmd/network_router: database conflict error (oid 0x0a8d, class Products.ZenModel.IpNetwork.IpNetwork) (1 conflicts (0 unresolved) since startup at Wed Jun 6 13:37:39 2012) -- 2012-06-06T15:16:14 INFO zen.ZenossInfo Telling zenjobs to start -- 2012-06-06T15:22:23 INFO zen.ZenossInfo Telling zeoctl to start -- 2012-06-06T15:41:04 INFO ZServer HTTP server started at Wed Jun 6 15:41:04 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:05 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:14 INFO ZServer HTTP server started at Wed Jun 6 15:41:14 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:14 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:16 INFO ZServer HTTP server started at Wed Jun 6 15:41:16 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:17 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:19 INFO ZServer HTTP server started at Wed Jun 6 15:41:19 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:20 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:24 INFO ZServer HTTP server started at Wed Jun 6 15:41:24 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:24 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:29 INFO ZServer HTTP server started at Wed Jun 6 15:41:29 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:30 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name) LockError: Couldn't lock '/usr/local/zenoss/var/Data.fs.lock' -- 2012-06-06T15:41:36 INFO ZServer HTTP server started at Wed Jun 6 15:41:36 2012 Hostname: 0.0.0.0 Port: 8080 -- 2012-06-06T15:41:36 ERROR zc.lockfile Error locking file /usr/local/zenoss/var/Data.fs.lock; pid=UNKNOWN Traceback (most recent call last): File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 76, in __init__ _lock_file(fp) File /usr/local/zenoss/lib/python/zc/lockfile/__init__.py, line 59, in _lock_file raise LockError(Couldn't lock %r % file.name)
Re: Zenoss Port Web-UI seems incomplete
[...] How are you accessing the system? What port? I have set it up locally, and can access it on port 8080: http://localhost:8080 -jgh That is exactly how I set it up which should actually just be this by default When I had the service started initially I used: service zenoss start (just to add here: I didn't know that one could use the 'service' command on FreeBSD and thought it was only RPM based Linux centric) I noticed that some of the other daemons hadn't started so I decided to reboot. Running /usr/local/etc/rc.d/zenoss stop/start after the restart still didn't get the web-ui functioning?? so I took the errors in the logs and posted here. Am confused! Regards, Kaya ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Zenoss Port Web-UI seems incomplete
Kaya Saman wrote on 06.06.2012 21:55: [...] How are you accessing the system? What port? I have set it up locally, and can access it on port 8080: http://localhost:8080 -jgh That is exactly how I set it up which should actually just be this by default When I had the service started initially I used: service zenoss start (just to add here: I didn't know that one could use the 'service' command on FreeBSD and thought it was only RPM based Linux centric) It was added since 8.3 if I recall correctly. It's the same that if you run it as /usr/local/etc/rc.d/zenoss start. I noticed that some of the other daemons hadn't started so I decided to reboot. Running /usr/local/etc/rc.d/zenoss stop/start after the restart still didn't get the web-ui functioning?? Why you starting it manually? As far I understand you added zenoss_enable=YES into /etc/rc.conf, so it should start automatically on boot. so I took the errors in the logs and posted here. Am confused! Ok, at least you are now connected with right people that using Zenoss and actually maintaining the port. So I'm now going to shadow :) -- Regards, Ruslan Tinderboxing kills... the drives. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Zenoss Port Web-UI seems incomplete
On Wed, Jun 06, 2012 at 10:03:20PM +0400, Ruslan Mahmatkhanov thus spake: Kaya Saman wrote on 06.06.2012 21:55: [...] How are you accessing the system? What port? I have set it up locally, and can access it on port 8080: http://localhost:8080 -jgh That is exactly how I set it up which should actually just be this by default When I had the service started initially I used: service zenoss start (just to add here: I didn't know that one could use the 'service' command on FreeBSD and thought it was only RPM based Linux centric) It was added since 8.3 if I recall correctly. It's the same that if you run it as /usr/local/etc/rc.d/zenoss start. I noticed that some of the other daemons hadn't started so I decided to reboot. Running /usr/local/etc/rc.d/zenoss stop/start after the restart still didn't get the web-ui functioning?? Why you starting it manually? As far I understand you added zenoss_enable=YES into /etc/rc.conf, so it should start automatically on boot. so I took the errors in the logs and posted here. Am confused! Ok, at least you are now connected with right people that using Zenoss and actually maintaining the port. So I'm now going to shadow :) -- Regards, Ruslan Tinderboxing kills... the drives. In regards to the error, this sounds familiar with non-default zope.conf files. If you have changed your zone.conf file, I would go with the default configuration file, restart the service, and see if there is still an issue. If there is no issue after this, please send us a unified diff of the zone.conf files. The reason I ask to do this, is that I changed nothing and it worked out-of-the-box. Thanks, Jason -- Jason Helfman System Administrator experts-exchange.com http://www.experts-exchange.com/M_4830110.html E4AD 7CF1 1396 27F6 79DD 4342 5E92 AD66 8C8C FBA5 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Zenoss Port Web-UI seems incomplete
On 06/06/2012 07:27 PM, Jason Helfman wrote: On Wed, Jun 06, 2012 at 10:03:20PM +0400, Ruslan Mahmatkhanov thus spake: Kaya Saman wrote on 06.06.2012 21:55: [...] How are you accessing the system? What port? I have set it up locally, and can access it on port 8080: http://localhost:8080 -jgh That is exactly how I set it up which should actually just be this by default When I had the service started initially I used: service zenoss start (just to add here: I didn't know that one could use the 'service' command on FreeBSD and thought it was only RPM based Linux centric) It was added since 8.3 if I recall correctly. It's the same that if you run it as /usr/local/etc/rc.d/zenoss start. I noticed that some of the other daemons hadn't started so I decided to reboot. Running /usr/local/etc/rc.d/zenoss stop/start after the restart still didn't get the web-ui functioning?? Why you starting it manually? As far I understand you added zenoss_enable=YES into /etc/rc.conf, so it should start automatically on boot. so I took the errors in the logs and posted here. Am confused! Ok, at least you are now connected with right people that using Zenoss and actually maintaining the port. So I'm now going to shadow :) -- Regards, Ruslan Tinderboxing kills... the drives. In regards to the error, this sounds familiar with non-default zope.conf files. If you have changed your zone.conf file, I would go with the default configuration file, restart the service, and see if there is still an issue. If there is no issue after this, please send us a unified diff of the zone.conf files. The reason I ask to do this, is that I changed nothing and it worked out-of-the-box. Thanks, Jason Hi Jason, I didn't edit anything. that's my point. Initially it worked but after I cycled the system it stopped working. Zenoss starts however, it seems some sub-services don't and the web-ui is one of them. I will take a look again and send the requested diff tomorrow GMT time and wait for a response. Actually I think I'll take a backup of the zope.conf file and copy the zope.conf.in file over and see if that changes anything. Regards, Kaya ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Zenoss Port Web-UI seems incomplete
On 06/06/2012 11:03, Ruslan Mahmatkhanov wrote: It was added since 8.3 if I recall correctly. 7.3, according to The Fine Manpage. :) It's the same that if you run it as /usr/local/etc/rc.d/zenoss start. It's actually better, since 'service' starts things from a clean environment, identical to what you get at boot time. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
