Seite 1 von 1

kein opsi auf SuSE

Verfasst: 05 Jun 2014, 16:17
von oz42
Hallo,

meine installation auf SuSE SLES nach der Anleitung "opsi Getting Started" lief so lala durch. Nach der manuellen Nachinstallation von JRE 7 und python-pyasn1 scheint alles da zu sein, was man braucht, aber opsiconfd will nicht starten:

Code: Alles auswählen

==================================================================
=             opsi configuration service starting                =
==================================================================
 (Logger.py|840)
[5] [Jun 05 16:10:22] Starting opsiconfd main thread (opsiconfd.py|447)
[5] [Jun 05 16:10:22] Opening socket /var/run/opsiconfd/opsiconfd.socket for interprocess communication. (opsiconfd.py|424)
[2] [Jun 05 16:10:22] Traceback: (Logger.py|754)
[2] [Jun 05 16:10:22]      line 160 in '_createConnectionPool' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/MySQL.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 74 in '__init__' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/MySQL.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 224 in 'connect' in file '/usr/lib64/python2.6/site-packages/sqlalchemy/pool.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 387 in '__init__' in file '/usr/lib64/python2.6/site-packages/sqlalchemy/pool.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 739 in '_do_get' in file '/usr/lib64/python2.6/site-packages/sqlalchemy/pool.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 188 in '_create_connection' in file '/usr/lib64/python2.6/site-packages/sqlalchemy/pool.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 270 in '__init__' in file '/usr/lib64/python2.6/site-packages/sqlalchemy/pool.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 330 in '__connect' in file '/usr/lib64/python2.6/site-packages/sqlalchemy/pool.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 72 in 'creator' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/MySQL.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 71 in 'Connect' in file '/usr/lib64/python2.6/site-packages/MySQLdb/__init__.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 170 in '__init__' in file '/usr/lib64/python2.6/site-packages/MySQLdb/connections.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      ==>>> (2002, "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)") (MySQL.py|163)
[2] [Jun 05 16:10:22] Traceback: (Logger.py|754)
[2] [Jun 05 16:10:22]      line 453 in 'run' in file '/usr/lib64/python2.6/site-packages/opsiconfd/opsiconfd.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 264 in '_createBackendInstance' in file '/usr/lib64/python2.6/site-packages/opsiconfd/opsiconfd.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 209 in '__init__' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/BackendManager.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 314 in '__init__' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/BackendManager.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 364 in '__loadBackends' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/BackendManager.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 422 in '__init__' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/MySQL.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 137 in '__init__' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/MySQL.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      line 164 in '_createConnectionPool' in file '/usr/lib64/python2.6/site-packages/OPSI/Backend/MySQL.py' (Logger.py|754)
[2] [Jun 05 16:10:22]      ==>>> Backend I/O error: Failed to connect to database 'opsi' address 'localhost': (2002, "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)") (opsiconfd.py|469)
[5] [Jun 05 16:10:22] Stopping opsiconfd main thread (opsiconfd.py|175)
[5] [Jun 05 16:10:22] Opsiconfd main thread exiting... (opsiconfd.py|472)
Fehlt noch eine andere Komponente, die im Guide nicht erwähnt wird?

Olaf

Re: kein opsi auf SuSE

Verfasst: 06 Jun 2014, 12:11
von n.wenselowski
Hallo,

läuft MySQL und wurde konfiguriert?
Hinweis zur Konfiguration im Getting Started.

Ansonsten hier noch der Hinweis, dass wir momentan nur SLES 11sp1 unterstützen.


Gruß

Niko

Re: kein opsi auf SuSE

Verfasst: 06 Jun 2014, 12:33
von oz42
Nur SLES11 Sp1? Schade, denn das wiederum wird ja von SuSE nicht mehr unterstützt...
Ich werde demnächst einen Versuch mit Debian starten.

Olaf