1. Forum
  2. FSXNet
  3. FSX MYS

  • MUTIL and No 2020 messages

    From Analog@21:2/123 to All on Mon Feb 3 23:03:47 2020
    Gents,

    I'm not sure the cause, but if I RESCAN any of my uplinks (all Mystic) I'm getting no messages after 2019. I'm on A44 latest release and have copied all the executables over the existing ones.

    Additionally, I get some weird behavior that if I go to the last message
    using the index reader in any rescanned base and read it, I cannot open that message base any more in the Index Reader.

    is there still a bug in the rescan routine? I know a few of my uplinks are on A44 so I can't pinpoint the cause. It's basically corrupted all my echos for those I've rescanned.

    Cheers,

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/01/28 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)
  • From Analog@21:2/123 to All on Mon Feb 3 23:19:53 2020
    I'm not sure the cause, but if I RESCAN any of my uplinks (all Mystic)
    I'm getting no messages after 2019. I'm on A44 latest release and have copied all the executables over the existing ones.

    Additionally, every echo I rescan has one message in it that is completely foobared and usually dated way before the echo even existed. It throws characters all over the Message Reader.

    If anyone wants to login and take a look at what I mean, let me know.

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)
  • From g00r00@21:1/108 to Analog on Tue Feb 4 12:09:27 2020
    Gents,

    Please upgrade to the latest version and report back.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From g00r00@21:1/108 to Analog on Tue Feb 4 12:32:54 2020
    Gents,

    Please upgrade to the latest version and report back.

    Are you using the new reader or the old one? The new one is the M! menu command that has been available for testing, and it will be replacing the old one in A45. I am not investigating anything with the old reader at this point.

    As far as the weird message thing, there was a bug in A43 only where if you did an echomail RESCAN it could import a funky message or two, so that might explain any weirdness there.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Analog@21:2/123 to g00r00 on Tue Feb 4 12:11:40 2020
    As far as the weird message thing, there was a bug in A43 only where if you did an echomail RESCAN it could import a funky message or two, so
    that might explain any weirdness there.

    Ok, I'm on A44 latest, but I assume rescanning A43 uplinks will cause them to not be able to send me anything past 12/30/2019? I am not receiving any
    message on the rescan past this date. I do get new messages but everything between now and 2019 does not come through.

    The weird message or two is a symptom of the Mystic A43 uplink then?

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)
  • From Analog@21:2/123 to g00r00 on Tue Feb 4 12:42:42 2020
    Are you using the new reader or the old one? The new one is the M! menu command that has been available for testing, and it will be replacing
    the old one in A45. I am not investigating anything with the old reader at this point.

    g00r00,

    I was using the old one but changed to the new one and the problem persists:

    If I hit enter on a message bases (with messages) that has a garbled message, it will not open it. I think the real problem is the garbled message is
    messing up the base data structure making it problematic to read. I think I'm going to try to manually edit the record (using some python code) and purge
    the message. Not going to be easy, I'll have to write a few lines of code to clean these.

    Cheers,

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)
  • From g00r00@21:1/108 to Analog on Tue Feb 4 14:59:07 2020
    As far as the weird message thing, there was a bug in A43 only where you did an echomail RESCAN it could import a funky message or two, so that might explain any weirdness there.

    Ok, I'm on A44 latest, but I assume rescanning A43 uplinks will cause
    them to not be able to send me anything past 12/30/2019? I am not receiving any message on the rescan past this date. I do get new
    messages but everything between now and 2019 does not come through.

    The weird message or two is a symptom of the Mystic A43 uplink then?

    Yes, sorry I should have mentioned if the uplink that you send the request to RESCAN from is on A43, it may corrupt the last message or two in the packet.

    There was a memory leak that I've since fixed up and the issue only existed
    in A43 (A42 was fine, A44 will be fine).

    A43 also has that 2020 date bug too, so yeah, hubs really should upgrade to
    A44 ASAP.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From g00r00@21:1/108 to Analog on Tue Feb 4 14:59:53 2020
    I was using the old one but changed to the new one and the problem persists:

    If I hit enter on a message bases (with messages) that has a garbled message, it will not open it. I think the real problem is the garbled message is messing up the base data structure making it problematic to read. I think I'm going to try to manually edit the record (using some python code) and purge the message. Not going to be easy, I'll have to write a few lines of code to clean these.

    What I would do is just backup the message base data files (just in case), delete the weird messages, and then run message pack.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: Sector 7 (21:1/108)
  • From Analog@21:2/123 to g00r00 on Tue Feb 4 14:08:27 2020
    What I would do is just backup the message base data files (just in
    case), delete the weird messages, and then run message pack.

    Ok I was hoping this would be that simple. I will do this. Cheers for all
    your help. We are very appreciative of you...

    |19|15┌─|16|07┤ |08De|07ad|15be|07a|08tz b|07b|15s
    |07└─┘├─┐ |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
    |11■ |07└|19|15─|16|07┘ |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
    |12≡|15A|07n|08al|07o|15g|12≡ |08:>.|13F|05dn |131|08:|13305|08/|132|08.
    |08:>.|15S|08ci |1577|08:|151|08/|15131|08.
    |08:>.|11T|03qw |111337|08:|113|08/|1113|08.

    --- Mystic BBS v1.12 A44 2020/02/02 (Linux/64)
    * Origin: deadbeatz.org (21:2/123)