bad mountpoint

Antworten
cschmitz
Beiträge: 13
Registriert: 16 Mär 2015, 08:22

bad mountpoint

Beitrag von cschmitz »

Hallo,

wir haben immer wieder das Problem, dass sich ein Client am Opsi zwar meldet (last seen ist aktuell), aber die entsprechenden Updates/Installationen nicht durchführen kann. Die allgemeine Fehlermeldung laut log (s.u.) lautet "Bad mountpoint".

Unser aufwendiger Workaround:
- Einloggen als Admin
- De-Installation des Opsi-Clients inkl. manuellem Löschen von c:\opsi.org
- Neu-Installation des Opsi-Clients von einem Share

Woran liegt der Fehler? Lässt sich der Fehler auch schneller/einfacher beheben?

Anbei das Client-log:

Code: Alles auswählen

(515)     [5] [Mar 25 04:58:03] [ service connection            ] Modules file signature verified (customer: myCompany)   (JSONRPC.pyo|611)
(516)     [6] [Mar 25 04:58:03] [ service connection            ] <JSONRPCBackend(host=u'opsiserver01', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
(517)     [5] [Mar 25 04:58:04] [ service connection            ] Connected to config server 'https://opsiserver01:4447/rpc'   (OpsiService.pyo|355)
(518)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}]    [ 1] product ***:             setup   (EventProcessing.pyo|651)
(519)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}]    [ 2] product firefox-deutsch:     setup   (EventProcessing.pyo|651)
(520)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}]    [ 3] product hwaudit:             setup   (EventProcessing.pyo|651)
(521)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}]    [ 4] product ***-agent:    setup   (EventProcessing.pyo|651)
(522)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}]    [ 5] product swaudit:             setup   (EventProcessing.pyo|651)
(523)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}] Start processing action requests   (EventProcessing.pyo|668)
(524)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}] Selecting depot for products [u' *** ', u'firefox-deutsch', u'hwaudit', u'***-agent', u'swaudit']   (Config.pyo|392)
(525)     [5] [Mar 25 04:58:04] [ event processing gui_startup{installation_pending}] MasterOnly --> 'False'   (Config.pyo|393)
(526)     [6] [Mar 25 04:58:05] [ event processing gui_startup{installation_pending}] Dynamic depot selection disabled   (Config.pyo|449)
(527)     [6] [Mar 25 04:58:05] [ event processing gui_startup{installation_pending}] Master depot for products [u' *** ', u'firefox-deutsch', u'hwaudit', u'***-agent', u'swaudit'] is opsiserver01.mydomain.com   (Config.pyo|473)
(528)     [5] [Mar 25 04:58:05] [ event processing gui_startup{installation_pending}] Selected depot is: <OpsiConfigserver(id=u'opsiserver01.mydomain.com', isMasterDepot=True)>   (Config.pyo|517)
(529)     [6] [Mar 25 04:58:05] [ event processing gui_startup{installation_pending}] Setting config value depot_server.depot_id   (Config.pyo|204)
(530)     [6] [Mar 25 04:58:05] [ event processing gui_startup{installation_pending}] Setting config value depot_server.url   (Config.pyo|204)
(531)     [6] [Mar 25 04:58:05] [ opsiclientd                   ] Searching pids of process name winlogon.exe (session id: 1)   (Windows.pyo|1447)
(532)     [6] [Mar 25 04:58:05] [ opsiclientd                   ] Found process winlogon.exe with matching name (pid 780, session 1)   (Windows.pyo|1470)
(533)     [5] [Mar 25 04:58:05] [ opsiclientd                   ] Executing: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsiclientd_rpc.exe "mypcclient123.mydomain.com" "*** confidential ***" "4441" "setCurrentActiveDesktopName("1", System.getActiveDesktopName())"' in session '1' on desktop 'winsta0\winlogon'   (Windows.pyo|1634)
(534)     [6] [Mar 25 04:58:05] [ opsiclientd                   ] Process startet, pid: 1176   (Windows.pyo|1637)
(535)     [6] [Mar 25 04:58:05] [ opsiclientd                   ] Waiting for process ending: 1176 (timeout: 60 seconds)   (Windows.pyo|1640)
(536)     [6] [Mar 25 04:58:08] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02838DF0> started processing   (Worker.pyo|251)
(537)     [5] [Mar 25 04:58:08] [ control server                ] New session created   (Session.pyo|184)
(538)     [5] [Mar 25 04:58:09] [ control server                ] Authorization request from mypcclient123.mydomain.com@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.28)   (ControlServer.pyo|162)
(539)     [5] [Mar 25 04:58:09] [ opsiclientd                   ] -----> Executing: backend_getInterface()   (JsonRpc.pyo|134)
(540)     [6] [Mar 25 04:58:09] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
(541)     [6] [Mar 25 04:58:11] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x029D1C38> started processing   (Worker.pyo|251)
(542)     [6] [Mar 25 04:58:11] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.28'   (Worker.pyo|397)
(543)     [5] [Mar 25 04:58:11] [ control server                ] Authorization request from mypcclient123.mydomain.com@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.28)   (ControlServer.pyo|162)
(544)     [5] [Mar 25 04:58:11] [ opsiclientd                   ] -----> Executing: setCurrentActiveDesktopName(1, u'Winlogon')   (JsonRpc.pyo|134)
(545)     [5] [Mar 25 04:58:11] [ opsiclientd                   ] rpc setCurrentActiveDesktopName: current active desktop name for session 1 set to 'Winlogon'   (ControlServer.pyo|565)
(546)     [6] [Mar 25 04:58:11] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
(547)     [6] [Mar 25 04:58:13] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x029D39E0> started processing   (Worker.pyo|251)
(548)     [6] [Mar 25 04:58:13] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.28'   (Worker.pyo|397)
(549)     [5] [Mar 25 04:58:13] [ control server                ] Authorization request from mypcclient123.mydomain.com@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.28)   (ControlServer.pyo|162)
(550)     [5] [Mar 25 04:58:13] [ opsiclientd                   ] -----> Executing: backend_exit()   (JsonRpc.pyo|134)
(551)     [6] [Mar 25 04:58:13] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
(552)     [5] [Mar 25 04:58:13] [ opsiclientd                   ] Process 1176 ended with exit code 0   (Windows.pyo|1650)
(553)     [5] [Mar 25 04:58:13] [ event processing gui_startup{installation_pending}] Updating action processor   (EventProcessing.pyo|398)
(554)     [5] [Mar 25 04:58:13] [ event processing gui_startup{installation_pending}] Mounting depot share smb://opsiserver01/opsi_depot   (EventProcessing.pyo|366)
(555)     [6] [Mar 25 04:58:13] [ event processing gui_startup{installation_pending}] Added depot 'opsiserver01' to trusted domains   (EventProcessing.pyo|375)
(556)     [3] [Mar 25 04:58:13] [ event processing gui_startup{installation_pending}] Bad mountpoint ''   (Windows.pyo|714)
(557)     [3] [Mar 25 04:58:13] [ event processing gui_startup{installation_pending}] Failed to update action processor: Bad mountpoint ''   (EventProcessing.pyo|531)
(558)     [5] [Mar 25 04:58:14] [ event processing gui_startup{installation_pending}] Starting action processor in session '1' on desktop 'winlogon'   (EventProcessing.pyo|819)
(559)     [6] [Mar 25 04:58:14] [ event processing gui_startup{installation_pending}] Running command "C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe" "mypcclient123.mydomain.com" "*** confidential ***" "4441" "c:\\opsi.org\\log\\opsiclientd.log" "6" "smb://opsiserver01/opsi_depot" "" "pcpatch" "*** confidential ***" "1" "winlogon" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://opsiserver01:4447/rpc\" /clientid mypcclient123.mydomain.com /username mypcclient123.mydomain.com /password *** confidential *** " 10800 "" "" false in session '1' on desktop 'winlogon'   (EventProcessing.pyo|298)
(560)     [6] [Mar 25 04:58:14] [ event processing gui_startup{installation_pending}] Searching pids of process name winlogon.exe (session id: 1)   (Windows.pyo|1447)
(561)     [6] [Mar 25 04:58:14] [ event processing gui_startup{installation_pending}] Found process winlogon.exe with matching name (pid 780, session 1)   (Windows.pyo|1470)
(562)     [5] [Mar 25 04:58:14] [ event processing gui_startup{installation_pending}] Executing: '"C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe" "mypcclient123.mydomain.com" "*** confidential ***" "4441" "c:\\opsi.org\\log\\opsiclientd.log" "6" "smb://opsiserver01/opsi_depot" "" "pcpatch" "*** confidential ***" "1" "winlogon" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://opsiserver01:4447/rpc\" /clientid mypcclient123.mydomain.com /username mypcclient123.mydomain.com /password *** confidential *** " 10800 "" "" false' in session '1' on desktop 'winsta0\winlogon'   (Windows.pyo|1634)
(563)     [6] [Mar 25 04:58:14] [ event processing gui_startup{installation_pending}] Process startet, pid: 3972   (Windows.pyo|1637)
(564)     [6] [Mar 25 04:58:14] [ event processing gui_startup{installation_pending}] Waiting for process ending: 3972 (timeout: 0 seconds)   (Windows.pyo|1640)
(565)     [3] [Mar 25 04:58:14] [ action_processor_starter.exe  ] Failed to read version info from file u'/etc/opsi/version': [Errno 2] No such file or directory: u'/etc/opsi/version'   (Backend.pyo|206)
(566)     [6] [Mar 25 04:58:16] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x029D3DF0> started processing   (Worker.pyo|251)
(567)     [5] [Mar 25 04:58:16] [ control server                ] New session created   (Session.pyo|184)
(568)     [5] [Mar 25 04:58:16] [ control server                ] Authorization request from mypcclient123.mydomain.com@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.28)   (ControlServer.pyo|162)
(569)     [5] [Mar 25 04:58:16] [ opsiclientd                   ] -----> Executing: backend_getInterface()   (JsonRpc.pyo|134)
(570)     [6] [Mar 25 04:58:16] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
(571)     [6] [Mar 25 04:58:16] [ action_processor_starter.exe  ] <JSONRPCBackend(host=u'localhost', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
(572)     [6] [Mar 25 04:58:16] [ action_processor_starter.exe  ] Impersonating network account 'pcpatch'   (action_processor_starter.py|98)
(573)     [5] [Mar 25 04:58:16] [ action_processor_starter.exe  ] Mounting depot share smb://opsiserver01/opsi_depot   (action_processor_starter.py|103)
(574)     [6] [Mar 25 04:58:18] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02A0B6E8> started processing   (Worker.pyo|251)
(575)     [6] [Mar 25 04:58:18] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.28'   (Worker.pyo|397)
(576)     [5] [Mar 25 04:58:18] [ control server                ] Authorization request from mypcclient123.mydomain.com@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.28)   (ControlServer.pyo|162)
(577)     [5] [Mar 25 04:58:18] [ opsiclientd                   ] -----> Executing: setStatusMessage(u'1', u'Verbinde mit Depot-Freigabe smb://opsiserver01/opsi_depot')   (JsonRpc.pyo|134)
(578)     [5] [Mar 25 04:58:18] [ opsiclientd                   ] DEBUG: [<EventProcessingThread(Thread-16, started daemon 5240)>]    (Opsiclientd.pyo|431)
(579)     [5] [Mar 25 04:58:18] [ opsiclientd                   ] DEBUG: 1    (Opsiclientd.pyo|433)
(580)     [5] [Mar 25 04:58:18] [ opsiclientd                   ] rpc setStatusMessage: Setting status message to 'Verbinde mit Depot-Freigabe smb://opsiserver01/opsi_depot'   (ControlServer.pyo|541)
(581)     [6] [Mar 25 04:58:18] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
(582)     [3] [Mar 25 04:58:18] [ action_processor_starter.exe  ] Bad mountpoint ''   (Windows.pyo|714)
(583)     [2] [Mar 25 04:58:18] [ action_processor_starter.exe  ] Traceback:   (Logger.pyo|757)
(584)     [2] [Mar 25 04:58:18] [ action_processor_starter.exe  ]   File "action_processor_starter.py", line 109, in <module>
(585)        (Logger.pyo|757)
(586)     [2] [Mar 25 04:58:18] [ action_processor_starter.exe  ]   File "OPSI\System\Windows.pyo", line 715, in mount
(587)        (Logger.pyo|757)
(588)     [2] [Mar 25 04:58:18] [ action_processor_starter.exe  ]      ==>>> Bad mountpoint ''   (action_processor_starter.py|121)
(589)     [6] [Mar 25 04:58:20] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02A0B9E0> started processing   (Worker.pyo|251)
(590)     [6] [Mar 25 04:58:21] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.28'   (Worker.pyo|397)
(591)     [5] [Mar 25 04:58:21] [ control server                ] Authorization request from mypcclient123.mydomain.com@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.28)   (ControlServer.pyo|162)
(592)     [5] [Mar 25 04:58:21] [ opsiclientd                   ] -----> Executing: setStatusMessage(u'1', u"Failed to process action requests: Bad mountpoint ''")   (JsonRpc.pyo|134)
(593)     [5] [Mar 25 04:58:21] [ opsiclientd                   ] DEBUG: [<EventProcessingThread(Thread-16, started daemon 5240)>]    (Opsiclientd.pyo|431)
(594)     [5] [Mar 25 04:58:21] [ opsiclientd                   ] DEBUG: 1    (Opsiclientd.pyo|433)
(595)     [5] [Mar 25 04:58:21] [ opsiclientd                   ] rpc setStatusMessage: Setting status message to 'Failed to process action requests: Bad mountpoint '''   (ControlServer.pyo|541)
(596)     [6] [Mar 25 04:58:21] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
(597)     [3] [Mar 25 04:58:21] [ action_processor_starter.exe  ] Failed to process action requests: Bad mountpoint ''   (action_processor_starter.py|128)
(598)     [6] [Mar 25 04:58:23] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02A0BE18> started processing   (Worker.pyo|251)
(599)     [6] [Mar 25 04:58:23] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.28'   (Worker.pyo|397)
(600)     [5] [Mar 25 04:58:23] [ control server                ] Authorization request from mypcclient123.mydomain.com@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.28)   (ControlServer.pyo|162)
(601)     [5] [Mar 25 04:58:23] [ opsiclientd                   ] -----> Executing: backend_exit()   (JsonRpc.pyo|134)
(602)     [6] [Mar 25 04:58:23] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
(603)     [5] [Mar 25 04:58:23] [ event processing gui_startup{installation_pending}] Process 3972 ended with exit code 0   (Windows.pyo|1650)
(604)     [6] [Mar 25 04:58:23] [ event processing gui_startup{installation_pending}] Session id set to 1   (EventProcessing.pyo|173)
(605)     [5] [Mar 25 04:58:26] [ event processing gui_startup{installation_pending}] Writing log to service   (EventProcessing.pyo|257)
LG cschmitz
Benutzeravatar
j.schneider
uib-Team
Beiträge: 2045
Registriert: 29 Mai 2008, 15:14

Re: bad mountpoint

Beitrag von j.schneider »

Hallo,

könnte etwas mit der Konfiguration "clientconfig.depot.drive" zu tun haben.
Bitte mal bei den Host-Parametern schauen.


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


cschmitz
Beiträge: 13
Registriert: 16 Mär 2015, 08:22

Re: bad mountpoint

Beitrag von cschmitz »

Unter clientconfig.depot.drive ist, wie bei allen anderen Clients, der default "p:" eingestellt.
Benutzeravatar
j.schneider
uib-Team
Beiträge: 2045
Registriert: 29 Mai 2008, 15:14

Re: bad mountpoint

Beitrag von j.schneider »

Welche opsi-client-agent-Version ist im Einsatz?


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


cschmitz
Beiträge: 13
Registriert: 16 Mär 2015, 08:22

Re: bad mountpoint

Beitrag von cschmitz »

4.0.7.23-5
Benutzeravatar
j.schneider
uib-Team
Beiträge: 2045
Registriert: 29 Mai 2008, 15:14

Re: bad mountpoint

Beitrag von j.schneider »

Dann würde ich dringend eine Migration auf opsi 4.2 empfehlen.


Vielen Dank für die Nutzung von opsi. Im Forum ist unser Support begrenzt.

Für den professionellen Einsatz und individuelle Beratung empfehlen wir einen Support-Vertrag und eine Schulung.
Gerne informieren wir Sie zu unserem Angebot.

uib GmbH
Telefon: +49 6131 27561 0
E-Mail: sales@uib.de


Jan.Schmidt
Beiträge: 439
Registriert: 08 Jul 2017, 12:02

Re: bad mountpoint

Beitrag von Jan.Schmidt »

j.schneider hat geschrieben: 29 Mär 2022, 10:36 Dann würde ich dringend eine Migration auf opsi 4.2 empfehlen.
.... und wenn du das WAN Modul einsetzt - besorg dir vorher eine (die letzte) 4.1.er Version - die muss auf den WAN clients drauf sein, wenn die über das WAN Modul die 4.2er Version kriegen sollen.
Benutzeravatar
SisterOfMercy
Beiträge: 1556
Registriert: 22 Jun 2012, 19:18

Re: bad mountpoint

Beitrag von SisterOfMercy »

j.schneider hat geschrieben: 29 Mär 2022, 10:36 Dann würde ich dringend eine Migration auf opsi 4.2 empfehlen.
Yes, but via 4.1, right?
Bitte schreiben Sie Deutsch, when I'm responding in the German-speaking part of the forum!
cschmitz
Beiträge: 13
Registriert: 16 Mär 2015, 08:22

Re: bad mountpoint

Beitrag von cschmitz »

j.schneider hat geschrieben: 29 Mär 2022, 10:36 Dann würde ich dringend eine Migration auf opsi 4.2 empfehlen.
Eine Migration auf 4.2 bedeutet bei bis zu 644 Clients einen hohen Aufwand und diverse andere Probleme, die auftreten können. Wir hatten einstig auch diverse Pfade auf unserem Server umgestellt, um dies auf unsere Umgebung anzupassen. Des Weiteren werden in der neuen Version auch diverse Funktionen umgestellt bzw. anders umgesetzt. Dies führt unter Umständen ebenfalls zu erheblichen Störungen in unserem Ablauf. Das gesamte Testing würde einige Tage in Anspruch nehmen. Eine Migration nur wegen 2-3 kaputten Cients durchzuführen, halte ich jetzt für vermessen. Gibt es nicht eine andere Lösung?

Ist in opsi 4.2. der entsprechende Fehler überhaupt behoben?
Funktioniert ein opsi 4.2 Client mit einer Server Version von 4.1.1.101
Jan.Schmidt
Beiträge: 439
Registriert: 08 Jul 2017, 12:02

Re: bad mountpoint

Beitrag von Jan.Schmidt »

Salve,
jeder ist seines glückes Schmied.

Wegen 2-3 Maschinen eine Software von "wird nicht mehr weiter entwickelt und macht demnächst immer mehr Proleme" auf "wird aktuell weiter gepflegt und ist damit auch zukunftssicher" umzuheben würde ich auch ncht machen.

Viel Spass noch
:oops:
Antworten