Re: [SOGo] Debian 13 / SOGo / 500 error

["Oli Z."]

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 (odhia...@gmail.com):

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 <users@sogo.nu> 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,

    19 Quai Perrache 69002 Lyon
    www.alinto.com <http://www.alinto.com>

    -----Original Message-----
    From: users-requ...@sogo.nu <users-requ...@sogo.nu> On Behalf Of
    qhivert
    Sent: lundi 5 janvier 2026 14:41
    To: users@sogo.nu
    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>

    -----Original Message-----
    From: users-requ...@sogo.nu <users-requ...@sogo.nu> On Behalf Of
    "Oli Z."
    Sent: lundi 5 janvier 2026 12:37
    To: users@sogo.nu
    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." (o...@trustserv.de):
    > 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 (qhiv...@alinto.eu):
    >> 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 '^$|^.*#' ¯\_(ツ)_/¯ :-)

-- Quentin Hivert || Alinto || R&D Lead Developer [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]

smime.p7s
Description: Kryptografische S/MIME-Signatur