1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • eventsignal logfile in a36?

    From h7@21:1/155 to All on Monday, December 04, 2017 10:49:15

    i upgraded to a36 and for some reason the new MIS hung up and started
    creating a log called eventsignal.txt (not documented log in whatsnew etc).

    filled up my 20gb on the VPS quite quickly. I was lucky enough to catch it
    live before my message bases etc were written over since the log file grew to more than 9gb in a very short period of time.

    i run MIS as a server and not daemon. killing the MIS didnt help, the server had stayed alive likely because of the huge volume of the logs being written.

    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11

    i dont know what caused it.

    |08\ |07H7|08 of |07Blocktronics/dIVINE sTYLERS!/aCCESSiON/TRSi/Break!Ascii |08\ |07Haciend bbs sysop |08(|15telnet://haciend.com|08)|07

    --- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
    * Origin: Haciend.com | Scandinavian demoscene bbssince 1996 (21:1/155)
  • From h7@21:1/155 to g00r00 on Monday, December 04, 2017 10:49:15
    not sure if you noticed this, i posted it ac
    cidently to All not directly toyou.
    if the thing works as intended, could you consider limiting o
    r aggregatingthe error messages? me, e
    sc, caphood and likely others have experienced the
    signal 11 thing now.---
    i upgraded to a36 and for some reason the new MIS hung up and started
    creating a log called eventsignal.txt (not documented log in whatsnew etc). filled up my 20gb on the VPS quite quickly. I was lucky enough to cat
    ch itlive before my message bases etc were written over sinc
    e the log file grew tomore than 9gb in a very short period o
    f time. i run MIS as a server and not daemon. killi
    ng the MIS didnt help, the serverhad stayed alive likely bec
    ause of the huge volume of the logs being written.Dec
    04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11Dec 04 10:38:24 MIS Received 11
    Dec 04 10:38:24 MIS Received 11i dont know what caused it.
    \ H7 of Blocktronics/dIVINE sTYLERS!/aCCESSiON/
    TRSi/Break!Ascii\ Haciend bbs sysop (
    telnet://haciend.com)
    --- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
    * Origin: Haciend.com | Scandinavian demoscene bbssince 1996 (21:1/155)
  • From esc@21:2/142 to h7 on Wednesday, December 27, 2017 17:08:52
    i upgraded to a36 and for some reason the new MIS hung up and started creating a log called eventsignal.txt (not documented log in whatsnew etc).

    Shut down mis, delete eventsignal.txt, and
    touch /mystic/logs/eventsignal.txt
    chmod -w eventsignal.txt

    I _think_ this and the 100% cpu are related.

    --- Mystic BBS v1.12 A37 2017/12/21 (Linux/32)
    * Origin: lo fidelity bbs (21:2/142)
  • From g00r00@21:1/108 to h7 on Wednesday, December 27, 2017 13:47:44
    i upgraded to a36 and for some reason the new MIS hung up and started creating a log called eventsignal.txt (not documented log in whatsnew etc).

    Thanks, I think this is fixed in the latest A37 prealpha but only time will tell.

    --- Mystic BBS v1.12 A37 2017/12/26 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From h7@21:1/155 to g00r00 on Friday, December 29, 2017 10:31:23
    i upgraded to a36 and for some reason the new MIS hung up and started creating a log called eventsignal.txt (not documented log in whatsnew etc).

    Thanks, I think this is fixed in the latest A37 prealpha but only time will tell.

    i had to upgrade to prealpha, it started again out of the blue. i have no
    idea what triggered it. had to reboot my vm because the process didnt die, likely because there was so much stuff in some buffer or so. with prealpha
    its stable.

    |08\ |07H7|08 of |07Blocktronics/dIVINE sTYLERS!/aCCESSiON/TRSi/Break!Ascii |08\ |07Haciend bbs sysop |08(|15telnet://haciend.com|08)|07

    --- Mystic BBS v1.12 A37 2017/12/23 (Linux/64)
    * Origin: Haciend.com | Scandinavian demoscene bbssince 1996 (21:1/155)