• sbbsecho and file attaches

    From mark lewis@VERT to digital man on Monday, August 05, 2019 23:13:00
    sadly, sbbsecho is still broken with regard to file attaches... i can't tell what the problem is but now when it hits a netmail with a valid file attach on my system, it seems to just exit... there is no

    SBBSecho exiting with error level X, Packets(Y imported, Z sent)

    line and the ctrl/sbbsecho.bsy file is left behind as well as bsy files in my BSO for systems that may have been processed during that run... it is like the loop is exiting at a certain point and not completing the job or something...

    i have the latest CVS code as of 2019-08-05 14:42 -0400

    ummm... what is this number at the beginning of this line in the ctrl/sbbsecho.bsy file?

    26825 SBBSecho 3.08-Linux r3.131 Aug 5 2019 GCC 7.4.0

    is that the PID of that execution of sbbsecho? if yes, i can definitely say that sbbsecho is exiting in this file attach scenario because "ps aux" on my system does not show that PID at all... i've tried to watch/catch sbbsecho execution but the crazy thing is really fast :lol:

    could we maybe get a header line logged when sbbsecho starts up? maybe write that line that goes in the bsy file to the log, too? currently the only way i can tell where one sbbsecho session starts is to find the "exiting with error level" line of the previous run...


    for now i will remove the netmail message in question and manually create the flo file so i can get this new nodelist segment sent out...

    )\/(ark

    Once men turned their thinking over to machines in the hope that this would set
    them free. But that only permitted other men with machines to enslave them.
    ... We've done "promiscuity" entendres?.... Check!
    ---
    * Origin: (1:3634/12.73)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to mark lewis on Tuesday, August 06, 2019 00:48:16
    Re: sbbsecho and file attaches
    By: mark lewis to digital man on Mon Aug 05 2019 04:13 pm


    sadly, sbbsecho is still broken with regard to file attaches... i can't tell what the problem is but now when it hits a netmail with a valid file attach on my system, it seems to just exit... there is no

    SBBSecho exiting with error level X, Packets(Y imported, Z sent)

    If you don't have debug-log level set, you won't *always* get the log entry (depends on if there are any non-zero stats to report).

    line and the ctrl/sbbsecho.bsy file is left behind as well as bsy files in my BSO for systems that may have been processed during that run... it is like the loop is exiting at a certain point and not completing the job or something...

    i have the latest CVS code as of 2019-08-05 14:42 -0400

    ummm... what is this number at the beginning of this line in the ctrl/sbbsecho.bsy file?

    26825 SBBSecho 3.08-Linux r3.131 Aug 5 2019 GCC 7.4.0

    It's the PID.

    is that the PID of that execution of sbbsecho?

    Yes.

    if yes, i can definitely say
    that sbbsecho is exiting in this file attach scenario because "ps aux" on my system does not show that PID at all... i've tried to watch/catch sbbsecho execution but the crazy thing is really fast :lol:

    Is it possible it's crashing? There may be a core file you can use to find the cause.

    could we maybe get a header line logged when sbbsecho starts up?

    If you have the debug log level set, then you should see an "invoked with options" log line every time SBBSecho starts up:

    08/05/19 17:43:49 SBBSecho 3.08-Linux r3.131 Aug 5 2019 GCC 6.3.0 invoked with options: -linf

    maybe write
    that line that goes in the bsy file to the log, too? currently the only way i can tell where one sbbsecho session starts is to find the "exiting with error level" line of the previous run...

    for now i will remove the netmail message in question and manually create the flo file so i can get this new nodelist segment sent out...

    It sounds like it may be crashing. If you just run sbbsecho from a command prompt, hopefully that'll make it clear what's happening.

    digital man

    Synchronet/BBS Terminology Definition #57:
    RIP = Remote Imaging Protocol (e.g. RIPscrip)
    Norco, CA WX: 89.0F, 34.0% humidity, 14 mph ENE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From mark lewis@VERT to Digital Man on Tuesday, August 06, 2019 16:09:28
    On 2019 Aug 05 17:48:16, you wrote to me:

    sadly, sbbsecho is still broken with regard to file attaches... i can't
    tell what the problem is but now when it hits a netmail with a valid
    file attach on my system, it seems to just exit... there is no

    SBBSecho exiting with error level X, Packets(Y imported, Z sent)

    If you don't have debug-log level set, you won't *always* get the log
    entry
    (depends on if there are any non-zero stats to report).

    hummm... [time passes] ok now i have debug logging enabled for sbbsecho... will
    keep a closer eye on it...

    is that the PID of that execution of sbbsecho?

    Yes.

    thanks :)

    if yes, i can definitely say that sbbsecho is exiting in this file
    attach scenario because "ps aux" on my system does not show that PID at
    all... i've tried to watch/catch sbbsecho execution but the crazy thing
    is really fast :lol:

    Is it possible it's crashing? There may be a core file you can use to find the cause.

    haven't found any core files...

    could we maybe get a header line logged when sbbsecho starts up?

    If you have the debug log level set, then you should see an "invoked with options" log line every time SBBSecho starts up:

    08/05/19 17:43:49 SBBSecho 3.08-Linux r3.131 Aug 5 2019 GCC 6.3.0 invoked with options: -linf

    based on that, i didn't have debug logging set... it was set to informational :/

    maybe write
    that line that goes in the bsy file to the log, too? currently the only
    way i can tell where one sbbsecho session starts is to find the "exiting
    with error level" line of the previous run...

    for now i will remove the netmail message in question and manually
    create the flo file so i can get this new nodelist segment sent out...

    It sounds like it may be crashing. If you just run sbbsecho from a command prompt, hopefully that'll make it clear what's happening.

    i'll try that next time...

    )\/(ark

    Once men turned their thinking over to machines in the hope that this would set
    them free. But that only permitted other men with machines to enslave them.
    ... I *do* have a 32" waist. My fat is there to protect my perfect body ;*)
    ---
    * Origin: (1:3634/12.73)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to mark lewis on Wednesday, August 07, 2019 03:25:30
    Re: sbbsecho and file attaches
    By: mark lewis to Digital Man on Tue Aug 06 2019 09:09 am


    On 2019 Aug 05 17:48:16, you wrote to me:

    sadly, sbbsecho is still broken with regard to file attaches... i can't
    tell what the problem is but now when it hits a netmail with a valid
    file attach on my system, it seems to just exit... there is no

    SBBSecho exiting with error level X, Packets(Y imported, Z sent)

    If you don't have debug-log level set, you won't *always* get the log
    entry
    (depends on if there are any non-zero stats to report).

    hummm... [time passes] ok now i have debug logging enabled for sbbsecho... will keep a closer eye on it...

    is that the PID of that execution of sbbsecho?

    Yes.

    thanks :)

    if yes, i can definitely say that sbbsecho is exiting in this file
    attach scenario because "ps aux" on my system does not show that PID at
    all... i've tried to watch/catch sbbsecho execution but the crazy thing
    is really fast :lol:

    Is it possible it's crashing? There may be a core file you can use to find the cause.

    haven't found any core files...

    could we maybe get a header line logged when sbbsecho starts up?

    If you have the debug log level set, then you should see an "invoked with options" log line every time SBBSecho starts up:

    08/05/19 17:43:49 SBBSecho 3.08-Linux r3.131 Aug 5 2019 GCC 6.3.0 invoked with options: -linf

    based on that, i didn't have debug logging set... it was set to informational :/

    maybe write
    that line that goes in the bsy file to the log, too? currently the only
    way i can tell where one sbbsecho session starts is to find the "exiting
    with error level" line of the previous run...

    for now i will remove the netmail message in question and manually
    create the flo file so i can get this new nodelist segment sent out...

    It sounds like it may be crashing. If you just run sbbsecho from a command prompt, hopefully that'll make it clear what's happening.

    i'll try that next time...

    I haven't done anything to fix it, so you should still be able to reproduce it (likey a crash), but I don't know the cause or how to trigger it.

    digital man

    This Is Spinal Tap quote #45:
    I don't really think the end can be assessed as of itself as being the end Norco, CA WX: 75.4F, 59.0% humidity, 7 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Rampage@VERT/SESTAR to Digital Man on Wednesday, August 07, 2019 14:18:27
    Re: sbbsecho and file attaches
    By: Digital Man to mark lewis on Tue Aug 06 2019 20:25:30

    It sounds like it may be crashing. If you just run sbbsecho from a command prompt, hopefully that'll make it clear what's happening.

    i'll try that next time...

    I haven't done anything to fix it, so you should still be able to reproduce it (likey a crash), but I don't know the cause or how to trigger it.

    the way to trigger it is via a netmail message with a file attached... i'll try to gather more data...

    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Digital Man@VERT to Rampage on Thursday, August 08, 2019 05:15:55
    Re: sbbsecho and file attaches
    By: Rampage to Digital Man on Wed Aug 07 2019 07:18 am

    Re: sbbsecho and file attaches
    By: Digital Man to mark lewis on Tue Aug 06 2019 20:25:30

    It sounds like it may be crashing. If you just run sbbsecho from a command prompt, hopefully that'll make it clear what's happening.

    i'll try that next time...

    I haven't done anything to fix it, so you should still be able to reproduce it (likey a crash), but I don't know the cause or how to trigger it.

    the way to trigger it is via a netmail message with a file attached... i'll try to gather more data...

    I tried that (and attachment to an FTN netmail message) and it worked without issue.

    digital man

    Synchronet/BBS Terminology Definition #48:
    NAPLPS = North American Presentation Layer Protocol Syntax (ANSI X3.110)
    Norco, CA WX: 66.7F, 85.0% humidity, 3 mph E wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Rampage@VERT/SESTAR to Digital Man on Thursday, August 08, 2019 17:56:40
    Re: sbbsecho and file attaches
    By: Digital Man to Rampage on Wed Aug 07 2019 22:15:55

    the way to trigger it is via a netmail message with a file attached... i'll try to gather more data...

    I tried that (and attachment to an FTN netmail message) and it worked without issue.

    i don't know then... unless maybe it has something to do with the makeup of the msg files that makenl is creating for sbbsecho to process and send on toward the destination... i've only seen the problem with locally generated 3rd party msg files... the routed netmails with missing attachment were a different problem...

    )\/(ark

    ---
    Synchronet The SouthEast Star Mail HUB - SESTAR
  • From Digital Man@VERT to Rampage on Thursday, August 08, 2019 18:42:06
    Re: sbbsecho and file attaches
    By: Rampage to Digital Man on Thu Aug 08 2019 10:56 am

    Re: sbbsecho and file attaches
    By: Digital Man to Rampage on Wed Aug 07 2019 22:15:55

    the way to trigger it is via a netmail message with a file attached... i'll try to gather more data...

    I tried that (and attachment to an FTN netmail message) and it worked without issue.

    i don't know then... unless maybe it has something to do with the makeup of the msg files that makenl is creating for sbbsecho to process and send on toward the destination... i've only seen the problem with locally generated 3rd party msg files... the routed netmails with missing attachment were a different problem...

    Any time SBBSecho leaves a stale .bsy file around, that very likely means it crashed. So if you can reproduce that crash and provide me with a backtrace (e.g. from gdb) - that'd be very much appreciated.

    You can just "gdb sbbsecho" and type "run" at the (gdb) prompt. If/when it crashes, you can use "bt" to print a backtrace, then copy/paste to me.

    For more details:
    http://wiki.synchro.net/howto:gdb

    digital man

    Synchronet/BBS Terminology Definition #70:
    SyncEdit = A defunct 3rd party full-screen editor written for Synchronet
    Norco, CA WX: 80.6F, 58.0% humidity, 1 mph ESE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From mark lewis@VERT to Digital Man on Friday, August 09, 2019 21:20:26
    On 2019 Aug 08 11:42:06, you wrote to Rampage:

    i don't know then... unless maybe it has something to do with the
    makeup of the msg files that makenl is creating for sbbsecho to process
    and send on toward the destination... i've only seen the problem with
    locally generated 3rd party msg files... the routed netmails with
    missing attachment were a different problem...

    Any time SBBSecho leaves a stale .bsy file around, that very likely
    means it crashed. So if you can reproduce that crash and provide me
    with a backtrace (e.g. from gdb) - that'd be very much appreciated.

    i'll see what i can do... i'm going to update to the latest code (at that time)
    before testing, though ;)

    You can just "gdb sbbsecho" and type "run" at the (gdb) prompt.
    If/when it crashes, you can use "bt" to print a backtrace, then
    copy/paste to me.

    gotcha... i'm actually fairly versed with bt and "thread apply all bt" in my testing work with several games and simulators :P

    )\/(ark

    Once men turned their thinking over to machines in the hope that this would set
    them free. But that only permitted other men with machines to enslave them.
    ... We are born naked, wet and hungry - and then things get worse.
    ---
    * Origin: (1:3634/12.73)
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net
  • From Digital Man@VERT to mark lewis on Friday, August 09, 2019 20:11:59
    Re: sbbsecho and file attaches
    By: mark lewis to Digital Man on Fri Aug 09 2019 02:20 pm

    You can just "gdb sbbsecho" and type "run" at the (gdb) prompt.
    If/when it crashes, you can use "bt" to print a backtrace, then copy/paste to me.

    gotcha... i'm actually fairly versed with bt and "thread apply all bt" in my testing work with several games and simulators :P

    Okay, cool. In this case, sbbsecho is single-threaded, so just "bt" should be all that's needed.

    digital man

    Synchronet "Real Fact" #82:
    Flapuebarg unf vagreany ebg13 fhccbeg sbe fhcresvpvnyyl rapelcgvat grkg.
    Norco, CA WX: 88.7F, 34.0% humidity, 6 mph ENE wind, 0.00 inches rain/24hrs

    ---
    Synchronet Vertrauen Home of Synchronet [vert/cvs/bbs].synchro.net