When I log in I am seeing a message that there is an upcoming event on Monday Nov 7 at 5:00 AM and my time has been reduced.Ive been getting the same thing.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else seeing that?
Hello All,
When I log in I am seeing a message that there is an upcoming event on Monday Nov 7 at 5:00 AM and my time has been reduced.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else seeing that?
Seems like something is not reading the time correctly. Is anyone else
seeing that?
This sounds like a bug that was created and fixed on Nov-29.
Re: Event timing
By: Digital Man to Al on Sun Dec 06 2020 12:36 pm
Seems like something is not reading the time correctly. Is anyone else
seeing that?
This sounds like a bug that was created and fixed on Nov-29.
I am up to date as of yesterday but I just saw that message when I logged on a minute ago. I wonder if there is a remnant of that issue hanging around here?
It's not a big issue at all but I wonder if the event closed the BBS to users before running.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else seeing that?
Hello All,
When I log in I am seeing a message that there is an upcoming event on Monday Nov 7 at 5:00 AM and my time has been reduced.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else seeing that?
Ttyl :-),
Al
... My opinions are my own; mistakes are the computer's fault.
---
â– Synchronet â– The Rusty MailBox - Penticton, BC Canada
You're running Synchronet now, Al?
It's not a big issue at all but I wonder if the event closed the BBS
to users before running.
Let me know if it happens again?
Re: Event timing
By: Digital Man to Al on Sun Dec 06 2020 02:35 pm
It's not a big issue at all but I wonder if the event closed the BBS
to users before running.
Let me know if it happens again?
I just logged in and I see that message again although the event did run this morning it is saying the event will run tomorrow at 5:00 AM.
I usually see that message before the event runs and then it goes away.
I'll let you know what happens around the next event.
I usually see that message before the event runs and then it goes
away.
I'll let you know what happens around the next event.
Or if it's actually preventing users from logging in or not.
Re: Event timing
By: Digital Man to Al on Mon Dec 07 2020 11:22 am
I usually see that message before the event runs and then it goes
away.
I'll let you know what happens around the next event.
Or if it's actually preventing users from logging in or not.
Right now I am getting that message on login although my log indicates the event did run at 5:00 this morning and it did wait for nodes to be inactive so I think the event is running as expected.
I am just seeing the upcoming event message for an event that did run earlier.
Re: Event timing
By: Al to All on Sun Dec 06 2020 10:08 am
Hello All,
When I log in I am seeing a message that there is an upcoming event on Monday Nov 7 at 5:00 AM and my time has been reduced.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else seeing that?
This sounds like a bug that was created and fixed on Nov-29.
Re: Event timing
By: The Millionaire to Al on Sun Dec 06 2020 07:38 pm
Yes.
Ttyl :-),
Al
... If you tell the truth you don't have to remember anything.
--- SBBSecho 3.11-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757.2)
Hello All,
When I log in I am seeing a message that there is an upcoming event on Monday Nov 7 at 5:00 AM and my time has been reduced.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else seeing that?
This sounds like a bug that was created and fixed on Nov-29.
When I just logged in, I got similar.
Your time has been reduced due to an upcoming event on Mon Dec 14 2020 05:00:00
and I updated last night.
Okay, seems harmless.
If I can reproduce, I can fix it, but so far I haven't seen that problem here.
Can I be your Co-Sysop?
Re: Re: Event timing
By: Nelgin to Digital Man on Sun Dec 13 2020 03:31 pm
Hello All,
When I log in I am seeing a message that there is an upcoming event on
Monday Nov 7 at 5:00 AM and my time has been reduced.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else
seeing that?
This sounds like a bug that was created and fixed on Nov-29.
When I just logged in, I got similar.
Your time has been reduced due to an upcoming event on Mon Dec 14 2020 05:00:00
and I updated last night.
But Dec 14 hasn't happened yet. So that doesn't sound like a bug.
But Dec 14 hasn't happened yet. So that doesn't sound like a bug.However I don't have any jobs scheduled that are set to force users offline on Monday at 5am. The only one I have is Sunday at 5am.
I seem to recall we had this dicussion in the past but the reason or solution elutes me.
Digital wrote:
Re: Re: Event timing
By: Nelgin to Digital Man on Sun Dec 13 2020 03:31 pm
Hello All,
When I log in I am seeing a message that there is an upcoming event on
Monday Nov 7 at 5:00 AM and my time has been reduced.
I do have a forced MSGMAINT event that runs Sunday morning at 5:00 AM and that event did run successfully at 5:00 AM this morning.
Seems like something is not reading the time correctly. Is anyone else
seeing that?
This sounds like a bug that was created and fixed on Nov-29.
When I just logged in, I got similar.
Your time has been reduced due to an upcoming event on Mon Dec 14 2020 05:00:00
and I updated last night.
But Dec 14 hasn't happened yet. So that doesn't sound like a bug.
However I don't have any jobs scheduled that are set to force users offline on Monday at 5am. The only one I have is Sunday at 5am.
I seem to recall we had this dicussion in the past but the reason or solution elutes me.
Re: Re: Event timing
By: Nelgin to Digital Man on Mon Dec 14 2020 01:38 am
Howdy,
But Dec 14 hasn't happened yet. So that doesn't sound like a bug.However I don't have any jobs scheduled that are set to force users offline on Monday at 5am. The only one I have is Sunday at 5am.
I seem to recall we had this dicussion in the past but the reason or solution elutes me.
Yes, I see this everyweek.
The event runs Sun 5am, but on Sunday afternoon I see the message as well.
I reported it to you a little while ago, and your comment (IIRC) then was it was a 20yo bug. But I dont recall seeing a commit that addressed it - and I havent updated recently...
Your time has been reduced due to an upcoming event on Mon Dec 14 2020 05:00:00
and I updated last night.
But Dec 14 hasn't happened yet. So that doesn't sound like a bug.
Re: Event timing
By: The Millionaire to Alan Ianson on Sun Dec 13 2020 01:47 pm
Netmail or email me.
Ttyl :-),
Al
... Discoveries are often made by not following instructions.
---
â– Synchronet â– The Rusty MailBox - Penticton, BC Canada
But Dec 14 hasn't happened yet. So that doesn't sound like a bug.However I don't have any jobs scheduled that are set to force users offline on Monday at 5am. The only one I have is Sunday at 5am.
I seem to recall we had this dicussion in the past but the reason or solution elutes me.
Yes, I see this everyweek.
The event runs Sun 5am, but on Sunday afternoon I see the message as well.
I reported it to you a little while ago, and your comment (IIRC) then was it was a 20yo bug. But I dont recall seeing a commit that addressed it - and I havent updated recently...
...ëîåï
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 595 |
Nodes: | 8 (0 / 8) |
Uptime: | 03:44:33 |
Calls: | 10,784 |
Files: | 5 |
Messages: | 469,235 |