| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 41 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 106:32:33 |
| Calls: | 209 |
| Files: | 820 |
| Messages: | 106,850 |
Ok, here is a strange one..
I have my 16bit door maint setup to run at 0145 every day, noticed it
ran at 2145 tonight..
synchronet 9:46 PM srvc 0219 ActiveUser-UDP [40.136.248.88] Hostname: h88.248.136.40.dynamic.ip.windstream.net
synchronet 9:46 PM srvc 0219 ActiveUser-UDP [40.136.248.88]
Connection accepted on 192.168.1.5 port 11 from port 54194
synchronet 9:45 PM evnt DOORMAINT Running 16-bit DOS timed event:
DOORMAINT synchronet 9:45 PM srvc 0218 ActiveUser-UDP [40.136.248.88] JavaScript service thread terminated (1 clients remain, 21 total, 945
served) synchronet 9:45 PM srvc 0218 ActiveUser-UDP [40.136.248.88]
Hostname: h88.248.136.40.dynamic.ip.windstream.net
Any idea whats up with that??
It's not running late either, it's running early because on the
terminal output window it showed the date as 10/2. Here is Log entry
Info:
synchronet
evnt DOORMAINT Running 16-bit DOS timed event: DOORMAINT
nelgin wrote to kk4qbn <=-
Ok, here is a strange one..
I have my 16bit door maint setup to run at 0145 every day, noticed it
ran at 2145 tonight..
synchronet 9:46 PM srvc 0219 ActiveUser-UDP [40.136.248.88] Hostname: h88.248.136.40.dynamic.ip.windstream.net
synchronet 9:46 PM srvc 0219 ActiveUser-UDP [40.136.248.88]
Connection accepted on 192.168.1.5 port 11 from port 54194
synchronet 9:45 PM evnt DOORMAINT Running 16-bit DOS timed event:
DOORMAINT synchronet 9:45 PM srvc 0218 ActiveUser-UDP [40.136.248.88] JavaScript service thread terminated (1 clients remain, 21 total, 945 served) synchronet 9:45 PM srvc 0218 ActiveUser-UDP [40.136.248.88] Hostname: h88.248.136.40.dynamic.ip.windstream.net
Any idea whats up with that??
It's not running late either, it's running early because on the
terminal output window it showed the date as 10/2. Here is Log entry
Info:
synchronet
evnt DOORMAINT Running 16-bit DOS timed event: DOORMAINT
Do you have "Exclusive Execution" set to yes or something like that?
Maybe you can post your scfg settings for the timed events and I can compare to mine.
Actually, this is mine if you want to compare.
[DOSMAINT Timed Event]
1: Internal Code DOSMAINT
2: Start-up Directory ../xtrn/dosutils
3: Command Line maint.bat
4: Enabled Yes
5: Execution Node Any
6: Execution Months Any
7: Execution Days of Month Any
8: Execution Days of Week All
9: Execution Time 00:00
10: Requires Exclusive Exec No
11: Force Users Off-line No
12: Native Executable/Script No
13: Use Shell or New Context No
14: Background Execution No
15: Always Run After (re)Init No
16: Error Log Level Debug
As you can probably tell, this will run the bat script until dosemu
rather than calling a linux script that calls dosemu for each game that requires maintenance.
Do you have "Exclusive Execution" set to yes or something like that? Maybe you can post your scfg settings for the timed events and I can compare to mine.
Actually, this is mine if you want to compare.
[DOSMAINT Timed Event]
1: Internal Code DOSMAINT
2: Start-up Directory ../xtrn/dosutils 3: Command Line
maint.bat
4: Enabled Yes
5: Execution Node Any
6: Execution Months Any
7: Execution Days of Month Any
8: Execution Days of Week All
9: Execution Time 00:00
10: Requires Exclusive Exec No
11: Force Users Off-line No
12: Native Executable/Script No
13: Use Shell or New Context No
14: Background Execution No
15: Always Run After (re)Init No
16: Error Log Level Debug
I am also struggling with this (maint for dos doors) a bit... Would you mind posting your 'maint.bat' file also (or at least a bit of it)?
13: Use Shell or New Context No
kk4qbn wrote to Gamgee <=-
Re: Re: Out of sync Events
By: Gamgee to nelgin on Wed Oct 02 2024 14:35:00
I am also struggling with this (maint for dos doors) a bit... Would you mind posting your 'maint.bat' file also (or at least a bit of it)?
I run dosemu and I think you guys use dosemu2, dont know for sure, but here are some of the games out of my maint.bat "which runs well, if on time :-)"
REM FOODFITE
echo foodfite >>e:\maint\maint.log
time /T >>e:\maint\maint.log
chdir ..\ff
ffbull.exe foodfite.cfg
chdir ..\maint
Also, was the word "until" in your paragraph above a typo? Should that
be "within" or something? Trying to understand the flow of things.
Nope, It's set to no, would'nt that just force everyone off to run the event though if it was set to yes??
Ok, here is a strange one..
I have my 16bit door maint setup to run at 0145 every day, noticed it ran at 2145 tonight..
synchronet 9:45 PM evnt DOORMAINT Running 16-bit DOS timed event: DOORMAINT
Any idea whats up with that??
It's not running late either, it's running early because on the terminal output window it showed the date as 10/2. Here is Log entry Info:
synchronet
evnt DOORMAINT Running 16-bit DOS timed event: DOORMAINT
PRIORITY
6
SYSLOG_FACILITY
19
SYSLOG_IDENTIFIER
synchronet
SYSLOG_TIMESTAMP
Oct 2 01:45:40
You do have your set to log users off. What if you turn of that off for testing?
That time seems to be the expected time. Maybe whatever is formatting that time for the log text isn't accounting for timezone offset?
nelgin wrote to Gamgee <=-
Re: Re: Out of sync Events
By: Gamgee to nelgin on Wed Oct 02 2024 14:35:00
Also, was the word "until" in your paragraph above a typo? Should that
be "within" or something? Trying to understand the flow of things.
Probably. That happens when I'm multitasking and I hear a word someone
is saying or in some music and just write that instead of what I'm thinking :)
my maint.bat is nothing special, just whatever the game wants
e:
cd \tw2002
extern MULTITASK=NO
cd \shuffle
shufword shuffle.cfg /E
Re: Out of sync Events
By: Digital Man to kk4qbn on Thu Oct 03 2024 00:13:12
That time seems to be the expected time. Maybe whatever is formatting that time for the log text isn't accounting for timezone offset?
Why would it run it early though? If the expected time was 10/2 at 0100
(I had errantly posted that I had it configured for 0145 because of that
If something was stuck with the bbs (happens sometimes) and the event was running late it would say that it was the next days event would it?
I'm going to see if I can dig up the terminal server output somewhere, because yea i'ts not showing correctly on the cockpit formatted logs.
If something was stuck with the bbs (happens sometimes) and the event was
running late it would say that it was the next days event would it?
I'm not sure what you're referring to here.
Re: Out of sync Events
By: kk4qbn to Digital Man on Thu Oct 03 2024 07:40 am
If it ran at 0145 instead of 0100, that would be *late* not early. Why would it? Because another event was running possibly.
I'm not sure what you're referring to here.
Re: Out of sync Events
By: Digital Man to kk4qbn on Thu Oct 03 2024 04:17 pm
If something was stuck with the bbs (happens sometimes) and the event was
running late it would say that it was the next days event would it?
I'm not sure what you're referring to here.
I think he might be referring to exclusive events that get stuck and don't finish, which could push other events to run later than they normally are configured to run.
Re: Out of sync Events
By: kk4qbn to Digital Man on Thu Oct 03 2024 07:40 am
If it ran at 0145 instead of 0100, that would be *late* not early. Why would it? Because another event was running possibly.
It did'nt run at 0145, it ran at 2145, the day before.
I'm afraid now that it is logging through syslog I cannot get the log formatted like it was on the terminal service.. either way it appeared as if it was running a future event instead of running it late, that is what I was referring to. it really does'nt matter, It just looked off to me, probably operator error.. some way..
I'm afraid now that it is logging through syslog I cannot get the log formatted like it was on the terminal service.. either way it appeared as if it was running a future event instead of running it late, that is what I was referring to. it really does'nt matter, It just looked off to me, probably operator error.. some way..
I'm afraid now that it is logging through syslog I cannot get the logRandom, odd, unexplainable stuff happens from time to time and it's annoying, especially when you know it happened but you cannot get it to happen again and it just doesn't make sense.
formatted like it was on the terminal service.. either way it appeared as
if it was running a future event instead of running it late, that is what I
I have a rsyslog.d config file that helps split logs for each function of the bbs into a separate file, such as mail, ftp, web, term, events, services, and "other stuff" I can dig out. It might be a good start to format the logs how you want them, it also helps debugging because you're not trying to look through one big log.
kk4qbn wrote to All <=-
I mean, It really does'nt matter, I just knew I wasn't tripping when it started running but it was running for 10/2, not 10/1 but it was 0945pm 10/1
kk4qbn wrote to nelgin <=-
Yes, that could be some help, I mean sbbs technically "Should" be
writing to /var/log/sbbs.log but there's nothing there. and I cannot
find where cockpit has it saved, I presume it's grabbing it straight
from the log stream and saving it somewhere.
I have no idea why it's not saving ANY logfile to /var/log. it *should* be. So yeah, I'd appreciate it if you could dig them up when you get
the time.
I have no idea why it's not saving ANY logfile to /var/log. it *should* be. So yeah, I'd appreciate it if you could dig them up when you get the time.
I mean, It really does'nt matter, I just knew I wasn't tripping when it
started running but it was running for 10/2, not 10/1 but it was 0945pm
10/1
Could it just be that the BBS machine's time (or TIME ZONE) is set wrong? Sometimes the easiest answer is the correct one... ;-)
I have no idea why it's not saving ANY logfile to /var/log. it *should*
be. So yeah, I'd appreciate it if you could dig them up when you get the
time.
I'm not certain that SBBS will log to /var/log/sbbs.log by default. I had to modify my /etc/syslog.conf to make it do that.
This is documented here: https://wiki.synchro.net/config:nix#logging
Maybe this would explain it?
Maybe syslogd isn't installed/running?
and I see I have it set to 0100 not 0145.. definatly not 2145 the day before :)
Re: Re: Out of sync Events
By: kk4qbn to nelgin on Wed Oct 02 2024 05:00 pm
and I see I have it set to 0100 not 0145.. definatly not 2145 the day
before :)
Just shotgunning, but daylight saving time in/off? Software time and Bios time different?