• MBSE bugs in mbout sta

    From Vince Coen@2:250/1 to All on Wed Jan 9 13:55:25 2019
    Hello All!

    I have reported this before as far as the first isue but found a second problem :

    1. The size counts are double than the actual figures.
    2. Aging is also wrong but in this case way wrong for example showing a node
    with
    ...H.. 0 33010108 10/20h 2:250/9@fidonet

    where the files arrived over the last two days and mail packets only go back 2 days.

    Clearly a serious case of can't calculate correctly.
    I did have a quick look at the code but could not spot the obvious so can any one else do
    so?



    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Andrew Leary@1:320/219 to Vince Coen on Wed Jan 9 11:36:24 2019
    Hello Vince!

    09 Jan 19 13:55, you wrote to all:

    I have reported this before as far as the first isue but found a
    second problem :

    1. The size counts are double than the actual figures.
    2. Aging is also wrong but in this case way wrong for example showing
    a node
    with
    ...H.. 0 33010108 10/20h 2:250/9@fidonet

    where the files arrived over the last two days and mail packets only
    go back 2 days.

    I will take a look at this over the next few days. I think the age may be the last successful outbound connect to that system, but I won't know until I look at the code. As far as the size issue, I should be able to check that at the same time.

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Vince Coen@2:250/1 to Andrew Leary on Thu Jan 10 14:31:31 2019
    Hello Andrew!

    Wednesday January 09 2019 11:36, you wrote to me:

    Thanks, I do use it a lot - well would do even more if it is accurate.


    Hello Vince!

    09 Jan 19 13:55, you wrote to all:

    I have reported this before as far as the first isue but found a
    second problem :

    1. The size counts are double than the actual figures.
    2. Aging is also wrong but in this case way wrong for example
    showing a node
    with
    ...H.. 0 33010108 10/20h 2:250/9@fidonet

    where the files arrived over the last two days and mail packets
    only go back 2 days.

    I will take a look at this over the next few days. I think the age
    may be the last successful outbound connect to that system, but I
    won't know until I look at the code. As far as the size issue, I
    should be able to check that at the same time.

    Andrew



    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Andrew Leary@1:320/219 to Vince Coen on Mon Jan 14 02:45:46 2019
    Hello Vince!

    10 Jan 19 14:31, you wrote to me:

    I have reported this before as far as the first isue but found a
    second problem :

    1. The size counts are double than the actual figures.
    2. Aging is also wrong but in this case way wrong for example
    showing a node
    with
    ...H.. 0 33010108 10/20h 2:250/9@fidonet

    where the files arrived over the last two days and mail packets
    only go back 2 days.

    I will take a look at this over the next few days. I think the age
    may be the last successful outbound connect to that system, but I
    won't know until I look at the code. As far as the size issue, I
    should be able to check that at the same time.

    My initial review of the code did not turn up anything that looks out of whack. I even manually added up what was in the queue for one of my downlinks that was marked undialable, and it came out exactly to the byte on size, and the age appeared to be that of the oldest file in the queue for him. Does the node that you see the problem with use a filebox?

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Vince Coen@2:250/1 to Andrew Leary on Mon Jan 14 23:53:41 2019
    Hello Andrew!

    Monday January 14 2019 02:45, you wrote to me:

    Hello Vince!

    10 Jan 19 14:31, you wrote to me:

    I have reported this before as far as the first isue but found
    a second problem :

    1. The size counts are double than the actual figures.
    2. Aging is also wrong but in this case way wrong for example
    showing a node
    with
    ...H.. 0 33010108 10/20h 2:250/9@fidonet

    where the files arrived over the last two days and mail
    packets only go back 2 days.

    I will take a look at this over the next few days. I think the
    age may be the last successful outbound connect to that system,
    but I won't know until I look at the code. As far as the size
    issue, I should be able to check that at the same time.

    My initial review of the code did not turn up anything that looks out
    of whack. I even manually added up what was in the queue for one of my downlinks that was marked undialable, and it came out exactly to the
    byte on size, and the age appeared to be that of the oldest file in
    the queue for him. Does the node that you see the problem with use a filebox?

    No, no nodes have boxes set up.

    Had problems with them a few years back that may have been the reason why some nodes was getting echos for others so just killed them all off.


    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Vince Coen@2:250/1 to Andrew Leary on Tue Jan 15 00:18:07 2019
    Hello Andrew!

    Monday January 14 2019 02:45, you wrote to me:

    Hello Vince!

    10 Jan 19 14:31, you wrote to me:

    I have reported this before as far as the first isue but found
    a second problem :

    1. The size counts are double than the actual figures.
    2. Aging is also wrong but in this case way wrong for example
    showing a node
    with
    ...H.. 0 33010108 10/20h 2:250/9@fidonet

    where the files arrived over the last two days and mail
    packets only go back 2 days.

    I will take a look at this over the next few days. I think the
    age may be the last successful outbound connect to that system,
    but I won't know until I look at the code. As far as the size
    issue, I should be able to check that at the same time.

    My initial review of the code did not turn up anything that looks out
    of whack. I even manually added up what was in the queue for one of my downlinks that was marked undialable, and it came out exactly to the
    byte on size, and the age appeared to be that of the oldest file in
    the queue for him. Does the node that you see the problem with use a filebox?

    No, no nodes have boxes set up.

    Had problems with them a few years back that may have been the reason why some nodes was getting echos for others so just killed them all off.

    I have now got a back up system running on a Pi 3B+ that rsync with the primary
    system so when I get a chance I will take a look at what mbout does with that after a rsync run.

    .. hmm might as well try it now .....

    Allowing for a small time difference they are the same :

    Primary:

    -bash-4.3$ mbout sta

    MBOUT: MBSE BBS 1.0.7.11 Outbound Manager
    Copyright (C) 1997-2018 MBSE Development Team, All Rights Reserved

    flavor try size age address
    ...H.. 1 3425356 7/00h 2:250/6@fidonet
    ...H.. 0 1830136 12:19m 2:250/5@fidonet
    ...H.. 0 54412 16:56m 2:250/2@fidonet
    ...H.. 0 164214 11:53 2:250/8@fidonet
    ...H.. 0 2548 11:53 2:250/1.1@fidonet
    ...H.. 0 164826960 8/15h 2:250/9@fidonet
    ...H.. 0 154660 11:54 2:250/4@fidonet


    BAckup :

    mbse@raspberrypi:~ $ mbout sta

    MBOUT: MBSE BBS 1.0.7.11 Outbound Manager
    Copyright (C) 1997-2018 MBSE Development Team, All Rights Reserved

    flavor try size age address
    ...H.. 0 2548 14:18 2:250/1.1@fidonet
    ...H.. 0 54412 16:58m 2:250/2@fidonet
    ...H.. 0 164826960 8/15h 2:250/9@fidonet
    ...H.. 1 3425356 7/00h 2:250/6@fidonet
    ...H.. 0 5320 1/16h 2:250/25@fidonet
    ...H.. 0 164214 14:18 2:250/8@fidonet
    ...H.. 0 154660 14:19 2:250/4@fidonet
    ...H.. 0 1830136 12:22m 2:250/5@fidonet

    Both running same version and yes recompiled as primary is AMD and Pi is Arm x32 bit for some reason despite cpu being x64 but distro (Rasbian) is only 32. The older Pi's are all 32bit.

    Pi has had a change to the primary AKA to 2:250/10 where primary is 2:250/1

    and yes I did stop mbsebbs running on the Pi before running rsync then I restarted it.

    Do have different mbsebbs / mbsed scripts in /etc/init.d | /etc/rc.d/init.d

    Cannot see where it comes from though in the codebase.


    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)
  • From Andrew Leary@1:320/219 to Vince Coen on Sat Jan 19 20:22:50 2019
    Hello Vince!

    15 Jan 19 00:18, you wrote to me:

    No, no nodes have boxes set up.

    Had problems with them a few years back that may have been the reason
    why some nodes was getting echos for others so just killed them all
    off.

    I have now got a back up system running on a Pi 3B+ that rsync with
    the primary system so when I get a chance I will take a look at what
    mbout does with that after a rsync run.

    .. hmm might as well try it now .....

    Allowing for a small time difference they are the same :

    Primary:

    -bash-4.3$ mbout sta

    MBOUT: MBSE BBS 1.0.7.11 Outbound Manager
    Copyright (C) 1997-2018 MBSE Development Team, All Rights
    Reserved

    flavor try size age address
    ...H.. 1 3425356 7/00h 2:250/6@fidonet
    ...H.. 0 1830136 12:19m 2:250/5@fidonet
    ...H.. 0 54412 16:56m 2:250/2@fidonet
    ...H.. 0 164214 11:53 2:250/8@fidonet
    ...H.. 0 2548 11:53 2:250/1.1@fidonet
    ...H.. 0 164826960 8/15h 2:250/9@fidonet
    ...H.. 0 154660 11:54 2:250/4@fidonet

    Run one of these again, and send me the output, along with a .zip file containing your /home/mbse/var/bso/outbound and /home/mbse/var/ticqueue.

    I just need to see is in your outbound .hlo files and the tic queue so I can try to figure out where it's going wrong for you.

    Do you have any symlinks to or from your outbound directory? Are you using the DOS path translation feature (mbsetup 1.4.7) or the TMail filebox support (mbsetup 1.4.10.9 and 1.4.10.10?)

    Without seeing what is on your system when you get these incorrect results, I can only speculate as to why it's not working correctly.

    Andrew

    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Phoenix BBS * phoenix.bnbbbs.net (1:320/219)
  • From Vince Coen@2:250/1 to Andrew Leary on Sun Jan 20 18:35:57 2019
    Hello Andrew!

    Saturday January 19 2019 20:22, you wrote to me:

    Sent to you direct.


    Vince

    Hello Vince!

    15 Jan 19 00:18, you wrote to me:

    No, no nodes have boxes set up.

    Had problems with them a few years back that may have been the
    reason why some nodes was getting echos for others so just killed
    them all off.

    I have now got a back up system running on a Pi 3B+ that rsync
    with the primary system so when I get a chance I will take a look
    at what mbout does with that after a rsync run.

    .. hmm might as well try it now .....

    Allowing for a small time difference they are the same :

    Primary:

    -bash-4.3$ mbout sta

    MBOUT: MBSE BBS 1.0.7.11 Outbound Manager
    Copyright (C) 1997-2018 MBSE Development Team, All Rights
    Reserved

    flavor try size age address
    ...H.. 1 3425356 7/00h 2:250/6@fidonet
    ...H.. 0 1830136 12:19m 2:250/5@fidonet
    ...H.. 0 54412 16:56m 2:250/2@fidonet
    ...H.. 0 164214 11:53 2:250/8@fidonet
    ...H.. 0 2548 11:53 2:250/1.1@fidonet
    ...H.. 0 164826960 8/15h 2:250/9@fidonet
    ...H.. 0 154660 11:54 2:250/4@fidonet

    Run one of these again, and send me the output, along with a .zip file
    containing your /home/mbse/var/bso/outbound and
    /home/mbse/var/ticqueue.

    I just need to see is in your outbound .hlo files and the tic queue so
    I can try to figure out where it's going wrong for you.

    Do you have any symlinks to or from your outbound directory? Are you
    using the DOS path translation feature (mbsetup 1.4.7) or the TMail
    filebox support (mbsetup 1.4.10.9 and 1.4.10.10?)

    Without seeing what is on your system when you get these incorrect
    results, I can only speculate as to why it's not working correctly.

    Andrew



    Vince

    --- Mageia Linux v6 X64/Mbse v1.0.7.11/GoldED+/LNX 1.1.501-b20150715
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)