Title: BTS activities for Tuesday, February 05 2019
BTS Activities
Home page: http://www.sogo.nu/bugs
Project: SOGo
For the period covering: Tuesday, February 05 2019
idlast updatestatus (resolution)categorysummary
Christian,
I'm using mailcow dockerized.
When I change PREFORK, nothing happens... number of process is the same.
I changed WOWorkersCount to 100 and I have 101 proccess's
[root@mail ~]# ps -ef | grep -i sogo | wc -l
101
What's recommended workers to 280 mailboxes?
This is
Hi all,
We are currently using the latest nightly SOGo release 4.0.5, and came
all the way from version 2.something. We did not face any major issues
ever since.
Unfortunately at some point one of the updates seems to have broken a
part of the calendar sharing functionality.
All users are
Hello
This means, you do not have enough workers running.
Beware WOWorkersCount in sogo.conf only affects SOGo when running in
manual debug mode.
Check your default configuration used on startup.
On Debian/Ubuntu systems you will find it in /etc/default/sogo
Value PREFORK will set the amount of
Hi again,
I have constantly with bellow error:
sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR]
<0x0x56396fb74f00[WOWatchDog]> No child available to handle incoming request!
sogo-mailcow_1 | Feb 5 11:38:30 05e81f192545 sogod [11]: [ERROR]
Thank you for the clarification. __
Regards,
Pedro Antunes
On 05/02/2019, 08:08, "users-requ...@sogo.nu on behalf of Christian Mack"
wrote:
Hello
You use ActiveSync.
ActiveSync blocks one worker for long times.
Those messages are normal then.
So nothing to worry
On Ubuntu:
wash@lists:~$ apt list | grep gnustep | grep installed
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
gnustep-base-common/bionic,now 1.25.1-2ubuntu3 all [installed,automatic]
gnustep-base-runtime/bionic,now 1.25.1-2ubuntu3 amd64 [installed,automatic]
Hello
You use ActiveSync.
ActiveSync blocks one worker for long times.
Those messages are normal then.
So nothing to worry about, as long as you don't get:
... [WARN] <0x0x56316ad28f30[WOWatchDogChild]> safety belt -- sending
KILL signal to pid 18838
Only then is your worker killed, because it
