forum.opsi.org

Verfasst: **31 Jan 2021, 17:53**

Hi,

wenn wir auf einige Clients swaudit laufen lassen, erhalten wir folgenden Fehler.

[5] [2021-01-31 17:38:19.628] [swaudit] Execution of: opsiservicecall_auditSoftwareOnClient_setObsolete
[5] [2021-01-31 17:38:19.628] [swaudit]
[6] [2021-01-31 17:38:19.628] [swaudit] "method": "auditSoftwareOnClient_setObsolete"
[6] [2021-01-31 17:38:19.750] [swaudit] JSON Bench for auditSoftwareOnClient_setObsolete "params":["mlr181w.ilr.ing.dom.tu-dresden.de"],"i Start: 17:38:19:628 Time: 00:00:00:122
[6] [2021-01-31 17:38:19.750] [swaudit] JSON result:
[6] [2021-01-31 17:38:19.750] [swaudit] If
[6] [2021-01-31 17:38:19.750] [swaudit] errorsOccuredSinceMark > 0 <<< result false
[6] [2021-01-31 17:38:19.750] [swaudit] Then
[6] [2021-01-31 17:38:19.751] [swaudit] EndIf
[5] [2021-01-31 17:38:19.767] [swaudit] Execution of: opsiservicecall_auditSoftware_createObjects
[5] [2021-01-31 17:38:19.767] [swaudit]
[6] [2021-01-31 17:38:19.772] [swaudit] "method": "auditSoftware_createObjects"
[3] [2021-01-31 17:39:49.901] [swaudit] HTTPSender Post failed
[3] [2021-01-31 17:39:49.901] [swaudit] HTTPSender result: 0 msg:
[6] [2021-01-31 17:39:49.901] [swaudit] Retry with communicationmode: 1
[6] [2021-01-31 17:39:51.215] [swaudit] Retry with communicationmode: 2
[3] [2021-01-31 17:41:21.351] [swaudit] HTTPSender Post failed
[3] [2021-01-31 17:41:21.351] [swaudit] HTTPSender result: 0 msg:
[3] [2021-01-31 17:41:21.351] [swaudit] Error:
[6] [2021-01-31 17:41:21.378] [swaudit] If
[6] [2021-01-31 17:41:21.378] [swaudit] errorsOccuredSinceMark > 0 <<< result true
[6] [2021-01-31 17:41:21.378] [swaudit] Then
[2] [2021-01-31 17:41:21.525] [swaudit] Error level set to fatal
[6] [2021-01-31 17:41:21.525] [swaudit] Process aborted
[1] [2021-01-31 17:41:21.525] [swaudit] ___________________
[1] [2021-01-31 17:41:21.525] [swaudit] script finished: failed
[1] [2021-01-31 17:41:21.525] [swaudit] 5 errors
[1] [2021-01-31 17:41:21.525] [swaudit] 0 warnings
[1] [2021-01-31 17:41:21.525] [swaudit]
[1] [2021-01-31 17:41:21.525] [swaudit] installed product: swaudit Version: 4.1.0.4-1

Was können wir dagegen tun?

Viele Grüße
Andreas

Verfasst: **01 Feb 2021, 09:11**

Moin Andreas,

wie löst ihr denn das Event aus? Ist das ein "on_demand" oder beim Rechner Start?
Scheinbar gibt es ein Problem in der Kommunikation vom Client zum OPSI-Server...

Beste Grüße

Thomas

Verfasst: **01 Feb 2021, 17:43**

In diesem speziellen Falle war es on Demand. Es ist aber auch schon beim Rechnerstart aufgetreten.

Viele Grüße
Andreas

Verfasst: **02 Feb 2021, 09:49**

Ist das für den Client reproduzierbar oder tritt das sporadisch auf?

Was sagt

Code: Alles auswählen

opsi-package-manager -l opsi-winst

Wie sieht die

Code: Alles auswählen

/etc/opsi/backendManager/dispatch.conf

aus?

Gruss
Bardo Wolf

Verfasst: **14 Feb 2021, 11:06**

Das ist für die Clients reproduzierbar.

Hier die beiden Infos vom OPSI-Server.

Code: Alles auswählen

opsi-package-manager -l opsi-winst
--------------------------------------
- ilropsi.ilrw.ing.dom.tu-dresden.de -
--------------------------------------
   Product ID                Version                   Name
   ====================================================================================================================================================================================================================================
   opsi-winst                4.12.4.12-1               winst

Code: Alles auswählen

more /etc/opsi/backendManager/dispatch.conf
# -*- coding: utf-8 -*-
# = = = = = = = = = = = = = = = = = = = = = = =
# =      backend dispatch configuration       =
# = = = = = = = = = = = = = = = = = = = = = = =
#
# This file configures which methods are dispatched to which backends.
# Entries has to follow the form:
# <regular expression to match method name(s)> : <comma separated list of backend name(s)>
#
# Backend names have to match a backend configuraton file basename <backend name>.conf beneath /etc/opsi/backends.
# For every method executed on backend dispatcher the first matching regular expression will be decisive.
#
# Typical configurations:
#    file, opsipxeconfd and dhcpd backend:
#       backend_.*         : file, opsipxeconfd, dhcpd
#       host_.*            : file, opsipxeconfd, dhcpd
#       productOnClient_.* : file, opsipxeconfd
#       configState_.*     : file, opsipxeconfd
#       .*                 : file
#
#    jsonrpc, opsipxeconfd and dhcpd backend:
#       backend_.*         : jsonrpc, opsipxeconfd, dhcpd
#       .*                 : jsonrpc
#
#    file as main backend, mysql as hw/sw invent and license management backend, opsipxeconfd and dhcpd backend:
#       backend_.*         : file, mysql, opsipxeconfd, dhcpd
#       host_.*            : file, opsipxeconfd, dhcpd
#       productOnClient_.* : file, opsipxeconfd
#       configState_.*     : file, opsipxeconfd
#       license.*          : mysql
#       softwareLicense.*  : mysql
#       audit.*            : mysql
#       .*                 : file
#

backend_.*         : file, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
.*                 : file

Verfasst: **23 Feb 2021, 12:06**

AndiMb83 hat geschrieben:

Code: Alles auswählen

more /etc/opsi/backendManager/dispatch.conf
# -*- coding: utf-8 -*-
# = = = = = = = = = = = = = = = = = = = = = = =
# =      backend dispatch configuration       =
# = = = = = = = = = = = = = = = = = = = = = = =
#
# This file configures which methods are dispatched to which backends.
# Entries has to follow the form:
# <regular expression to match method name(s)> : <comma separated list of backend name(s)>
#
# Backend names have to match a backend configuraton file basename <backend name>.conf beneath /etc/opsi/backends.
# For every method executed on backend dispatcher the first matching regular expression will be decisive.
#
# Typical configurations:
#    file, opsipxeconfd and dhcpd backend:
#       backend_.*         : file, opsipxeconfd, dhcpd
#       host_.*            : file, opsipxeconfd, dhcpd
#       productOnClient_.* : file, opsipxeconfd
#       configState_.*     : file, opsipxeconfd
#       .*                 : file
#
#    jsonrpc, opsipxeconfd and dhcpd backend:
#       backend_.*         : jsonrpc, opsipxeconfd, dhcpd
#       .*                 : jsonrpc
#
#    file as main backend, mysql as hw/sw invent and license management backend, opsipxeconfd and dhcpd backend:
#       backend_.*         : file, mysql, opsipxeconfd, dhcpd
#       host_.*            : file, opsipxeconfd, dhcpd
#       productOnClient_.* : file, opsipxeconfd
#       configState_.*     : file, opsipxeconfd
#       license.*          : mysql
#       softwareLicense.*  : mysql
#       audit.*            : mysql
#       .*                 : file
#

backend_.*         : file, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
.*                 : file

I think your backend configuration is incorrect. Install mysql or mariadb in a recent version (follow the getting started manual, there is some mention of the strict mode for older versions).
There is no backend for audit data, so that won't work.

This will also work when you have no mysql module activated:

Code: Alles auswählen

backend_.*         : file, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
license.*          : mysql
softwareLicense.*  : mysql
audit.*            : mysql
.*                 : file

Verfasst: **25 Feb 2021, 08:58**

Hallo,

super, vielen lieben Dank! Das war das Problem. So richtig kann ich mir die Ursache aber nicht erklären.

Viele Grüße
Andreas

forum.opsi.org

swaudit erzeugt Fehler

swaudit erzeugt Fehler

Re: swaudit erzeugt Fehler

Re: swaudit erzeugt Fehler

Re: swaudit erzeugt Fehler

Re: swaudit erzeugt Fehler

Re: swaudit erzeugt Fehler

Re: swaudit erzeugt Fehler