[SOLVED] Sogo "Request failed" after update

NethServer release 7.9.2009 (final)

SOGO version 5.6.0

Updating on Wednesday:

nethserver-mail-common noarch 2.32.0-1.ns7 nethserver-updates 1.5 M
nethserver-mail-filter noarch 2.32.0-1.ns7 nethserver-updates 95 k
nethserver-mail-getmail noarch 2.32.0-1.ns7 nethserver-updates 54 k
nethserver-mail-p3scan noarch 2.32.0-1.ns7 nethserver-updates 53 k
nethserver-mail-server noarch 2.32.0-1.ns7 nethserver-updates 133 k
nethserver-mail-smarthost noarch 2.32.0-1.ns7 nethserver-updates 60 k
rspamd x86_64 3.2-1 nethserver-updates 6.2 M
sogo x86_64 5.6.0-1.ns7 nethforge 20 M
sogo-activesync x86_64 5.6.0-1.ns7 nethforge 143 k
sogo-ealarms-notify x86_64 5.6.0-1.ns7 nethforge 17 k
sogo-tool x86_64 5.6.0-1.ns7 nethforge 61 k
sope49-appserver x86_64 1:4.9-5.6.0.1.ns7 nethforge 924 k
sope49-cards x86_64 5.6.0-1.ns7 nethforge 209 k
sope49-core x86_64 1:4.9-5.6.0.1.ns7 nethforge 349 k
sope49-gdl1 x86_64 1:4.9-5.6.0.1.ns7 nethforge 173 k
sope49-gdl1-contentstore x86_64 5.6.0-1.ns7 nethforge 68 k
sope49-gdl1-mysql x86_64 1:4.9-5.6.0.1.ns7 nethforge 38 k
sope49-ldap x86_64 1:4.9-5.6.0.1.ns7 nethforge 54 k
sope49-mime x86_64 1:4.9-5.6.0.1.ns7 nethforge 306 k
sope49-sbjson x86_64 1:2.3.1-5.6.0.1.ns7 nethforge 21 k
sope49-xml x86_64 1:4.9-5.6.0.1.ns7 nethforge 208 k

After that login Sogo web > OK
And than open emails > OK
… but after ~ 5 min I see the last opened email, but it is not possible to open another email or create a new one …>> “Request failed !” on a black window
… I have to login again and … if I need too long to write an email “Request failed” …
I tried to get more WOWorkers (from 25 >> 50) , but this is not the reason, get the same alert
There is nextcloud too on nethserver → no problems !

systemctl status sogod

● sogod.service - SOGo is a groupware server
Loaded: loaded (/usr/lib/systemd/system/sogod.service; enabled; vendor preset: disabled)
Active: active (running) since Thu 2022-06-02 15:39:13 CEST; 19min ago
Process: 1268 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -WOPidFile /var/run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log (code=exited, status=0/SUCCESS)
Main PID: 1559 (sogod)
CGroup: /system.slice/sogod.service
├─1559 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1673 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1674 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1675 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1676 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1678 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1679 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1686 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1688 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1689 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1690 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1691 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1692 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1700 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1701 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1708 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1711 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1712 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1726 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1727 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1728 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1729 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1744 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1745 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1747 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1762 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1764 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1773 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1774 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1777 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1785 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1787 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1793 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1794 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1795 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1796 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1798 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1812 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1813 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1819 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1821 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1833 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1834 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1835 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1846 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1848 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1849 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1851 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1859 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
├─1860 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…
└─1861 /usr/sbin/sogod -WOWorkersCount 50 -WOPidFile /var/run/sogo…

Jun 02 15:39:13 msrv.eds.lan systemd[1]: Starting SOGo is a groupware server…
Jun 02 15:39:13 msrv.eds.lan systemd[1]: Can’t open PID file /var/run/sogo/s…y
Jun 02 15:39:13 msrv.eds.lan systemd[1]: Started SOGo is a groupware server.
Hint: Some lines were ellipsized, use -l to show in full.

1 Like

Same issue all of my Nethserver installations. Everything woks exept the SOGo web interface.

For @stephdl my SOGo 2.6 will not display/refresh the screen after ~5 minutes of logging in. If I delete the cookies and refresh I am able to login and see the web interface until it times out again. I am using Win 11 Chrome. My activesync/Outlook client works as expected. Let me know what logs you are after.

Upgrading
The session table ( OCSSessionsFolderURL ) must be dropped prior to restart sogod. This will allow users to use larger passwords (up to 2048 characters).

https://www.sogo.nu/bugs/view.php?id=5528

1 Like

could you reproduce @dnutan

Sorry, I don’t have SOGo (tagged the post as bug but we can change it if it is not)

1 Like

it seems I can reproduce it

I can confirm I have the same issue.

[root@prometheus ~]# mysql 
MariaDB [(none)]> use sogo;
MariaDB [sogo]> drop table if exists sogo_sessions_folder;
Query OK, 0 rows affected (0.07 sec)
MariaDB [sogo]> exit
Bye
[root@prometheus ~]# killall sogod
[root@prometheus ~]# systemctl start sogod

it seems good by dropping the table and restarting sogod

3 Likes

testing, fingers crossed :wink:

1 Like

After 10 minutes of inactivity, the SOGo UI responds good again with no errors.

I won’t tick the solution box for more confirmation from others would be nice.

2 Likes

This resolved my issue. Thank you.

1 Like

Thank you for your help, now everything working fine! Thanks again!

1 Like

We need to push a fix for everybody

read your emails and tried at 8 o’clock:
till now sogo is OK

THANKS TO ALL THAT GOOD BOYS

1 Like

hello world, someone to test

yum install http://packages.nethserver.org/nethserver/7.9.2009/nethforge-autobuild/x86_64/Packages/nethserver-sogo-1.8.5-1.16.pr57.g9730315.ns7.noarch.rpm

once installed, trigger signal-event nethserver-sogo-update

you must have no error in messages log for the event nethserver-sogo-update and the action nethserver-sogo-MigrationV5.3.0ToV5.6.0

Jun  3 16:53:11 prometheus esmith::event[23165]: Action: /etc/e-smith/events/nethserver-sogo-update/S31nethserver-sogo-MigrationV5.3.0ToV5.6.0 SUCCESS [0.021977]

the table must exist at the end

[root@prometheus ~]# ll /var/lib/mysql/sogo/sogo_sessions_folder.frm 
-rw-rw---- 1 mysql mysql 20976 Jun  3 16:53 /var/lib/mysql/sogo/sogo_sessions_folder.frm
3 Likes

Can I test this despite I have performed the workaround?

Yes it is possible, the goal is to verify that the table is dropped then created again. An authenticated user must authenticate again because his session will be removed

2 Likes

I can confirm that for me the issue has been resolved. Many thanks @stephdl !

3 Likes

i also can confirm this fixed it :slight_smile:

1 Like