1. Forum
  2. fsxNet
  3. ENiGMA 1/2 BBS Support

  • .tic handling

    From deepthaw@21:2/128 to All on Tue Nov 17 09:56:54 2020
    Hi all,

    Thanks to some top minds on here I realized I was an idiot and was using a packet password when none was needed, and after a night full of finally realizing synchronet's binkit was still running and that's why binkd wasn't working and... well, my networks work now.

    Having some issues with incoming .tic file handling however. Here's the error from my log:

    "level":50,"error":"Invalid: No local area for \"Area\" of FSX_MUTL","reason":"No local area for \"Area\" of FSX_MUTL

    Here's the config from my conf.hjson (irrelevant stuff trimmed out):

    storageTags: {
    weekly_nodelists_fsx_net_etc__fsx_node: FSX_NODE
    weekly_infopacks_fsx_net_etc__fsx_info: FSX_INFO
    mystic_bbs_software__fsx_myst: FSX_MYST
    mystic_bbs_utils_mods_etc__fsx_mutl: FSX_MUTL
    bbs_software_current_legacy__fsx_soft: FSX_SOFT
    }

    (then within areas)

    mystic_bbs_utils_mods_etc: {
    name: Mystic BBS Utils, Mods etc.
    desc: Mystic BBS Utils, Mods etc.
    storageTags: [
    mystic_bbs_utils_mods_etc__fsx_mutl
    ]
    }

    (finally ...)

    ticAreas {

    FSX_MUTL: {
    areaTag: mystic_bbs_utils_mods_etc
    storageTag: mystic_bbs_utils_mods_etc__fsx_mutl
    hashTags: fsxnet,mystic,mods
    }
    }

    the filebase isn't catastrophically misconfigured since I was able to upload about 9,000 files into it and all of my areas for tic files are browseable, if empty. I imagine it's something simple like all my mistakes so far, but I'm just overlooking it.

    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.19.0)
    * Origin: cortex (21:2/128)
  • From NuSkooler@21:1/121 to deepthaw on Tue Nov 17 16:32:15 2020

    Twas Tuesday, November 17th when deepthaw said...
    the filebase isn't catastrophically misconfigured since I was able to upload about 9,000 files into it and all of my areas for tic files are browseable, if empty. I imagine it's something simple like all my mistakes so far, but I'm just overlooking it.

    Yeah seems reasonable at glance - and if the *areas* are showing up fine, that should be OK.

    See if setting the ticAreas entry to lower case (fsx_mutil) and see if that helps. There may be a bug around something like that.


    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)
  • From deepthaw@21:2/128 to NuSkooler on Tue Nov 17 23:57:58 2020

    On 11/17/2020 4:32 pm NuSkooler said...
    See if setting the ticAreas entry to lower case (fsx_mutil) and see if that helps. There may be a bug around something like that.

    Didn't help, still getting the same error.

    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.19.0)
    * Origin: cortex (21:2/128)
  • From NuSkooler@21:1/121 to deepthaw on Wed Nov 18 10:05:22 2020

    On Tuesday, November 17th deepthaw was heard saying...
    Didn't help, still getting the same error.

    Might need to see a full config - if you can send me a private pastebin or similar (Feel free to redact).


    --
    NuSkooler
    Xibalba BBS @ xibalba.l33t.codes / 44510(telnet) 44511(ssh)
    ENiGMA 1/2 BBS WHQ | Phenom | 67 | iMPURE | ACiDic
    --- ENiGMA 1/2 v0.0.12-beta (linux; x64; 12.13.1)
    * Origin: Xibalba -+- xibalba.l33t.codes:44510 (21:1/121)