Unable to login to Files after 14-07-24 updates

Mister2

I have just applied the following updates (installed from Admin GUI Update process this morning - 14-07-24):-

After a reboot of Grommunio server I am no longer able to log in to Grommunio Files, the following error popups up when trying to connect the latest Nextcloud Client on a MacBook (Sonoma 14.5):-

'There was an error accessing the 'token' endpoint:
Error transferring https://domain.com/files/index.php/login/v2/poll - server replied: - Service Unavailable'

Tried reboot of server but issue remains. Have now 'rolled back' the updates via a Proxmox snapshot, taken immediately before the updates were applied, and Files now working again, but obviously something is broken by applying the updates above.

Anyone else experienced this error. Any suggestions to resolve.

I like to keep the server up to date, but now slightly out of date due to rollback.

WalterH

Mister2 server replied: - Service Unavailable'

Did you verified that all services are up and running after the update?

Andy

I can confirm, before was possible, now I get an alert

Mister2

WalterH Yes I did. Performed 2 reboots (one after updates were installed and then a second one when I realised there was an issue). Admin GUI showed a full set of 'Green Lights'. Also there were no errors reported in the logs available through the Admin GUI.

WalterH

Hi,

I mean on command line: systemctl --failed to show failed services.

Mister2

WalterH No I didn't. I was a bit short on time so just reverted to my Proxmox snapshot which allowed files to work normally. My Linix skills are very poor so n to always sure what to do when things don't work as expected.

I'll try another pass tonight and see if issue is still happening and try the 'systemctl --failed' option

Mister2

WalterH So I have recloned my live Grommunio server and applied the following updates (a few more than yesterday but mainly OpenSUSE updates) - this is output of Admin GUI Updates command:-

This system : Grommunio.server

Uptime : 0:02

Load : Last Minute: 0.50, Last 5 Minutes: 0.39, Last 15 Minutes: 0.17

IP Address : 192.168.50.35 192.168.200.35

Executed : /usr/sbin/grommunio-update update community

Start : Mon 2024-07-15 21:05:43 BST

Operation : Update

[36m▶[0m Starting Update (zypper ref && zypper up -y).
[36m▶[0m on repository community.
Credentials = [32m[0m:[31m[0m.
Repository URL = https://download.grommunio.com/community/openSUSE_Leap_15.5/?ssl_verify=no
grep: /etc/yum.repos.d/: No such file or directory
\x1b[31mNo correct package manager found.\x1b[0m │
Repository 'base' is up to date.
Repository 'debug' is up to date.
Repository 'debug-update' is up to date.
Repository 'grommunio' is up to date.
Repository 'repo-backports-update' is up to date.
Repository 'repo-sle-update' is up to date.
Repository 'update' is up to date.
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
The following 13 packages are going to be upgraded:
grommunio-admin-api grommunio-web gromox gromox-debuginfo gromox-debugsource libLLVM15 libonig4 libpython3_6m1_0 libssh2-1 libvmime-suse8 python3 python3-base python3-curses
13 packages to upgrade.
Overall download size: 63.9 MiB. Already cached: 0 B. After the operation, additional 187.0 KiB will be used.
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: gromox-debugsource-2.30.38.g713d40b-lp155.23.1.x86_64 (grommunio) (1/13), 1.0 MiB
Retrieving: gromox-debugsource-2.30.38.g713d40b-lp155.23.1.x86_64.rpm [...done (493.7 KiB/s)]
Retrieving: libvmime-suse8-0.9.2.203-lp155.1.2.x86_64 (grommunio) (2/13), 708.2 KiB
Retrieving: libvmime-suse8-0.9.2.203-lp155.1.2.x86_64.rpm [...done (599.1 KiB/s)]
Retrieving: gromox-debuginfo-2.30.38.g713d40b-lp155.23.1.x86_64 (grommunio) (3/13), 17.9 MiB
Retrieving: gromox-debuginfo-2.30.38.g713d40b-lp155.23.1.x86_64.rpm [........done (14.4 MiB/s)]
Retrieving: gromox-2.30.38.g713d40b-lp155.23.1.x86_64 (grommunio) (4/13), 2.2 MiB
Retrieving: gromox-2.30.38.g713d40b-lp155.23.1.x86_64.rpm [....done (2.0 MiB/s)]
Retrieving: grommunio-web-3.9.25.g24c99c75-lp155.100.1.noarch (grommunio) (5/13), 11.3 MiB
Retrieving: grommunio-web-3.9.25.g24c99c75-lp155.100.1.noarch.rpm [......done (10.3 MiB/s)]
Retrieving: libLLVM15-15.0.7-150500.4.9.6.x86_64 (repo-sle-update) (6/13), 21.9 MiB
Retrieving: libLLVM15-15.0.7-150500.4.9.6.x86_64.rpm [............done (21.6 MiB/s)]
Retrieving: libonig4-6.7.0-150000.3.6.1.x86_64 (repo-sle-update) (7/13), 127.6 KiB
Retrieving: libonig4-6.7.0-150000.3.6.1.x86_64.rpm [..done (2.7 KiB/s)]
Retrieving: libssh2-1-1.11.0-150200.9.2.1.x86_64 (repo-sle-update) (8/13), 125.6 KiB
Retrieving: libssh2-1-1.11.0-150200.9.2.1.x86_64.rpm [..done (2.7 KiB/s)]
Retrieving: python3-base-3.6.15-150300.10.65.1.x86_64 (repo-sle-update) (9/13), 7.5 MiB
Retrieving: python3-base-3.6.15-150300.10.65.1.x86_64.rpm [.....done (18.9 MiB/s)]
Retrieving: libpython3_6m1_0-3.6.15-150300.10.65.1.x86_64 (repo-sle-update) (10/13), 874.4 KiB
Retrieving: libpython3_6m1_0-3.6.15-150300.10.65.1.x86_64.rpm [..done (3.1 KiB/s)]
Retrieving: python3-3.6.15-150300.10.65.2.x86_64 (repo-sle-update) (11/13), 87.8 KiB
Retrieving: python3-3.6.15-150300.10.65.2.x86_64.rpm [..done (2.7 KiB/s)]
Retrieving: python3-curses-3.6.15-150300.10.65.2.x86_64 (repo-sle-update) (12/13), 86.1 KiB
Retrieving: python3-curses-3.6.15-150300.10.65.2.x86_64.rpm [..done (2.8 KiB/s)]
Retrieving: grommunio-admin-api-1.15.18.c2253e7-lp155.108.1.noarch (grommunio) (13/13), 220.8 KiB
Retrieving: grommunio-admin-api-1.15.18.c2253e7-lp155.108.1.noarch.rpm [..done (4.2 KiB/s)]
Checking for file conflicts: [...........done]
( 1/13) Installing: gromox-debugsource-2.30.38.g713d40b-lp155.23.1.x86_64 [......done]
( 2/13) Installing: libvmime-suse8-0.9.2.203-lp155.1.2.x86_64 [...done]
( 3/13) Installing: gromox-debuginfo-2.30.38.g713d40b-lp155.23.1.x86_64 [...............................done]
( 4/13) Installing: gromox-2.30.38.g713d40b-lp155.23.1.x86_64 [........done]
( 5/13) Installing: grommunio-web-3.9.25.g24c99c75-lp155.100.1.noarch [.........................done]
( 6/13) Installing: libLLVM15-15.0.7-150500.4.9.6.x86_64 [.......................................done]
( 7/13) Installing: libonig4-6.7.0-150000.3.6.1.x86_64 [..done]
( 8/13) Installing: libssh2-1-1.11.0-150200.9.2.1.x86_64 [..done]
( 9/13) Installing: python3-base-3.6.15-150300.10.65.1.x86_64 [.................done]
(10/13) Installing: libpython3_6m1_0-3.6.15-150300.10.65.1.x86_64 [...done]
(11/13) Installing: python3-3.6.15-150300.10.65.2.x86_64 [..done]
(12/13) Installing: python3-curses-3.6.15-150300.10.65.2.x86_64 [..done]
(13/13) Installing: grommunio-admin-api-1.15.18.c2253e7-lp155.108.1.noarch [....done]
There are running programs which still use files and libraries deleted or updated by recent upgrades. They should be restarted to benefit from the latest updates. Run 'zypper ps -s' to list these programs.
[32m▶[0m Update completed successfully.
[36m▶[0m Updating postfix configuration with new maps if exist
[36m▶[0m Running post-update/upgrade checksdbop: Current database schema: gx-131
[36m▶[0m Checking for pending service restart or reboot

Restarting service firewalld after update: ... done

Restarting service grommunio-cui@tty1 after update: ... done

Restarting service php-fpm after update: ... done

End Update : Mon 2024-07-15 21:06:32 BST

After updates have been applied I now get the following error when attempting to either login to Files via the https://mail.mydomain.com/files or via the sign in to the Nextcloud app on my MacBook.

You asked for the output of 'systemctl --failed' and this is shown below:-

systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.

so it seems that there are no failed services. I then performed a reboot of the server and received the following output from the above command

_systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION >
● grommunio-files-cron.service loaded failed failed Run grommunio Files cron-jo>

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed._

This service error goes away after a few minutes as expected.

Opening the Nextcloud client after the reboot returns me back to the original error in post #1. So bug reported is still causing an issue as Files can no longer be opened/used with the current updates.

Any further ideas on this.

Andy

There is something more effect. If I log in my account at first I get very shortly a unauthority message which turns after 1 second to the follow

but I was not logged in Files before. After clicking OK it seems all is running as usual except above login. Regarding the test I got same result:

localhost:~ # systemctl --failed
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed.
localhost:~ #

Andy

With the updates released this morning, I can log in again.

Mister2

Andy I can concur. Have just applied updates to test machine and Files is now working via Web and MacBook client. Now off to update my live server.

As always, thanks to the DEV's for getting this sorted so quickly.