windows10-upgrade - 1803 nach 1903 bleibt stecken.

Antworten
g.burck
Beiträge: 199
Registriert: 23 Mai 2018, 16:44

windows10-upgrade - 1803 nach 1903 bleibt stecken.

Beitrag von g.burck »

Moin,

Beim Versuch von 1803 auf 1903 zu aktualisieren hängt der PC ewig im Preparing.
Files_copy_event_starter finished ist die letzte Meldung die ausgegeben wird.

Einen aktuellen log eintrag im configed sehe ich auch nicht.

Ich habe es sowohl mit einem vorhandenen Rechner mit 1803 wie auch mit einer frisch aufgesetzten VM versucht.
Ein Upgrade von 1809 zu 1903 läuft (fast) sauber durch.

Grüße

Gregor
opsi config editor Version 4.1.9.8.5 (2021/04/12)

opsiconfd 4.2.0.286
g.burck
Beiträge: 199
Registriert: 23 Mai 2018, 16:44

Re: windows10-upgrade - 1803 nach 1903 bleibt stecken.

Beitrag von g.burck »

Mal noch einen Nachtrag:

Die letzten Einträge aus dem lokalem log file:

Code: Alles auswählen

[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Updating action processor   (EventProcessing.pyo|398)
[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Mounting depot share smb://10.0.1.24/opsi_depot   (EventProcessing.pyo|366)
[6] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Added depot '10.0.1.24' to trusted domains   (EventProcessing.pyo|375)
[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Mounting '\\10.0.1.24\opsi_depot' to 'p:'   (Windows.pyo|775)
[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Updating action processor from depot dir 'p:\opsi-winst\\files\\opsi-winst'   (EventProcessing.pyo|445)
[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Local action processor exists and seems to be up to date   (EventProcessing.pyo|456)
[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Unmounting depot share   (EventProcessing.pyo|391)
[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Starting action processor in session '1' on desktop 'default'   (EventProcessing.pyo|819)
[6] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Running command "C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe" "ph-w1803to1903.peiker-holding.de" "*** confidential ***" "4441" "c:\\opsi.org\\log\\opsiclientd.log" "6" "smb://10.0.1.24/opsi_depot" "p:" "pcpatch" "*** confidential ***" "1" "default" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://ph-opsi.peiker-holding.de:4447/rpc\" /clientid ph-w1803to1903.peiker-holding.de /username ph-w1803to1903.peiker-holding.de /password *** confidential *** " 10800 "" "" false in session '1' on desktop 'default'   (EventProcessing.pyo|298)
[6] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Searching pids of process name winlogon.exe (session id: 1)   (Windows.pyo|1447)
[6] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Found process winlogon.exe with matching name (pid 524, session 1)   (Windows.pyo|1470)
[5] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Executing: '"C:\Program Files (x86)\opsi.org\opsi-client-agent\action_processor_starter.exe" "ph-w1803to1903.peiker-holding.de" "*** confidential ***" "4441" "c:\\opsi.org\\log\\opsiclientd.log" "6" "smb://10.0.1.24/opsi_depot" "p:" "pcpatch" "*** confidential ***" "1" "default" "\"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe\" /opsiservice \"https://ph-opsi.peiker-holding.de:4447/rpc\" /clientid ph-w1803to1903.peiker-holding.de /username ph-w1803to1903.peiker-holding.de /password *** confidential *** " 10800 "" "" false' in session '1' on desktop 'winsta0\default'   (Windows.pyo|1634)
[6] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Process startet, pid: 6948   (Windows.pyo|1637)
[6] [Jul 25 13:58:29] [ event processing on_demand{user_logged_in}] Waiting for process ending: 6948 (timeout: 0 seconds)   (Windows.pyo|1640)
[3] [Jul 25 13:58:30] [ 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 25 13:58:31] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02B694B8> started processing   (Worker.pyo|251)
[5] [Jul 25 13:58:31] [ control server                ] New session created   (Session.pyo|184)
[5] [Jul 25 13:58:31] [ control server                ] Authorization request from ph-w1803to1903.peiker-holding.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.62)   (ControlServer.pyo|161)
[5] [Jul 25 13:58:31] [ opsiclientd                   ] -----> Executing: backend_getInterface()   (JsonRpc.pyo|134)
[6] [Jul 25 13:58:31] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[6] [Jul 25 13:58:31] [ action_processor_starter.exe  ] <JSONRPCBackend(host=u'localhost', deflate=False)>: Connected to service   (JSONRPC.pyo|497)
[6] [Jul 25 13:58:31] [ action_processor_starter.exe  ] Impersonating network account 'pcpatch'   (action_processor_starter.py|98)
[5] [Jul 25 13:58:31] [ action_processor_starter.exe  ] Mounting depot share smb://10.0.1.24/opsi_depot   (action_processor_starter.py|103)
[6] [Jul 25 13:58:32] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02B69300> started processing   (Worker.pyo|251)
[6] [Jul 25 13:58:32] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62'   (Worker.pyo|397)
[5] [Jul 25 13:58:32] [ control server                ] Authorization request from ph-w1803to1903.peiker-holding.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.62)   (ControlServer.pyo|161)
[5] [Jul 25 13:58:32] [ opsiclientd                   ] -----> Executing: setStatusMessage(u'1', u'Verbinde mit Depot-Freigabe smb://10.0.1.24/opsi_depot')   (JsonRpc.pyo|134)
[5] [Jul 25 13:58:32] [ opsiclientd                   ] DEBUG: [<EventProcessingThread(Thread-92, started daemon 4040)>]    (Opsiclientd.pyo|431)
[5] [Jul 25 13:58:32] [ opsiclientd                   ] DEBUG: 1    (Opsiclientd.pyo|433)
[5] [Jul 25 13:58:32] [ opsiclientd                   ] rpc setStatusMessage: Setting status message to 'Verbinde mit Depot-Freigabe smb://10.0.1.24/opsi_depot'   (ControlServer.pyo|506)
[6] [Jul 25 13:58:32] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[5] [Jul 25 13:58:32] [ action_processor_starter.exe  ] Mounting '\\10.0.1.24\opsi_depot' to 'p:'   (Windows.pyo|775)
[5] [Jul 25 13:58:32] [ action_processor_starter.exe  ] Starting action processor   (action_processor_starter.py|112)
[6] [Jul 25 13:58:33] [ control server                ] Worker <ocdlib.ControlServer.WorkerOpsiclientdJsonRpc instance at 0x02B69C10> started processing   (Worker.pyo|251)
[6] [Jul 25 13:58:33] [ control server                ] Reusing session for client '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62'   (Worker.pyo|397)
[5] [Jul 25 13:58:33] [ control server                ] Authorization request from ph-w1803to1903.peiker-holding.de@127.0.0.1 (application: opsi jsonrpc module version 4.0.7.62)   (ControlServer.pyo|161)
[5] [Jul 25 13:58:33] [ opsiclientd                   ] -----> Executing: setStatusMessage(u'1', u'Action processor l\xe4uft')   (JsonRpc.pyo|134)
[5] [Jul 25 13:58:33] [ opsiclientd                   ] DEBUG: [<EventProcessingThread(Thread-92, started daemon 4040)>]    (Opsiclientd.pyo|431)
[5] [Jul 25 13:58:33] [ opsiclientd                   ] DEBUG: 1    (Opsiclientd.pyo|433)
[5] [Jul 25 13:58:33] [ opsiclientd                   ] rpc setStatusMessage: Setting status message to 'Action processor läuft'   (ControlServer.pyo|506)
[6] [Jul 25 13:58:33] [ opsiclientd                   ] Got result   (JsonRpc.pyo|142)
[5] [Jul 25 13:58:33] [ action_processor_starter.exe  ] Running command '"C:\Program Files (x86)\opsi.org\opsi-client-agent\\opsi-winst\\winst32.exe" /opsiservice "https://ph-opsi.peiker-holding.de:4447/rpc" /clientid ph-w1803to1903.peiker-holding.de /username ph-w1803to1903.peiker-holding.de /password *** confidential *** ' as user 'pcpatch' on desktop 'default'   (Windows.pyo|1928)
[6] [Jul 25 13:58:33] [ action_processor_starter.exe  ] Process startet, pid: 2348   (Windows.pyo|1931)
[6] [Jul 25 13:58:33] [ action_processor_starter.exe  ] Waiting for process ending: 2348 (timeout: 10800 seconds)   (Windows.pyo|1934)
[5] [Jul 25 13:58:40] [ control pipe                  ] Session 'MiYkYF0DHGRkAug42hBXCKO2fBVb2CJ9' from ip '10.0.1.24', application 'opsi-RpcThread/4.1.1.65' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 13:58:40] [ control pipe                  ] Session timer <_Timer(Thread-52, started daemon 5832)> canceled   (Session.pyo|128)
[5] [Jul 25 13:58:40] [ control pipe                  ] Session 'MiYkYF0DHGRkAug42hBXCKO2fBVb2CJ9' from ip '10.0.1.24', application 'opsi-RpcThread/4.1.1.65' deleted   (Session.pyo|225)
[5] [Jul 25 13:58:44] [ opsiclientd                   ] Session 'Jh0EGGRc0U2hwTUC9OwJxe59W7yKItpv' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 13:58:44] [ opsiclientd                   ] Session timer <_Timer(Thread-59, started daemon 6164)> canceled   (Session.pyo|128)
[5] [Jul 25 13:58:44] [ opsiclientd                   ] Session 'Jh0EGGRc0U2hwTUC9OwJxe59W7yKItpv' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' deleted   (Session.pyo|225)
[5] [Jul 25 13:58:55] [ opsiclientd                   ] Session 'tShzkBEssxnZur0gostorQCtg9feBPWR' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 13:58:55] [ opsiclientd                   ] Session timer <_Timer(Thread-75, started daemon 6516)> canceled   (Session.pyo|128)
[5] [Jul 25 13:58:55] [ opsiclientd                   ] Session 'tShzkBEssxnZur0gostorQCtg9feBPWR' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' deleted   (Session.pyo|225)
[5] [Jul 25 13:59:20] [ opsiclientd                   ] Session 'At7WhyUOJv17m0LOB1BcGdc5haLZ5hj7' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 13:59:20] [ opsiclientd                   ] Session timer <_Timer(Thread-83, started daemon 6076)> canceled   (Session.pyo|128)
[5] [Jul 25 13:59:20] [ opsiclientd                   ] Session 'At7WhyUOJv17m0LOB1BcGdc5haLZ5hj7' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' deleted   (Session.pyo|225)
[5] [Jul 25 14:00:14] [ opsiclientd                   ] Session 'x9fy4rb345rgfOdZH97x0NY6kztQ4ZN2' from ip '10.0.1.24', application 'opsi-RpcThread/4.1.1.65' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 14:00:14] [ opsiclientd                   ] Session timer <_Timer(Thread-90, started daemon 5724)> canceled   (Session.pyo|128)
[5] [Jul 25 14:00:14] [ opsiclientd                   ] Session 'x9fy4rb345rgfOdZH97x0NY6kztQ4ZN2' from ip '10.0.1.24', application 'opsi-RpcThread/4.1.1.65' deleted   (Session.pyo|225)
[5] [Jul 25 14:00:18] [ opsiclientd                   ] Session 'ivshJCy36BdKvJijnTiOPYG9mHQFfkES' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 14:00:18] [ opsiclientd                   ] Session timer <_Timer(Thread-97, started daemon 6732)> canceled   (Session.pyo|128)
[5] [Jul 25 14:00:18] [ opsiclientd                   ] Session 'ivshJCy36BdKvJijnTiOPYG9mHQFfkES' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' deleted   (Session.pyo|225)
[5] [Jul 25 14:00:29] [ opsiclientd                   ] Session 'pJ6hWuICoych4F2hP0RzVqVGHlHSA5ew' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 14:00:29] [ opsiclientd                   ] Session timer <_Timer(Thread-113, started daemon 6860)> canceled   (Session.pyo|128)
[5] [Jul 25 14:00:29] [ opsiclientd                   ] Session 'pJ6hWuICoych4F2hP0RzVqVGHlHSA5ew' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' deleted   (Session.pyo|225)
[5] [Jul 25 14:00:33] [ opsiclientd                   ] Session 'j9wzakC8Vbgl6bfxvAzmxm9MWr21OI04' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' expired after 120 seconds   (Session.pyo|190)
[6] [Jul 25 14:00:33] [ opsiclientd                   ] Session timer <_Timer(Thread-119, started daemon 5980)> canceled   (Session.pyo|128)
[5] [Jul 25 14:00:33] [ opsiclientd                   ] Session 'j9wzakC8Vbgl6bfxvAzmxm9MWr21OI04' from ip '127.0.0.1', application 'opsi jsonrpc module version 4.0.7.62' deleted   (Session.pyo|225)
opsi config editor Version 4.1.9.8.5 (2021/04/12)

opsiconfd 4.2.0.286
Benutzeravatar
CKoehler
Beiträge: 35
Registriert: 14 Sep 2015, 21:12
Wohnort: Braunschweig

Re: windows10-upgrade - 1803 nach 1903 bleibt stecken.

Beitrag von CKoehler »

Moin,

das Verhalten hatte ich beim ersten Mal auch festgestellt.
Da das Upgrade ja in dem temporären Benutzer läuft, solltest du die Möglichkeit haben, den TaskManager zu öffnen.
Dort dürftest du feststellen, dass das eigentliche Upgrade nun im Hintergrund (ohne GUI) ausgeführt wird.
Leider habe ich gerade nicht im Kopf wie der Prozess heißt. Ich glaube es war die "setup.exe".
Dürfte sich auf jeden Fall in der CPU/RAM/HDD-Last bemerkbar machen.

In meinen Tests hat das gesamte Upgrade zwischen ca. 45 Minuten (SSD) und ca. 1,5 Stunden (HDD) gedauert.

Meine Empfehlung: Mal im TaskManager kontrollieren und abwarten. ;)

Grüße
Christopher
Let's try something new: opsi-docker
g.burck
Beiträge: 199
Registriert: 23 Mai 2018, 16:44

Re: windows10-upgrade - 1803 nach 1903 bleibt stecken.

Beitrag von g.burck »

Moin,

OK ich schaue noch mal genau darauf. Ich habe zwar den Task manager offengehabt, aber da sich dort fast nichts tat (CPU nahe am idle) und auch das log file nicht mehr aktualisiert wurde, dachte ich nach 20 Minuten, da passiert nichts mehr.

Grüße

Gregor
opsi config editor Version 4.1.9.8.5 (2021/04/12)

opsiconfd 4.2.0.286
g.burck
Beiträge: 199
Registriert: 23 Mai 2018, 16:44

Re: windows10-upgrade - 1803 nach 1903 bleibt stecken.

Beitrag von g.burck »

So, habe es mal über Nacht laufen lassen. VM auf einem i7 mit SSD,...

Sa genauso aus wie Gestern bevor ich gegangen bin,...

PS Ich lasse es erst mal, bin dann mal zwei Wochen im Urlaub,...
opsi config editor Version 4.1.9.8.5 (2021/04/12)

opsiconfd 4.2.0.286
Antworten