Hello, I think the table for alarm is missing in this case: OCSEMailAlarmsFolderURL
-- Quentin Hivert || Alinto || R&D Lead Developer 19 Quai Perrache 69002 Lyon www.alinto.com -----Original Message----- From: [email protected] <[email protected]> On Behalf Of "Oli Z." Sent: vendredi 2 janvier 2026 13:12 To: [email protected] Subject: Re: [SOGo] Debian 13 / SOGo / 500 error i created the mariadb db and configured sogo to use that. i can see it created the tables: MariaDB [sogo]> show tables; +-------------------------------+ | Tables_in_sogo | +-------------------------------+ | sogo_folder_info | | sogo_sessions_folder | | sogo_user_profile | | sogomedom0016dd9f714 | | sogomedom0016dd9f714_acl | | sogomedom0016dd9f714_quick | +-------------------------------+ 6 rows in set (0,001 sec) but i still get the exact same behaviour. I am wondering if it could be because of the passwords. I use special chars, so all my passwords are more or less %xy. Could it be that the backend has problems with that? It always fails with the same error: Jan 02 13:03:00 sogod [302429]: 85.xxx "GET /SOGo/so/[email protected]/Calendar/alarmslist?browserTime=1767355380 HTTP/1.1" 500 36/0 0.049 - - 340K - 14 I can execute the sql that is shown in the log MariaDB [sogo]> SELECT c_path4 FROM sogo_folder_info WHERE c_path2 = '[email protected]' AND c_folder_type = 'Appointment'; +----------+ | c_path4 | +----------+ | personal | +----------+ 1 row in set (0,001 sec) Is there any way to turn on debug logging in the backend itself? Because everything else is just wild guessing. It clearly fails in the backend, not in any way with the db. Am 31.12.25 um 13:27 schrieb "Oli Z." ([email protected]): > I am not a fan of guessing, i prefer hard facts. If i would knew that > this is caused by the db mix, i would go with mariadb or postgresql > only. But i dont know that. > > I will see, for testing purposes, if it works in mariadb only. There > is no way to get all this migrated in 2hrs with testing etc. - i have > roundcube and other applications that rely on the database. In 2 hrs i > might have the test-machine set up and running. Anyway, i will see > what happens when "everything" (SOGo) runs in mariadb. > > Am 29.12.25 um 12:33 schrieb Washington Odhiambo ([email protected]): >> I remember you said something to the effect that you only have about >> 10 or so users. >> Why don't you just setup a system based on >> Postfixadmin+PostgreSQL+SOGo, then migrate the users from MySQL? >> https://www.linuxbabe.com/mail-server/postfixadmin-ubuntu-postgresql >> It should be easier. Takes about 2hrs at most, IIRC. >> >> Alternatively, stick to MariaDB for everything. >> >> >> >> On Sun, Dec 28, 2025 at 8:37 PM Oli <[email protected]> wrote: >> >> No i did not >> >> >> Am 28. Dezember 2025 12:36:09 UTC schrieb Washington Odhiambo >> <[email protected]>: >> >> You resolved this issue already, I suppose. >> >> >> On Sun, Dec 28, 2025 at 3:25 PM "Oli Z." <[email protected]> wrote: >> >> See my last log, thats exactly this >> >> Am 24.12.25 um 09:15 schrieb Washington Odhiambo >> ([email protected]): >> > >> > >> > On Wed, Dec 24, 2025 at 11:07 AM "Oli Z." >> <[email protected]> wrote: >> > >> > > I have never used a mixed DB setup where some >> stuff is in MySQL >> > while >> > others are in PostGreSQL. >> > >> > It should make no difference if the users are >> authenticated via ldap, >> > mysql or postgresql. I mean thats how its supposed >> to work, isnt it. >> > >> > >> > True. As long as SOGo can make the connections. >> > >> > I use sha512-crypt in my db - to what should i >> change it in SOGo >> > then? >> > Does SOGo automatically detect what is used? >> > The authentication against sql works. I get an 500 >> from SOGo after >> > authentication. That means, the authentication >> should work >> > including the >> > configuration (e.g. password hash). At least thats >> how i >> > understand it. >> > >> > >> > You are at that point where: >> > >> > SOGoDebugRequests = YES; >> > ImapDebugEnabled = YES; >> > PGDebugEnabled = YES; >> > MySQL4DebugEnabled = YES; >> > >> > Wil be helpful. >> > >> > >> > >> > >> > -- >> > Best regards, >> > Odhiambo WASHINGTON, >> > Nairobi,KE >> > +254 7 3200 0004/+254 7 2274 3223 >> > In an Internet failure case, the #1 suspect is a >> constant: DNS. >> > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) >> > [How to ask smart questions: >> > http://www.catb.org/~esr/faqs/smart-questions.html] >> >> >> >> -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 >> Mail gesendet. >> >> >> >> -- >> Best regards, >> Odhiambo WASHINGTON, >> Nairobi,KE >> +254 7 3200 0004/+254 7 2274 3223 >> In an Internet failure case, the #1 suspect is a constant: DNS. >> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) >> [How to ask smart questions: >> http://www.catb.org/~esr/faqs/smart-questions.html]
