[SOGo] BTS activities for Friday, April 23 2021

[SOGo reporter]

Title: BTS activities for Friday, April 23 2021





  
BTS Activities

  Home page: https://sogo.nu/bugs
  Project: SOGo
  For the period covering: Friday, April 23 2021

  
  
idlast updatestatus (resolution)categorysummary
	
	
	  
	
5305
	2021-04-23 04:13:10
	updated (open)
	ActiveSync
	Spike of IMAP sessions at first EAS sync
	
	  
	
5133
	2021-04-23 11:55:18
	updated (open)
	Backend Calendar
	task-only list is visible in calendar
	
	  
	
5306
	2021-04-23 05:35:14
	updated (open)
	Web Mail
	Return receipt (Disposition-Notification-To) not handled by the webmail
	
	  
	
  
  


-- users@sogo.nuhttps://inverse.ca/sogo/lists

[SOGo] SOGo grokking

[Odhiambo Washington]

A brand new server, SOGO-5.0.1 groks badly:

https://pastebin.ubuntu.com/p/xrYQkZrp4d/

Might someone be able to figure out what is going on?




-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Re: [SOGo] database performance

[Sven Schwedas]

On 23.04.21 15:20, infoomatic (infooma...@gmx.at) wrote:

Hi,

I have been a big fan of postgresql for more than 10 years now. Out of
interest, did anyone do any performance tests on SOGo like postgresql vs
mariadb/mysql ... are there any significant differences?



We didn't do any formal benchmarks, but we moved from running SOGo on 
MySQL to Postgres a few years back and didn't notice any meaningful 
performance difference. Sogo's typical workloads don't really favour one 
or the other as far as I can tell.




OpenPGP_signature
Description: OpenPGP digital signature

[SOGo] database performance

[infoomatic]

Hi,

I have been a big fan of postgresql for more than 10 years now. Out of
interest, did anyone do any performance tests on SOGo like postgresql vs
mariadb/mysql ... are there any significant differences?

Regards,

infoomatic

-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] sogo systemd logrotation issue

[mj]

Hi,

We're running sogo 5 on an upgraded squeeze -> jessie -> stretch -> 
buster system, our init system is now systemd, and it uses a 'generated' 
unit file for sogo:



root@sogo:/etc/logrotate.d# systemctl list-unit-files | grep sogo
sogo.service generated


Now, we occasionally get this midnight error from logrotate, after log 
rotation:



Apr 23 00:02:14 sogo systemd[1]: sogo.service: Found left-over process 28417 
(sogod) in control group while starting unit. Ignoring.
Apr 23 00:02:14 sogo systemd[1]: This usually indicates unclean termination of 
a previous run, or service implementation deficiencies.
Apr 23 00:02:14 sogo systemd[1]: sogo.service: Found left-over process 28418 
(sogod) in control group while starting unit. Ignoring.
Apr 23 00:02:14 sogo systemd[1]: This usually indicates unclean termination of 
a previous run, or service implementation deficiencies.
Apr 23 00:02:14 sogo systemd[1]: sogo.service: Found left-over process 28419 
(sogod) in control group while starting unit. Ignoring.
Apr 23 00:02:14 sogo systemd[1]: This usually indicates unclean termination of 
a previous run, or service implementation deficiencies.


This causes the logrotate sogo postrotate script ("/bin/systemctl 
restart sogo.service") to fail, and after that sogo is no longer 
running. :-(


I now created a script to verify that sogo is running, and restart it if 
it is not. But solving the issue at it's root (the failing restart) 
would be much better.


Anyone here experienced the same..? And how did you solve it?

Thanks and enjoy your weekend, everybody!

MJ
--
users@sogo.nu
https://inverse.ca/sogo/lists