Subj : Another Error To : DesotoFireflite From : Digital Man Date : Sat Jan 29 2022 12:37:54 Re: Another Error By: DesotoFireflite to Digital Man on Sat Jan 29 2022 07:46 am > 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 running external program: > >> Remind Me Logon > >> 1/28 01:35:13p Node 1 Executing external: > >> remindme remind1.cfg BYPASS > >> 1/28 01:35:13p Node 1 !ERROR 2 (Resource > >> temporarily unavailable) opening \\.\mailslot\sbbsexec\wr1 > >> 1/28 01:35:13p Node 1 VDD Open failed (not loaded > >> yet?) > > DM> I think that's a slightly different issue. Does this program just run > DM> 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. -- digital man (rob) Rush quote #54: He'd love to spend the night in Zion, he's been a long, long while in Babylon Norco, CA WX: 63.7øF, 19.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.14-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) .