Created attachment 189503 [details]
Upgrading from sogo-3.2.8 to 3.2.9 and 3.2.10 is successful but login fails with Unhandled error response and the following error from sogo log
[WOWatchDogChild]> (terminated due to signal 6)
I have a similar problem after upgrade
~ # uname -v
FreeBSD 11.1-STABLE #0 r328533: Mon Jan 29 13:47:58 MSK 2018 root@mx1:/usr/obj/usr/src/sys/GENERIC
~ # pkg info sogo3
Name : sogo3
Version : 3.2.10_2
Installed on : Wed Jan 31 12:45:29 2018 MSK
Origin : www/sogo3
Architecture : FreeBSD:11:amd64
Prefix : /usr/local
Categories : gnustep www
Licenses : GPLv2
Maintainer : firstname.lastname@example.org
WWW : http://sogo.nu/
Comment : Groupware server with a focus on scalability and open standards
ACTIVESYNC : off
Shared Libs required:
Shared Libs provided:
repo_type : binary
repository : FreeBSD
Flat size : 48.4MiB
SOGo is a fully supported and trusted groupware server with a focus on
scalability and open standards. It provides a rich AJAX-based Web
interface and supports multiple native clients through the use of
standard protocols such as CalDAV, CardDAV and GroupDAV.
Jan 31 13:18:00 sogod : <0x0x80ca92b90[WOWatchDogChild]> child 24500 exited
Jan 31 13:18:00 sogod : <0x0x80ca92b90[WOWatchDogChild]> (terminated due to signal 6)
Jan 31 13:18:00 sogod : <0x0x80b269410[WOWatchDog]> child spawned with pid 24505
I can confirm the issue! this is since the last changes in the gnustep/libobjc (cc the committer from that change). also note that SOGo works if you rebuild it with WITH_DEBUG, which may make it hard to fix.
Can anyone else confirm whether this is still an issue in the current port version (3.2.10_2)? I am the port maintainer and I only upgraded myself recently to latest versions of both 2.x and 3.x. I was too busy for a long time to stay current with sogo versions since my production servies ran great for me. The latest ports work fine for me in my personal server, albeit with light usage. But logging in is fine.
Off topic, but I'm just about to submit sogo4 ports (the sogo2 and sogo3 ports will remain active, since I still use sogo2 by preference).
This port is expired and has been removed, can you retry with www/sogo4 instead?
(In reply to Rene Ladan from comment #4)
I can confirm that I had no issues with sogo4