forum.opsi.org

Hallo zusammen,

ich habe (noch immer) folgendes Problem: Beim installieren von Windows XP kommt folgender Fehler:

Sammle Hardware-Informationen.

(1054, "Unknown column 'notes' in 'field list' ")

Logfile:
[4] [Sep 17 12:10:15] Sending hardware information to service (winxppro.py|16)
[6] [Sep 17 12:10:15] Executing jsonrpc method 'setHardwareInformation' (JSONRPC.py|225)
[6] [Sep 17 12:10:15] Options: {'params': ('patest2.busatis.local', {u'SYSTEM_SLOT': [{u'maxDataWidth': '32', u'currentUsage': 'Unknown', u'name': 'PCI Slot J8B3', u'description': None}], u'USB_CONTROLLER': ................ (gekürzt)
[6] [Sep 17 12:10:15] Using method POST (JSONRPC.py|283)
[1] [Sep 17 12:10:16] Traceback: (Logger.py|648)
[1] [Sep 17 12:10:16] line 610 in '<module>' in file '/usr/local/bin/master.py' (Logger.py|648)
[1] [Sep 17 12:10:16] line 17 in '<module>' in file '/mnt/opsi/install/winxppro/winxppro.py' (Logger.py|648)
[1] [Sep 17 12:10:16] line 1 in 'setHardwareInformation' in file '<string>' (Logger.py|648)
[1] [Sep 17 12:10:16] line 262 in '_jsonRPC' in file '/var/lib/python-support/python2.6/OPSI/Backend/JSONRPC.py' (Logger.py|648)
[1] [Sep 17 12:10:16] ==>>> (1054, "Unknown column 'notes' in 'field list'") (master.py|626)
[6] [Sep 17 12:10:16] Executing jsonrpc method 'unsetProductActionRequest' (JSONRPC.py|225)
[6] [Sep 17 12:10:16] Options: {'params': ('winxppro', 'patest2.busatis.local')} (JSONRPC.py|229)
[6] [Sep 17 12:10:16] Using method POST (JSONRPC.py|283)
[6] [Sep 17 12:10:16] Executing jsonrpc method 'setProductInstallationStatus' (JSONRPC.py|225)
[6] [Sep 17 12:10:16] Options: {'params': ('winxppro', 'patest2.busatis.local', 'failed')} (JSONRPC.py|229)
[6] [Sep 17 12:10:16] Using method POST (JSONRPC.py|283)
[6] [Sep 17 12:30:22] Executing: cat /var/tmp/opsi/sysconf.ini (master.py|643)

Ich verwende das Mysql Backend für die HW/SW Inventarisierung und denke das es damit zu tun hat.

Meine Fragen dazu:
1) Muß man beim Update auf opsi V3.4 das Script /usr/share/opsi/init-opsi-mysql-db.py ausführen?
2) kann ich einfach auf das FILE31 backend umschalten und nach dem Test ob's it diesem funktioniert wieder zurück auf das mysql-backend?

lg
Bernhard

2 x Ja

Hallo,

Beim ausführen von /usr/share/opsi/init-opsi-mysql-db.py
erhalte ich folgenden Fehler:

*******************************************************************************
* This tool will create an initial mysql database for use as opsi backend. *
* The config file /etc/opsi/backendManager.d/21_mysql.conf will be recreated. *
* =>>> Press <CTRL> + <C> to abort <<<= *
*******************************************************************************

Database host [localhost]:
Database admin user [root]:
Database admin password [password]:
Opsi database name [opsi]:
Opsi database user [opsi]:
Opsi database password [opsi]:

Connecting to host 'localhost' as user 'root'
Creating database 'opsi' and user 'opsi'
Testing connection
Connection / credentials ok!
Creating mysql backend config file /etc/opsi/backendManager.d/21_mysql.conf
Updating database from opsi 3.3 to 3.4
Traceback:
line 158 in '<module>' in file '/usr/share/opsi/init-opsi-mysql-db.py'
line 77 in 'db_query' in file '/var/lib/python-support/python2.5/OPSI/Backend/MySQL.py'
line 148 in 'db_execute' in file '/var/lib/python-support/python2.5/OPSI/Backend/MySQL.py'
line 166 in 'execute' in file '/var/lib/python-support/python2.5/MySQLdb/cursors.py'
line 35 in 'defaulterrorhandler' in file '/var/lib/python-support/python2.5/MySQLdb/connections.py'
==>>> (1060, "Duplicate column name 'hostId'")
ERROR: (1060, "Duplicate column name 'hostId'")

Was kann ich tun, damit das Update ohne Fehler durchläuft?

lg
Bernhard

Hallo,

die Datenbank komplett löschen würde helfen.

Gruß
Jan Schneider