forum.opsi.org

Muss ich auf hwaudit 4.0.6 warten oder gibt es ein Trick?

Dec 07 15:39:58 [notice] Sending hardware information to service (hwaudit.py|878)
Dec 07 15:39:58 [debug] Executing jsonrpc method 'auditHardwareOnHost_setObsolete' on host opsi-server (JSONRPC.pyo|111)
Dec 07 15:39:58 [debug2] jsonrpc: {"params": ["test-client.domain"], "id": 3, "method": "auditHardwareOnHost_setObsolete"} (JSONRPC.pyo|114)
Dec 07 15:39:58 [debug2] Request to host opsi-server', baseUrl: /rpc, query '{"params": ["test-client.domain"], "id": 3, "method": "auditHardwareOnHost_setObsolete"}' (JSONRPC.pyo|649)
Dec 07 15:39:58 [debug] Starting new HTTPS connection (0) to opsi-server:4447 (HTTP.pyo|589)
Dec 07 15:39:58 [debug] Connection established to: opsi-server (HTTP.pyo|602)
Dec 07 15:39:58 [debug] Failed to get peer cert: 'NoneType' object has no attribute 'getpeercert' (HTTP.pyo|171)
Dec 07 15:39:58 [debug] Closing connection: <httplib.HTTPSConnection instance at 0x03EBA1C0> (HTTP.pyo|516)
Dec 07 15:39:58 [debug] Content-Type: application/json;charset=utf-8, Content-Encoding:  (JSONRPC.pyo|686)
Dec 07 15:39:58 [debug2] {"id": 3, "result": null, "error": {"message": "(1054, \"Unbekanntes Tabellenfeld 'sku' in where clause\")", "class": "OperationalError"}} (JSONRPC.pyo|692)
Dec 07 15:39:58 [critical] Traceback: (Logger.pyo|767)
Dec 07 15:39:58 [critical]      line 101 in 'processResult' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
Dec 07 15:39:58 [critical]      ==>>> (1054, "Unbekanntes Tabellenfeld 'sku' in where clause") (JSONRPC.pyo|105)
Dec 07 15:39:58 [critical] Traceback: (Logger.pyo|767)
Dec 07 15:39:58 [critical]      line 904 in '<module>' in file 'hwaudit.py' (Logger.pyo|767)
Dec 07 15:39:58 [critical]      line 890 in 'main' in file 'hwaudit.py' (Logger.pyo|767)
Dec 07 15:39:58 [critical]      line 1 in 'auditHardwareOnHost_setObsolete' in file '<string>' (Logger.pyo|767)
Dec 07 15:39:58 [critical]      line 638 in '_jsonRPC' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
Dec 07 15:39:58 [critical]      line 133 in 'execute' in file 'OPSI\Backend\JSONRPC.pyo' (Logger.pyo|767)
Dec 07 15:39:58 [critical]      line 124 in 'waitForResult' in file 'OPSI\Backend\Backend.pyo' (Logger.pyo|767)
Dec 07 15:39:58 [critical]      ==>>> (1054, "Unbekanntes Tabellenfeld 'sku' in where clause") (hwaudit.py|906)

ii opsi-atftpd 0.7.dfsg-5 i386 advanced TFTP server - opsi version with pcre, fifo and max-blksize patches
ii opsi-configed 4.0.6.3.5.1-2 all OPSI config editor
ii opsi-depotserver 4.0.6.4-1 all opsi depotserver configuration package
ii opsi-linux-bootimage 20151125-1 i386 opsi bootimage for netboot tasks.
ii opsi-utils 4.0.6.9-1 all utilites for working with opsi.
ii opsiconfd 4.0.6.11-2 all opsi configuration service
ii opsipxeconfd 4.0.5.5-2 all opsi pxe configuration daemon
ii python-opsi 4.0.6.34-1 all opsi python library

Hi,

rfrankow hat geschrieben:Muss ich auf hwaudit 4.0.6 warten oder gibt es ein Trick?

tatsächlich. Scheint uns durch die Lappen gegangen zu sein. Wir klären das.

Aber das Problem ist nicht das Produkt, sondern die Serverseite. Da hier audit ins mysql läuft, mal checken ob in der Datei

Code: Alles auswählen

/etc/opsi/backendManager/dispatch.conf

bei Backend auch mysql mit auftaucht. Wenn nein, eintragen und:

Code: Alles auswählen

opsi-setup --init-current-config

ausführen.

Danke der Info. Klasse Support, weiter so.
Das nachtragen von mysql in der Zeile backend_.* der Datei dispatch.conf hat geholfen.

forum.opsi.org

failed hwaudit 4.0.5-3

failed hwaudit 4.0.5-3

Re: failed hwaudit 4.0.5-3

Re: failed hwaudit 4.0.5-3