I have a lot of updates (+100), I have done “Update all”
I see since a long time: “Event: Installing nethserver-xxx-x.x.x-x.ns7.x86_64”
Always in loading and /!\ and “Ooops!”.
Not the first time.
How it is the progress?
What is the process now?
check the webconsole (F12) of your browser when the error appears, I think we do not store this kind of error in log.
consoleCleared.SoftwareCenter.vue:1:487
███╗ ██╗███████╗████████╗██╗ ██╗███████╗███████╗██████╗ ██╗ ██╗███████╗██████╗
████╗ ██║██╔════╝╚══██╔══╝██║ ██║██╔════╝██╔════╝██╔══██╗██║ ██║██╔════╝██╔══██╗
██╔██╗ ██║█████╗ ██║ ███████║███████╗█████╗ ██████╔╝██║ ██║█████╗ ██████╔╝
██║╚██╗██║██╔══╝ ██║ ██╔══██║╚════██║██╔══╝ ██╔══██╗╚██╗ ██╔╝██╔══╝ ██╔══██╗
██║ ╚████║███████╗ ██║ ██║ ██║███████║███████╗██║ ██║ ╚████╔╝ ███████╗██║ ██║
╚═╝ ╚═══╝╚══════╝ ╚═╝ ╚═╝ ╚═╝╚══════╝╚══════╝╚═╝ ╚═╝ ╚═══╝ ╚══════╝╚═╝ ╚═╝ App.vue:313
API exec: system-authorization/read
$ /usr/libexec/nethserver/api/system-authorization/read | jq nethserver.js:41:9
API exec: system-task/read
$ /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/system-task/read | jq nethserver.js:41:9
API exec: system-settings/read
$ echo '{"action":"hints"}' | /usr/bin/sudo /usr/libexec/nethserver/api/system-settings/read | jq nethserver.js:41:9
tasks undefined App.vue:451
tasks no running tasks App.vue:451
API exec: system-task/read
$ /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/system-task/read | jq nethserver.js:41:9
API exec: system-packages/read
$ echo '{"action":"get-config"}' | /usr/bin/sudo /usr/libexec/nethserver/api/system-packages/read | jq nethserver.js:41:9
API exec: system-packages/read
$ echo '{"action":"list-available"}' | /usr/bin/sudo /usr/libexec/nethserver/api/system-packages/read | jq nethserver.js:41:9
API exec: system-authorization/read
$ /usr/libexec/nethserver/api/system-authorization/read | jq nethserver.js:41:9
tasks undefined App.vue:451
tasks no running tasks App.vue:451
API exec: system-packages/read
$ echo '{"action":"list-updates"}' | /usr/bin/sudo /usr/libexec/nethserver/api/system-packages/read | jq nethserver.js:41:9
API exec: system-packages/read
$ echo '{"action":"changelog"}' | /usr/bin/sudo /usr/libexec/nethserver/api/system-packages/read | jq nethserver.js:41:9
API exec: system-packages/update
$ echo '{"action":"update","packages":[]}' | /usr/bin/setsid /usr/bin/sudo /usr/libexec/nethserver/api/system-packages/update | jq nethserver.js:41:9
TypeError: e is null[webConsoleMoreInfoLabel] jquery.js:4591:13
e https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:4591:13
boxSizingReliable https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:4627:17
at https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:4794:14
get https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:4969:26
css https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:4936:21
k.fn[o]/< https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:7659:21
z https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:2908:20
k.fn[o] https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/base1/jquery.js:7644:24
refresh_now https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/system/system.js:48:71831
refresh/< https://XXX.XXX.XXX.XXX:9090/cockpit/$HASH/system/system.js:48:72447
The last part is repeated several times (+2000 for the moment)
Oh! mr Picky @Neustradamus!
How are you and your ejabber? 
Anyway…
Would you try to run yum update via web console?
The problem is that there are more than 100 updates.
I wait ejabberd changes in the code, … a 20.03 is here too.
This was the question… Would you or would you not? Using the CONSOLE into cockpit, not Software.
I have launched one time the “Update all”, and there is a problem of sync…
I have not done since a long time 
May I assume that the problem is solved?
I have done “F5” in the browser, the job has been progressed…
But there is a bug.
Many packages will be updated at the end of the operations.
Maybe your bug will be waived…
Is it possible to have updates of the status of your server? Maybe your alleged bug is still there, maybe not.
There were 100+ updates.
I do not know where there was a problem but it was not the first time.
After these 100+ updates are you having the same bug?