• ERROR: Unable to find echonode 0 while bundling

    From bcw142@21:1/145 to All on Saturday, January 21, 2017 19:20:00
    Anyone know what that 'ERROR: Unable to find echonode 0 while bundling'
    is caused by? I have Nodes 1-4, there is no 0 so what is it about? An example is:
    + Jan 21 19:08:43 Extracting 0000ffd3.su6
    - Jan 21 19:08:43 unzip -oqjC "/mystic/echomail/in/0000ffd3.su6" "*.pkt"
    -d /mystic/temputil/
    + Jan 21 19:08:43 Importing 0d64dfd5.pkt (21:1/100 to 21:1/145)
    + Jan 21 19:08:43 Import #508 to FSX_BOT
    + Jan 21 19:08:43 Export FSX_BOT #508 to 21:1/145.1@fsxnet
    + Jan 21 19:08:43 Bundling Messages
    ! Jan 21 19:08:43 ERROR: Unable to find echonode 0 while bundling
    - Jan 21 19:08:43 EXEC: zip -qj9 /mystic/echomail/out/fidonet/00010091.pnt/00000001.saa /mystic/temputil/0ced83a8.pkt
    + Jan 21 19:08:43 Adding PKT "/mystic/echomail/out/fidonet/00010091.pnt/00000001.saa" to FLO /mystic/echomail/out/fidonet/00010091.pnt/00000001.hlo
    + Jan 21 19:08:43 Results: 1 echo, 0 net, 0 dupes, 1 tossed in 0.21s
    + Jan 21 19:08:43 Process: Linking Messages

    So things are working, but what is that echonode 0 business?

    ...Listening to http://listen.totalfm.nz:8000/stream ;)

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)
  • From Avon@21:1/101 to bcw142 on Sunday, January 22, 2017 13:50:00
    On 01/21/17, bcw142 pondered and said...

    Anyone know what that 'ERROR: Unable to find echonode 0 while bundling'
    is caused by? I have Nodes 1-4, there is no 0 so what is it about? An example is:

    Check the post from bl00d to me within the last week or so about this in
    this echo area... he found a file in a temp dir that was leading to this
    issue. :)

    Best, Paul

    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From bcw142@21:1/145 to Avon on Sunday, January 22, 2017 03:59:00
    On 01/22/17, Avon said the following...
    On 01/21/17, bcw142 pondered and said...

    Anyone know what that 'ERROR: Unable to find echonode 0 while bundlin is caused by? I have Nodes 1-4, there is no 0 so what is it about? An example is:

    Check the post from bl00d to me within the last week or so about this in this echo area... he found a file in a temp dir that was leading to this issue. :)

    Best, Paul
    --- Mystic BBS v1.12 A31 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

    Seems to have been a few files that got stuck back at the end of December:
    ! Jan 22 03:42:58 Import from /mystic/echomail/in/
    ! Jan 22 03:42:58 Unknown inbound file RETRONET.1.Z58
    ! Jan 22 03:42:58 Unknown inbound file RETRONET.1.ZIP
    ! Jan 22 03:42:58 Unknown inbound file fsxinfo.1.zip
    Deleted them and the error seems to have gone.

    --- Mystic BBS v1.12 A31 (Raspberry Pi)
    * Origin: Mystic Pi BBS bcw142.zapto.org (21:1/145)