forum.opsi.org

opsi support forum
https://forum.opsi.org/

PCPTCH.EXE kann sich Verbinden, WINST32.EXE sporadisch nicht

https://forum.opsi.org/viewtopic.php?t=21

Seite 1 von 1

PCPTCH.EXE kann sich Verbinden, WINST32.EXE sporadisch nicht

Verfasst: 02 Jul 2008, 10:07
von heuft_kdi
Ich habe mit OPSI ein kleines Problem, welches Sporadisch auftritt (auf jeden fall mit pcptch.exe 3.8.2 und winst32.exe 4.4.9. Mit den neuen Versionen weiß ich es noch nicht, da wir die erst seit heute verteilen).

Das Problem ist, das sich PCPTCH ohne Probleme verbinden kann und auch die Einstellungen alle vom Server übernimmt sowie die Netzwerklaufwerke verbindet. Wenn nun aber WINST32.EXE sich die Software Liste holen will, kommt es zu einen Fehler:

Code: Alles auswählen

02.07.2008 06:36:32 JSON service request https://opsiserver.heuft.intern:4447/rpc?%7B%22id%22:1,%22method%22:%22getProductInstallationStatus%5FlistOfHashes%22,%22params%22:%5B%22edv-w03.heuft.intern%22%5D%7D
02.07.2008 06:36:33 JSON service request https://opsiserver.heuft.intern:4447/rpc?%7B%22id%22:1,%22method%22:%22getProductActionRequests%5FlistOfHashes%22,%22params%22:%5B%22edv-w03.heuft.intern%22%5D%7D
Error: --- opsi service problem ---Access denied: Connection as user 'edv-w03.heuft.intern' required!
Computername:edv-w03.heuft.intern
Computername according to Environment Variable :EDV-W03
opsi service URL https://opsiserver.heuft.intern:4447
Config path: I:\OPSI
Utils path:  O:\OPSI\_Opsi_Client\OPSI\UTILS
Depot path:  I:\OPSI
Beim nächsten Neustart ist dann auf einmal wieder alles OK:

Code: Alles auswählen

02.07.2008 08:55:22 JSON service request https://opsiserver.heuft.intern:4447/rpc?%7B%22id%22:1,%22method%22:%22getProductInstallationStatus%5FlistOfHashes%22,%22params%22:%5B%22edv-w03.heuft.intern%22%5D%7D
02.07.2008 08:55:22 JSON service request https://opsiserver.heuft.intern:4447/rpc?%7B%22id%22:1,%22method%22:%22getProductActionRequests%5FlistOfHashes%22,%22params%22:%5B%22edv-w03.heuft.intern%22%5D%7D
Computername:edv-w03.heuft.intern
Computername according to Environment Variable :EDV-W03
opsi service URL https://opsiserver.heuft.intern:4447
Config path: I:\OPSI
Utils path:  O:\OPSI\_Opsi_Client\OPSI\UTILS
Depot path:  I:\OPSI

02.07.2008 08:55:22 JSON service request https://opsiserver.heuft.intern:4447/rpc?%7B%22id%22:1,%22method%22:%22getInstallableLocalBootProductIds%5Flist%22,%22params%22:%5B%22edv-w03.heuft.intern%22%5D%7D
bootmode BKSTD
winst: Start sorting of products (02.07.2008 08:55:22)
02.07.2008 08:55:22 JSON service request https://opsiserver.heuft.intern:4447/rpc?%7B%22id%22:1,%22method%22:%22getProductDependencies%5FlistOfHashes%22,%22params%22:%5B%5D%7D
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Resolved sequence of products (02.07.2008 08:55:22): 
Product 11 	preloginloader : setup
Product 13 	ms_ie7 : update
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[...]
Woran kann das liegen? Das Problem dabei ist ja, das dadurch die Auslieferung von bestimmten Softwarepaketen unnötig verzögert wird. Und gerade beim Ausrollen eines Sicherheitspatches sollte es unter umständen ja schnell gehen. Und, der User merkt ja gar nicht, das hier etwas nicht funktioniert hat. Wir merken das nur daran, wenn wir in die Softwareliste schauen und sehen, das hier ein Produkt noch auf SETUP/UPDATE steht, obwohl wir genau wissen, das die Person den Rechner am Morgen gestartet hat.

Re: PCPTCH.EXE kann sich Verbinden, WINST32.EXE sporadisch nicht

Verfasst: 02 Jul 2008, 10:21
von j.schneider
Hallo,

was sagen denn die Server-seitigen Logs?
/var/log/opsi/opsiconfd/opsiconfd.log
/var/log/opsi/opsiconfd/<client-ip>.log

Da sollte etwas mehr zu `Connection as user 'edv-w03.heuft.intern' required!` stehen.

Welche Opsi Version wird verwendet?

Gruß
Jan Schneider

Re: PCPTCH.EXE kann sich Verbinden, WINST32.EXE sporadisch nicht

Verfasst: 02 Jul 2008, 10:38
von heuft_kdi
Wir verwenden noch OPSI 3.1 (und da augenscheinlich bei Opsi 3.3 LDAP noch nicht implementiert ist, werden wir auch erst einmal dabei bleiben).

Unsere opsiconfd.conf sieht so aus (bereinigt)

Code: Alles auswählen

[global]
        bm config = /etc/opsi/backendManager.d
        pid file = /var/run/opsiconfd.pid
        log file = /var/log/opsi/opsiconfd/%m.log
        symlink logs = no
        log level = 3
        log format = (%l) %D %M (%F|%N)
        max execution statistics = 250
[service]
        interface = 0.0.0.0
        http port = 0
        https port = 4447
        ssl server cert = /etc/opsi/opsiconfd.pem
        ssl server key = /etc/opsi/opsiconfd.pem
[session]
        session name = OPSISID
        verify ip = no
        resolve ip = no
        max inactive interval = 120
[directories]
        / = /usr/share/opsiconfd/static
        configed = /usr/lib/configed
Und hier nun der Auszug aus den LOG Files:
In der opsiconfd.log steht gar nichts zum Fraglichen Zeitpunkt

Und im Logfile vom Rechner steht folgendes:

Code: Alles auswählen

(3) Jul 02 06:36:30 Failed to resolve hostname 'edv-w03.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 528 in 'getPcpatchPassword' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 75 in 'getNetworkConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(2) Jul 02 06:36:30      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:30      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:30      line 23 in 'getGeneralConfig_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:30      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:30 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(3) Jul 02 06:36:32 Failed to resolve hostname 'edv-w03.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(3) Jul 02 06:36:33 Failed to resolve hostname 'edv-w03.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(2) Jul 02 06:36:33      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:33      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:33      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:33      line 806 in 'getProductInstallationStatus_listOfHashes' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:33      line 422 in '_execMethod' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:33      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:33      line 1200 in 'getProductInstallationStatus_listOfHashes' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 06:36:33      line 1122 in 'getProductIds_list' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 06:36:33      line 170 in 'getHostDn' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 06:36:33 Host 'opsiserver.heuft.intern' does not exist: No results for search in baseDn: 'ou=Machines,o=hs,dc=heuft,dc=intern', filter: '(&(objectClass=opsiHost)(cn=opsiserver))', scope: 2 (opsico
nfd|760)
(2) Jul 02 06:36:33      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:33      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 06:36:33      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 06:36:33      line 876 in 'getProductActionRequests_listOfHashes' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 06:36:33      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 06:36:33 Access denied: Connection as user 'edv-w03.heuft.intern' required! (opsiconfd|760)
(3) Jul 02 08:55:20 Failed to resolve hostname 'edv-w03.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(3) Jul 02 08:55:22 Failed to resolve hostname 'edv-w03.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(2) Jul 02 08:55:22      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 08:55:22      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 08:55:22      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 08:55:22      line 806 in 'getProductInstallationStatus_listOfHashes' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 08:55:22      line 422 in '_execMethod' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 08:55:22      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 08:55:22      line 1200 in 'getProductInstallationStatus_listOfHashes' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 08:55:22      line 1122 in 'getProductIds_list' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 08:55:22      line 170 in 'getHostDn' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 08:55:22 Host 'opsiserver.heuft.intern' does not exist: No results for search in baseDn: 'ou=Machines,o=hs,dc=heuft,dc=intern', filter: '(&(objectClass=opsiHost)(cn=opsiserver))', scope: 2 (opsico
nfd|760)
(3) Jul 02 08:55:22 No policy found for: cn=EDV-W03,ou=Machines,o=HS,dc=heuft,dc=intern, con: cn=productDeployments,cn=policies,cn=opsi,o=hs,dc=heuft,dc=intern, fil: (objectClass=opsiPolicyProductDeployment)
, ia: opsiProductReference, ml: 100 (LDAP.py|1461)
(2) Jul 02 08:55:33      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 08:55:33      line 811 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 08:55:33 Method 'setMacAddress' is not valid (opsiconfd|760)
(3) Jul 02 08:55:33 No products found (objectClass: opsiNetBootProduct) (LDAP.py|1117)
(3) Jul 02 08:56:50 Failed to resolve hostname 'edv-w03.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(3) Jul 02 08:56:52 Failed to resolve hostname 'edv-w03.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(2) Jul 02 08:56:53      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 08:56:53      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 02 08:56:53      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 08:56:53      line 806 in 'getProductInstallationStatus_listOfHashes' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 02 08:56:53      line 422 in '_execMethod' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 02 08:56:53      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 02 08:56:53      line 1200 in 'getProductInstallationStatus_listOfHashes' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 08:56:53      line 1122 in 'getProductIds_list' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 08:56:53      line 170 in 'getHostDn' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/LDAP.py' (opsiconfd|756)
(2) Jul 02 08:56:53 Host 'opsiserver.heuft.intern' does not exist: No results for search in baseDn: 'ou=Machines,o=hs,dc=heuft,dc=intern', filter: '(&(objectClass=opsiHost)(cn=opsiserver))', scope: 2 (opsico
nfd|760)
(3) Jul 02 08:56:53 No policy found for: cn=EDV-W03,ou=Machines,o=HS,dc=heuft,dc=intern, con: cn=productDeployments,cn=policies,cn=opsi,o=hs,dc=heuft,dc=intern, fil: (objectClass=opsiPolicyProductDeployment)
, ia: opsiProductReference, ml: 100 (LDAP.py|1461)
(3) Jul 02 08:56:53 No policy found for: cn=EDV-W03,ou=Machines,o=HS,dc=heuft,dc=intern, con: cn=ms_ie7,cn=productProperties,cn=policies,cn=opsi,o=hs,dc=heuft,dc=intern, fil: (&(objectClass=opsiPolicyProduct
Property)(opsiProductReference=cn=ms_ie7,cn=products,cn=opsi,o=hs,dc=heuft,dc=intern)), ia: None, ml: 100 (LDAP.py|1827)
(3) Jul 02 08:56:57 No products found (objectClass: opsiNetBootProduct) (LDAP.py|1117)
Die ganzen 'Failed to resolv hostname' kommen da her, weil die WINDOWS Clients nicht in der DNS eingetragen sind und das Reverse Lookup über WINS nicht ordentlich funktioniert hat (wir haben das getestet) weswegen wir diese Funktion wieder ausgebaut haben.

Beim Neustart um 08:55:20 wurden dann zwei Pakete installiert, wovon eines einen Neustart angetriggert hat.

Re: PCPTCH.EXE kann sich Verbinden, WINST32.EXE sporadisch nicht

Verfasst: 07 Jul 2008, 14:11
von heuft_kdi
Also, langsam wird es 'Ärgerlich'.

ich hatte heute wieder ein Problem beim Ausrollen mehrere Pakete. Beim durchforsten der Logfiles habe ich mich dann gewundert, warum ein Paket zweimal installiert wurde. Ein Blick ins Server Log zeigte dann folgendes:

Code: Alles auswählen

(3) Jul 07 07:32:46 No policy found for: cn=TFH-W04,ou=Machines,o=HS,dc=heuft,dc=intern, con: cn=ms_excel_viewer,cn=productProperties,cn=policies,cn=opsi,o=hs,dc=heuft,dc=intern, fil: (&(objectClass=opsiPolicyProductProperty)(opsiProductReference=cn=ms_excel_viewer,cn=products,cn=opsi,o=hs,dc=heuft,dc=intern)), ia: None, ml: 100 (LDAP.py|1827)
(3) Jul 07 07:33:03 No products found (objectClass: opsiNetBootProduct) (LDAP.py|1117)
(3) Jul 07 07:33:03 No policy found for: cn=TFH-W04,ou=Machines,o=HS,dc=heuft,dc=intern, con: cn=ms_word_viewer,cn=productProperties,cn=policies,cn=opsi,o=hs,dc=heuft,dc=intern, fil: (&(objectClass=opsiPolicyProductProperty)(opsiProductReference=cn=ms_word_viewer,cn=products,cn=opsi,o=hs,dc=heuft,dc=intern)), ia: None, ml: 100 (LDAP.py|1827)
(3) Jul 07 07:33:34 No products found (objectClass: opsiNetBootProduct) (LDAP.py|1117)
(3) Jul 07 07:33:34 No policy found for: cn=TFH-W04,ou=Machines,o=HS,dc=heuft,dc=intern, con: cn=wmp11,cn=productProperties,cn=policies,cn=opsi,o=hs,dc=heuft,dc=intern, fil: (&(objectClass=opsiPolicyProductProperty)(opsiProductReference=cn=wmp11,cn=products,cn=opsi,o=hs,dc=heuft,dc=intern)), ia: None, ml: 100 (LDAP.py|1827)
(3) Jul 07 07:35:47 Failed to resolve hostname 'tfh-w04.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
(1) Jul 07 07:35:47 Failed to execute rpc, cannot get bm instance from session! (opsiconfd|793)
(1) Jul 07 07:35:47 rpc is: {'params': ['wmp11', 'tfh-w04.heuft.intern', 'installed'], 'id': 1, 'method': 'setProductInstallationStatus'} (opsiconfd|794)
(1) Jul 07 07:35:47 session is: <twisted.web.server.Session instance at 0xb75c45ec> (opsiconfd|795)
(2) Jul 07 07:35:47 Failed to execute rpc, cannot get bm instance from session! (opsiconfd|764)
(2) Jul 07 07:35:47      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 07 07:35:47      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 07 07:35:47      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 07 07:35:47      line 902 in 'setProductActionRequest' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 07 07:35:47      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
(2) Jul 07 07:35:47 Access denied: Connection as user 'tfh-w04.heuft.intern' required! (opsiconfd|760)
(2) Jul 07 07:35:47      line 746 in 'run' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 07 07:35:47      line 817 in 'execute' in file '/usr/sbin/opsiconfd' (opsiconfd|756)
(2) Jul 07 07:35:47      line 0 in '?' in file '<string>' (opsiconfd|756)
(2) Jul 07 07:35:47      line 1059 in 'getProductProperties_hash' in file '/etc/opsi/backendManager.d/50_interface.conf' (opsiconfd|756)
(2) Jul 07 07:35:47      line 393 in '_verifyUser' in file '/usr/lib/python2.4/site-packages/OPSI/Backend/BackendManager.py' (opsiconfd|756)
Wieso geht hier ab und zu die Autorisierung flöten?

Das kann doch nicht daran liegen, das die Rechner nicht in der DNS sind.
Erschwerend kommt hinzu, das ich in der /etc/opsi/opsiconfd.conf eigentlich stehen habe

Code: Alles auswählen

[session]
        session name = OPSISID
        verify ip = no
        resolve ip = no
        max inactive interval = 120
Also sollte die DNS doch vollkommen Egal sein.

Also, warum bekomme ich regelmässig noch Einträge wie diese:

Code: Alles auswählen

Failed to resolve hostname 'tfh-w04.heuft.intern': (-2, 'Der Name oder der Dienst ist nicht bekannt') (opsiconfd|633)
und warum ab und zu

Code: Alles auswählen

Access denied: Connection as user 'tfh-w04.heuft.intern' required! (opsiconfd|760)
?
Alle Zeiten sind UTC+02:00
Seite 1 von 1

Powered by phpBB® Forum Software © phpBB Limited

Deutsche Übersetzung durch phpBB.de