Sorry, I got another error this morning, thought I fixed them all yesterday, but I can'r figure out whats going on by the error code. I tried to duplicate it just now by logging on as the user, but nothing showed up. Below is the error, hopefully it will tell you something I don't see. Thanks In Advance.
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
Re: Another Error
By: DesotoFireflite to Digital Man on Wed Jan 26 2022 01:50 pm
Sorry, I got another error this morning, thought I fixed them all
yesterday, but I can'r figure out whats going on by the error code. I
tried to duplicate it just now by logging on as the user, but nothing
showed up. Below is the error, hopefully it will tell you something I
don't see. Thanks In Advance.
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE
(Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE
(Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE
(Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
If you look at the systems logs at the time of this error, what do you see? Does it appear the user just disconnected in the door? If the user disconnected and thus the process (door game) has terminated, then the errors are harmless.
I'll make a change to not log those errors if the process (e.g. door game) is no longer running.
Re: Another Error
By: Digital Man to DesotoFireflite on Wed Jan 26 2022 01:52 pm
Re: Another Error
By: DesotoFireflite to Digital Man on Wed Jan 26 2022 01:50 pm
Sorry, I got another error this morning, thought I fixed them all
yesterday, but I can'r figure out whats going on by the error code. I
tried to duplicate it just now by logging on as the user, but nothing
showed up. Below is the error, hopefully it will tell you something I
don't see. Thanks In Advance.
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE
(Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE
(Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE
(Error=38)
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
If you look at the systems logs at the time of this error, what do you see? Does it appear the user just disconnected in the door? If the user disconnected and thus the process (door game) has terminated, then the errors are harmless.
No, it doesn't appear to be a door, It looks like mail from what I can tell. Here it is from just before the error.
1/26 09:38:09a Node 1 <David Skulimoski> activate: computer slot 106 >= 43
1/26 09:38:09a Node 1 <David Skulimoski> CTerm activate_font: 3 106
1/26 09:38:09a Node 1 <David Skulimoski> CTerm query response: [=1;43;0;0;107;115;106n
1/26 09:38:09a Node 1 <David Skulimoski> CTerm activate_font result: 0
1/26 09:38:09a Node 1 <David Skulimoski> running external program: Remind Me Logon
1/26 09:38:09a Node 1 <David Skulimoski> Executing external: remindme remind1.cfg BYPASS
1/26 09:38:09a Node 1 <David Skulimoski> CreateFile(\\.\mailslot\sbbsexec\wr1)=0xa38
1/26 09:38:11a Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
I was on my website when this happened, but I wasn't reading mail or files at the time.
I'll make a change to not log those errors if the process (e.g. door game) is no longer running.
It wasn't a dropped called, he logged off the correct way. Hope this helps. Again, Thanks.
Wed Jan 26 09:38:11 2022 master/efa03b787
term Node 1 <David Skulimoski> !VDD WriteFile(0xa38, 1) FAILURE (Error=38)
I suspect the program (in this case, "remindme") is terminating while there is still input from the remote user that's trying to be sent to it. Is it always this "remindme" program that's been run when this error occurs?
I suspect the program (in this case, "remindme") is terminating while
there is still input from the remote user that's trying to be sent to
it. Is it always this "remindme" program that's been run when this
error occurs?
I just committed a change which will ignore (not log) WriteFile() failures if/when the child process ("remindme" in this example) has terminated. Let
Re: Another Error
By: Digital Man to DesotoFireflite on Wed Jan 26 2022 08:12 pm
I suspect the program (in this case, "remindme") is terminating while
there is still input from the remote user that's trying to be sent to
it. Is it always this "remindme" program that's been run when this
error occurs?
OK, you say this was a door program causing this issue, and remindme is a door that shows reminders that users have setup to show them at login. There is no user action on this, but I guess if the user hits the enter key during the process, it would be the same as user input during the process causing the error. Makes Sense Now. I think knowing this, I can duplicate the problem on my side to see it happening.
I suspect the program (in this case, "remindme") is terminating
while there is still input from the remote user that's trying to
be sent to it. Is it always this "remindme" program that's been run
when this error occurs?
OK, you say this was a door program causing this issue, and remindme is
a door that shows reminders that users have setup to show them at
There is no user action on this, but I guess if the user hits the enter
key during the process, it would be the same as user input during the
process causing the error. Makes Sense Now. I think knowing this, I can
duplicate the problem on my side to see it happening.
Cool. Yeah, I didn't really mean to imply "cause", but more "trigger the issue". It's not really even an issue (if the program is in fact terminated), just rather unnecessary noise in the logs.
Cool. Yeah, I didn't really mean to imply "cause", but more "trigger the >> issue". It's not really even an issue (if the program is in fact
terminated), just rather unnecessary noise in the logs.
I was in fact able to duplicate the issue everytime today, by holding down the enter key during the brief time the remindme door is doing it's thing > the way some users, I'm sure have been doing. I plan to download and install
your fix tomorrow. I was going to do it today, but I like to give the GetHub time to process the fix. I'll let you know how it does. Again, thanks for > all you do.
It seems your fix works fine, It still shows up on the Terminal Server Window, but it doesn't throw an error anymore to the log file. Here is a snipit from the Terminal Server Window, so you can see what is going on. I'm so glad I was able to duplicate the error locally so you could narrow it down. Again, Thanks so much, we have success.
1/28 01:35:13p Node 1 <David Skulimoski> running external program: Remind Me Logon
1/28 01:35:13p Node 1 <David Skulimoski> Executing external: remindme remind1.cfg BYPASS
1/28 01:35:13p Node 1 <David Skulimoski> !ERROR 2 (Resource temporarily unavailable) opening \\.\mailslot\sbbsexec\wr1
1/28 01:35:13p Node 1 <David Skulimoski> VDD Open failed (not loaded yet?)
It seems your fix works fine, It still shows up on the Terminal Server
Window, but it doesn't throw an error anymore to the log file. Here is
a snipit from the Terminal Server Window, so you can see what is going
on. I'm so glad I was able to duplicate the error locally so you could
narrow it down. Again, Thanks so much, we have success.
1/28 01:35:13p Node 1 <David Skulimoski> running external program:
Remind Me Logon
1/28 01:35:13p Node 1 <David Skulimoski> Executing external:
remindme remind1.cfg BYPASS
1/28 01:35:13p Node 1 <David Skulimoski> !ERROR 2 (Resource
temporarily unavailable) opening \\.\mailslot\sbbsexec\wr1
1/28 01:35:13p Node 1 <David Skulimoski> VDD Open failed (not loaded
yet?)
I think that's a slightly different issue. Does this program just run and terminate very quickly?
Re: Another Error
By: Digital Man to DesotoFireflite on Fri Jan 28 2022 08:46 pm
It seems your fix works fine, It still shows up on the Terminal Server
Window, but it doesn't throw an error anymore to the log file. Here is
a snipit from the Terminal Server Window, so you can see what is going
on. I'm so glad I was able to duplicate the error locally so you could
narrow it down. Again, Thanks so much, we have success.
1/28 01:35:13p Node 1 <David Skulimoski> running external program:
Remind Me Logon
1/28 01:35:13p Node 1 <David Skulimoski> Executing external:
remindme remind1.cfg BYPASS
1/28 01:35:13p Node 1 <David Skulimoski> !ERROR 2 (Resource
temporarily unavailable) opening \\.\mailslot\sbbsexec\wr1
1/28 01:35:13p Node 1 <David Skulimoski> VDD Open failed (not loaded
yet?)
I think that's a slightly different issue. Does this program just run and terminate very quickly?
Yes, when it run in BYPASS mode, all it does is check to see if there is a reminder set for the user logging in, and if a reminder exist, it show it to the user. If no reminder exist, it just closes. All this takes place in seconds. The only this the user sees is a quick screen from the door saying "Checking Reminders". I've had this door running on Synchronet since I started running it back with version 3.13 I believe, or earlier. I can't tell you if it was throwing the error before the update, but I just started noticing it since the update as I've been paying attention to the error log because of the update if that makes sense. Sorry I got long winded, just wanted to give you a slight history to help narrow down the issue. Anyway, you seem to have fixed the original issue :) sigh, fingers crossed.
The first log message "ERROR 2 .. opening .. mailslot" is a debug-level message, so I'm not going to do anything to suppress that. I did just commit a change that will suppress the warning-level log message ("VDD Open failed") if the process has already terminated this point.
I'm pretty sure if you look through your logs you'll find that all of these log messages have been happening under these conditions (user presses a key while the process is running but the process terminates before sbbs has a chance to send it the mailslot). There have been no recent changes in this logic.
So... if you have debug-level logging enabled, I'd expect to still see that "ERROR 2 .. opening .. mailslot" message under these conditions, but not the warning.
| Sysop: | Chris Crash |
|---|---|
| Location: | Huntington Beach, CA. |
| Users: | 585 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 28:55:51 |
| Calls: | 10,757 |
| Files: | 5 |
| Messages: | 452,141 |