1. Forum
  2. fsxnet
  3. FSX MYS

  • errors.log

    From Gods69@21:3/220 to All on Mon Jun 8 10:19:16 2026
    Hi,
    I've somme errors on my errors.log in Mystic.
    - "can't find xfer.log"
    - "cannot write to /mystic/data/chat1.dat"
    There is a easy way to fix it or i must forget that?
    Thanks.

    ... Test-tube babies shouldn't throw stones.

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Gods69 BBS (21:3/220)
  • From Accession@21:1/200 to Gods69 on Mon Jun 8 18:10:46 2026
    Hey Gods69!

    On Mon, 08 Jun 2026 10:19:16 +0200, you wrote:

    I've somme errors on my errors.log in Mystic.
    - "can't find xfer.log"
    - "cannot write to /mystic/data/chat1.dat"
    There is a easy way to fix it or i must forget that?
    Thanks.

    Check to see if those files are actually present, and if not "touch xfer.log". It would be odd if Mystic didn't autocreate it's own log files if they don't actually exist.

    As for chat1.dat, that could be a permissions issue if the file is actually there (assuming you're using Linux, since you're posting from a Linux BBS). Check that chat1.dat isn't owned by any other user than what the BBS is running from, and the permissions of the directory that file is in (or supposed to be in). If the file doesn't contain anything important, you could just delete it and recreate it with the user you run your BBS with.. and if the file happens to also be missing, "touch chat1.dat" to create it.

    If you run your BBS on Linux as a user, and you accidentally modify/change files in Mystic's directory structure as root or another user, you will run into these problems, as you would with just about any other program, too.

    Hope that helps.

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    --- GoldED+/LNX 1.1.5-b20260425
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From Gods69@21:3/220 to Accession on Tue Jun 9 09:42:39 2026
    Check to see if those files are actually present, and if not "touch xfer.log". It would be odd if Mystic didn't autocreate it's own log
    files if they don't actually exist.

    I've already created the file "xfer.log" in the /mystic/logs directory but
    the file don't update, it stay with 0 bytes.

    important, you could just delete it and recreate it with the user you
    run your BBS with.. and if the file happens to also be missing, "touch chat1.dat" to create it.

    "chat1.dat" don't exist. I've created one. Let see is this change something...

    ... If at first you don't succeed, try something else.

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Gods69 BBS (21:3/220)