TECHZEN Zenoss User Community ARCHIVE  

Problem importing MIBs

Subject: Problem importing MIBs
Author: [Not Specified]
Posted: 2015-04-24 10:06

Hello all!

I am having a problem when trying to import MIBs.

[zenoss@5ed99ac27c90 site]$ zenmib run -v 10
2015-04-23 15:19:12,271 DEBUG zen.MySqlZodbFactory: cache-servers is set and poll-interval is not specified so poll-interval is set to 60 seconds.
2015-04-23 15:19:12,287 WARNING relstorage.adapters.mysql: Unable to connect: (2003, "Can't connect to MySQL server on '127.0.0.1' (111)")

It tries to connect to a SQL server on port 111, but in the container holding the Zenoss Core application there is no SQL server listening there. It listens on port 111 in the standard environment, and I had no problems with the installation except this

I have tried both manual installation and the auto-deploy script, and the problem is present regardless.

The system is CentOS 7 64bit with Zenoss Core v5.0.2
Please let me know if any further info is necessary.

All help is appreciated!

Carsten



Subject: Problem importing MIBs
Author: [Not Specified]
Posted: 2015-06-03 09:10

I've the same issue, and also this error:

Traceback (most recent call last):
File "/opt/zenoss/Products/ZenModel/zenmib.py", line 1012, in
zm = ZenMib()
File "/opt/zenoss/Products/ZenUtils/ZCmdBase.py", line 96, in __init__
self.zodbConnect()
File "/opt/zenoss/Products/ZenUtils/ZCmdBase.py", line 104, in zodbConnect
self.db, self.storage = connectionFactory.getConnection(**self.options.__dict__)
File "/opt/zenoss/Products/ZenUtils/MySqlZodbFactory.py", line 165, in getConnection
storage = relstorage.storage.RelStorage(adapter, **relstoreParams)
File "/opt/zenoss/lib/python2.7/site-packages/relstorage/storage.py", line 167, in __init__
self._adapter.schema.prepare()
File "/opt/zenoss/lib/python2.7/site-packages/relstorage/adapters/schema.py", line 856, in prepare
self.connmanager.open_and_call(callback)
File "/opt/zenoss/lib/python2.7/site-packages/relstorage/adapters/connmanager.py", line 73, in open_and_call
conn, cursor = self.open()
File "/opt/zenoss/Products/ZenUtils/patches/mysqladaptermonkey.py", line 70, in open
conn, cursor = original(self, *args, **kwargs)
File "/opt/zenoss/lib/python2.7/site-packages/relstorage/adapters/mysql.py", line 231, in open
conn = MySQLdb.connect(**self._params)
File "/opt/zenoss/lib/python2.7/site-packages/MySQLdb/__init__.py", line 81, in Connect
return Connection(*args, **kwargs)
File "/opt/zenoss/lib/python2.7/site-packages/MySQLdb/connections.py", line 187, in __init__
super(Connection, self).__init__(*args, **kwargs2)
_mysql_exceptions.OperationalError: (2003, "Can't connect to MySQL server on '127.0.0.1' (111)")

Does someone has some suggestion

Thanks

D.



Subject: make sure your MariaDB is
Author: Andrew Kirch
Posted: 2015-06-03 12:19

make sure your MariaDB is running, and that Zenoss can talk to it. 111 is a "connection refused" error, not a port.

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



Subject: First, that 111 refers to the
Author: [Not Specified]
Posted: 2015-06-03 12:25

First, that 111 refers to the MySQL error code, not a port. It means "Connection Refused."

Second, can you confirm which container you're in You have to be in one that has access to MySQL, like Zope or zenhub. There's a "serviced service run" command for exactly this purpose. Instead of attaching to run zenmib, try:

$ serviced service run zope zenmib ...

It will mount the current directory as /mnt/pwd in the container, and use that as the working directory in the command.



Subject: you need to run zenmib by
Author: Andrew Kirch
Posted: 2015-06-04 10:30

you need to run zenmib by attaching to the docker container. Read up for examples.

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



Subject: solved
Author: [Not Specified]
Posted: 2015-06-08 00:23

It works.
I've executed zenmib in the zope container.

Thaks

D.



Subject: There is a trick: if ou
Author: [Not Specified]
Posted: 2016-01-06 07:41

There is a trick: if ou connect into a container with "serviced service shell", the current directory is mounted as /mnt/pwd.

Well documented, as usual.



< Previous
unable to access control center on fresh install
  Next
Zenoss5 (deployed via auto-deploy scripts ) - unable to discover network
>