<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">It’s the de-duplication that’s causing it.<div><br></div><div>As a workaround, add this command into your crontab a few minutes before your announcement.</div><div><br></div><div>run_cmd("clear/dupefile”)</div><div><br></div><div>So if your announcement is every two hours</div><div><br></div><div>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)</div><div><br></div><div>You’d add this:</div><div><br></div><div>40 00,03,06,09,12,15,18,21 * * * run_cmd("clear/dupefile”)</div><div><br></div><div>That way, the dupe file is cleared at 40 minutes past the hour and then your local announcement is made five minutes later.</div><div><br></div><div>Be aware that this is opening you to more duplications across the network.</div><div><br></div><div>I think you’re right, local sysop announcements don’t really need to go through the dupe checking.</div><div><br></div><div>73 Keith</div><div><br></div><div><br></div><div><p style="margin: 0px; font-style: normal; font-variant-caps: normal; font-stretch: normal; font-size: 11px; line-height: normal; font-family: Menlo; font-size-adjust: none; font-kerning: auto; font-variant-alternates: normal; font-variant-ligatures: normal; font-variant-numeric: normal; font-variant-east-asian: normal; font-variant-position: normal; font-variant-emoji: normal; font-feature-settings: normal; font-optical-sizing: auto; font-variation-settings: normal; color: rgb(46, 174, 187);"><span style="font-variant-ligatures: no-common-ligatures"><br></span></p><div><blockquote type="cite"><div>On 15 Sep 2024, at 15:52, IZ2LSC via Dxspider-support <dxspider-support@tobit.co.uk> wrote:</div><br class="Apple-interchange-newline"><div><div>I'm having the same issue even if the messages are different (I<br>inserted a time stamp).<br>It's not good at all that sysop local announces are dropped!!!<br><br>73<br>Andrea<br><br>--><br><br>Il giorno sab 8 giu 2024 alle ore 20:24 Keith Maton via<br>Dxspider-support <dxspider-support@tobit.co.uk> ha scritto:<br><blockquote type="cite"><br>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.<br><br>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).<br><br>G6NHU-2 downtime on 10th June from 07:00z to 14:00z - Current time is<br><br>G6NHU-2 will be offline on 10th June from 07:00z to 14:00z - Time now is<br><br>This cluster (G6NHU-2) will be down on 10/06/2024 between 07:00z and 14:00z -<br><br>But I’m still only getting the occasional one delivered. No errors in the log, they just don’t get delivered.<br><br>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!<br><br>73 Keith.<br><br><br><br><br><br><blockquote type="cite">On 8 Jun 2024, at 14:56, CieNTi via Dxspider-support <dxspider-support@tobit.co.uk> wrote:<br><br>Hi Keith,<br><br>If I'm not wrong, you need to include some variability to the message in order to be shown and not considered a duplicate.<br><br>From http://www.dxcluster.org/main/cron.html<br><br><br> # some people like to do an hourly announce to say who they are. There is a<br> # slight complication about this because of the announce duplicate checking<br> # so you need to make each announce unique. I do this by adding a date and time<br> # stamp on the end<br><br> 0 * * * * run_cmd('ann CLUSTER: GB7DJK JO02LQ at ' . cldate . ' ' . ztime)<br><br>CieNTi<br><br><br>On 2024-06-08 14:41, Keith Maton via Dxspider-support wrote:<br><blockquote type="cite">Hey all,<br>My node is going to be down for a few hours next week and I wanted to<br>set up an announcement in my cron to let people know.<br>I set up a single line like this and it worked.<br>But it only worked once.<br>20 * * * * run_cmd("Announce Downtime for G6NHU-2 on 10th June 07:00z-14:00z”)<br>The announcement only appeared on connected users once.<br>So I figured that perhaps there’s some kind of de-duplication to block<br>the same announcement from appearing multiple times.<br>To get around this, I changed the wording slightly and edited my<br>crontab accordingly to send the two announcements alternately, one<br>hour apart.<br>20 01,03,05,07,09,11,13,15,17,19,21,23 * * * run_cmd("Announce<br>Downtime for G6NHU-2 on 10th June 07:00z-14:00z")<br>20 02,04,06,08,10,12,14,16,18,20,22,00 * * * run_cmd("Announce<br>Downtime for G6NHU-2 on 10th June from 07:00z to 14:00z”)<br>Watching my debug log at 11:20z, the following appeared.<br>1717845601^(cron) cron: LOCALTIME 20 12 8 6 6 -> doing<br>'run_cmd("Announce Downtime for G6NHU-2 on 10th June from 07:00z to<br>14:00z")'<br>1717845601^(cron) DXCron::run_cmd: Announce Downtime for G6NHU-2 on<br>10th June from 07:00z to 14:00z<br>1717845601^(progress) ANNTALK: G6NHU-2@G6NHU-2 via LOCAL -> *<br>'Downtime for G6NHU-2 on 10th June from 07:00z to 14:00z' route:<br>G6NHU-2<br>1717845601^(progress) CMD: 'Announce Downtime for G6NHU-2 on 10th June<br>from 07:00z to 14:00z' by G6NHU-2 ip: 127.0.0.1 10mS<br>And the announcement showed in my console window.<br>To LOCAL de G6NHU-2: Downtime for G6NHU-2 on 10th June from 07:00z to 14:00z<br>An hour later, the following showed in my debug log at 12:20z.<br>1717849201^(cron) cron: LOCALTIME 20 13 8 6 6 -> doing<br>'run_cmd("Announce Downtime for G6NHU-2 on 10th June 07:00z-14:00z")'<br>1717849201^(cron) DXCron::run_cmd: Announce Downtime for G6NHU-2 on<br>10th June 07:00z-14:00z<br>1717849201^(progress) ANNTALK: G6NHU-2@G6NHU-2 via LOCAL -> *<br>'Downtime for G6NHU-2 on 10th June 07:00z-14:00z' route: G6NHU-2<br>1717849201^(progress) CMD: 'Announce Downtime for G6NHU-2 on 10th June<br>07:00z-14:00z' by G6NHU-2 ip: 127.0.0.1 2mS<br>But nothing showed in my console window and the client I have logged<br>on didn’t show the announcement.<br>Crontab is processing the announcement correctly but it’s not being<br>showed to connected users.<br>Is this an intentional de-duplication or is something broken? If the<br>former, it’s not working quite properly because the text isn’t<br>identical.<br>I’ve now changed the wording even more to see if it makes any difference.<br>73 Keith<br>_______________________________________________<br>Dxspider-support mailing list<br>Dxspider-support@tobit.co.uk<br>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br></blockquote><br>_______________________________________________<br>Dxspider-support mailing list<br>Dxspider-support@tobit.co.uk<br>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br></blockquote><br><br>_______________________________________________<br>Dxspider-support mailing list<br>Dxspider-support@tobit.co.uk<br>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br></blockquote><br>_______________________________________________<br>Dxspider-support mailing list<br>Dxspider-support@tobit.co.uk<br>https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support<br></div></div></blockquote></div><br></div></body></html>