1. Forum
  2. FidoNet
  3. Mystic Support

  • error log filled with MUTIL 000 Runtime error 1

    From DENZUKO@1:124/5017 to All on Fri Feb 14 16:04:22 2020
    Hey guys,

    I'm seeing runtime errors pop up consistanly in the error.log. Does anyone
    know how to debug this or resolve it?

    I'm on the latest version of mystic for 64 bit Linux (ubuntu) Any help would
    be appreciated.

    Best Regards,
    Dwight Spencer at 1:124/5017.0
    Origin: XM Core BBS - bbs.dapla.net

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: XM Core (1:124/5017)
  • From g00r00@1:129/215 to DENZUKO on Fri Feb 14 12:02:51 2020
    I'm seeing runtime errors pop up consistanly in the error.log. Does
    anyone know how to debug this or resolve it?

    You would have to post the contents, so we could see some of the errors.

    There are some errors that are mostly harmless like running mutil without configuring any tasks I believe will result in an error log message, for example.

    I'm on the latest version of mystic for 64 bit Linux (ubuntu) Any help would be appreciated.
    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)

    A43 is not the latest. There is an A44 and also A45 pre-release versions for testing that are available. Both are in much better shape than A43 and I
    would suggest upgrading to one of them as soon as you can.

    --- Mystic BBS v1.12 A45 2020/02/13 (Windows/64)
    * Origin: Sector 7 (1:129/215)
  • From DENZUKO@1:124/5017 to g00r00 on Fri Feb 14 19:12:28 2020
    You would have to post the contents, so we could see some of the errors.

    error.log:2020.14.02 18:45:02 MUTIL 000 Runtime error 1 error.log:2020.14.02 19:00:03 MUTIL 000 Runtime error 1 mutil.log:----------------- MUTIL v1.12 A43 2019/03/02 Fri, Feb 14 2020
    (loglevel 2) mutil.log:----------------- MUTIL v1.12 A43 2019/03/02 Fri, Feb 14 2020 (loglevel 2)

    Other behaiver I'm noticing is my imports are backing up so I'm suspecting something with the imports.ini (a copy of mutil.ini just for fidonet on my system). So let me know if we need a pastebin of that too.


    A43 is not the latest. There is an A44 and also A45 pre-release
    versions for testing that are available. Both are in much better shape than A43 and I would suggest upgrading to one of them as soon as you can.
    Yeah I got the A44 sent over via the fdn. Just haven't had the time to get it into a docker container yet. Once I do it'll be avilalble to upgrade right away.

    Best Regards,
    Dwight Spencer at 1:124/5017.0
    Origin: XM Core BBS - bbs.dapla.net

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: XM Core (1:124/5017)
  • From Paul Hayton@3:770/100 to DENZUKO on Sat Feb 15 09:26:10 2020
    On 14 Feb 2020 at 07:12p, DENZUKO pondered and said...

    error.log:2020.14.02 18:45:02 MUTIL 000 Runtime error 1 error.log:2020.14.02 19:00:03 MUTIL 000 Runtime error 1 mutil.log:----------------- MUTIL v1.12 A43 2019/03/02 Fri, Feb 14 2020
    (loglevel 2) mutil.log:----------------- MUTIL v1.12 A43 2019/03/02 Fri, Feb 14 2020 (loglevel 2)

    Other behaiver I'm noticing is my imports are backing up so I'm
    suspecting something with the imports.ini (a copy of mutil.ini just for

    does the ini exist?

    also check you have enabled the function or functions you want to run within it.

    i create ini files called mailin.ini and mailout.ini and place the functions
    i want to run that relate to the processes captured in the ini name in each.

    Best, Paul

    --- Mystic BBS v1.12 A44 2020/02/04 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)
  • From g00r00@1:129/215 to DENZUKO on Fri Feb 14 15:17:56 2020
    error.log:2020.14.02 18:45:02 MUTIL 000 Runtime error 1 error.log:2020.14.02 19:00:03 MUTIL 000 Runtime error 1

    This is the message it prints when you run MUTIL without anything for it to do or something else is preventing it from starting up (like a missing directory).

    Some examples would be if you don't have anything enabled in "mutil.ini" and you type "mutil" on a command line. Or if you point it to an .INI file that doesn't exist. Usually its a "false alarm" message.

    I can see that this is too vague and confusing though, so in A45 I will have it give a clear reason why it failed to start. This will be in the next "test" A45 build.

    --- Mystic BBS v1.12 A45 2020/02/13 (Windows/64)
    * Origin: Sector 7 (1:129/215)