Automatic upgrade failes / needs hours and we are not reachable

[microtronx]

As i can see in the updater1.log an update / patchX29_64 has started at 6:47 and not it is 8:30 and all services are not running. Lines are not reachable:

2020/09/23 06:47:00.783|0001| Cleaning folder C:\ProgramData\3CX\Data\Updates
2020/09/23 06:49:52.487|0001| SP link: https://downloads-eu.3cx.com/downloads/v160/sp150/PatchX29_64.zip
2020/09/23 06:49:52.735|0007| Downloading new version...
2020/09/23 06:49:53.964|0008| Done
2020/09/23 06:49:54.019|0008| Unzipping service pack...
2020/09/23 06:50:50.638|0005| Starting updater2.exe

What the hell, Whats the reason for this? Not knowing that there is a patch running at 8:30 we have restarted the server and after long search i found the updater1.log with a actual timestamp and now it is clear that the updates was running for more than 1.5 hours ... restarting the system has leaved the 3cx installation in a dead state.

Now i downloaded that patchfile again, unzipped it into a directory and started the updater2.exe "pathtobinfolder" ... and hope system will come up again. But again, whats wrong with your latest patch?

 

[JohnS_3CX]

Hi @microtronx

Were you able to see any errors in the log?

Did you by any chance see the running services to see if any 3CX-related ones did not stop?

 

[microtronx]

Thats the problem. Not knowing that there is a "update in progress" we have restarted the server ...
I was able to get the system back running:

1. delete Rollback folders
2. delete update folder structures
3. create Update folder
4. Extract patch file into Update folder
5. rerun updater2.exe "...path 2 bin folder"

System has installed the update within 10 minutes and is now running.

 

[microtronx]

... but possible that the problem lies in the updater2.log file, i have deleted this also because it was >6MB, possible that this has slowed down the update process ??

 

[JohnS_3CX]

Understood. In this case there's not much that can be done since the operation was stop in the middle by the server reboot.

However, the update should not really be running for 1.5 hours and I think that Updater2.log would have shown us why (this is the updater that installs the patched files). If this file is now gone we will not be able to look further...

 

[JohnS_3CX]

See if you can find any file recovery tools to get this log file back, that may be the only hope to learn more