forum.opsi.org

Verfasst: **21 Feb 2011, 08:14**

hallo,
ich habe unseren opsiserver testweise von 3.4 auf 4.0 aktualisiert. hierbei hat auch alles geklappt. das problem tritt nun auf, wenn ich einem client den neuen opsi-client-agent installieren lasse.

der client kann den server erreichen, doch kann er das install-verzeichnis nicht mounten. falscher benutzername.
der preloginloader (opsiclientd) klappt hier wunderbar.

genauer liegt das problem an der config datei (im abschnitt [depot_server]) unter "c:\programme\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf" - diese wird wohl bei jeder verbindung mit dem server neu geschrieben, sodass lokale änderungen (um den benutzernamen zu korrigieren) keine wirkung haben.

beim preloginloader konnte ich auf dem server unter "/opt/pcbin/install/preloginloader/files/preloginloader/dist/opsiclientd/opsiclientd.conf" den benutzernamen auf dem server ändern und die lokale datei wurde dann mit der vom server ersetzt (so funktionierte es).

dieses vorgehen klappt aber beim opsi-client-agent nicht mehr! auf dem sever habe ich im ../install/opsi-client-agent/ die dateien "opsiclientd.conf" und "../cfg/config.ini" angepasst, doch wird die lokale opsiconfd.conf immer wieder mit irgendeiner anderen datei ersetzt (zumindest ist der benutzername immer wieder falsch). es wird also entweder eine andere datei verwendet, um die daten lokal zu überschreiben (wenn ja, welche?) oder es gibt lokal auf dem client noch ein "backup" der opsiclientd.conf, von der immer zurückgeschrieben wird...

welche datei/einstellung o.Ä. muss ich anpassen, um den smb-user zu ändern? (lokale änderungen bringen ja nix, weil sie immer wieder überschrieben werden.)
wäre super, wenn das noch gelöst wird, dann können wir endlich auf 4.0 upgraden und treeview usw. einkaufen

Verfasst: **21 Feb 2011, 09:41**

Hallo,

das sollte helfen:

Code: Alles auswählen

opsi-admin -d task setPcpatchPassword <password>

Gruß,
Jan Schneider

Verfasst: **21 Feb 2011, 10:25**

nein, daran liegts nicht..

wir haben probleme mit dem benutzerkonto (lokal/domäne) - wenn ich in der config-datei "meinsever\pcpatch" als user angebe, klappt der auth (beim preloginloader). da nun aber der opsi-client-agent die lokale opsiclientd.conf datei bei jedem aufruf ersetzt, kann ich diese änderung nicht lokal machen. welche datei muss ich also auf dem server anpassen? bzw. woher bekommt der client-agent die daten, mit der er die lokale datei ersetzt?

Verfasst: **21 Feb 2011, 10:40**

Ah, ok...

Code: Alles auswählen

/opt/pcbin/install/opsi-client-agent/files/opsi/dist/opsiclientd/opsiclientd.conf

[depotserver]
username = meinsever\\pcpatch

Verfasst: **21 Feb 2011, 11:05**

ja, so hatte ich das gedacht (da es beim preloginloader funktioniert) - doch wird diese datei wohl vom opsi-client-agent ignoriert...

bei jedem aufruf wird die datei ersetzt und zwar nicht mit dem wert aus der server-datei (in der ja username= server\pcpatch steht ~ ob \ oder \\ macht in dem fall wohl keinen unterschied) sondern mit dem normalen username=papatch...

sonst noch ideen oder dateien von denen der client-agent sich diese angabe zieht?

Verfasst: **22 Feb 2011, 08:25**

hmm, habe den client nochmal neu installiert - preloginloader drauf (klappt) und dann via opsiconfd den client-agent installieren lassen.

diesmal scheint das ändern der opsiconfd.conf serverseitig was zu bewirken, die datei wird lokal übernommen und der benutzername stimmt (vmopsi4lxsg7/pcpatch), dennoch klappt der mount nicht.

wenn ich mit den logindaten das laufwerk manuell verbinde klappts (und der prelognloader verwendet ja die gleichen daten). auch das pcpatch-passwort habe ich mal via opsi-admin erneuert...

hier das log. hoffe, man findet eine lösung. würden sehr gerne den 4er einsetzen.

6] [Feb 22 08:13:17] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01ABCAA8> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:17] [ control server ] Authorization request from @172.16.250.89 (ControlServer.pyo|320)
[5] [Feb 22 08:13:17] [ json rpc ] -----> Executing: fireEvent(u'on_demand') (JsonRpc.pyo|96)
[5] [Feb 22 08:13:17] [ opsiclientd ] Firing event 'on_demand' (ControlServer.pyo|731)
[6] [Feb 22 08:13:17] [ event generator on_demand ] Firing event '<ocdlib.Events.CustomEvent object at 0x01B3DE90>' (Events.pyo|365)
[6] [Feb 22 08:13:17] [ event generator on_demand ] Event info: (Events.pyo|366)
[6] [Feb 22 08:13:17] [ event generator on_demand ] Starting FireEventThread for listeners: [<OpsiclientdNT5(Thread-1, started daemon 1824)>] (Events.pyo|389)
[6] [Feb 22 08:13:17] [ json rpc ] Got result (JsonRpc.pyo|124)
[6] [Feb 22 08:13:17] [ event generator on_demand ] Calling processEvent on listener <OpsiclientdNT5(Thread-1, started daemon 1824)> (Events.pyo|384)
[5] [Feb 22 08:13:17] [ opsiclientd ] Processing event <ocdlib.Events.CustomEvent object at 0x01B3DE90> (Opsiclientd.pyo|321)
[6] [Feb 22 08:13:17] [ event processing on_demand ] Searching pids of process name winlogon.exe (session id: 0) (Windows.pyo|814)
[6] [Feb 22 08:13:17] [ event processing on_demand ] Found process winlogon.exe with matching name (pid 616, session 0) (Windows.pyo|836)
[6] [Feb 22 08:13:17] [ event processing on_demand ] Searching pids of process name winlogon.exe (session id: 0) (Windows.pyo|814)
[6] [Feb 22 08:13:17] [ event processing on_demand ] Found process winlogon.exe with matching name (pid 616, session 0) (Windows.pyo|836)
[6] [Feb 22 08:13:17] [ event processing on_demand ] Session id set to 0 (Opsiclientd.pyo|543)
[5] [Feb 22 08:13:17] [ opsiclientd ] Creating local user 'pcpatch' (Opsiclientd.pyo|177)
[6] [Feb 22 08:13:17] [ opsiclientd ] Admin group name is 'Administratoren' (Windows.pyo|1094)
[6] [Feb 22 08:13:17] [ opsiclientd ] Adding user 'pcpatch' to group 'Administratoren' (Windows.pyo|1041)
[5] [Feb 22 08:13:17] [ event processing on_demand ] ============= EventProcessingThread for occurcence of event '<ocdlib.Events.CustomEvent object at 0x01B3DE90>' started ============= (Opsiclientd.pyo|1288)
[5] [Feb 22 08:13:17] [ event processing on_demand ] Starting notification server on port 44000 (Opsiclientd.pyo|564)
[6] [Feb 22 08:13:17] [ event processing on_demand ] cannot send notification 'subjectsChanged', no client connected (Message.pyo|557)
[6] [Feb 22 08:13:17] [ opsiclientd ] Notification server starting (Message.pyo|603)
[5] [Feb 22 08:13:17] [ event processing on_demand ] Notification server started (Opsiclientd.pyo|580)
[6] [Feb 22 08:13:18] [ event processing on_demand ] Action processor name 'opsi-winst', version '4.10.8.7' (Opsiclientd.pyo|867)
[6] [Feb 22 08:13:18] [ json rpc ] cannot send notification 'messageChanged', no client connected (Message.pyo|557)
[6] [Feb 22 08:13:18] [ event processing on_demand ] cannot send notification 'messageChanged', no client connected (Message.pyo|557)
[6] [Feb 22 08:13:18] [ event processing on_demand ] cannot send notification 'messageChanged', no client connected (Message.pyo|557)
[5] [Feb 22 08:13:18] [ opsiclientd ] Block login now set to 'True' (Opsiclientd.pyo|102)
[6] [Feb 22 08:13:18] [ opsiclientd ] Starting block login notifier app (Opsiclientd.pyo|106)
[6] [Feb 22 08:13:18] [ opsiclientd ] Searching pids of process name winlogon.exe (session id: 0) (Windows.pyo|814)
[6] [Feb 22 08:13:18] [ opsiclientd ] Found process winlogon.exe with matching name (pid 616, session 0) (Windows.pyo|836)
[5] [Feb 22 08:13:18] [ opsiclientd ] Executing: 'C:\Programme\opsi.org\opsi-client-agent\\notifier.exe -s notifier\\block_login.ini' in session '0' on desktop 'winsta0\winlogon' (Windows.pyo|985)
[6] [Feb 22 08:13:18] [ opsiclientd ] Process startet, pid: 864 (Windows.pyo|987)
[5] [Feb 22 08:13:18] [ event processing on_demand ] Starting notifier application in session '0' (Opsiclientd.pyo|841)
[6] [Feb 22 08:13:18] [ opsiclientd ] Searching pids of process name winlogon.exe (session id: 0) (Windows.pyo|814)
[6] [Feb 22 08:13:18] [ opsiclientd ] Found process winlogon.exe with matching name (pid 616, session 0) (Windows.pyo|836)
[5] [Feb 22 08:13:18] [ opsiclientd ] Executing: 'C:\Programme\opsi.org\opsi-client-agent\\opsiclientd_rpc.exe "vmopsi5lxsg7.wpe.local" "*** confidential ***" "4441" "setCurrentActiveDesktopName("0", System.getActiveDesktopName())"' in session '0' on desktop 'winsta0\winlogon' (Windows.pyo|985)
[6] [Feb 22 08:13:18] [ opsiclientd ] Process startet, pid: 988 (Windows.pyo|987)
[6] [Feb 22 08:13:18] [ opsiclientd ] Waiting for process ending: 988 (timeout: 60 seconds) (Windows.pyo|990)
[6] [Feb 22 08:13:19] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01ABCA08> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:19] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:19] [ json rpc ] -----> Executing: backend_getInterface() (JsonRpc.pyo|96)
[6] [Feb 22 08:13:19] [ json rpc ] Got result (JsonRpc.pyo|124)
[6] [Feb 22 08:13:19] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01B99E68> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:19] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:19] [ json rpc ] -----> Executing: setCurrentActiveDesktopName(0, u'Default') (JsonRpc.pyo|96)
[5] [Feb 22 08:13:19] [ opsiclientd ] rpc setCurrentActiveDesktopName: current active desktop name for session 0 set to 'Default' (ControlServer.pyo|750)
[6] [Feb 22 08:13:19] [ json rpc ] Got result (JsonRpc.pyo|124)
[6] [Feb 22 08:13:19] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01B99E40> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:19] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:19] [ json rpc ] -----> Executing: backend_exit() (JsonRpc.pyo|96)
[6] [Feb 22 08:13:19] [ json rpc ] Got result (JsonRpc.pyo|124)
[5] [Feb 22 08:13:19] [ opsiclientd ] Process 988 ended with exit code 0 (Windows.pyo|1000)
[6] [Feb 22 08:13:19] [ event processing on_demand ] Running command C:\Programme\opsi.org\opsi-client-agent\\notifier.exe -p 44000 -s notifier\\action.ini in session '0' on desktop 'Default' (Opsiclientd.pyo|817)
[6] [Feb 22 08:13:19] [ event processing on_demand ] Searching pids of process name winlogon.exe (session id: 0) (Windows.pyo|814)
[6] [Feb 22 08:13:19] [ event processing on_demand ] Found process winlogon.exe with matching name (pid 616, session 0) (Windows.pyo|836)
[5] [Feb 22 08:13:19] [ event processing on_demand ] Executing: 'C:\Programme\opsi.org\opsi-client-agent\\notifier.exe -p 44000 -s notifier\\action.ini' in session '0' on desktop 'winsta0\Default' (Windows.pyo|985)
[6] [Feb 22 08:13:19] [ event processing on_demand ] Process startet, pid: 1204 (Windows.pyo|987)
[6] [Feb 22 08:13:19] [ event processing on_demand ] Session id set to 0 (Opsiclientd.pyo|543)
[6] [Feb 22 08:13:20] [ control server ] client connection made (Message.pyo|459)
[6] [Feb 22 08:13:20] [ control server ] sending notification 'subjectsChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:24] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:24] [ event processing on_demand ] User is allowed to cancel connection after 30 seconds (Opsiclientd.pyo|609)
[6] [Feb 22 08:13:24] [ event processing on_demand ] Starting ServiceConnectionThread, timeout is 30 seconds (Opsiclientd.pyo|614)
[5] [Feb 22 08:13:24] [ service connection ] Connecting to config server 'https://172.16.250.89:4447/rpc' #1 (OpsiService.pyo|82)
[6] [Feb 22 08:13:24] [ service connection ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:24] [ opsiclientd ] Starting new HTTPS connection (0) to 172.16.250.89:4447 (HTTP.pyo|408)
[6] [Feb 22 08:13:24] [ opsiclientd ] Connection established to: 172.16.250.89 (HTTP.pyo|411)
[6] [Feb 22 08:13:25] [ service connection ] Verifying modules file signature (JSONRPC.pyo|488)
[5] [Feb 22 08:13:25] [ service connection ] Modules file signature verified (customer: opsi community) (JSONRPC.pyo|505)
[6] [Feb 22 08:13:25] [ service connection ] <OPSI.Backend.JSONRPC.JSONRPCBackend instance at 0x01B7CEE0>: Connected to service (JSONRPC.pyo|399)
[6] [Feb 22 08:13:25] [ service connection ] sending notification 'messageChanged' to clients (Message.pyo|559)
[5] [Feb 22 08:13:25] [ service connection ] Connected to config server 'https://172.16.250.89:4447/rpc' (OpsiService.pyo|94)
[6] [Feb 22 08:13:25] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:25] [ event processing on_demand ] sending notification 'subjectsChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:25] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[5] [Feb 22 08:13:25] [ event processing on_demand ] Updating config file: 'C:\Programme\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf' (Config.pyo|274)
[5] [Feb 22 08:13:25] [ event processing on_demand ] Config file 'C:\Programme\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf' written (Config.pyo|304)
[5] [Feb 22 08:13:25] [ event processing on_demand ] Getting config from service (Opsiclientd.pyo|714)
[6] [Feb 22 08:13:25] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId clientconfig.depot.dynamic, values [False] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId license-management.use, values [False] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId clientconfig.configserver.url, values [u'https://172.16.250.89:4447/rpc'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Setting config value config_service.url (Config.pyo|155)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId pcptchlabel1, values [u'opsi'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId opsi-linux-bootimage.append, values [] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId product_sort_algorithm, values [u'algorithm1'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId pcptchlabel2, values [u'wachendorff'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId clientconfig.windows.domain, values [u'WPE'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId button_stopnetworking, values [u''] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId pcptchbitmap1, values [u'winst1.bmp'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId pcptchbitmap2, values [u'winst2.bmp'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId clientconfig.depot.drive, values [u'P:'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Setting config value depot_server.drive (Config.pyo|155)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId nextbootservertype, values [u'service'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId secsuntilconnectiontimeout, values [u'60'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId utilsdrive, values [u'P:'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId configdrive, values [u'O:'] (Opsiclientd.pyo|752)
[6] [Feb 22 08:13:25] [ event processing on_demand ] Got config state from service: configId clientconfig.depot.id, values [u'vmopsi4lxsg7.wpe.local'] (Opsiclientd.pyo|752)
[5] [Feb 22 08:13:25] [ event processing on_demand ] Got config from service (Opsiclientd.pyo|771)
[6] [Feb 22 08:13:25] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[5] [Feb 22 08:13:25] [ event processing on_demand ] Updating config file: 'C:\Programme\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf' (Config.pyo|274)
[5] [Feb 22 08:13:25] [ event processing on_demand ] No need to write config file 'C:\Programme\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf', config file is up to date (Config.pyo|306)
[6] [Feb 22 08:13:25] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[5] [Feb 22 08:13:25] [ event processing on_demand ] [ 1] product swaudit: setup (Opsiclientd.pyo|1079)
[5] [Feb 22 08:13:25] [ event processing on_demand ] Start processing action requests (Opsiclientd.pyo|1086)
[5] [Feb 22 08:13:25] [ event processing on_demand ] Selecting depot (Config.pyo|314)
[5] [Feb 22 08:13:26] [ event processing on_demand ] Selected depot is: <OpsiConfigserver id 'vmopsi4lxsg7.wpe.local'> (Config.pyo|431)
[6] [Feb 22 08:13:26] [ event processing on_demand ] Setting config value depot_server.depot_id (Config.pyo|155)
[6] [Feb 22 08:13:26] [ event processing on_demand ] Setting config value depot_server.url (Config.pyo|155)
[6] [Feb 22 08:13:26] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:26] [ opsiclientd ] Searching pids of process name winlogon.exe (session id: 0) (Windows.pyo|814)
[6] [Feb 22 08:13:26] [ opsiclientd ] Found process winlogon.exe with matching name (pid 616, session 0) (Windows.pyo|836)
[5] [Feb 22 08:13:26] [ opsiclientd ] Executing: 'C:\Programme\opsi.org\opsi-client-agent\\opsiclientd_rpc.exe "vmopsi5lxsg7.wpe.local" "*** confidential ***" "4441" "setCurrentActiveDesktopName("0", System.getActiveDesktopName())"' in session '0' on desktop 'winsta0\winlogon' (Windows.pyo|985)
[6] [Feb 22 08:13:26] [ opsiclientd ] Process startet, pid: 548 (Windows.pyo|987)
[6] [Feb 22 08:13:26] [ opsiclientd ] Waiting for process ending: 548 (timeout: 60 seconds) (Windows.pyo|990)
[6] [Feb 22 08:13:27] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01B99E90> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:27] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:27] [ json rpc ] -----> Executing: backend_getInterface() (JsonRpc.pyo|96)
[6] [Feb 22 08:13:27] [ json rpc ] Got result (JsonRpc.pyo|124)
[6] [Feb 22 08:13:27] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01C75D00> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:27] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:27] [ json rpc ] -----> Executing: setCurrentActiveDesktopName(0, u'Default') (JsonRpc.pyo|96)
[5] [Feb 22 08:13:27] [ opsiclientd ] rpc setCurrentActiveDesktopName: current active desktop name for session 0 set to 'Default' (ControlServer.pyo|750)
[6] [Feb 22 08:13:27] [ json rpc ] Got result (JsonRpc.pyo|124)
[6] [Feb 22 08:13:27] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01C72990> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:27] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:27] [ json rpc ] -----> Executing: backend_exit() (JsonRpc.pyo|96)
[6] [Feb 22 08:13:27] [ json rpc ] Got result (JsonRpc.pyo|124)
[5] [Feb 22 08:13:27] [ opsiclientd ] Process 548 ended with exit code 0 (Windows.pyo|1000)
[5] [Feb 22 08:13:27] [ event processing on_demand ] Updating action processor (Opsiclientd.pyo|901)
[6] [Feb 22 08:13:27] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[5] [Feb 22 08:13:27] [ event processing on_demand ] Mounting depot share smb://vmopsi4lxsg7/opt_pcbin/install (Opsiclientd.pyo|879)
[6] [Feb 22 08:13:27] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[5] [Feb 22 08:13:27] [ event processing on_demand ] Mounting '\\vmopsi4lxsg7\opt_pcbin' to 'P:' (Windows.pyo|437)
[5] [Feb 22 08:13:30] [ event processing on_demand ] Local action processor exists and seems to be up to date (Opsiclientd.pyo|932)
[5] [Feb 22 08:13:30] [ event processing on_demand ] Starting action processor in session '0' on desktop 'Default' (Opsiclientd.pyo|1240)
[6] [Feb 22 08:13:30] [ event processing on_demand ] Running command C:\Programme\opsi.org\opsi-client-agent\action_processor_starter.exe "vmopsi5lxsg7.wpe.local" "*** confidential ***" "4441" "c:\\tmp\\opsiclientd.log" "6" "smb://vmopsi4lxsg7/opt_pcbin/install" "P:" "vmopsi4lxsg7\pcpatch" "*** confidential ***" "0" "Default" "\"C:\Programme\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://172.16.250.89:4447/rpc\" /clientid vmopsi5lxsg7.wpe.local /username vmopsi5lxsg7.wpe.local /password *** confidential ***" 10800 "pcpatch" "*** confidential ***" in session '0' on desktop 'Default' (Opsiclientd.pyo|817)
[6] [Feb 22 08:13:30] [ event processing on_demand ] Searching pids of process name winlogon.exe (session id: 0) (Windows.pyo|814)
[6] [Feb 22 08:13:31] [ event processing on_demand ] Found process winlogon.exe with matching name (pid 616, session 0) (Windows.pyo|836)
[5] [Feb 22 08:13:31] [ event processing on_demand ] Executing: 'C:\Programme\opsi.org\opsi-client-agent\action_processor_starter.exe "vmopsi5lxsg7.wpe.local" "*** confidential ***" "4441" "c:\\tmp\\opsiclientd.log" "6" "smb://vmopsi4lxsg7/opt_pcbin/install" "P:" "vmopsi4lxsg7\pcpatch" "*** confidential ***" "0" "Default" "\"C:\Programme\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://172.16.250.89:4447/rpc\" /clientid vmopsi5lxsg7.wpe.local /username vmopsi5lxsg7.wpe.local /password *** confidential ***" 10800 "pcpatch" "*** confidential ***"' in session '0' on desktop 'winsta0\Default' (Windows.pyo|985)
[6] [Feb 22 08:13:31] [ event processing on_demand ] Process startet, pid: 2132 (Windows.pyo|987)
[6] [Feb 22 08:13:31] [ event processing on_demand ] Waiting for process ending: 2132 (timeout: 0 seconds) (Windows.pyo|990)
[6] [Feb 22 08:13:31] [ action_processor_starter.exe ] Starting new HTTPS connection (0) to localhost:4441 (HTTP.pyo|408)
[6] [Feb 22 08:13:31] [ action_processor_starter.exe ] Connection established to: localhost (HTTP.pyo|411)
[6] [Feb 22 08:13:31] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01C72E90> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:31] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:32] [ json rpc ] -----> Executing: backend_getInterface() (JsonRpc.pyo|96)
[6] [Feb 22 08:13:32] [ json rpc ] Got result (JsonRpc.pyo|124)
[6] [Feb 22 08:13:32] [ action_processor_starter.exe ] <OPSI.Backend.JSONRPC.JSONRPCBackend instance at 0x00E9F148>: Connected to service (JSONRPC.pyo|399)
[6] [Feb 22 08:13:32] [ action_processor_starter.exe ] Impersonating user 'pcpatch' (action_processor_starter.py|89)
[5] [Feb 22 08:13:32] [ action_processor_starter.exe ] Mounting depot share smb://vmopsi4lxsg7/opt_pcbin/install (action_processor_starter.py|99)
[6] [Feb 22 08:13:32] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01C74F08> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:32] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:32] [ json rpc ] -----> Executing: setStatusMessage(u'0', u'Verbinde mit Depot-Freigabe smb://vmopsi4lxsg7/opt_pcbin/install') (JsonRpc.pyo|96)
[5] [Feb 22 08:13:32] [ opsiclientd ] rpc setStatusMessage: Setting status message to 'Verbinde mit Depot-Freigabe smb://vmopsi4lxsg7/opt_pcbin/install' (ControlServer.pyo|738)
[6] [Feb 22 08:13:32] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:32] [ json rpc ] Got result (JsonRpc.pyo|124)
[5] [Feb 22 08:13:32] [ action_processor_starter.exe ] Mounting '\\vmopsi4lxsg7\opt_pcbin' to 'P:' (Windows.pyo|437)
[3] [Feb 22 08:13:36] [ action_processor_starter.exe ] Failed to mount '\\vmopsi4lxsg7\opt_pcbin': (1326, 'WNetAddConnection2', 'Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.') (Windows.pyo|450)
[2] [Feb 22 08:13:36] [ action_processor_starter.exe ] Traceback: (Logger.pyo|710)
[2] [Feb 22 08:13:36] [ action_processor_starter.exe ] line 103 in '<module>' in file 'action_processor_starter.py' (Logger.pyo|710)
[2] [Feb 22 08:13:36] [ action_processor_starter.exe ] line 451 in 'mount' in file 'OPSI\System\Windows.pyo' (Logger.pyo|710)
[2] [Feb 22 08:13:36] [ action_processor_starter.exe ] ==>>> Failed to mount '\\vmopsi4lxsg7\opt_pcbin': (1326, 'WNetAddConnection2', 'Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.') (action_processor_starter.py|117)
[6] [Feb 22 08:13:36] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01C740A8> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:36] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:37] [ json rpc ] -----> Executing: setStatusMessage(u'0', u"Failed to process action requests: Failed to mount '\\\\vmopsi4lxsg7\\opt_pcbin': (1326, 'WNetAddConnection2', 'Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.')") (JsonRpc.pyo|96)
[5] [Feb 22 08:13:37] [ opsiclientd ] rpc setStatusMessage: Setting status message to 'Failed to process action requests: Failed to mount '\\vmopsi4lxsg7\opt_pcbin': (1326, 'WNetAddConnection2', 'Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.')' (ControlServer.pyo|738)
[6] [Feb 22 08:13:37] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:37] [ json rpc ] Got result (JsonRpc.pyo|124)
[3] [Feb 22 08:13:37] [ action_processor_starter.exe ] Failed to process action requests: Failed to mount '\\vmopsi4lxsg7\opt_pcbin': (1326, 'WNetAddConnection2', 'Anmeldung fehlgeschlagen: unbekannter Benutzername oder falsches Kennwort.') (action_processor_starter.py|124)
[6] [Feb 22 08:13:37] [ control server ] Worker <ocdlib.ControlServer.ControlServerJsonRpcWorker instance at 0x01C6C738> started processing (ControlServer.pyo|371)
[5] [Feb 22 08:13:37] [ control server ] Authorization request from vmopsi5lxsg7.wpe.local@127.0.0.1 (ControlServer.pyo|320)
[5] [Feb 22 08:13:37] [ json rpc ] -----> Executing: backend_exit() (JsonRpc.pyo|96)
[6] [Feb 22 08:13:37] [ json rpc ] Got result (JsonRpc.pyo|124)
[5] [Feb 22 08:13:37] [ event processing on_demand ] Process 2132 ended with exit code 0 (Windows.pyo|1000)
[6] [Feb 22 08:13:37] [ event processing on_demand ] Session id set to 0 (Opsiclientd.pyo|543)
[6] [Feb 22 08:13:37] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[6] [Feb 22 08:13:41] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
[5] [Feb 22 08:13:41] [ event processing on_demand ] Writing log to service (Opsiclientd.pyo|780)
[6] [Feb 22 08:13:41] [ event processing on_demand ] sending notification 'messageChanged' to clients (Message.pyo|559)
-------------------- submitted part of log file ends here, see the rest of log file on client --------------------

Verfasst: **23 Feb 2011, 09:12**

.. ich glaube langsam, dass der neue client-agent die "opsiclientd.conf" für den mount gar nicht verwendet.
im bereich [depot_server] sind alle angaben bis auf "drive" und "username" leer. dennoch scheint der agent zu wissen, welchen pfad er mounten soll (siehe log)

kann es sein, dass er die infos für den mount (ziel, username, pw) vom server jedes mal direkt bekommt (json o.Ä.)? und wenn ja, was muss ich dann auf dem server wo ändern, damit der username stimmt? (wie gesagt, er muss server\pcpatch sein wegen problemen mit der domäne)

wäre toll, nochmal weitere ratschläge zu erhalten. danke.

Verfasst: **23 Feb 2011, 11:32**

Hallo,

ja, die Option "[depot_server] username" scheint in neueren Versionen nicht mehr zu funktionieren.
Ein Fix ist in arbeit...

Gruß,
Jan Schneider

Verfasst: **23 Feb 2011, 13:03**

j.schneider hat geschrieben:ja, die Option "[depot_server] username" scheint in neueren Versionen nicht mehr zu funktionieren.
Ein Fix ist in arbeit...

nja, und woher bekommt der client dann die daten für den mount? die müssen ja dann irgendwo auf dem server stehen?
gibt es bei der neuen version keine möglichkeit den benutzernamen anzupassen?

oder handelt es sich schlichtweg um einen bug (der hoffentlich bald behoben werden kann)?

so, problem gelöst..

es lag an der samba einstellung (security = ads) muss zu "user" umgestellt werden. dann läuft alles prima

forum.opsi.org

keine verbindung nach update von 3.4 auf 4.0

keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0

Re: keine verbindung nach update von 3.4 auf 4.0