forum.opsi.org

Hi,

I just want to ask, whether is normal, that the instalation of swaudit package takes very long time when the installation process is in the phase "writing log data back to service". We recently updated 50 clients to latest opsi version and we also set to update the swaudit on all clients. When the users came to work in the morning it tooks very long time to boot the machine. The swaudit package hangs for a long time on "writing data back to service". The opsi server was under heavy load. the opsiconfd python processes were using all processors on the serveron 100%. The server When I strace the opsiconfd processes. There is lot of tux wait and poll fnctions calling. Further, the load is reproducible. When you set to setup the swaudit on one client, the load of one opsiconfd process is 100% on the server processor.

Is there something wrong in my installation?

Thank you in advance,

Jan Hubeny

please check / post your

Code: Alles auswählen

/etc/opsi/backendManager/dispatch.conf

regards,
bardo wolf

content of requested file (without comments)

Code: Alles auswählen

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

ok, the file-backend slows down the swaudit.

see
http://download.uib.de/opsi4.0/doc/html ... dp30629168

- install mysql-server
- run opsi-setup --configure-mysql
- change your dispatch.conf

Code: Alles auswählen

# 
Recommended standard configuration (dhcpd not at the opsi server)
#    file as main backend, mysql as hw/sw invent
#     and license management backend and opsipxeconfd backend:
backend_.*         : file, mysql, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
license.*          : mysql
softwareLicense.*  : mysql
audit.*            : mysql
.*                 : file

Code: Alles auswählen

opsi-setup --init-current-config
opsi-setup --set-rights
/etc/init.d/opsiconfd restart
/etc/init.d/opsipxeconfd restart

regards,
bardo wolf

Thank you,

it seems, that the chenge of backend helped.

Regards,

Jan Hubeny

we have exactly the same issue, but with the hwaudit (win7 prod install). we configured the mysql backend as you wrote previously, but the problem still occurs.
if it helps, we install windows from a depot server, but we did the backend configuration on the central server.

the dispatch.conf.default file on the depot contains the following lines:

backend_.* : jsonrpc, opsipxeconfd, dhcpd
.* : jsonrpc

the central server configuration file:

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

I think this is the proper configuration.

regards, np

I think I figured out the root cause - after I comment out the hwaudit lines from setup.py, the installation started working.
running via product installation, hwaudit runs smoothly.

inszekt_ hat geschrieben:
the central server configuration file:

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

I think this is the proper configuration.

Please note your configuration might lead to some problems.

Code: Alles auswählen

# Recommended standard configuration (dhcpd not at the opsi server)
#    file as main backend, mysql as hw/sw invent
#     and license management backend and opsipxeconfd backend:
backend_.*         : file, mysql, opsipxeconfd
host_.*            : file, opsipxeconfd
productOnClient_.* : file, opsipxeconfd
configState_.*     : file, opsipxeconfd
license.*          : mysql
softwareLicense.*  : mysql
audit.*            : mysql
.*                 : file

(see http://download.uib.de/opsi4.0/doc/html ... arted.html)

Especially the last Update

http://download.uib.de/opsi4.0/doc/html ... notes.html

with changes on Hardware Inventory "The Dell Express Code is now determined for Dell computers" will be broken with your config cause in the line

Code: Alles auswählen

backend_.*              : file, opsipxeconfd

mysql is missing.

regards,
bardo wolf

and what about with this config? (this is the current, not working settings)

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

Hi,

Code: Alles auswählen

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

will not work.
The lines are parsed from the top and the first matching wins.
This is for any 'audit*' file in this case.

use instead (the 'license' lines are useful if you perhaps later add a license management):

Code: Alles auswählen

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

like the example from the getting started:
http://download.uib.de/opsi_stable/doc/ ... ig-backend

regards

d.oertel

forum.opsi.org

swaudit time consuming and heavy load on opsi server

swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server

Re: swaudit time consuming and heavy load on opsi server