Subj : Re: SBBSecho logging. To : Digital Man From : Bill McGarrity Date : Mon Nov 06 2017 20:25:55 -=> Digital Man wrote to Bill McGarrity <=- DM> Re: Re: SBBSecho logging. DM> By: Bill McGarrity to Digital Man on Tue Jan 05 2016 07:40 pm > -=> Digital Man wrote to Bill McGarrity <=- > > DM> Re: Re: SBBSecho logging. > DM> By: Bill McGarrity to Digital Man on Mon Jan 04 2016 02:32 pm > > > -=> Digital Man wrote to Bill McGarrity <=- > > > Hiya Rob... > > > > -=> Joe Delahaye wrote to Bill McGarrity <=- > > > > JD> Re: Re: SBBSecho logging. > > > JD> By: Bill McGarrity to Joe Delahaye on Sun Jan 03 2016 17:40:00 > > > > JD>> The above is already being tested. We found that although the > > > JD>> packet name at least was created, (archived), when the > > > connections > > > JD>> were made, the mail went to the one system, and tried to send to > > > the > > > JD>> other, but file not found. > > > > BM> Were there not two separate PKT's created for each node? Why not > > > BM> remove archieving from the equation and just create a .*lo file > > > BM> as well and check your binkd logs. > > > > > JD> I tried that, resulting in an over abundance of .pkt files > > > JD> sitting in the outbound. Some of my nodes only collect mail > > > JD> maybe once a week or less, and that becomes a problem in my mind > > > JD> at least . When packets are created, it seems that they mostly > > > JD> go to the master outbound folder, with the .lo files mostly going > > > JD> to the proper areas (i.e. outbound.002), but not always > > > > OK.... that's fair. One other thing, could you post from echocfg your > > > "Toggle Options"? If I can remember correctly, you had Fuzzy Zone > > > disabled. I've always had that enabled and have no issue. > > > DM> Fuzzy Zone operations effect NetMail only, not EchoMail. > > > > One thing I did find in my logs... > > > 2016-01-04 14:12:24 ERROR line 1836 renaming c:\fd\outbound\04141202.pk_ > > to c:\fd\outbound\04141202.pkt > > DM> Interesting. Is this a one time occurrence or have you seen this error > DM> before? Is it possible there were 2 instance of SBBSecho running at > DM> this time (e.g. one spawned by Synchronet timed event and another > DM> spawned by another means)? I don't really have another explanation for > DM> that at this time, but it certainly should not happen. > > OK... that is quite possible. Naturally I run fidoin when I get something > from my uplink and then it processes it to downlinks but I also have a timed > event fidoout running every 10 minutes for netmail to be processed. There > could be an overlap. Interesting... DM> When you say you "run fidoin", does that mean you trigger the timed DM> event by touching a semaphore file or you're running SBBSecho DM> externally somehow? Yes, fidoin is triggered by a semaphore ONLY. Being I have downlinks, as soon as sbbsecho does it's thing importing, it creates outbound pkt's, as you well know. I run a timed event for fidoout incase there are any *.msg's sitting in my netmail so they get converted and sent. I don't get many callers but if someone wants to send a netmail, I really don't want it sitting around waiting for fidoout to run. DM> The normal/best way to run SBBSecho (for both import and export) is DM> *only* from the Synchronet event thread. This will insure that there is DM> only one instance of SBBSecho running at a time and avoid race DM> conditions that could cause the kind of error you reported. Agreed, but now that you told me the stray pk_ gets converted after 60 minutes, i'm not too worried. Yes, statistically two instances can, and have run together but it doesn't create a huge issue. Thanks!! -- Bill Telnet: tequilamockingbirdonline.net Web: bbs.tequilamockingbirdonline.net FTP: ftp.tequilamockingbirdonline.net:2121 IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697 Radio: radio.tequilamockingbirdonline.net:8010/live .... Look Twice... Save a Life!!! Motorcycles are Everywhere!!! --- MultiMail/Win32 v0.50 * Origin: TequilaMockingbird Online - Toms River, NJ (1:266/404) .