1. Forum
  2. FSXNET
  3. FSX_ENG

  • Import errors

    From pokeswithastick@1:1/0 to All on Mon Feb 17 22:58:45 2020
    I'm seeing a lot of errors in the logs today about failed FSX_NET imports.

    msg:"Not importing non-unique message"

    and in my mail/ftn_in folder there are many *.mo? files backed up.

    Restarting Enigma doesn't seem to clear this backlog although I have a 5 minute
    scan schedule set in addition to watching the toss file.

    Maybe because I'm running binkd on a different machine and using NFS to share the mail dir?

    Any ideas much appreciated.

    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.14.1)
    * Origin: sbb systems ~ (web https://bbs.sbbsystems.com | telnet bbs.sbbsystems.com:8888 | ssh bbs.sbbsystems.com:8889) (21:2/159)
  • From Avon@21:1/101 to pokeswithastick on Tue Feb 18 20:03:55 2020
    On 17 Feb 2020 at 10:58p, pokeswithastick pondered and said...

    I'm seeing a lot of errors in the logs today about failed FSX_NET
    imports.

    msg:"Not importing non-unique message"

    So this is particular to the echomail area FSX_NET?

    [snip]

    FSX_NET - Discussions about fsxNet. Chat about current network operations,
    plans for the future and how to best implement them.

    [snip]

    or do you mean all fsxNet messages are blocked?

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From pokeswithastick@1:1/0 to Avon on Tue Feb 18 08:16:52 2020
    Hi Paul,

    I am only connected to FSX_NET so I think it is more likely to be how I have set up Enigma and Binkd to work together over a network share.

    I don't want to cause a panic in the FSX_GEN area - I'm pretty sure if there were problems we'd have heard about it :)

    Messages are coming through this morning fine and being imported successfully.

    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.14.1)
    * Origin: sbb systems ~ (web https://bbs.sbbsystems.com | telnet bbs.sbbsystems.com:8888 | ssh bbs.sbbsystems.com:8889) (21:2/159)
  • From Avon@21:1/101 to pokeswithastick on Tue Feb 18 21:30:47 2020
    On 18 Feb 2020 at 08:16a, pokeswithastick pondered and said...

    Hi Paul,

    I am only connected to FSX_NET so I think it is more likely to be how I have set up Enigma and Binkd to work together over a network share.

    I don't want to cause a panic in the FSX_GEN area - I'm pretty sure if there were problems we'd have heard about it :)

    Messages are coming through this morning fine and being imported successfully.

    Hey there :)

    Yep all good, I'm probably of little help to you with that, but sing out if
    you want me to check on anything :)

    --- Mystic BBS v1.12 A45 2020/02/16 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From NuSkooler@21:1/121 to pokeswithastick on Thu Feb 20 23:38:15 2020

    On Monday, February 17th pokeswithastick said...
    msg:"Not importing non-unique message"
    and in my mail/ftn_in folder there are many *.mo? files backed up.

    Can you pastebin a run of your log showing this with the log level set to trace
    if it's not already? The non-unique message can be normal if you just get truely (as in same hash) dupe messages in packets, but the packet files piling up is no good.

    There should be some additional logging in there about what is causing the problem.

    BTW for your own viewing if you're not already, the logs can be viewed pretty printed like this:
    tail -F ./logs/enigma-bbs.log | ./node_modules/bunyan/bin/bunyan
    (from the enigma dir)



    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.11-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From pokeswithastick@1:1/0 to NuSkooler on Sat Feb 22 16:37:59 2020
    Sure I'll do that. Moved the bbs to a model 3a+ to give it more grunt as well.
    It's noticably faster :)

    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.14.1)
    * Origin: sbb systems ~ (web https://bbs.sbbsystems.com | telnet bbs.sbbsystems.com:8888 | ssh bbs.sbbsystems.com:8889) (21:2/159)
  • From pokeswithastick@1:1/0 to NuSkooler on Mon Feb 24 20:54:52 2020
    It was my setup not keeping up with the messages. Moving to a Pi 3 + cleared a
    huge backlog.

    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.14.1)
    * Origin: sbb systems ~ (web https://bbs.sbbsystems.com | telnet bbs.sbbsystems.com:8888 | ssh bbs.sbbsystems.com:8889) (21:2/159)
  • From NuSkooler@21:1/121 to pokeswithastick on Mon Feb 24 21:18:51 2020

    On Monday, February 24th pokeswithastick was heard saying...

    It was my setup not keeping up with the messages. Moving to a Pi 3 + cleared a huge backlog.

    Interesting... I guess if it's working fine now I won't worry about it much. I've tried on a model 2 a few times, but it's been quite a long time back.



    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.11-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From pokeswithastick@21:2/159 to NuSkooler on Sat Mar 21 11:09:02 2020

    On Mar 21st 11:00 am pokeswithastick said...
    On Feb 25th 4:31 am NuSkooler said...
    Interesting... I guess if it's working fine now I won't worry
    about it much. I've tried on a model 2 a few times, but it's been quite a long time back.

    I spoke to soon and its happening again. If I attach to the k3s container I can see a zombie unzip process.

    ps -A 617 root 0:00 [unzip]

    I might try altering the default archiving configuration to see if I can get more logs or using 7zip in place of InfoZip


    Not sure if this sent or not so sending again.


    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.16.1)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)
  • From NuSkooler@21:1/121 to pokeswithastick on Tue Mar 31 19:31:10 2020

    Twas Saturday, March 21st when pokeswithastick said...
    I spoke to soon and its happening again. If I attach to the k3s container I can see a zombie unzip process.

    Sorry for the long delay. I'm not sure if you're the one I spoke with on IRC/Discord, but this has been fixed in the latest versions. In 0.0.10-alpha you'd need to adjust your unzip args (in config.hjson) to add the force or no overwrite flag.



    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.11-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From pokeswithastick@21:2/159 to NuSkooler on Wed Apr 1 08:58:15 2020

    On Apr 1st 8:17 am NuSkooler said...
    Sorry for the long delay. I'm not sure if you're the one I spoke with on IRC/Discord, but this has been fixed in the latest versions. In 0.0.10-alpha you'd need to adjust your unzip args (in config.hjson) to add the force or no overwrite flag.

    No it wasn't but thanks I shall try this and post back with how I get on.



    --- ENiGMA 1/2 v0.0.11-beta (linux; arm; 12.16.1)
    * Origin: sbb systems ~ https://bbs.sbbsystems.com (21:2/159)