BSOD rdbss.sys RDR_FILE_SYSTEM

Antworten
brainy84
Beiträge: 164
Registriert: 24 Mär 2011, 22:58

BSOD rdbss.sys RDR_FILE_SYSTEM

Beitrag von brainy84 »

Hallo zusammen,

wir nutzen seit der Corona-Krise unser OpenVPN in Zusammenhang mit opsi,wie so viele wahrscheinlich, verstärkt. Wir haben Windows 10 1903 und 1909 Clients. Diese greifen über ein dediziert geroutetes Netzwerk auf die Unternehmensumgebung zu, Es werden die aktuellen opsi-Versionen verwendet.

Bei Updates über das VPN bekomme ich ein BSOD (siehe oben). Dabei wird meistens (nicht immer) Libreoffice aktualisiert, manchmal aber auch KeePass oder andere Software. Der BSOD tritt nur in der VPN-Umgebung in Verbindung mit opsi auf. Vor Ort im Unternehmensnetzwerk funktionieren die Updates tadellos. Hat vielleicht jemand Erfahrung mit diesem Verhalten oder eine ähnliche Konstellation, bei der diese Verhalten nicht vorhanden ist.

Anbei das opsiclientd-Log des Rechners (die failed sections, da ansonsten zu groß):

Code: Alles auswählen

[Jul 09 14:49:44] [ event processing software_on_demand{user_logged_in}] Mounting '\\tclanopsi02\opsi_depot' to 'p:'   (Windows.pyo|775)
[5] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Updating action processor from depot dir 'p:\opsi-winst\\files\\opsi-winst'   (EventProcessing.pyo|447)
[5] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Local action processor exists and seems to be up to date   (EventProcessing.pyo|458)
[5] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Unmounting depot share   (EventProcessing.pyo|393)
[5] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Starting action processor in session '1' on desktop 'default'   (EventProcessing.pyo|821)
[6] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Running command "C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe" "client1.intern.example.de" "*** confidential ***" "4441" "c:\\opsi.org\\log\\opsiclientd.log" "6" "smb://tclanopsi02/opsi_depot" "p:" "pcpatch" "*** confidential ***" "1" "default" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://opsi.intern.example.de:4447\" /clientid client1.intern.example.de /username client1.intern.example.de /password *** confidential *** " 10800 "" "" false in session '1' on desktop 'default'   (EventProcessing.pyo|300)
[6] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Searching pids of process name winlogon.exe (session id: 1)   (Windows.pyo|1447)
[6] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Found process winlogon.exe with matching name (pid 1332, session 1)   (Windows.pyo|1470)
[5] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Executing: '"C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe" "client1.intern.example.de" "*** confidential ***" "4441" "c:\\opsi.org\\log\\opsiclientd.log" "6" "smb://tclanopsi02/opsi_depot" "p:" "pcpatch" "*** confidential ***" "1" "default" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://opsi.intern.example.de:4447\" /clientid client1.intern.example.de /username client1.intern.example.de /password *** confidential *** " 10800 "" "" false' in session '1' on desktop 'winsta0\default'   (Windows.pyo|1634)
[6] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Process startet, pid: 12532   (Windows.pyo|1637)
[6] [Jul 09 14:49:45] [ event processing software_on_demand{user_logged_in}] Waiting for process ending: 12532 (timeout: 0 seconds)   (Windows.pyo|1640)
[3] [Jul 09 14:49:46] [ 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)
[6] [Jul 09 14:49:48] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02C264E0> started processing   (Worker.pyo|251)
[5] [Jul 09 14:49:48] [ control server                ] New session created   (Session.pyo|184)
[5] [Jul 09 14:49:48] [ control server                ] Authorization request from client1.intern.example.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.62)   (ControlServer.pyo|164)
[5] [Jul 09 14:49:48] [ opsiclientd                   ] -----> Executing: backend_getInterface()   (JsonRpc.pyo|134)
[6] [Jul 09 14:49:48] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[6] [Jul 09 14:49:48] [ action_processor_starter.exe  ] <JSONRPCBackend(host=u'localhost', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[6] [Jul 09 14:49:48] [ action_processor_starter.exe  ] Impersonating network account 'pcpatch'   (action_processor_starter.py|102)
[5] [Jul 09 14:49:48] [ action_processor_starter.exe  ] Mounting depot share smb://tclanopsi02/opsi_depot   (action_processor_starter.py|107)
[6] [Jul 09 14:49:50] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02D4AA80> started processing   (Worker.pyo|251)
[6] [Jul 09 14:49:50] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62'   (Worker.pyo|397)
[5] [Jul 09 14:49:50] [ control server                ] Authorization request from client1.intern.example.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.62)   (ControlServer.pyo|164)
[5] [Jul 09 14:49:50] [ opsiclientd                   ] -----> Executing: setStatusMessage(u'1', u'Verbinde mit Depot-Freigabe smb://tclanopsi02/opsi_depot')   (JsonRpc.pyo|134)
[5] [Jul 09 14:49:50] [ opsiclientd                   ] DEBUG: [<EventProcessingThread(Thread-45, started daemon 13664)>]    (Opsiclientd.pyo|431)
[5] [Jul 09 14:49:50] [ opsiclientd                   ] DEBUG: 1    (Opsiclientd.pyo|433)
[5] [Jul 09 14:49:50] [ opsiclientd                   ] rpc setStatusMessage: Setting status message to 'Verbinde mit Depot-Freigabe smb://exampleopsi02/opsi_depot'   (ControlServer.pyo|557)
[6] [Jul 09 14:49:50] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[5] [Jul 09 14:49:50] [ action_processor_starter.exe  ] Mounting '\\exampleopsi02\opsi_depot' to 'p:'   (Windows.pyo|775)
[5] [Jul 09 14:49:51] [ action_processor_starter.exe  ] Starting action processor   (action_processor_starter.py|116)
[6] [Jul 09 14:49:53] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02D4AA58> started processing   (Worker.pyo|251)
[6] [Jul 09 14:49:53] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62'   (Worker.pyo|397)
[5] [Jul 09 14:49:53] [ control server                ] Authorization request from client1.intern.example.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.62)   (ControlServer.pyo|164)
[5] [Jul 09 14:49:53] [ opsiclientd                   ] -----> Executing: setStatusMessage(u'1', u'Action processor l\xe4uft')   (JsonRpc.pyo|134)
[5] [Jul 09 14:49:53] [ opsiclientd                   ] DEBUG: [<EventProcessingThread(Thread-45, started daemon 13664)>]    (Opsiclientd.pyo|431)
[5] [Jul 09 14:49:53] [ opsiclientd                   ] DEBUG: 1    (Opsiclientd.pyo|433)
[5] [Jul 09 14:49:53] [ opsiclientd                   ] rpc setStatusMessage: Setting status message to 'Action processor läuft'   (ControlServer.pyo|557)
[6] [Jul 09 14:49:53] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)


6] [Jul 09 14:32:10] [ opsiclientd                   ]   File "httplib.pyo", line 1109, in _send_request
   (Logger.pyo|757)
[6] [Jul 09 14:32:10] [ opsiclientd                   ]   File "httplib.pyo", line 1065, in endheaders
   (Logger.pyo|757)
[6] [Jul 09 14:32:10] [ opsiclientd                   ]   File "httplib.pyo", line 892, in _send_output
   (Logger.pyo|757)
[6] [Jul 09 14:32:10] [ opsiclientd                   ]   File "httplib.pyo", line 854, in send
   (Logger.pyo|757)
[6] [Jul 09 14:32:10] [ opsiclientd                   ]   File "httplib.pyo", line 1282, in connect
   (Logger.pyo|757)
[6] [Jul 09 14:32:10] [ opsiclientd                   ]   File "httplib.pyo", line 831, in connect
   (Logger.pyo|757)
[6] [Jul 09 14:32:10] [ opsiclientd                   ]   File "socket.pyo", line 557, in create_connection
   (Logger.pyo|757)
[6] [Jul 09 14:32:10] [ opsiclientd                   ]      ==>>> Failed to process method 'backend_getInterface': [Errno 11001] getaddrinfo failed   (JSONRPC.pyo|125)
[3] [Jul 09 14:32:10] [ service connection            ] Failed to connect to config server 'https://opsi.intern.example.de:4447': [Errno 11001] getaddrinfo failed   (OpsiService.pyo|366)
[5] [Jul 09 14:32:13] [ service connection            ] Connecting to config server 'https://opsi.intern.example.de:4447' #2   (OpsiService.pyo|326)
[3] [Jul 09 14:32:13] [ service connection            ] 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)
[4] [Jul 09 14:32:18] [ opsiclientd                   ] Connecting to u'opsi.intern.example.de' did not succeed after retrying.   (HTTP.pyo|601)
[6] [Jul 09 14:32:18] [ opsiclientd                   ] Traceback:   (Logger.pyo|757)
[6] [Jul 09 14:32:18] [ opsiclientd                   ]   File "OPSI\Backend\JSONRPC.pyo", line 121, in process
   (Logger.pyo|757)
[6] [Jul 09 14:32:18] [ opsiclientd                   ]   File "OPSI\Backend\JSONRPC.pyo", line 714, in _request
   (Logger.pyo|757)
[6] [Jul 09 14:32:18] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:18] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 598, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "OPSI\Util\HTTP.pyo", line 529, in urlopen
   (Logger.pyo|757)
[6] [Jul 09 14:32:19] [ opsiclientd                   ]   File "httplib.pyo", line 1069, in request
   (Logger.pyo|757)

[6] [Jul 09 14:49:29] [ event processing software_on_demand{user_logged_in}] Running command C:\Program Files (x86)\opsi.org\opsi-client-agent\\notifier.exe -p 44003 -i event -s notifier\\event.ini in session '1' on desktop 'default'   (EventProcessing.pyo|300)
[6] [Jul 09 14:49:29] [ event processing software_on_demand{user_logged_in}] Searching pids of process name winlogon.exe (session id: 1)   (Windows.pyo|1447)
[6] [Jul 09 14:49:29] [ event processing software_on_demand{user_logged_in}] Found process winlogon.exe with matching name (pid 1332, session 1)   (Windows.pyo|1470)
[5] [Jul 09 14:49:29] [ event processing software_on_demand{user_logged_in}] Executing: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\\notifier.exe -p 44003 -i event -s notifier\\event.ini' in session '1' on desktop 'winsta0\default'   (Windows.pyo|1634)
[6] [Jul 09 14:49:29] [ event processing software_on_demand{user_logged_in}] Process startet, pid: 14544   (Windows.pyo|1637)
[6] [Jul 09 14:49:29] [ event processing software_on_demand{user_logged_in}] Session id set to 1   (EventProcessing.pyo|175)
[6] [Jul 09 14:49:32] [ event processing software_on_demand{user_logged_in}] User is allowed to cancel connection after 1 seconds   (EventProcessing.pyo|133)
[6] [Jul 09 14:49:32] [ event processing software_on_demand{user_logged_in}] Starting ServiceConnectionThread, timeout is 10 seconds   (OpsiService.pyo|164)
[5] [Jul 09 14:49:32] [ service connection            ] Connecting to config server 'https://opsi.intern.example.de:4447' #1   (OpsiService.pyo|326)
[3] [Jul 09 14:49:32] [ service connection            ] 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)
[6] [Jul 09 14:49:34] [ opsiclientd                   ] client connection made   (Message.pyo|443)
[6] [Jul 09 14:49:34] [ service connection            ] Verifying modules file signature   (JSONRPC.pyo|586)
[5] [Jul 09 14:49:34] [ service connection            ] Modules file signature verified (customer: example GmbH)   (JSONRPC.pyo|611)
[6] [Jul 09 14:49:34] [ service connection            ] <JSONRPCBackend(host=u'opsi.intern.example.de', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[5] [Jul 09 14:49:35] [ service connection            ] Connected to config server 'https://opsi.intern.example.de:4447'   (OpsiService.pyo|355)
[5] [Jul 09 14:49:35] [ event processing software_on_demand{user_logged_in}] Trying to read config from file: 'C:\Program Files (x86)\opsi.org\opsi-client-agent\opsiclientd\opsiclientd.conf'   (Config.pyo|287)
[6] [Jul 09 14:49:35] [ event processing software_on_demand{user_logged_in}] Setting config value global.log_file   (Config.pyo|204)
[6] [Jul 09 14:49:35] [ event processing software_on_demand{user_logged_in}] Setting config value global.log_level   (Config.pyo|204)
Ich hoffe, ich konnte das Thema einigermaßen rüberbringen.

Grüße

brainy84
Nach oben
Benutzeravatar
SisterOfMercy
Beiträge: 1523
Registriert: 22 Jun 2012, 19:18

Re: BSOD rdbss.sys RDR_FILE_SYSTEM

Beitrag von SisterOfMercy »

No problems here with OpenVPN. My home users never bring their computer here. ;)

https://docs.microsoft.com/en-us/window ... ile-system
"One possible cause of this bug check is depletion of nonpaged pool memory. If the nonpaged pool memory is completely depleted, this error can stop the system. However, during the indexing process, if the amount of available nonpaged pool memory is very low, another kernel-mode driver requiring nonpaged pool memory can also trigger this error."

Have you ran memtest on the clients, and I'm not sure if they are talking about the windows search indexing, otherwise disable that service.

Code: Alles auswählen

[WinBatch_indexing]
"%SystemRoot%\system32\sc.exe" config WSearch start= disabled
"%SystemRoot%\system32\net.exe" stop WSearch
If you can reproduce the issue, try getting a memory dump. Then use this to check it out: https://www.nirsoft.net/utils/blue_screen_view.html
Bitte schreiben Sie Deutsch, when I'm responding in the German-speaking part of the forum!
Nach oben
Jan.Schmidt
Beiträge: 439
Registriert: 08 Jul 2017, 12:02

Re: BSOD rdbss.sys RDR_FILE_SYSTEM

Beitrag von Jan.Schmidt »

brainy84 hat geschrieben: Anbei das opsiclientd-Log des Rechners (die failed sections, da ansonsten zu groß):

Code: Alles auswählen

[Jul 09 14:49:44] [ event processing software_on_demand{user_logged_in}] Mounting '\\tclanopsi02\opsi_depot' to 'p:'   (Windows.pyo|775)

Code: Alles auswählen

"client1.intern.example.de" "*** confidential ***" "4441" "c:\\opsi.org
Ich hoffe, ich konnte das Thema einigermaßen rüberbringen.

Grüße

brainy84
ist das "echt" oder anonymisiert???
* tclanopsi02 ohne fqdn
* intern.example.de
Nach oben
brainy84
Beiträge: 164
Registriert: 24 Mär 2011, 22:58

Re: BSOD rdbss.sys RDR_FILE_SYSTEM

Beitrag von brainy84 »

anonymisiert ersetze tclanopsi02 durch example.

Grüße

brainy84
Nach oben
brainy84
Beiträge: 164
Registriert: 24 Mär 2011, 22:58

Re: BSOD rdbss.sys RDR_FILE_SYSTEM

Beitrag von brainy84 »

Hi,

Wsearch didn't fix it. I try the bluescreen software next time.

thanks for the hint.

kind regards brainy84
Nach oben
Antworten

Zurück zu „Freier Support“