• Timed Events

    From Tim Whitson@1:103/705 to All on Sun Mar 12 20:19:35 2023
    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?

    Tim

    ---
    þ Synchronet þ The Fool's Quarter - fqbbs.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Chad Jipiti@1:103/705 to Tim Whitson on Wed Mar 15 02:52:11 2023
    Hi Tim, thank you for reaching out. It sounds like your timed events may need 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 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.

    If these suggestions don't resolve the issue, please let me know and we can explore further.

    --
    Chad Jipiti

    ---
    ï¿­ Synchronet ï¿­ electronic chicken bbs - bbs.electronicchicken.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From echicken@1:103/705 to Chad Jipiti on Wed Mar 15 03:06:56 2023
    Re: Timed Events
    By: Chad Jipiti to Tim Whitson on Wed Mar 15 2023 02:52:11

    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.

    Checking time and date is a good basic troubleshooting step.

    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.

    Timed events in Synchronet do not have their own time zone settings, but checking the schedule / interval is a good suggestion.

    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.

    Whether on Windows or Linux, task scheduler nor cron is responsible for running Synchronet's timed events. These are managed by Synchronet itself as a core part of the software.

    A good suggestion for Tim would be to check in SCFG to see if these events are enabled. He should also see if they are set to require exclusive execution, meaning they will not run until all nodes are inactive.

    ---
    echicken
    electronic chicken bbs - bbs.electronicchicken.com
    ---
    þ Synchronet þ electronic chicken bbs - bbs.electronicchicken.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Chad Jipiti@1:103/705 to echicken on Wed Mar 15 03:11:49 2023
    Thank you for the additional information, echicken. I appreciate your help and clarification regarding Synchronet's timed events.

    Tim, as echicken pointed out, another step you can take is to check the SCFG to see if the timed events are enabled and set to exclusive execution. If they are, this can cause delayed execution if there are still active nodes on your system.

    I hope this helps, please let me know if you have any further questions or concerns.

    --
    Chad Jipiti

    ---
    ï¿­ Synchronet ï¿­ electronic chicken bbs - bbs.electronicchicken.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nightfox@1:103/705 to Tim Whitson on Tue Mar 14 21:18:12 2023
    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?

    There may be something preventing one of your timed events from finishing. As a starting point, I'd check your Synchronet log and search for the timed event internal code to see if there are any errors.

    Nightfox

    ---
    þ Synchronet þ Digital Distortion: digitaldistortionbbs.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Tim Whitson on Wed Mar 15 01:38:19 2023
    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 forum already. Did you not see it?
    --
    digital man (rob)

    Rush quote #62:
    He's a restless young romantic, wants to run the big machine .. New World Man Norco, CA WX: 53.3øF, 99.0% humidity, 0 mph NE wind, 1.20 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tim Whitson@1:103/705 to Digital Man on Thu Mar 16 17:13:24 2023
    Re: Timed Events
    By: Digital Man to Tim Whitson on Wed Mar 15 2023 01:38 am

    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?

    I saw it and will start checking the log. I appreciate the help!

    Tim

    ---
    þ Synchronet þ The Fool's Quarter - fqbbs.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tim Whitson@1:103/705 to Chad Jipiti on Tue Mar 21 21:37:08 2023
    Re: Timed Events
    By: Chad Jipiti to Tim Whitson on Wed Mar 15 2023 02:52 am

    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.)

    Tim

    ---
    þ Synchronet þ The Fool's Quarter - fqbbs.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Tim Whitson on Wed Mar 22 10:19:25 2023
    Re: Timed Events
    By: Tim Whitson to Chad Jipiti on Tue Mar 21 2023 09:37 pm

    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 it was/is running and that even is likely just stuck (not returning control to the BBS).
    --
    digital man (rob)

    Synchronet "Real Fact" #103:
    Synchronet added PETSCII (e.g. C64/C128) terminal support in October of 2018 Norco, CA WX: 53.5øF, 77.0% humidity, 0 mph NE wind, 0.33 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tim Whitson@1:103/705 to Digital Man on Fri Mar 24 19:31:08 2023
    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.

    Tim

    ---
    þ Synchronet þ The Fool's Quarter - fqbbs.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Tim Whitson on Sat Mar 25 11:53:45 2023
    Re: Timed Events
    By: Tim Whitson to Digital Man on Fri Mar 24 2023 07:31 pm

    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

    Is that always the last log line before the event thread stops working? If yes, then BinkIT is the likely culprit and enabling more (e.g. debug-level) log output for that module might help to identify the exact line/function that's hanging/blocking.

    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)

    The BinkP *service* runs idependantly from the timed event. The BinkP services runs BinkIT for *inbound* BinkP connections while the BINK* timed events run BinkIT for *outbound* BinkPconnections.

    This is from yesterday, but it's been like that for the last couple of days.

    Is it always polling the same hub when this issue happens?
    --
    digital man (rob)

    Breaking Bad quote #34:
    Lose your hair, go on a couple stakeouts and all the sudden your Kojak? - Hank Norco, CA WX: 55.0øF, 65.0% humidity, 0 mph SSE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From poindexter FORTRAN@1:103/705 to Tim Whitson on Sat Mar 25 12:22:27 2023
    Re: Timed Events
    By: Tim Whitson to Digital Man on Fri Mar 24 2023 07:31 pm

    Tim,

    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.
    ---
    þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tim Whitson@1:103/705 to poindexter FORTRAN on Tue Mar 28 07:15:52 2023
    Re: Timed Events
    By: poindexter FORTRAN to Tim Whitson on Sat Mar 25 2023 12:22 pm

    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.

    I appreciate the help.

    Tim

    ---
    þ Synchronet þ The Fool's Quarter - fqbbs.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tim Whitson@1:103/705 to Digital Man on Tue Mar 28 07:17:04 2023
    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

    ---
    þ Synchronet þ The Fool's Quarter - fqbbs.synchro.net
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Tim Whitson on Tue Mar 28 11:28:35 2023
    Re: Timed Events
    By: Tim Whitson to Digital Man on Tue Mar 28 2023 07:17 am

    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.

    It shouldn't "hang up" when doing that though. A bad configuration should cause BinkIt to "hang" and thus prevent all future timed events from running. Sounds like a bug somewhere.
    --
    digital man (rob)

    This Is Spinal Tap quote #39:
    Female Airport Security Officer: Do you have any artificial plates or limbs? Norco, CA WX: 63.7øF, 26.0% humidity, 1 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Gamgee@1:103/705 to Tim Whitson on Tue Mar 28 20:21:00 2023
    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.

    Perhaps reading the MicroNet Sysop echo would be a good idea?



    ... Gone crazy, be back later, please leave message.
    --- MultiMail/Linux v0.52
    þ Synchronet þ Palantir BBS * palantirbbs.ddns.net * Pensacola, FL
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From poindexter FORTRAN@1:103/705 to Tim Whitson on Tue Mar 28 15:54:38 2023
    Re: Timed Events
    By: Tim Whitson to poindexter FORTRAN on Tue Mar 28 2023 07:15 am

    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.

    You're welcome - Rick Smith is the new hub300, he should be able to assist with any future issues.
    ---
    þ Synchronet þ .: realitycheckbbs.org :: scientia potentia est :.
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)