we had a running opsi installation. Today, I did some updates to the test system (yum update, installation of some other rpms's).
Problem: I'm not able to contact the opsiconfd because it crashes everytime while login:
/var/log/messages
Code: Alles auswählen
Mar 28 18:41:55 opsi-dev kernel: opsiconfd[1595]: segfault at 7fe02d4cfbc0 ip 00007fe02d4cfbc0 sp 00007fff27f7e4b8 error 15
System: Centos 6.2, x64
Linux opsi-dev.dtnet.de 2.6.32-220.7.1.el6.x86_64 #1 SMP Wed Mar 7 00:52:02 GMT 2012 x86_64 x86_64 x86_64 GNU/Linux
Python: python-2.6.6-29.el6.x86_64
Code: Alles auswählen
[root@opsi-dev log]# rpm -qa | grep opsi
opsi-atftp-0.7.dfsg-9.1.x86_64
opsi-linux-bootimage-20120119-1.1.noarch
python-opsi-4.0.1.36-1.1.noarch
opsipxeconfd-4.0.1.5-1.1.noarch
opsi-depotserver-4.0.1.11-1.1.noarch
opsi-utils-4.0.1.16-1.1.noarch
opsi-configed-4.0.1.24-1.1.noarch
opsiconfd-4.0.1.9-5.1.noarch
Maybe somebody will check this behavior ...
I installed fprintd-pam before because of some error messages inside the logfile - of course, the errors now reappeared - but opsi works

/var/log/secure
Code: Alles auswählen
Mar 28 18:55:30 opsi-dev python: PAM unable to dlopen(/lib64/security/pam_fprintd.so): /lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory
Mar 28 18:55:30 opsi-dev python: PAM adding faulty module: /lib64/security/pam_fprintd.so
Mar 28 18:55:30 opsi-dev python: PAM unable to dlopen(/lib64/security/pam_fprintd.so): /lib64/security/pam_fprintd.so: cannot open shared object file: No such file or directory
Mar 28 18:55:30 opsi-dev python: PAM adding faulty module: /lib64/security/pam_fprintd.so
Danny
(DT Netsolution GmbH)