Am 06.01.26 um 14:04 schrieb Washington Odhiambo ([email protected]):
Please remember, I was responding to Quentin's question about "Debian repo directly -> https://packages.debian.org/trixie/sogo";This package is not from Alinto, as he stated.So in my case I suppose he doesn't need the debug info, which I believe he only needed for the SOGo packaged by Alinto.root@debianPC:/home/wash/public_html# cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian trixie main The details you asked for are below: root@debianPC:/home/wash# uname -aLinux debianPC.wash.lan 6.12.57+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.57-1 (2025-11-05) x86_64 GNU/Linuxroot@debianPC:/home/wash# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 13 (trixie)" NAME="Debian GNU/Linux" VERSION_ID="13" VERSION="13 (trixie)" VERSION_CODENAME=trixie DEBIAN_VERSION_FULL=13.2 ID=debian HOME_URL="https://www.debian.org/"; SUPPORT_URL="https://www.debian.org/support"; BUG_REPORT_URL="https://bugs.debian.org/"; root@debianPC:/home/wash# cat /etc/debian_version 13.2 root@debianPC:/home/wash# dpkg -l | grep -i sogoii sogo 5.12.1-3 amd64 Scalable groupware server ii sogo-activesync 5.12.1-3 amd64 Scalable groupware server - ActiveSync module ii sogo-common 5.12.1-3 all Scalable groupware server - common filesroot@debianPC:/home/wash# systemctl status sogo ● sogo.service - SOGo is a groupware serverLoaded: loaded (/usr/lib/systemd/system/sogo.service; enabled; preset: enabled) Active: active (running) since Tue 2026-01-06 12:44:26 EAT; 2h 58min agoInvocation: b45caa89337948bda6b8450b3087dfed Docs: https://sogo.nu/files/docs/SOGoInstallationGuide.htmlProcess: 1270846 ExecStart=/usr/sbin/sogod -WOWorkersCount ${PREFORK} -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log (code=exited, status=0/SUCCESS)Main PID: 1270856 (sogod) Tasks: 4 (limit: 4460) Memory: 53M (peak: 55M) CPU: 11.297s CGroup: /system.slice/sogo.service├─1270856 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log ├─1270858 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log ├─1270859 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.log └─1270860 /usr/sbin/sogod -WOWorkersCount 3 -WOPidFile /run/sogo/sogo.pid -WOLogFile /var/log/sogo/sogo.logJan 06 12:44:26 debianPC.wash.lan systemd[1]: Starting sogo.service - SOGo is a groupware server... Jan 06 12:44:26 debianPC.wash.lan systemd[1]: Started sogo.service - SOGo is a groupware server.root@debianPC:/home/wash# root@debianPC:/home/wash/public_html# systemctl stop sogo root@debianPC:/home/wash/public_html# cp /dev/null /var/log/sogo/sogo.log root@debianPC:/home/wash/public_html# systemctl start sogo root@debianPC:/home/wash/public_html# less /var/log/sogo/sogo.log Jan 06 16:01:17 sogod [1358483]: version 5.12.1 -- startingJan 06 16:01:17 sogod [1358483]: vmem size check enabled: shutting down app when vmem > 4096 MB. Currently at 94 MB *Jan 06 16:01:17 sogod [1358483]: <0x0x556965133650[SOGoProductLoader]> SOGo products loaded from '/usr/lib/x86_64-linux-gnu/GNUstep/SOGo':* Jan 06 16:01:17 sogod [1358483]: <0x0x556965133650[SOGoProductLoader]> MailPartViewers.SOGo, PreferencesUI.SOGo, CommonUI.SOGo, AdministrationUI.SOGo, MailerUI.SOGo, SchedulerUI.SOGo, ActiveSync.SOGo, Contacts.SOGo, MainUI.SOGo, ContactsUI.SOGo, Mailer.SOGo, Appointments.SOGo Jan 06 16:01:17 sogod [1358483]: All products loaded - current memory usage at 102 MB Jan 06 16:01:17 sogod [1358483]: <0x0x556965156c90[WOWatchDog]> listening on 127.0.0.1:20000 <http://127.0.0.1:20000> Jan 06 16:01:17 sogod [1358483]: <0x0x556965156c90[WOWatchDog]> watchdog process pid: 1358483 Jan 06 16:01:17 sogod [1358483]: <0x0x7fb5de2b20e0[WOWatchDogChild]> watchdog request timeout set to 10 minutes Jan 06 16:01:17 sogod [1358483]: <0x0x556965156c90[WOWatchDog]> preparing 3 children Jan 06 16:01:17 sogod [1358483]: <0x0x556965156c90[WOWatchDog]> child spawned with pid 1358484 Jan 06 16:01:17 sogod [1358483]: <0x0x556965156c90[WOWatchDog]> child spawned with pid 1358485 Jan 06 16:01:17 sogod [1358483]: <0x0x556965156c90[WOWatchDog]> child spawned with pid 1358486 Jan 06 16:01:22 sogod [1358485]: <0x0x5569651934a0[WOHttpAdaptor]> notified the watchdog that we are ready Jan 06 16:01:22 sogod [1358486]: <0x0x5569651934a0[WOHttpAdaptor]> notified the watchdog that we are ready Jan 06 16:01:23 sogod [1358484]: <0x0x5569651934a0[WOHttpAdaptor]> notified the watchdog that we are ready/var/log/sogo/sogo.logI am using the same. With MySQL for authentication and PostgreSQL for SOGo stuff storage. I am using Nginx, not Apache. My Nginx.conf: https://paste.ubuntu.com/p/fDrZtX5FQ5/My sogo.conf: I already shared it - On Tue, Jan 6, 2026 at 3:36 PM "Oli Z." <[email protected]> wrote: Could you add those debug flags, run it and then send them to Quentin? IMO this should not be possible that it runs for you when its a problem in the ObjectiveC-Library. Can you tell me what you exactly did? How did you install SOGo? Please provide: uname -a dpkg -l | grep -i sogo your apache2 config your sogo config Thanks! Am 06.01.26 um 10:56 schrieb Washington Odhiambo ([email protected]): > I tested it on a Debian Trixie VM and it's working fine - so far. > > > > On Mon, Jan 5, 2026 at 6:32 PM qhivert <[email protected]> wrote: > > Hello, > > After some exchange with Oli and new logs files, it seems there is > a problem > with a method defined by the gnustep objective-c library. I know > there has > been some changes with Gnustep/objective-c in Debian 13. > > Alinto doesn't provide a Sogo package for Debian 13 yet but there > is one in > Debian repo directly -> https://packages.debian.org/trixie/sogo > > Has anyone use it successfully ? > > Cheers, > -- > Quentin Hivert || Alinto || R&D Lead Developer > 19 Quai Perrache 69002 Lyon > www.alinto.com <http://www.alinto.com> <http://www.alinto.com> > > -----Original Message----- > From: [email protected] <[email protected]> On Behalf Of > qhivert > Sent: lundi 5 janvier 2026 14:41 > To: [email protected] > Subject: RE: [SOGo] Debian 13 / SOGo / 500 error > > Well, no errors in your log, I've tested your sogo.conf and it > works well... > > Either there is something very obvious that I don't see, or you > found a very > peculiar bug. > > Put that in your sogo.conf and reproduce the problem. > > SoObjectRequestHandlerDebugEnabled = YES; > SoSelectorInvocationDebugEnabled = YES; > SoDebugRequestClassification = YES; > SoDebugObjectTraversal = YES; > SOGoDebugRequests = YES; > ImapDebugEnabled = YES; > ImapLogEnabled = YES; > MySQL4DebugEnabled = YES; > SOGoUIxDebugEnabled = YES; > SoObjectMethodDispatcherDebugEnabled = YES; > SoPageInvocationDebugEnabled = YES; > SoRendererDebugEnabled = YES; > WOLogComponents = YES; > WODebugComponentLookup = YES; > WODebugResourceLookup = YES; > SoProductResourceManagerDebugEnabled = YES; > WOResourceURLAssociationDebugEnabled = YES; > WEResourceManagerDebugEnabled = YES; > NGLogDefaultLogLevel = "ALL"; > > Then send me the log directly (not here) in an attachment file please. > > Regards, > -- > Quentin Hivert || Alinto || R&D Lead Developer > 19 Quai Perrache 69002 Lyon > www.alinto.com <http://www.alinto.com> <http://www.alinto.com> > > -----Original Message----- > From: [email protected] <[email protected]> On Behalf Of > "Oli Z." > Sent: lundi 5 janvier 2026 12:37 > To: [email protected] > Subject: Re: [SOGo] Debian 13 / SOGo / 500 error > > update: it added now that table (empty) after setting > SOGoEnableEMailAlarms > to YES, but still the same error. > > Am 05.01.26 um 12:17 schrieb "Oli Z." ([email protected]): > > Thanks, that sounds reasonable, but the documentation says this is > > only required if SOGoEnableEMailAlarms is set. I did not set this > > flag. I added now: > > OCSEMailAlarmsFolderURL = > > "mysql://xx:xxx@localhost/sogo/sogo_alarms_folder"; - and: > > OCSAdminURL = "mysql://xx:xxx@localhost/sogo/sogo_admin"; > > > > Because i also found an error because of missing OCSAdminURL. > > Unfortunately, the error still exists. It added now the sogo_admin > > table but not the sogo_alarms_folder > > > > Am 05.01.26 um 10:35 schrieb qhivert ([email protected]): > >> Hello, > >> I think the table for alarm is missing in this case: > >> OCSEMailAlarmsFolderURL > >> > > > > -- > 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] -- 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]
smime.p7s
Description: Kryptografische S/MIME-Signatur
