• Issue with Bluewave downloads

    From Blue White@21:4/134 to apam on Sat Oct 12 19:36:34 2019
    I upgraded to the latest as of 0900 USET this morning. Just tried to
    download a bluewave packet. The process gets through checking 5 or 6
    areas, and then abuptly drops carrier.

    I tried it a couple of times and got the same result, so I restored the binaries, utils, source, and anything else with an update date of today back
    to my previous compile from sometime in March.



    ... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/125.99 to Blue White on Sun Oct 13 13:38:46 2019
    I upgraded to the latest as of 0900 USET this morning. Just tried to download a bluewave packet. The process gets through checking 5 or 6 areas, and then abuptly drops carrier.

    Hmm, I've not been able to reproduce this.. would it be possible to grab
    a copy of your message bases?

    Andrew


    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From Blue White@21:4/134 to apam on Sun Oct 13 09:58:02 2019
    apam wrote to Blue White <=-

    I upgraded to the latest as of 0900 USET this morning. Just tried to download a bluewave packet. The process gets through checking 5 or 6 areas, and then abuptly drops carrier.

    Hmm, I've not been able to reproduce this.. would it be possible to
    grab a copy of your message bases?

    I shall try to tar them all up and send them to you in a bit.


    ... DalekDOS v(overflow): (I)Obey (V)ision impaired (E)xterminate
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From Blue White@21:4/134 to apam on Sun Oct 13 14:54:18 2019
    I upgraded to the latest as of 0900 USET this morning. Just tr
    ied to
    download a bluewave packet. The process gets through checking
    5 or 6
    areas, and then abuptly drops carrier.

    Hmm, I've not been able to reproduce this.. would it be possible to
    grab
    a copy of your message bases?

    OK, I have a gzipped tarball. It is still over 62,000,000 bytes so I
    cannot email attach it. Do you have any suggestions? Thanks!


    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/125.99 to Blue White on Mon Oct 14 10:37:13 2019
    OK, I have a gzipped tarball. It is still over 62,000,000 bytes so I cannot email attach it. Do you have any suggestions? Thanks!

    You could upload it to my synchronet bbs, but you'll have to rename it to something 8.3 filename.

    nocturnal.hopto.org 2023

    Andrew


    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From Blue White@21:4/134 to apam on Mon Oct 14 17:18:04 2019
    Good afternoon,
    I just uploaded it as a personal upload to you. I renamed it
    possum.gz from the original possum.tar.gz.

    Thanks!

    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/125.99 to Blue White on Tue Oct 15 10:01:02 2019
    Good afternoon,
    I just uploaded it as a personal upload to you. I renamed it
    possum.gz from the original possum.tar.gz.

    Thanks for that. I've set it up here, but still can't reproduce the
    problem :(

    Could you send me your ini files too? Perhaps that has something to do
    with it..

    ANdrew

    --- MagickaBBS v0.13alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From Blue White@21:4/134 to apam on Tue Oct 15 16:53:24 2019
    apam wrote to Blue White <=-

    Good afternoon,
    I just uploaded it as a personal upload to you. I renamed it
    possum.gz from the original possum.tar.gz.

    Thanks for that. I've set it up here, but still can't reproduce the problem :(

    Could you send me your ini files too? Perhaps that has something to do with it..

    They should be in that tarball. I included both the msgs and config
    folders. I am not 100% certain, but I think it was hanging when it tried
    to transition from the localmail.ini file (local group) to the fidonet.ini
    file (fido group). Seems like I was seeing all of my local area names show
    up before it hung.


    ... Computer Hacker wanted. Must have own axe.
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/125.99 to Blue White on Wed Oct 16 14:57:02 2019
    Could you send me your ini files too? Perhaps that has something to
    do with it..

    I'm an idiot. I see you included them with the other archive... Sorry.

    Andrew

    --- MagickaBBS v0.13alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From apam@21:1/125.99 to Blue White on Wed Oct 16 15:41:14 2019
    They should be in that tarball. I included both the msgs and config folders.

    You did, sorry I missed it.

    I am not 100% certain, but I think it was hanging when it
    tried to transition from the localmail.ini file (local group) to the fidonet.ini file (fido group). Seems like I was seeing all of my
    local area names show up before it hung.

    Hmm. I still can't reproduce it. It might be to do with the last read
    pointers - could you try resetting all of them after upgrading and then download packets? (Keep a copy of your current setup obviously in case it doesn't work)

    Andrew

    --- MagickaBBS v0.13alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From Blue White@21:4/134 to apam on Wed Oct 16 18:37:18 2019
    apam wrote to Blue White <=-

    Hmm. I still can't reproduce it. It might be to do with the last read pointers - could you try resetting all of them after upgrading and then download packets? (Keep a copy of your current setup obviously in case
    it doesn't work)

    Resetting them to all read or just some arbitrary position?


    ... Computer Hacker wanted. Must have own axe.
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/125.99 to Blue White on Thu Oct 17 09:37:30 2019
    apam wrote to Blue White <=-

    Hmm. I still can't reproduce it. It might be to do with the last pointers - could you try resetting all of them after upgrading an download packets? (Keep a copy of your current setup obviously in
    it doesn't work)

    Resetting them to all read or just some arbitrary position?

    I was thinking unread, and then seeing if downloading works. You will
    have to do several packets though as your bluewave is limited to 5000
    messages per packet.

    Andrew

    --- MagickaBBS v0.13alpha (Linux/armv7l)
    * Origin: Twilight BBS (21:1/125.99)
  • From Blue White@21:4/134 to apam on Sun Oct 20 16:28:20 2019
    apam wrote to Blue White <=-

    Hmm. I still can't reproduce it. It might be to do with the l pointers - could you try resetting all of them after upgradin download packets? (Keep a copy of your current setup obviousl
    it doesn't work)

    Resetting them to all read or just some arbitrary position?

    I was thinking unread, and then seeing if downloading works. You will
    have to do several packets though as your bluewave is limited to 5000 messages per packet.

    Andrew

    Well, that might be easier said than done. I tried doing a git pull this afternoon and it aborted because it said I had changes that I needed to
    commit first. As I have not changed users.c or any of the other source
    code it had listed, I find this difficult to believe. As I don't want to
    lose the code (in case I need to fall back due to this issue) I am leery
    to remove the offending members.

    Thanks!


    --- MagickaBBS v0.12alpha (Linux/armv7l)
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)
  • From apam@21:1/126 to Blue White on Mon Oct 21 09:39:05 2019
    Well, that might be easier said than done. I tried doing a git pull this afternoon and it aborted because it said I had changes that I needed to commit first. As I have not changed users.c or any of the other source code it had listed, I find this difficult to believe. As I don't want to lose the code (in case I need to fall back due to this issue) I am leery to remove the offending members.

    That is odd.

    unless when you restored your files last time you didn't restore the .git directory along with it. It may think it's still running a recent version
    that has been modified back to an old version (if that makes sense?)

    My suggestion is to make a backup of everything, the entire MagickaBBS directory, so you can delete the offending files and update cleanly, then
    if it doesn't work just delete your MagickaBBS directory and copy the old
    one back over.

    Of course, if the version you are using is working for you and you are
    happy with it the way it is, don't worry about it :)

    Andrew


    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand (21:1/126)
  • From Blue White@21:4/134 to apam on Mon Oct 21 11:53:30 2019
    apam wrote to Blue White <=-

    unless when you restored your files last time you didn't restore the
    .git directory along with it. It may think it's still running a recent version that has been modified back to an old version (if that makes sense?)

    With it being a 'dot' directory, I wonder if I indeed did not restore it!
    I will go ahead and back it up, remove the files it complains about and see what happens next. Thanks!


    ... Got my tie caught in the fax... Suddenly I was in L.A.
    --- MultiMail
    * Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)