• SBBSECHO Errors

    From Mojo@1:103/705 to Digital Man on Sun Jul 9 19:12:36 2017
    Re: SBBSECHO Errors
    By: Digital Man to Mojo on Tue Jul 04 2017 06:29 pm

    There's your problem. It looks like Arrowbridge is prepending the caret (^) symbol on the path to the attached file path. FTS-1 (http://ftsc.org/docs/fts-0001.016) doesn't seem to support this syntax. Is there a configuration option to disable this behavior for this doorgame?


    I will have to look into this and see if there is a way I can make it stop doing this.

    Thanks for your help...


    Mojo

    ---
    * Synchronet * Mojo's World BBS - mojo.synchro.net
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Mojo@1:103/705 to Digital Man on Mon Jul 3 11:12:36 2017
    Hi Digital Man,

    I am getting errors every time FIDOIN & FIDOOUT runs and I am not sure why all of the sudden it has started doing this. It was not doing it when I moving the BBS over to a machine with windows 7 on it. It ran for almost two full months on windows 7 and it just started doing this the middle of last week. It is filling up the error log with FIDOIN returned - 1 and FIDOOUT returned - 1... I have not changed anything in the settings. I had it running on windows xp and decided to upgrade to windows 7 to run it on. Any suggestions or ideas as to what can help take care of this problem would be of great help.


    Thanks
    Mojo

    ---
    * Synchronet * Mojo's World BBS - mojo.synchro.net
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mojo on Mon Jul 3 12:26:14 2017
    Re: SBBSECHO Errors
    By: Mojo to Digital Man on Mon Jul 03 2017 11:12 am

    Hi Digital Man,

    I am getting errors every time FIDOIN & FIDOOUT runs and I am not sure why all of the sudden it has started doing this. It was not doing it when I moving the BBS over to a machine with windows 7 on it. It ran for almost two full months on windows 7 and it just started doing this the middle of last week. It is filling up the error log with FIDOIN returned - 1 and FIDOOUT returned - 1... I have not changed anything in the settings. I had it running on windows xp and decided to upgrade to windows 7 to run it on. Any suggestions or ideas as to what can help take care of this problem would be of great help.

    Are you using these events (e.g. for Fido networking)? If not, just disable them in SCFG. If you are using them, then take a look at your data/sbbsecho.log file and see what that says. If you can't figure out the problem, report back with:
    1. The version of SBBSecho you're running
    2. The command-lines you have configured in SCFG for those timed-events
    3. The errors reported in the sbbsecho.log file

    digital man

    Synchronet "Real Fact" #9:
    The name "DOVE-Net" comes from: The Beast's DOmain / VErtrauen network.
    Norco, CA WX: 84.4oF, 37.0% humidity, 7 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.01-Win32
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Bill McGarrity@1:266/404 to Mojo on Mon Jul 3 20:03:00 2017
    Mojo wrote to Digital Man on 07-03-17 11:12 <=-

    Hi Digital Man,

    I am getting errors every time FIDOIN & FIDOOUT runs and I am not sure
    why all of the sudden it has started doing this. It was not doing it
    when I moving the BBS over to a machine with windows 7 on it. It ran
    for almost two full months on windows 7 and it just started doing this
    the middle of last week. It is filling up the error log with FIDOIN returned - 1 and FIDOOUT returned - 1... I have not changed anything in the settings. I had it running on windows xp and decided to upgrade to windows 7 to run it on. Any suggestions or ideas as to what can help
    take care of this problem would be of great help.


    Look in your secure and insecure incoming folders and see if there are any untossed pkts. Also see if there are any unsent pkts in your outbound folder, including NETMAIL.


    --

    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)
  • From Mojo@1:103/705 to Bill McGarrity on Tue Jul 4 11:24:22 2017
    Re: SBBSECHO Errors
    By: Bill McGarrity to Mojo on Mon Jul 03 2017 08:03 pm

    Look in your secure and insecure incoming folders and see if there are any untossed pkts. Also see if there are any unsent pkts in your outbound folder, including NETMAIL.



    I have been checking this since this problem and the incoming and outgoing are all being taken care of and as of now 11:23am July 4 2017 there is nothing waiting to be processed..


    Thanks
    Mojo

    ---
    * Synchronet * Mojo's World BBS - mojo.synchro.net
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Mojo@1:103/705 to Digital Man on Tue Jul 4 12:25:16 2017
    Re: SBBSECHO Errors
    By: Digital Man to Mojo on Mon Jul 03 2017 12:26 pm

    Are you using these events (e.g. for Fido networking)? If not, just disable them in SCFG. If you are using them, then take a look at your data/sbbsecho.log file and see what that says. If you can't figure out the problem, report back with:
    1. The version of SBBSecho you're running
    2. The command-lines you have configured in SCFG for those timed-events
    3. The errors reported in the sbbsecho.log file


    Yes, i am using the FIDO networking.


    Version SBBSecho 3.00-Win32 r3.33 Mar 31 2017 MSC 1800 invoked with options: -lesr!


    FIDOIN command line
    %!sbbsecho%. -lesr!

    FIDOOUT command line
    %!sbbsecho%. -linf


    Here is a copy of the last entry in the log file.



    2017-07-04 12:13:02 SBBSecho 3.00-Win32 r3.33 Mar 31 2017 MSC 1800 invoked with options: -lesr!
    2017-07-04 12:13:02 1 packers, 43 linked-nodes, 0 echolists configured 2017-07-04 12:13:02 DUPLICATE AREA (BN_HQ) in area file (c:\sbbs\data\AREAS.BBS), IGNORED!
    2017-07-04 12:13:02 DUPLICATE AREA (BN_GENERAL) in area file (c:\sbbs\data\AREAS.BBS), IGNORED!
    2017-07-04 12:13:02 DUPLICATE AREA (ARCHERY) in area file (c:\sbbs\data\AREAS.BBS), IGNORED!
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 1:120/302 to 1:261/38: c:\sbbs\temp\sbbsecho\5955b27e.pkt
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 57:57/29 to 57:57/1: c:\sbbs\temp\sbbsecho\59588139.pkt
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 777:777/19 to 777:777/777: c:\sbbs\temp\sbbsecho\5958813a.pkt
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 510:321/5 to 510:199/1: c:\sbbs\temp\sbbsecho\5958813b.pkt
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 46:1/141 to 46:1/100: c:\sbbs\temp\sbbsecho\5958813c.pkt
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 411:411/11 to 411:411/0: c:\sbbs\temp\sbbsecho\5958813d.pkt
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 10:10/151 to 10:10/1: c:\sbbs\temp\sbbsecho\5958813e.pkt
    2017-07-04 12:13:02 Stray Outbound Packet (type 2+) found, from 33:356/6 to 33:352/0: c:\sbbs\temp\sbbsecho\5958813f.pkt
    2017-07-04 12:13:02 8 stray outbound packets (8 total pkts) found in c:\sbbs\temp\sbbsecho\
    2017-07-04 12:13:02 Unpacking bundle: c:\sbbs\binkd\insec\1f6481be.tu1 (1.4KB) 2017-07-04 12:13:02 Executing: c:\sbbs\exec\pkunzip c:\sbbs\binkd\insec\1f6481be.tu1 c:\sbbs\binkd\insec\
    2017-07-04 12:13:02 Deleting c:\sbbs\binkd\insec\1f6481be.tu1 (from line 2114) 2017-07-04 12:13:02 Importing c:\sbbs\binkd\insec\1F6481A8.PKT (Type 2e, 2.4KB) from 1:261/38 to 1:120/302
    2017-07-04 12:13:02 Deleting c:\sbbs\binkd\insec\1F6481A8.PKT (from line 4941) 2017-07-04 12:13:02 Imported: 1 msgs ham <- HAM
    2017-07-04 12:13:02 Imported: 1 msgs syncsyso <- SYNC_SYSOPS 2017-07-04 12:13:02 Imported: 2 msgs total
    2017-07-04 12:13:02 c:\sbbs\binkd\out\1.msg BRE System (169:1/107) To: BRE System (169:1/162) Unknown user
    2017-07-04 12:13:02 c:\sbbs\binkd\out\8.msg ZOM-IBBS (24:100/1) To: Zombie Slots (24:120/3) Unknown user
    2017-07-04 12:13:02 c:\sbbs\binkd\out\9.msg MEG-IBBS (24:100/1) To: Mega Slots (24:120/3) Unknown user
    2017-07-04 12:13:02 Packing NetMail (10.MSG) from Arrowbridge II (10:10/151) to Arrowbridge II (10:3/1), attr: 0191, subject: ^d:\l10\ab2\OUTBOUND\A2100201.113 2017-07-04 12:13:02 Routing NetMail (10.MSG) to 10:10/1
    2017-07-04 12:13:02 Node (10:10/1) successfully locked via: c:\sbbs\binkd\out.00a\000a0001.bsy
    2017-07-04 12:13:02 ERROR line 470, attachment file not found: ^d:\l10\ab2\OUTBOUND\A2100201.113
    2017-07-04 12:13:02 Deleting c:\sbbs\binkd\out.00a\000a0001.bsy (from line 2293)
    2017-07-04 12:13:02 Deleting c:\sbbs\ctrl\sbbsecho.bsy (from line 2297) 2017-07-04 12:13:02 SBBSecho exiting with error level 1, NetMail(0 imported, 0 exported, 0 packed), EchoMail(2 imported, 0 exported)

    ---
    * Synchronet * Mojo's World BBS - mojo.synchro.net
    * Origin: Vertrauen - vert.synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Mojo on Tue Jul 4 18:29:30 2017
    Re: SBBSECHO Errors
    By: Mojo to Digital Man on Tue Jul 04 2017 12:25 pm

    Here is a copy of the last entry in the log file.

    2017-07-04 12:13:02 Packing NetMail (10.MSG) from Arrowbridge II (10:10/151) to Arrowbridge II (10:3/1), attr: 0191, subject: ^d:\l10\ab2\OUTBOUND\A2100201.113 2017-07-04 12:13:02 Routing NetMail (10.MSG) to 10:10/1
    2017-07-04 12:13:02 Node (10:10/1) successfully locked via: c:\sbbs\binkd\out.00a\000a0001.bsy
    2017-07-04 12:13:02 ERROR line 470, attachment file not found: ^d:\l10\ab2\OUTBOUND\A2100201.113

    There's your problem. It looks like Arrowbridge is prepending the caret (^) symbol on the path to the attached file path. FTS-1 (http://ftsc.org/docs/fts-0001.016) doesn't seem to support this syntax. Is there a configuration option to disable this behavior for this doorgame?

    digital man

    Synchronet/BBS Terminology Definition #14:
    DOCSIS = Data Over Cable Service Interface Specification
    Norco, CA WX: 85.2oF, 39.0% humidity, 13 mph ESE wind, 0.00 inches rain/24hrs --- SBBSecho 3.01-Win32
    * Origin: Vertrauen - vert.synchro.net (1:103/705)