Title: BTS activities for Tuesday, January 24 2017
BTS Activities
Home page: http://www.sogo.nu/bugs
Project: SOGo
For the period covering: Tuesday, January 24 2017
idlast updatestatus (resolution)categorysummary
You would think so, but no :D
The query in the cronjob is rounding down to the full minute and then takes the
range from then to -5 mins.
So the alarm may come a bit late (at the event start time or shortly after),
but it is sent.
Since I have only a small setup and use these notifications
On 2017-01-24 1:42 AM, Greg Kunyavsky (gr...@kgbconsulting.ca) wrote:
I am no closer to finding the issue, but I am getting this message
pretty consistently
*** stack smashing detected ***: /usr/sbin/sogod terminated
But no core file.
Try starting SOGo from gdb - so don't reduce the number
23.01.2017 22:35, Ludovic Marcotte (lmarco...@inverse.ca) пишет:
> The Inverse Team is pleased to announce the immediate availability of
> SOGo v3.2.6. This is a minor release of SOGo which focuses on various
> enhancements and improved stability over previous versions.
Where is the tag in git?
I am no closer to finding the issue, but I am getting this message
pretty consistently
*** stack smashing detected ***: /usr/sbin/sogod terminated
But no core file. How do I get a core dump?
I tried setting ulimit and /proc/sys/kernel/core_pattern
root@mail01:~#ulimit -c unlimited
I have upgraded to 2.3.17 an since the upgrade I see a lots of errors
like this in the sogo.log:
Jan 24 07:32:25 sogod [1963]: [ERROR] >UIxCalListingActions> event
'04008200E00074C5B7101A82E008102F1AD3A8F7D1011000696C4B6963CA5D458C7B4BA9A14467C8'
has a computed
Am 24.01.2017 um 07:35 schrieb Konrad Mauz:
I have upgraded to 2.3.17 an since the upgrade I see a lots of errors
Sorry. I upgraded from 2.3.17 to 2.3.19 this morning ;-)
like this in the sogo.log:
Jan 24 07:32:25 sogod [1963]: [ERROR] >UIxCalListingActions> event
