Messages

16

Directory and Authentication / Zentyal 4.2 - Cannot login to web interface (SOGO)

« on: December 01, 2018, 03:37:37 pm »

Hi,

I have a Zentyal 4.2 with the following problem; Once upon a few days SOGO web interface stop to work. Users can't login to sogo (when they provide credentials and click "Login" nothing happens) until the sogo service is restarted. When this happen the sogo web interface looks broken (see the attachment). I have found hundreds of the following log lines in /var/log/sogo/sogo.log:

Code: [Select]

Nov 30 15:33:06 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944a69c48> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:01:35 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944942708> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:01:35 sogod [3601]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944e46a28> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:05:47 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944b5ecb8> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:14:23 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944c20a88> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:14:54 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x5629449e67a8> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:15:53 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x5629452165b8> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:25:47 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944ec8e28> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:30:53 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x5629448caa88> NAME:SoAuthRequired REASON:authentication required
Nov 30 18:38:26 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x5629448ed238> NAME:SoAuthRequired REASON:authentication required
Nov 30 19:00:38 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x5629449f5818> NAME:SoAuthRequired REASON:authentication required
Nov 30 19:00:40 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x5629452462b8> NAME:SoAuthRequired REASON:authentication required
Nov 30 20:15:00 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x56294495a878> NAME:SoAuthRequired REASON:authentication required
Nov 30 20:15:00 sogod [3601]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944f85348> NAME:SoAuthRequired REASON:authentication required
Nov 30 20:15:02 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x5629452096f8> NAME:SoAuthRequired REASON:authentication required
Nov 30 21:54:41 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944a56c18> NAME:SoAuthRequired REASON:authentication required
Nov 30 21:54:43 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562944dc0c08> NAME:SoAuthRequired REASON:authentication required
Nov 30 22:14:01 sogod [3602]: |SOGo|     handle miss error: <SoAuthRequiredException: 0x562945016f28> NAME:SoAuthRequired REASON:authentication required

Edit: Somehow I cannot add attachments on this forum so uploaded sogo screen here: https://www51.zippyshare.com/v/vQOJtPUO/file.html

17

Installation and Upgrades / Re: Zentyal management web interface won't start after reboot

« on: January 30, 2018, 02:51:49 pm »

I just got the same problem in Zentyal 5. After server reboot Zentyal management web interface is not working anymore. Sogo works. It seems that web managament interface uses nginx while sogo uses Apache.

/var/log/nginx/error.log:

Code: [Select]

[emerg] 4175#4175: SSL_CTX_use_PrivateKey_file("/var/lib/zentyal/conf/ssl/ssl.pem") failed (SSL: error:0B080074:x509 certificate routines:X509_check_private_key:key values mismatch)

sudo journalctl -xe:

Code: [Select]

-- Subject: Unit nginx.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit nginx.service has failed.
--
-- The result is failed.
Jan 30 15:36:11 zentyal systemd[1]: nginx.service: Unit entered failed state.
Jan 30 15:36:11 zentyal systemd[1]: nginx.service: Failed with result 'exit-code'.
Jan 30 15:36:11 zentyal sudo[3594]: pam_unix(sudo:session): session closed for user root
Jan 30 15:36:31 zentyal sudo[3608]: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: cannot open shared object
Jan 30 15:36:31 zentyal sudo[3608]: PAM adding faulty module: pam_cap.so
Jan 30 15:36:31 zentyal sudo[3608]:     kris : TTY=pts/0 ; PWD=/home/kris ; USER=root ; COMMAND=/bin/journalctl -xe
Jan 30 15:36:31 zentyal sudo[3608]: pam_unix(sudo:session): session opened for user root by kris(uid=0)

Edit:
Solved! I had to reinstall libpam-systemd... I've no idea how this could happened. I know that Ubuntu updates are always dangerous but this time it stopped working without updating anything. It looks bad for the future.