Since today i can not logon to SOGo and Nextcloud.
Guacamole works fine, also Zoneminder.
Nextcloud prompts immediately an error at launch: “internal server error”
SOGo does let me put in the credentials, but then says: “wrong username or passord”
I looked into the Nextcloud logs, and found lot of exception with the error:“message”:“Lost connection to LDAP server.”
In the message logs in only find:
core sogo-backup.sh: <0x0x1519e50[LDAPSource]> <NSException: 0x1455b70> NAME:LDAPException REASON:operation bind failed: Invalid credentials (0x31) INFO:{“error_code” = 49; login =
and
WARNING: Method [public void org.apache.guacamole.auth.jdbc.connection.ConnectionDirectory.add(org.apache.guacamole.net.auth.Identifiable) throws org.apache.guacamole.GuacamoleException] is synthetic and is being intercepted by [org.mybatis.guice.transactional.TransactionalMethodInterceptor@49908839]. This could indicate a bug. The method may be intercepted twice, or may not be intercepted at all.
You are right, Guacamole and Zoneminder works as i don’t use LDAP on them.
Here are the results of the commands:
account-provider-test
ldap_sasl_bind(SIMPLE): Can’t contact LDAP server (-1)
systemctl status mysqld -l
● mysqld.service - MariaDB database server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor prese t: disabled)
Active: inactive (dead) since Thu 2022-03-17 08:57:44 GMT; 11h ago
Main PID: 1542 (code=exited, status=0/SUCCESS)
Mar 17 08:55:31 systemd[1]: Starting MariaDB database server…
Mar 17 08:55:31 mariadb-prepare-db-dir[1222]: Database MariaDB is probably initialized in /var/lib/mysql already, nothing is done.
Mar 17 08:55:31 mariadb-prepare-db-dir[1222]: If this is not the case, make sure the /var/lib/mysql is empty before running mariadb-prepare-db-dir.
Mar 17 08:55:32 mysqld_safe[1542]: 220317 08:55:32 mysqld_safe Logging to ‘/var/log/mariadb/mariadb.log’.
Mar 17 08:55:32 mysqld_safe[1542]: 220317 08:55:32 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
Mar 17 08:55:37 systemd[1]: Started MariaDB database server.
Mar 17 18:05:00 systemd[1]: Starting MariaDB 10.5 database server…
Mar 17 18:05:00 scl[16544]: Database MariaDB is probably initialized in /var/opt/rh/rh-mariadb105/lib/mysql-nextcloud already, nothing is done.
Mar 17 18:05:00 scl[16544]: If this is not the case, make sure the /var/opt/rh/rh-mariadb105/lib/mysql-nextcloud is empty before running mysql-prepare-db-dir.
Mar 17 18:05:00 mysqld-scl-helper[16588]: 2022-03-17 18:05:00 0 [Note] /opt/rh/rh-mariadb105/root/usr/libexec/mysqld (mysqld 10.5.9-MariaDB) starting as process 16588 …
Mar 17 18:05:00 systemd[1]: Started MariaDB 10.5 database server.
Mar 17 20:24:31 control-service: mysqld start
Mar 17 20:24:31 systemd: Starting MariaDB database server…
Mar 17 20:24:31 mariadb-prepare-db-dir: Socket file /var/lib/mysql/mysql.sock exists.
Mar 17 20:24:31 mariadb-prepare-db-dir: Is another MySQL daemon already running with the same unix socket?
Mar 17 20:24:31 systemd: mysqld.service: control process exited, code=exited status=1
Mar 17 20:24:31 systemd: Failed to start MariaDB database server.
Mar 17 20:24:31 systemd: Unit mysqld.service entered failed state.
Mar 17 20:24:31 systemd: mysqld.service failed.
Mar 17 20:44:52 systemd-nspawn[1214]: [ OK ] Reached target Network.
Mar 17 20:44:52 systemd-nspawn[1214]: [ OK ] Started Samba domain controller daemon.
Mar 17 20:44:52 systemd-nspawn[1214]: [ OK ] Started Login Service.
Mar 17 20:44:52 systemd-nspawn[1214]: [ OK ] Started Network Time Service.
Mar 17 20:44:52 systemd-nspawn[1214]: [ OK ] Reached target Multi-User System.
Mar 17 20:44:52 systemd-nspawn[1214]: [ OK ] Reached target Graphical Interface.
Mar 17 20:44:52 systemd-nspawn[1214]: Starting Update UTMP about System Runlevel Changes…
Mar 17 20:44:52 systemd-nspawn[1214]: [ OK ] Started Update UTMP about System Runlevel Changes.
Mar 17 20:44:53 systemd-nspawn[1214]: CentOS Linux 7 (Core)
Mar 17 20:44:53 systemd-nspawn[1214]: Kernel 3.10.0-1160.59.1.el7.x86_64 on an x86_64
Going to User and Groups, it does allows me to create a user without error.
No it does not unfortunately. It gives the same error, and the Nextcloud, SOGo issue remaind.
Running journalctl -M nsdc i see no error at all the past 2 days.
This is after latest reboot:
Reboot –
Mar 17 20:44:51 systemd-journal[14]: Runtime journal is using 8.0M (max allowed 693.0M, trying to leave 1.0G free of 6.7G available → current limit 693.0M).
Mar 17 20:44:51 systemd-journal[14]: Journal started
Mar 17 20:44:51 systemd[1]: Starting Flush Journal to Persistent Storage…
Mar 17 20:44:51 systemd-journal[14]: Permanent journal is using 280.0M (max allowed 4.0G, trying to leave 4.0G free of 472.7G available → current limit 4.0G).
Mar 17 20:44:51 systemd-journal[14]: Time spent on flushing to /var is 40.379ms for 4 entries.
Mar 17 20:44:51 systemd[1]: Started Flush Journal to Persistent Storage.
Mar 17 20:44:51 systemd[1]: Starting Create Volatile Files and Directories…
Mar 17 20:44:52 systemd[1]: Started Create Volatile Files and Directories.
Mar 17 20:44:52 systemd[1]: Starting Update UTMP about System Boot/Shutdown…
Mar 17 20:44:52 systemd[1]: Started Update UTMP about System Boot/Shutdown.
Mar 17 20:44:52 systemd[1]: Reached target System Initialization.
Mar 17 20:44:52 systemd[1]: Listening on NSDC container remote command server.
Mar 17 20:44:52 systemd[1]: Started Daily Cleanup of Temporary Directories.
Mar 17 20:44:52 systemd[1]: Reached target Timers.
Mar 17 20:44:52 systemd[1]: Listening on D-Bus System Message Bus Socket.
Mar 17 20:44:52 systemd[1]: Reached target Sockets.
Mar 17 20:44:52 systemd[1]: Reached target Basic System.
Mar 17 20:44:52 systemd[1]: Started D-Bus System Message Bus.
Mar 17 20:44:52 systemd[1]: Starting Network Service…
Mar 17 20:44:52 systemd[1]: Starting Login Service…
Mar 17 20:44:52 systemd[1]: Starting Network Time Service…
Mar 17 20:44:52 systemd[1]: Starting Permit User Sessions…
Mar 17 20:44:52 systemd[1]: Started Permit User Sessions.
Mar 17 20:44:52 systemd[1]: Started Console Getty.
Mar 17 20:44:52 systemd[1]: Reached target Login Prompts.
Mar 17 20:44:52 systemd-networkd[20]: host0 : Cannot configure IPv4 forwarding for interface host0: Read-only file system
Mar 17 20:44:52 systemd-networkd[20]: host0 : Cannot configure IPv6 forwarding for interface: Read-only file system
Mar 17 20:44:52 systemd-networkd[20]: Enumeration completed
Mar 17 20:44:52 systemd[1]: Started Network Service.
Mar 17 20:44:52 systemd[1]: Reached target Network.
Mar 17 20:44:52 systemd-networkd[20]: host0 : gained carrier
Mar 17 20:44:52 systemd-networkd[20]: host0 : link configured
Mar 17 20:44:52 systemd[1]: Started Samba domain controller daemon.
Mar 17 20:44:52 systemd[1]: Started Login Service.
Mar 17 20:44:52 systemd-logind[21]: New seat seat0.
Mar 17 20:44:52 ntpd[22]: ntpd 4.2.6p5@1.2349-o Thu Aug 8 11:47:59 UTC 2019 (1)
Mar 17 20:44:52 systemd[1]: Started Network Time Service.
Mar 17 20:44:52 systemd[1]: Reached target Multi-User System.
Mar 17 20:44:52 systemd[1]: Reached target Graphical Interface.
Mar 17 20:44:52 systemd[1]: Starting Update UTMP about System Runlevel Changes…
Mar 17 20:44:52 ntpd[26]: proto: precision = 0.050 usec
Mar 17 20:44:52 ntpd[26]: 0.0.0.0 c01d 0d kern kernel time sync enabled
Mar 17 20:44:52 systemd[1]: Started Update UTMP about System Runlevel Changes.
Mar 17 20:44:52 systemd[1]: Startup finished in 1.198s.
Mar 17 20:44:52 ntpd[26]: MS-SNTP signd operations currently block ntpd degrading service to all clients.
Mar 17 20:44:52 samba[25]: samba version 4.9.18 started.
Mar 17 20:44:52 samba[25]: Copyright Andrew Tridgell and the Samba Team 1992-2018
Mar 17 20:44:53 samba[25]: binary_smbd_main: samba: using ‘standard’ process model
Mar 17 20:44:53 winbindd[42]: [2022/03/17 20:44:53.439996, 0] …/source3/winbindd/winbindd_cache.c:3161(initialize_winbindd_cache)
Mar 17 20:44:53 winbindd[42]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Mar 17 20:44:53 winbindd[42]: [2022/03/17 20:44:53.447703, 0] …/lib/util/become_daemon.c:136(daemon_ready)
Mar 17 20:44:53 winbindd[42]: daemon_ready: daemon ‘winbindd’ finished starting up and ready to serve connections
Mar 17 20:44:53 smbd[32]: [2022/03/17 20:44:53.493391, 0] …/lib/util/become_daemon.c:136(daemon_ready)
Mar 17 20:44:53 smbd[32]: daemon_ready: daemon ‘smbd’ finished starting up and ready to serve connections
Mar 17 20:59:55 systemd[1]: Starting Cleanup of Temporary Directories…
Mar 17 20:59:55 systemd[1]: Started Cleanup of Temporary Directories.
Mar 17 21:23:27 systemd[1]: Created slice system-nsdc\x2drun.slice.
Mar 17 21:23:27 systemd[1]: Started nsdc-run worker process.
Mar 17 21:23:28 systemd[1]: Started nsdc-run worker process.
Mar 17 21:23:29 systemd[1]: Started nsdc-run worker process.
Mar 17 21:23:29 systemd[1]: Started nsdc-run worker process.
Mar 17 21:23:29 systemd[1]: Started nsdc-run worker process.
Mar 17 21:23:30 systemd[1]: Started nsdc-run worker process.
Ran those and finished without error, but same issue remained.
Though i was able to create the test user, i can not login with that account either. In SOGo it says the credentials are incorrect, and Nextcloud still internal error.
I am not really sure what exactly was the issue, but there was a rouge DHCP on the network. Once i did shut down that and rebooted the Nethserver the issue went away.
Thank you very much Markus to point me to the right direction and most of all staying on it even so late in the evening