Re: [SOGo] Alarm notify - repeating events

[Pierre Fumet]

Hello,
i also receive 6 times any alarm notification since a while.
I'm running 3.2.5.20170123-1 on Debian 8 with posgresql.

Is there's a bug opened about this specific issue = 6 clone notifications ?


On 24 January 2017 at 18:53, Christoph Kreutzer wrote :

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 only several hours 
before fixed events (real world garbage collection ;-) ) this is fine for me. 
However I will test a newer nightly with the normal job when I come to it.

Regards,
Christoph


Am 23.01.2017 um 08:06 schrieb Ralf Cirksena (c...@holmco.de) :

On Fri, Jan 20, 2017 at 03:09:45PM +0100 you wrote:


What I also observed was that the reminder with the default cron job (every 
minute) was send six times, because the tool uses a 5 minute window (seen it in 
the source code). I now changed to cron job to run every 6 mins at that is fine 
now. However, it???s a kind of weird.


What do you do with arlarms set to 3..5 minutes prior to the event? I guess you 
may miss a few alarms.


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

Re: [SOGo] Alarm notify - repeating events

[Christoph Kreutzer]

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 only several hours 
before fixed events (real world garbage collection ;-) ) this is fine for me. 
However I will test a newer nightly with the normal job when I come to it.

Regards,
Christoph

> Am 23.01.2017 um 08:06 schrieb Ralf Cirksena (c...@holmco.de) :
> 
> On Fri, Jan 20, 2017 at 03:09:45PM +0100 you wrote:
> 
>> What I also observed was that the reminder with the default cron job (every 
>> minute) was send six times, because the tool uses a 5 minute window (seen it 
>> in the source code). I now changed to cron job to run every 6 mins at that 
>> is fine now. However, it???s a kind of weird.
> 
> What do you do with arlarms set to 3..5 minutes prior to the event? I
> guess you may miss a few alarms.
> 
> 
> Regards
> -- 
> R. Cirksena 
> -- 
> users@sogo.nu
> https://inverse.ca/sogo/lists

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

Re: [SOGo] Alarm notify - repeating events

[Ralf Cirksena]

On Fri, Jan 20, 2017 at 03:09:45PM +0100 you wrote:

> What I also observed was that the reminder with the default cron job (every 
> minute) was send six times, because the tool uses a 5 minute window (seen it 
> in the source code). I now changed to cron job to run every 6 mins at that is 
> fine now. However, it???s a kind of weird.

What do you do with arlarms set to 3..5 minutes prior to the event? I
guess you may miss a few alarms.


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

Re: [SOGo] Alarm notify - repeating events

[Fabio Onorini]

Hello Christoph,
my problem is on reminder events.
So if I create a daily event, that start monday at 16:00, with alarm 5
minutes before event start, the system add record in alarms_folder table
with alarm_date monday at 15:55, but after mail sent, the record doesn't
become tuesday at 15:55.

I also noticed the problem that the alarm is sent 6 times, but if the
system would eliminate/update the records after sending the email, the
problem will solve automatically.


2017-01-20 15:09 GMT+01:00 Christoph Kreutzer :

> Hi Fabio,
>
> I’m testing this functionality also. I think in my case the update to the
> new time is working, as the most reminders are now scheduled for the next
> week. But I also have entries from the first week of january.
>
> What I also observed was that the reminder with the default cron job
> (every minute) was send six times, because the tool uses a 5 minute window
> (seen it in the source code). I now changed to cron job to run every 6 mins
> at that is fine now. However, it’s a kind of weird.
>
> I think I need more thorough testing here, however I’m short on time at
> the moment.
>
> Regards,
> Christoph
>
> Am 19.01.2017 um 10:48 schrieb Fabio Onorini (onofa...@gmail.com) <
> users@sogo.nu>:
>
> ... in addition to the previous reporting
> I would expect that expired alarms on non-recurring events are deleted
> from the table sogo_alarms_folder, but this does not happen.
>
> 2017-01-19 10:33 GMT+01:00 Fabio Onorini :
>
>> Hello sogo users,
>> I have some problems with events alarm.
>>
>> After upgrade to version 3.2.5, the system correctly add record in
>> sogo_alarms_folder table and cron script send mail.
>> The problem occured on recurring events. The record was not updated with
>> new alarm_date (next occurence).
>>
>> But on bugtracker the issue #1053 (https://sogo.nu/bugs/view.php?id=1053)
>> was updated to resolved status.
>>
>> Have you my same problem?
>>
>> --
>>
>> Fabio Onorini
>>
>
>
>
> --
>
> Fabio Onorini
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
>
>
> --
> users@sogo.nu
> https://inverse.ca/sogo/lists
>



-- 

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

Re: [SOGo] Alarm notify - repeating events

[Christoph Kreutzer]

Hi Fabio,

I’m testing this functionality also. I think in my case the update to the new 
time is working, as the most reminders are now scheduled for the next week. But 
I also have entries from the first week of january.

What I also observed was that the reminder with the default cron job (every 
minute) was send six times, because the tool uses a 5 minute window (seen it in 
the source code). I now changed to cron job to run every 6 mins at that is fine 
now. However, it’s a kind of weird.

I think I need more thorough testing here, however I’m short on time at the 
moment.

Regards,
Christoph

> Am 19.01.2017 um 10:48 schrieb Fabio Onorini (onofa...@gmail.com) 
> :
> 
> ... in addition to the previous reporting
> I would expect that expired alarms on non-recurring events are deleted from 
> the table sogo_alarms_folder, but this does not happen.
> 
> 2017-01-19 10:33 GMT+01:00 Fabio Onorini  >:
> Hello sogo users,
> I have some problems with events alarm.
> 
> After upgrade to version 3.2.5, the system correctly add record in 
> sogo_alarms_folder table and cron script send mail.
> The problem occured on recurring events. The record was not updated with new 
> alarm_date (next occurence).
> 
> But on bugtracker the issue #1053 (https://sogo.nu/bugs/view.php?id=1053 
> ) was updated to resolved status.
> 
> Have you my same problem?
> 
> -- 
> 
> Fabio Onorini
> 
> 
> 
> -- 
> 
> Fabio Onorini
> -- 
> users@sogo.nu 
> https://inverse.ca/sogo/lists 
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

[SOGo] Alarm notify - repeating events

[Fabio Onorini]

Hello sogo users,
I have some problems with events alarm.

After upgrade to version 3.2.5, the system correctly add record in
sogo_alarms_folder table and cron script send mail.
The problem occured on recurring events. The record was not updated with
new alarm_date (next occurence).

But on bugtracker the issue #1053 (https://sogo.nu/bugs/view.php?id=1053)
was updated to resolved status.

Have you my same problem?

-- 

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

Re: [SOGo] Alarm notify - repeating events

[Fabio Onorini]

... in addition to the previous reporting
I would expect that expired alarms on non-recurring events are deleted from
the table sogo_alarms_folder, but this does not happen.

2017-01-19 10:33 GMT+01:00 Fabio Onorini :

> Hello sogo users,
> I have some problems with events alarm.
>
> After upgrade to version 3.2.5, the system correctly add record in
> sogo_alarms_folder table and cron script send mail.
> The problem occured on recurring events. The record was not updated with
> new alarm_date (next occurence).
>
> But on bugtracker the issue #1053 (https://sogo.nu/bugs/view.php?id=1053)
> was updated to resolved status.
>
> Have you my same problem?
>
> --
>
> Fabio Onorini
>



-- 

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