[Dxspider-support] Local announcement not appearing to users

Sun Sep 15 16:12:18 BST 2024

It’s the de-duplication that’s causing it.

As a workaround, add this command into your crontab a few minutes before your announcement.

run_cmd("clear/dupefile”)

So if your announcement is every two hours

45 00,03,06,09,12,15,18,21 * * * run_cmd('Announce G6NHU-2 downtime on 27th August between 08:00z to 13:30z - Current time is ' . cldate . ' ' . ztime)

You’d add this:

40 00,03,06,09,12,15,18,21 * * * run_cmd("clear/dupefile”)

That way, the dupe file is cleared at 40 minutes past the hour and then your local announcement is made five minutes later.

Be aware that this is opening you to more duplications across the network.

I think you’re right, local sysop announcements don’t really need to go through the dupe checking.

73 Keith

> On 15 Sep 2024, at 15:52, IZ2LSC via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
> 
> I'm having the same issue even if the messages are different (I
> inserted a time stamp).
> It's not good at all that sysop local announces are dropped!!!
> 
> 73
> Andrea
> 
> -->
> 
> Il giorno sab 8 giu 2024 alle ore 20:24 Keith Maton via
> Dxspider-support <dxspider-support at tobit.co.uk> ha scritto:
>> 
>> Yeah, I think that’s what’s happening but even with three very different messages, I suspect they’re getting flagged as dupes and not being passed to my users.
>> 
>> I’ve set up these three, all with the time on the end and set to run at separate hours (so there’s still only one per hour).
>> 
>> G6NHU-2 downtime on 10th June from 07:00z to 14:00z - Current time is
>> 
>> G6NHU-2 will be offline on 10th June from 07:00z to 14:00z - Time now is
>> 
>> This cluster (G6NHU-2) will be down on 10/06/2024 between 07:00z and 14:00z -
>> 
>> But I’m still only getting the occasional one delivered.   No errors in the log, they just don’t get delivered.
>> 
>> I’ve sort of given up on this now because I’ve spent too much time on it.  I have put a note in my MoTD and on the node web site.  I just want to let people know that there’s a planned outage!
>> 
>> 73 Keith.
>> 
>> 
>> 
>> 
>> 
>>> On 8 Jun 2024, at 14:56, CieNTi via Dxspider-support <dxspider-support at tobit.co.uk> wrote:
>>> 
>>> Hi Keith,
>>> 
>>> If I'm not wrong, you need to include some variability to the message in order to be shown and not considered a duplicate.
>>> 
>>> From http://www.dxcluster.org/main/cron.html
>>> 
>>> 
>>> # some people like to do an hourly announce to say who they are. There is a
>>> # slight complication about this because of the announce duplicate checking
>>> # so you need to make each announce unique. I do this by adding a date and time
>>> # stamp on the end
>>> 
>>> 0 * * * * run_cmd('ann CLUSTER: GB7DJK JO02LQ at ' . cldate . ' ' . ztime)
>>> 
>>> CieNTi
>>> 
>>> 
>>> On 2024-06-08 14:41, Keith Maton via Dxspider-support wrote:
>>>> Hey all,
>>>> My node is going to be down for a few hours next week and I wanted to
>>>> set up an announcement in my cron to let people know.
>>>> I set up a single line like this and it worked.
>>>> But it only worked once.
>>>> 20 * * * * run_cmd("Announce Downtime for G6NHU-2 on 10th June 07:00z-14:00z”)
>>>> The announcement only appeared on connected users once.
>>>> So I figured that perhaps there’s some kind of de-duplication to block
>>>> the same announcement from appearing multiple times.
>>>> To get around this, I changed the wording slightly and edited my
>>>> crontab accordingly to send the two announcements alternately, one
>>>> hour apart.
>>>> 20 01,03,05,07,09,11,13,15,17,19,21,23 * * * run_cmd("Announce
>>>> Downtime for G6NHU-2 on 10th June 07:00z-14:00z")
>>>> 20 02,04,06,08,10,12,14,16,18,20,22,00 * * * run_cmd("Announce
>>>> Downtime for G6NHU-2 on 10th June from 07:00z to 14:00z”)
>>>> Watching my debug log at 11:20z, the following appeared.
>>>> 1717845601^(cron) cron: LOCALTIME 20 12 8 6 6 -> doing
>>>> 'run_cmd("Announce Downtime for G6NHU-2 on 10th June from 07:00z to
>>>> 14:00z")'
>>>> 1717845601^(cron) DXCron::run_cmd: Announce Downtime for G6NHU-2 on
>>>> 10th June from 07:00z to 14:00z
>>>> 1717845601^(progress) ANNTALK: G6NHU-2 at G6NHU-2 via LOCAL -> *
>>>> 'Downtime for G6NHU-2 on 10th June from 07:00z to 14:00z' route:
>>>> G6NHU-2
>>>> 1717845601^(progress) CMD: 'Announce Downtime for G6NHU-2 on 10th June
>>>> from 07:00z to 14:00z' by G6NHU-2 ip: 127.0.0.1 10mS
>>>> And the announcement showed in my console window.
>>>> To LOCAL de G6NHU-2: Downtime for G6NHU-2 on 10th June from 07:00z to 14:00z
>>>> An hour later, the following showed in my debug log at 12:20z.
>>>> 1717849201^(cron) cron: LOCALTIME 20 13 8 6 6 -> doing
>>>> 'run_cmd("Announce Downtime for G6NHU-2 on 10th June 07:00z-14:00z")'
>>>> 1717849201^(cron) DXCron::run_cmd: Announce Downtime for G6NHU-2 on
>>>> 10th June 07:00z-14:00z
>>>> 1717849201^(progress) ANNTALK: G6NHU-2 at G6NHU-2 via LOCAL -> *
>>>> 'Downtime for G6NHU-2 on 10th June 07:00z-14:00z' route: G6NHU-2
>>>> 1717849201^(progress) CMD: 'Announce Downtime for G6NHU-2 on 10th June
>>>> 07:00z-14:00z' by G6NHU-2 ip: 127.0.0.1 2mS
>>>> But nothing showed in my console window and the client I have logged
>>>> on didn’t show the announcement.
>>>> Crontab is processing the announcement correctly but it’s not being
>>>> showed to connected users.
>>>> Is this an intentional de-duplication or is something broken?  If the
>>>> former, it’s not working quite properly because the text isn’t
>>>> identical.
>>>> I’ve now changed the wording even more to see if it makes any difference.
>>>> 73 Keith
>>>> _______________________________________________
>>>> Dxspider-support mailing list
>>>> Dxspider-support at tobit.co.uk
>>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>>> 
>>> _______________________________________________
>>> Dxspider-support mailing list
>>> Dxspider-support at tobit.co.uk
>>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>> 
>> 
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
> 
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20240915/d68ed3cc/attachment.htm>