Can't login to web admin console

etsiot

Hi All,
I am experiencing the same issue as in this thread:
[https://community.grommunio.com/d/166-solved-after-update-141121-no-login-admin-if]

Have followed all steps as in the thread above:

repos have been updated
services are running (ngingx, grommunio-admin-api)
admin password has been changed
multple reboots

yet I get the admin pass wrong.
Is there some other resolution missing?

TIA

WalterH

Try to restart the admin interface, this may help:
systemctl restart grommunio-admin-api

etsiot

I have tried restarting grommunio-admin-api to no success..
I am also checking the logs in /var/log/grommunio yet I can't find some meaningful entry on that.
Any pointers please on where I should look next?

WalterH

II have seen the issue sometimes, but the issue usually disappeared so quickly that we could not debug it.
Try to set the admin password: grommunio-admin passwd
restart the admin interface: systemctl restart grommunio-admin-api
Did you see any useful information in log: journalctl -fu grommunio-admin-api ?

etsiot

I just tried yet another time with resetting the admin passwd and restarting the grommunio-admin-api.
When journalctl -fu grommunio-admin-api I get the following:
Jan 16 18:14:35 grommunio uwsgi[14061]: your server socket listen backlog is limited to 100 connections Jan 16 18:14:35 grommunio uwsgi[14061]: your mercy for graceful operations on workers is 60 seconds Jan 16 18:14:35 grommunio uwsgi[14061]: mapped 208576 bytes (203 KB) for 4 cores Jan 16 18:14:35 grommunio uwsgi[14061]: *** Operational MODE: threaded *** Jan 16 18:14:46 grommunio uwsgi[14061]: Could not load license: No such file or directory Jan 16 18:14:46 grommunio uwsgi[14061]: WSGI app 0 (mountpoint='') ready in 11 seconds on interpreter 0xaaaaf1b815b0 pid: 14061 (default app) Jan 16 18:14:46 grommunio uwsgi[14061]: *** uWSGI is running in multiple interpreter mode *** Jan 16 18:14:46 grommunio uwsgi[14061]: spawned uWSGI master process (pid: 14061) Jan 16 18:14:46 grommunio systemd[1]: Started grommunio admin api. Jan 16 18:14:46 grommunio uwsgi[14061]: spawned uWSGI worker 1 (pid: 14065, cores: 4)
yet I still can't login.
Goes on without saying, I have tried with multiple browsers (on OSX Big Sur)...

WalterH

Do you have characters like ! or $ in your password? Try a password like "Bla-1234" without quotation marks, does it work?

etsiot

Not really, I have put a very simple one, numbers only, just for that reason...

etsiot

Following yet another reboot, I am noticing a rather strange behaviour.
doing a systemctl status grommunio-admin-api
I get the following output which is wrong-dated
`grommunio-admin-api.service - grommunio admin api
Loaded: loaded (/usr/lib/systemd/system/grommunio-admin-api.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2021-04-29 15:00:20 EEST; 8 months 18 days ago
TriggeredBy: grommunio-admin-api.socket
Main PID: 493 (uwsgi)
Status: "uWSGI is ready"
Tasks: 7 (limit: 4495)
CGroup: /system.slice/grommunio-admin-api.service
├─ 493 /usr/sbin/uwsgi --ini /usr/share/grommunio-admin-api/api-config.ini
└─1195 /usr/sbin/uwsgi --ini /usr/share/grommunio-admin-api/api-config.ini

Apr 29 15:00:08 grommunio uwsgi[493]: *** Operational MODE: threaded ***
Apr 29 15:00:13 grommunio uwsgi[493]: Failed to detect schema version, assuming up-to-date schema
Apr 29 15:00:13 grommunio uwsgi[493]: Database connection failed with error 2002: Can't connect to local MySQL server through socket '/run/mysql/mysql.sock' (2)
Apr 29 15:00:19 grommunio uwsgi[493]: Could not load license: No such file or directory
Apr 29 15:00:20 grommunio uwsgi[493]: WSGI app 0 (mountpoint='') ready in 12 seconds on interpreter 0xaaaade3e95b0 pid: 493 (default app)
Apr 29 15:00:20 grommunio uwsgi[493]: *** uWSGI is running in multiple interpreter mode ***
Apr 29 15:00:20 grommunio uwsgi[493]: spawned uWSGI master process (pid: 493)
Apr 29 15:00:20 grommunio systemd[1]: Started grommunio admin api.
Apr 29 15:00:20 grommunio uwsgi[493]: spawned uWSGI worker 1 (pid: 1195, cores: 4)
Apr 29 15:00:20 grommunio uwsgi[1195]: [WARNING] (tasq) Database schema version too old (n102 required) - falling back to offline mode.`

Plus the last line throws a database schema too old msg?

If I then restart the service I get the following output:
systemctl status grommunio-admin-api
● grommunio-admin-api.service - grommunio admin api
Loaded: loaded (/usr/lib/systemd/system/grommunio-admin-api.service; enabled; vendor preset: disabled)
Active: active (running) since Sun 2022-01-16 18:35:38 EET; 1s ago
TriggeredBy: ● grommunio-admin-api.socket
Main PID: 14062 (uwsgi)
Status: "uWSGI is ready"
Tasks: 7 (limit: 4495)
CGroup: /system.slice/grommunio-admin-api.service
├─14062 /usr/sbin/uwsgi --ini /usr/share/grommunio-admin-api/api-config.ini
└─14066 /usr/sbin/uwsgi --ini /usr/share/grommunio-admin-api/api-config.ini

Jan 16 18:35:27 grommunio uwsgi[14062]: your server socket listen backlog is limited to 100 connections
Jan 16 18:35:27 grommunio uwsgi[14062]: your mercy for graceful operations on workers is 60 seconds
Jan 16 18:35:27 grommunio uwsgi[14062]: mapped 208576 bytes (203 KB) for 4 cores
Jan 16 18:35:27 grommunio uwsgi[14062]: *** Operational MODE: threaded ***
Jan 16 18:35:37 grommunio uwsgi[14062]: Could not load license: No such file or directory
Jan 16 18:35:38 grommunio uwsgi[14062]: WSGI app 0 (mountpoint='') ready in 11 seconds on interpreter 0xaaaae2d975b0 pid: 14062 (default app)
Jan 16 18:35:38 grommunio uwsgi[14062]: *** uWSGI is running in multiple interpreter mode ***
Jan 16 18:35:38 grommunio uwsgi[14062]: spawned uWSGI master process (pid: 14062)
Jan 16 18:35:38 grommunio systemd[1]: Started grommunio admin api.
Jan 16 18:35:38 grommunio uwsgi[14062]: spawned uWSGI worker 1 (pid: 14066, cores: 4)

Also, zypper search -s grommunio-admin-api
Loading repository data...
Warning: Repository 'Update Repository (Non-Oss)' appears to be outdated. Consider using a different mirror or server.
Reading installed packages...

WalterH

To update the database schema use: gromox-dbop -U than restart the server.

etsiot

Did that:
gromox-dbop -U Current schema n102

Restarted; when up again I still can't login to the web admin console.
What are the log files I should be checking pls?

mwilliams

etsiot

The logs in question are visible with journalctl -fu grommunio-admin-api, best timings would be directly after service start and when you try to login.

etsiot

Following a service restart I get the following output:
-- Reboot -- Jan 17 20:41:23 grommunio uwsgi[497]: SIGINT/SIGQUIT received...killing workers... Jan 17 20:41:23 grommunio systemd[1]: Stopping grommunio admin api... Jan 17 20:41:24 grommunio uwsgi[497]: worker 1 buried after 1 seconds Jan 17 20:41:24 grommunio uwsgi[497]: goodbye to uWSGI. Jan 17 20:41:24 grommunio systemd[1]: grommunio-admin-api.service: Succeeded. Jan 17 20:41:24 grommunio systemd[1]: Stopped grommunio admin api. Jan 17 20:41:24 grommunio systemd[1]: Starting grommunio admin api... Jan 17 20:41:24 grommunio uwsgi[14157]: [uWSGI] getting INI configuration from /usr/share/grommunio-admin-api/api-config.ini Jan 17 20:41:24 grommunio uwsgi[14157]: *** Starting uWSGI 2.0.19.1 (64bit) on [Mon Jan 17 20:41:24 2022] *** Jan 17 20:41:24 grommunio uwsgi[14157]: compiled with version: 7.5.0 on 11 December 2020 12:00:00 Jan 17 20:41:24 grommunio uwsgi[14157]: os: Linux-5.3.18-59.10-default #1 SMP Fri Jun 25 12:36:56 UTC 2021 (6856d31) Jan 17 20:41:24 grommunio uwsgi[14157]: nodename: grommunio Jan 17 20:41:24 grommunio uwsgi[14157]: machine: aarch64 Jan 17 20:41:24 grommunio uwsgi[14157]: clock source: unix Jan 17 20:41:24 grommunio uwsgi[14157]: pcre jit disabled Jan 17 20:41:24 grommunio uwsgi[14157]: detected number of CPU cores: 4 Jan 17 20:41:24 grommunio uwsgi[14157]: current working directory: /usr/share/grommunio-admin-api Jan 17 20:41:24 grommunio uwsgi[14157]: detected binary path: /usr/sbin/uwsgi Jan 17 20:41:24 grommunio uwsgi[14157]: chdir() to /usr/share/grommunio-admin-api Jan 17 20:41:24 grommunio uwsgi[14157]: your processes number limit is 14984 Jan 17 20:41:24 grommunio uwsgi[14157]: your memory page size is 4096 bytes Jan 17 20:41:24 grommunio uwsgi[14157]: detected max file descriptor number: 1024 Jan 17 20:41:24 grommunio uwsgi[14157]: lock engine: pthread robust mutexes Jan 17 20:41:24 grommunio uwsgi[14157]: thunder lock: disabled (you can enable it with --thunder-lock) Jan 17 20:41:24 grommunio uwsgi[14157]: - SystemD socket activation detected - Jan 17 20:41:24 grommunio uwsgi[14157]: uwsgi socket 1 attached to UNIX address /run/grommunio/admin-api.socket fd 3 Jan 17 20:41:24 grommunio uwsgi[14157]: Python version: 3.6.13 (default, Mar 10 2021, 18:30:35) [GCC] Jan 17 20:41:24 grommunio uwsgi[14157]: Python main interpreter initialized at 0xaaaafdc8f5b0 Jan 17 20:41:24 grommunio uwsgi[14157]: python threads support enabled Jan 17 20:41:24 grommunio uwsgi[14157]: your server socket listen backlog is limited to 100 connections Jan 17 20:41:24 grommunio uwsgi[14157]: your mercy for graceful operations on workers is 60 seconds Jan 17 20:41:24 grommunio uwsgi[14157]: mapped 208576 bytes (203 KB) for 4 cores Jan 17 20:41:24 grommunio uwsgi[14157]: *** Operational MODE: threaded *** Jan 17 20:41:34 grommunio uwsgi[14157]: Could not load license: No such file or directory Jan 17 20:41:35 grommunio uwsgi[14157]: WSGI app 0 (mountpoint='') ready in 11 seconds on interpreter 0xaaaafdc8f5b0 pid: 14157 (default app) Jan 17 20:41:35 grommunio uwsgi[14157]: *** uWSGI is running in multiple interpreter mode *** Jan 17 20:41:35 grommunio uwsgi[14157]: spawned uWSGI master process (pid: 14157) Jan 17 20:41:35 grommunio systemd[1]: Started grommunio admin api. Jan 17 20:41:35 grommunio uwsgi[14157]: spawned uWSGI worker 1 (pid: 14166, cores: 4)

However, no further log output on (unsuccessful) login...

mwilliams

The information provided is unfortunately not enough to identify your problem. Please follow the steps:

/usr/share/grommunio-admin-api/api-config.ini : disable-logging = true -> disable-logging = false
systemctl restart grommunio-admin-api
journalctl -fu grommunio-admin-api

And repost the information as you are trying to login.

WalterH

etsiot Das Log ist eigenartig, beim Login müssten diese Zeilen entstehen wenn Logging auf enabled gesetzt ist wie mwilliams geschrieben at:

Jan 20 17:03:12 icc-grommunio uwsgi[12711]: [pid: 12711|app: 0|req: 19/19] 192.168.130.65 () {56 vars in 882 bytes} [Thu Jan 20 17:03:12 2022] POST /api/v1/login => generated 788 bytes in 20 msecs (HTTP/1.1 200) 3 headers in 118 bytes (1 switches on core 1) Jan 20 17:03:12 icc-grommunio uwsgi[12711]: [pid: 12711|app: 0|req: 20/20] 192.168.130.65 () {50 vars in 1494 bytes} [Thu Jan 20 17:03:12 2022] GET /api/v1/profile => generated 471 bytes in 10 msecs (HTTP/1.1 200) 3 headers in 118 bytes (1 switches on core 3) Jan 20 17:03:12 icc-grommunio uwsgi[12711]: [pid: 12711|app: 0|req: 21/21] 192.168.130.65 () {50 vars in 1519 bytes} [Thu Jan 20 17:03:12 2022] GET /api/v1/domains?domainType=0 => generated 229 bytes in 18 msecs (HTTP/1.1 200) 3 headers in 118 bytes (1 switches on core 0) Jan 20 17:03:12 icc-grommunio uwsgi[12711]: [pid: 12711|app: 0|req: 25/22] 192.168.130.65 () {50 vars in 1508 bytes} [Thu Jan 20 17:03:12 2022] GET /api/v1/system/license => generated 201 bytes in 42 msecs (HTTP/1.1 200) 3 headers in 118 bytes (1 switches on core 2) Jan 20 17:03:12 icc-grommunio uwsgi[12711]: [pid: 12711|app: 0|req: 25/23] 192.168.130.65 () {50 vars in 1512 bytes} [Thu Jan 20 17:03:12 2022] GET /api/v1/system/dashboard => generated 748 bytes in 49 msecs (HTTP/1.1 200) 3 headers in 118 bytes (1 switches on core 1)
Wurde die Anleitung von mwilliams exakt abgearbeitet?

etsiot

Hello,

Enabled logging in /usr/share/grommunio-admin-api/api-config.ini and restarted the admin api, however no login info is logged?

Jan 18 08:59:15 grommunio uwsgi[14057]: your server socket listen backlog is limited to 100 connections Jan 18 08:59:15 grommunio uwsgi[14057]: your mercy for graceful operations on workers is 60 seconds Jan 18 08:59:15 grommunio uwsgi[14057]: mapped 208576 bytes (203 KB) for 4 cores Jan 18 08:59:15 grommunio uwsgi[14057]: *** Operational MODE: threaded *** Jan 18 08:59:25 grommunio uwsgi[14057]: Could not load license: No such file or directory Jan 18 08:59:26 grommunio uwsgi[14057]: WSGI app 0 (mountpoint='') ready in 11 seconds on interpreter 0xaaaae76b15b0 pid: 14057 (default app) Jan 18 08:59:26 grommunio uwsgi[14057]: *** uWSGI is running in multiple interpreter mode *** Jan 18 08:59:26 grommunio uwsgi[14057]: spawned uWSGI master process (pid: 14057) Jan 18 08:59:26 grommunio systemd[1]: Started grommunio admin api. Jan 18 08:59:26 grommunio uwsgi[14057]: spawned uWSGI worker 1 (pid: 14062, cores: 4) Jan 18 09:00:27 grommunio uwsgi[14057]: SIGINT/SIGQUIT received...killing workers... Jan 18 09:00:27 grommunio systemd[1]: Stopping grommunio admin api... Jan 18 09:00:28 grommunio uwsgi[14057]: worker 1 buried after 1 seconds Jan 18 09:00:28 grommunio uwsgi[14057]: goodbye to uWSGI. Jan 18 09:00:28 grommunio systemd[1]: grommunio-admin-api.service: Succeeded. Jan 18 09:00:28 grommunio systemd[1]: Stopped grommunio admin api. Jan 18 09:00:28 grommunio systemd[1]: Starting grommunio admin api... Jan 18 09:00:28 grommunio uwsgi[14122]: [uWSGI] getting INI configuration from /usr/share/grommunio-admin-api/api-config.ini Jan 18 09:00:28 grommunio uwsgi[14122]: *** Starting uWSGI 2.0.19.1 (64bit) on [Tue Jan 18 09:00:28 2022] *** Jan 18 09:00:28 grommunio uwsgi[14122]: compiled with version: 7.5.0 on 11 December 2020 12:00:00 Jan 18 09:00:28 grommunio uwsgi[14122]: os: Linux-5.3.18-59.10-default #1 SMP Fri Jun 25 12:36:56 UTC 2021 (6856d31) Jan 18 09:00:28 grommunio uwsgi[14122]: nodename: grommunio Jan 18 09:00:28 grommunio uwsgi[14122]: machine: aarch64 Jan 18 09:00:28 grommunio uwsgi[14122]: clock source: unix Jan 18 09:00:28 grommunio uwsgi[14122]: pcre jit disabled Jan 18 09:00:28 grommunio uwsgi[14122]: detected number of CPU cores: 4 Jan 18 09:00:28 grommunio uwsgi[14122]: current working directory: /usr/share/grommunio-admin-api Jan 18 09:00:28 grommunio uwsgi[14122]: detected binary path: /usr/sbin/uwsgi Jan 18 09:00:28 grommunio uwsgi[14122]: chdir() to /usr/share/grommunio-admin-api Jan 18 09:00:28 grommunio uwsgi[14122]: your processes number limit is 14984 Jan 18 09:00:28 grommunio uwsgi[14122]: your memory page size is 4096 bytes Jan 18 09:00:28 grommunio uwsgi[14122]: detected max file descriptor number: 1024 Jan 18 09:00:28 grommunio uwsgi[14122]: lock engine: pthread robust mutexes Jan 18 09:00:28 grommunio uwsgi[14122]: thunder lock: disabled (you can enable it with --thunder-lock) Jan 18 09:00:28 grommunio uwsgi[14122]: - SystemD socket activation detected - Jan 18 09:00:28 grommunio uwsgi[14122]: uwsgi socket 1 attached to UNIX address /run/grommunio/admin-api.socket fd 3 Jan 18 09:00:28 grommunio uwsgi[14122]: Python version: 3.6.13 (default, Mar 10 2021, 18:30:35) [GCC] Jan 18 09:00:28 grommunio uwsgi[14122]: Python main interpreter initialized at 0xaaaaf6c9a5b0 Jan 18 09:00:28 grommunio uwsgi[14122]: python threads support enabled Jan 18 09:00:28 grommunio uwsgi[14122]: your server socket listen backlog is limited to 100 connections Jan 18 09:00:28 grommunio uwsgi[14122]: your mercy for graceful operations on workers is 60 seconds Jan 18 09:00:28 grommunio uwsgi[14122]: mapped 208576 bytes (203 KB) for 4 cores Jan 18 09:00:28 grommunio uwsgi[14122]: *** Operational MODE: threaded *** Jan 18 09:00:39 grommunio uwsgi[14122]: Could not load license: No such file or directory Jan 18 09:00:39 grommunio uwsgi[14122]: WSGI app 0 (mountpoint='') ready in 11 seconds on interpreter 0xaaaaf6c9a5b0 pid: 14122 (default app) Jan 18 09:00:39 grommunio uwsgi[14122]: *** uWSGI is running in multiple interpreter mode *** Jan 18 09:00:39 grommunio uwsgi[14122]: spawned uWSGI master process (pid: 14122) Jan 18 09:00:39 grommunio systemd[1]: Started grommunio admin api. Jan 18 09:00:39 grommunio uwsgi[14122]: spawned uWSGI worker 1 (pid: 14126, cores: 4)

etsiot

just to make the above post clear, after restarting the api service, I did try to login 2-3 times but noting appeared in the logs...

etsiot

Any feedback on how this can be debugged/resolved?
Pretty sure quite a few others have experienced it.

etsiot

Yep, I did exactly the following:

/usr/share/grommunio-admin-api/api-config.ini : disable-logging = true -> disable-logging = false systemctl restart grommunio-admin-api journalctl -fu grommunio-admin-api

yet no login is logged...

WalterH

Can you please post the output of these 2 commands here:
rpm -qi gromox | head -4
and
cat /usr/share/grommunio-admin-api/api-config.ini

etsiot

Hi, sure...

rpm -qi gromox | head -4 Name : gromox Version : 1.13.0.8b5fc259 Release : lp153.1.1 Architecture: aarch64

cat /usr/share/grommunio-admin-api/api-config.ini [uwsgi] master = True plugin = python3 protocol = uwsgi socket = /run/grommunio/admin-api.socket chdir = /usr/share/grommunio-admin-api module = main callable = API processes = 1 threads = 4 die-on-term = true chmod-socket = 660 enable-threads = true disable-logging = false