Hi Gang,
I seem to be having issues with my timed events.
Specifically FIDOIN and TICKIT (but sometime others).
Running Syncronet 3.17c on Centos Linux.
Just in the last few weeks I have found that some of the timed events are hung and not running as scheduled.
I think it may be connected to being constantly swamped by hacking bots and very
short periods for which none of the 8 nodes are active.
I can fix it by setting a node toggle to Re-Run at Loggoff. Then the moment all nodes are free there is a flurry of timed event activity.
Has anyone else encountered this behaviour?
areJust in the last few weeks I have found that some of the timed events
hung and not running as scheduled.
More details would be needed (e.g. the last lines of your data/sbbsecho.log file at the time of "hang", in the case of FIDOIN->SBBSecho).
Do you have your timed events set to require exclusive execution? Most events (like those you listed) do not and should not be configured to require exclusive execution.
I have there Sched currently set to 24 times a day, and have split
the Events across various nodes.
Just in the last few weeks I have found that some of the timed events are hung and not running as scheduled.
More details would be needed (e.g. the last lines of your data/sbbsecho.log file at the time of "hang", in the case of FIDOIN->SBBSecho).
Hiya DM,
Last time it ran today was 12:11pm
2020-06-09 11:59:29 Imported: 1 msgs memories <- MEMORIES 2020-06-09 11:59:29 Imported: 18 msgs cooking <- COOKING 2020-06-09 11:59:29 Imported: 19 msgs total
2020-06-09 11:59:29 Writing 1 areas to ../data/badareas.lst
2020-06-09 11:59:29 Deleting /sbbs/ctrl/sbbsecho.bsy (from line 3038) 2020-06-09 11:59:29 SBBSecho (PID 11818) exiting with error level 0, Bundles(1 unpacked, 0 sent), Packets(1 imported, 0 sent), EchoMail(19 imported, 0 exported)
2020-06-09 12:11:22 SBBSecho 3.10-Linux r3.156 Apr 7 2020 GCC 4.8.5 (PID 12057)
invoked with options: -ce
2020-06-09 12:11:22 Configured: 1 archivers, 13 linked-nodes, 4 echolists 2020-06-09 12:11:22 NetMail directory: /usr/local/sbbs/fido/netmail/ 2020-06-09 12:11:22 Secure Inbound directory: /sbbs/fido/inbsecure/ 2020-06-09 12:11:22 Non-secure Inbound directory: /sbbs/fido/inbound/ 2020-06-09 12:11:22 Outbound (BSO root) directory: /sbbs/fido/outbound/ 2020-06-09 12:11:22 Read 391 areas from /sbbs/data/AREAS.BBS
2020-06-09 12:11:22 Read 1 areas from ../data/badareas.lst
2020-06-09 12:11:23 Read 217 echo statistics from ../data/echostats.ini 2020-06-09 12:11:23 Unpacking bundle: /sbbs/fido/inbsecure/def01201.tu0 (0.8KB) 2020-06-09 12:11:23 Executing: /usr/local/bin/unzip -j /sbbs/fido/inbsecure/def01201.tu0 -d /sbbs/fido/inbsecure/
2020-06-09 12:11:23 Deleting /sbbs/fido/inbsecure/def01201.tu0 (from line 2788) 2020-06-09 12:11:23 Importing /sbbs/fido/inbsecure/5edeefb8.pkt (Type 2e, 0.8KB)
from 3:712/848 to 3:712/620
2020-06-09 12:11:23 Deleting /sbbs/fido/inbsecure/5edeefb8.pkt (from line 5967) 2020-06-09 12:11:24 Writing 1 areas to ../data/badareas.lst
2020-06-09 12:11:24 Deleting /sbbs/ctrl/sbbsecho.bsy (from line 3038) 2020-06-09 12:11:24 SBBSecho (PID 12057) exiting with error level 0, Bundles(1 unpacked, 0 sent), Packets(1 imported, 0 sent)
Now umonitor just shows FIDOIN as (Pending) but it should have run at least a few
times since 12:11 (Time now is 3:46pm)
in my BINK* and FIDO* events, starting at the "Execution Node" and going down to the time, my settings are
ANY
ANY
ANY
ALL
00:00
1. Check the date and time settings on your server. If the time on your server is incorrect, this can cause issues with timed events.
2. Double-check your event scheduler configuration. Make sure that your events are set up with the correct time zone and that the interval is set correctly.
3. Ensure that the task scheduler service is running on your server. This service is responsible for running timed events on schedule.
4. If none of these suggestions help, try restarting the task scheduler service and see if that resolves the issue.
My timed events seem to be off. They run a lot later then they should. What's more, I can not manually run a timed event. Any ideas?
My timed events seem to be off. They run a lot later then they should. What's more, I can not manually run a timed event. Any ideas?
Re: Timed Events
By: Tim Whitson to All on Sun Mar 12 2023 08:19 pm
My timed events seem to be off. They run a lot later then they should. What's more, I can not manually run a timed event. Any ideas?
I responded to this same question from you in the Synchronet Discussion foru already. Did you not see it?
Hi Tim, thank you for reaching out. It sounds like your timed events may nee to be adjusted. Here are a few things you can try:
1. Check the date and time settings on your server. If the time on your serv is incorrect, this can cause issues with timed events.
2. Double-check your event scheduler configuration. Make sure that your even are set up with the correct time zone and that the interval is set correctly
3. Ensure that the task scheduler service is running on your server. This service is responsible for running timed events on schedule.
4. If none of these suggestions help, try restarting the task scheduler serv and see if that resolves the issue.
If these suggestions don't resolve the issue, please let me know and we can explore further.
--
Chad Jipiti
These did not work. It seems the only way I can get the events to run is to shut down and restart Synchronet. Once restarted the events will run for a couple of hours then quit. For example I reboot before going to work, the system is fine, I come home and no events have ran since 6:00 am in the morning. (Which is when I leave for work.)
Check your event log when this happens. It will tell you the last event that was/is running and that even is likely just stuck (not returning control to BBS).
Re: Timed Events
By: Digital Man to Tim Whitson on Wed Mar 22 2023 10:19 am
Check your event log when this happens. It will tell you the last event that was/is running and that even is likely just stuck (not returning control to BBS).
I've been watching the event log. I'll reboot the BBS and events will run fine. I come back several hours later and the last event that ran was:
06:53.07a BINKPOLL Connecting to 618:300/1@micronet at realitycheckBBS.org:24554
06:53.07a BINKPOLL Will encrypt session.
06:53.07a BINKPOLL Peer version: BinkIT/2.41,JSBinkP/4,sbbs3.20a/Win32 06:53.07a BINKPOLL Authentication successful: non-secure
Under the Services log, things keep running
The last entry being:
3/23 06:47:18p 3384 BINKP service terminated (0 clients remain, 0 total, 128 served)
This is from yesterday, but it's been like that for the last couple of days.
06:53.07a BINKPOLL Connecting to 618:300/1@micronet at realitycheckBBS.org:24554
06:53.07a BINKPOLL Will encrypt session.
06:53.07a BINKPOLL Peer version: BinkIT/2.41,JSBinkP/4,sbbs3.20a/Win32 06:53.07a BINKPOLL Authentication successful: non-secure
We made a hub change a few weeks back. realitycheckBBS is no longer hub for net300. You'll need to get a new nodelist (I should have sent one to you via email, check your SPAM folder...)
If not, you could download the most recent nodelist from https://www.minftn.net/ and it'll have the correct information for 300/1.
Is it always polling the same hub when this issue happens?
Re: Timed Events
By: Digital Man to Tim Whitson on Sat Mar 25 2023 11:53 am
Is it always polling the same hub when this issue happens?
Thank you for your help. I hadn't updated for the changes on Micronet. It was hanging up when trying to poll it. Now everything is working again.
Tim Whitson wrote to poindexter FORTRAN <=-
We made a hub change a few weeks back. realitycheckBBS is no longer hub for net300. You'll need to get a new nodelist (I should have sent one to you via email, check your SPAM folder...)
If not, you could download the most recent nodelist from https://www.minftn.net/ and it'll have the correct information for 300/1.
That was it, it was hanging up trying to poll Micronet. Thank
you for the help. It's amazing how something like this can
really mess things up.
That was it, it was hanging up trying to poll Micronet. Thank you for the help. It's amazing how something like this can really mess things up.
I appreciate the help.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (3 / 13) |
| Uptime: | 51:34:09 |
| Calls: | 6,650 |
| Calls today: | 2 |
| Files: | 12,200 |
| Messages: | 5,330,306 |