1. Forum
  2. Fsxnet Message
  3. FSX MYS

  • Logs filling filesystem

    From Tony Langdon@21:1/143 to All on Tuesday, December 12, 2017 21:56:11
    My BBS had been acting strangely this last day or so, and I was dreading that I may have another failing SD card (but I have a current backup of the BBS, so recovery would be easier, with reinstalling the offsite backup system being the only significant work left to do. The symptom was first I'd get a strange question about voting in a poll on login, and later, the system would hang (generating a QWK packet was guaranteed to do this!), leaving a stuck "mystic" process that had to be killed with kill -9

    Anyway, upon investigating the cause, I found I had a full disk (SD). One of the major culprits was eventsignal.txt, which had grown to over 4GB(!). This file seems to have grown rapidly, with a looping error. The last few lines read:

    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11

    Not sure why MIS would be receiving a signal 11 at 4:30 AM.

    Is there any way to prevent this log from suddenly filling up the disk?

    BTW, I'm running A36 on the Pi.


    ... APPLE: Nutritious lunchtime dessert which children trade for cupcakes.
    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
    * Origin: The Bridge - bridge.vkradio.com (21:1/143)
  • From Weatherman@21:1/132 to Tony Langdon on Tuesday, December 12, 2017 17:04:03

    My BBS had been acting strangely this last day or so, and I was dreading that I
    may have another failing SD card (but I have a current backup of the BBS, so recovery would be easier, with reinstalling the offsite backup system

    I was wondering where you went.. I put all your packets on pickup-only for the
    time being. Good to see you are back and figured out what happened.

    - Mark
    ÿÿÿ
    --- WWIVToss v.1.52
    * Origin: http://www.weather-station.org * Bel Air, MD -USA (21:1/132.0)
  • From Static@21:2/140 to Tony Langdon on Tuesday, December 12, 2017 18:27:15
    On 12/12/17, Tony Langdon said the following...

    Dec 12 04:30:38 MIS Received 11

    Signal 11 is a segmentation fault. Something is crashing and being relaunched rapidly. Corruption of memory or the executable file is certainly one way to cause that.

    --- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
    * Origin: Subcarrier BBS (21:2/140)
  • From Tony Langdon@21:1/143 to Weatherman on Wednesday, December 13, 2017 05:55:04
    Weatherman wrote to vk3jed <=-

    My BBS had been acting strangely this last day or so, and I was dreading that I
    may have another failing SD card (but I have a current backup of the BBS, so recovery would be easier, with reinstalling the offsite backup system

    I was wondering where you went.. I put all your packets on pickup-only for the
    time being. Good to see you are back and figured out what happened.

    Yeah, that's with this system. Freeway still has bigger issues.


    ... What?! I'm missing Star Tre$#%$^ NO CARRIER
    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
    * Origin: The Bridge - bridge.vkradio.com (21:1/143)
  • From Tony Langdon@21:1/143 to Static on Wednesday, December 13, 2017 05:55:04
    Static wrote to vk3jed <=-

    On 12/12/17, Tony Langdon said the following...

    Dec 12 04:30:38 MIS Received 11

    Signal 11 is a segmentation fault. Something is crashing and being relaunched rapidly. Corruption of memory or the executable file is certainly one way to cause that.

    Weird, since it's been OK since manually restarting everything (and clearing diskspace).


    ... You're actually going to do something. Can I watch?
    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
    * Origin: The Bridge - bridge.vkradio.com (21:1/143)
  • From Jeff Brissette@21:2/109 to All on Wednesday, December 13, 2017 16:16:15
    Tony, I had a similar issue. While the MIS Received 11 is a seg fault, I
    did not seem to get any errors in any other logs. Which was weird to say
    the least.

    I did end up setting all my MIS services so that they were IPV4 only.
    Instead of IPV4 and IPV6 (I didn't have an IPV6 address anyways) and
    somehow nearly all the MIS Received 11 seemed to disappear.


    Tony Langdon wrote:
    My BBS had been acting strangely this last day or so, and I was dreading
    that I
    may have another failing SD card (but I have a current backup of the BBS, so recovery would be easier, with reinstalling the offsite backup system being
    the
    only significant work left to do. The symptom was first I'd get a strange question about voting in a poll on login, and later, the system would hang (generating a QWK packet was guaranteed to do this!), leaving a stuck
    "mystic"
    process that had to be killed with kill -9

    Anyway, upon investigating the cause, I found I had a full disk (SD). One of the major culprits was eventsignal.txt, which had grown to over 4GB(!). This file seems to have grown rapidly, with a looping error. The last few lines read:

    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11
    Dec 12 04:30:38 MIS Received 11

    Not sure why MIS would be receiving a signal 11 at 4:30 AM.

    Is there any way to prevent this log from suddenly filling up the disk?

    BTW, I'm running A36 on the Pi.



    --- Mystic BBS/NNTP v1.12 A36 2017/12/03 (Linux/32)
    * Origin: RPG Circus BBS (21:2/109)
  • From g00r00@21:1/108 to Jeff Brissette on Wednesday, December 13, 2017 15:24:34
    I did end up setting all my MIS services so that they were IPV4 only. Instead of IPV4 and IPV6 (I didn't have an IPV6 address anyways) and somehow nearly all the MIS Received 11 seemed to disappear.

    Yep this makes sense to me. Most Linux installations already run in "dual stack" meaning that IPV6 will also answer IPV4. If you configure Mystic to also try to run in dual stack then it seems to be problematic.

    The original IPV6 in Mystic2Demo I think only allowed IPV4 or IPV6 to be selected in Linux, not dual stack. But I think there was a reason I changed it.

    Either way, I am going to change it back so if you pick IPV6 or IPV4+IPV6 in Unix really it will only listen on IPV6 (which also should accept IPV4) and that will hopefully clean up those segfaults.

    Also, in the next pre-alpha I toned down the eventsignal log so that it shouldn't even fill up your hard drive like that if it does happen again.

    --- Mystic BBS v1.12 A37 2017/12/13 (Windows/32)
    * Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)
  • From Tony Langdon@21:1/143 to Jeff Brissette on Wednesday, December 13, 2017 20:57:08
    Jeff Brissette wrote to All <=-

    Tony, I had a similar issue. While the MIS Received 11 is a seg fault,
    I did not seem to get any errors in any other logs. Which was weird to
    say the least.

    Yeah, very weird. :(

    I did end up setting all my MIS services so that they were IPV4 only. Instead of IPV4 and IPV6 (I didn't have an IPV6 address anyways) and somehow nearly all the MIS Received 11 seemed to disappear.

    Unfortunately, that's not a helpful solution for me, as I do have native IPv6 here, and better network connectivity on IPv6. But it might give g00r00 a clue for bug hunting. :)


    ... The computer made me do it!
    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
    * Origin: The Bridge - bridge.vkradio.com (21:1/143)
  • From Static@21:2/140 to Tony Langdon on Wednesday, December 13, 2017 16:17:56
    On 12/13/17, Tony Langdon said the following...

    Jeff Brissette wrote to All <=-

    Tony, I had a similar issue. While the MIS Received 11 is a seg fault I did not seem to get any errors in any other logs. Which was weird t say the least.

    Yeah, very weird. :(

    Maybe not. Whichever process crashed probably didn't have time to complain about it.

    --- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
    * Origin: Subcarrier BBS (21:2/140)
  • From Tony Langdon@21:1/143 to Static on Thursday, December 14, 2017 19:59:02
    Static wrote to vk3jed <=-

    Maybe not. Whichever process crashed probably didn't have time to
    complain about it.

    Good point. :)


    ... An argument is where two people are trying to get the LAST word in FIRST! ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
    * Origin: The Bridge - bridge.vkradio.com (21:1/143)
  • From Tony Langdon@21:1/143 to g00r00 on Thursday, December 14, 2017 19:59:02
    g00r00 wrote to Jeff Brissette <=-

    Yep this makes sense to me. Most Linux installations already run in
    "dual stack" meaning that IPV6 will also answer IPV4. If you configure Mystic to also try to run in dual stack then it seems to be
    problematic.

    In my experience, IPv6 doesn't work in that configuration, but IPv4 still does.
    But that was in an early version of MIS2. I never got segfaults then though.

    The original IPV6 in Mystic2Demo I think only allowed IPV4 or IPV6 to
    be selected in Linux, not dual stack. But I think there was a reason I changed it.

    Either way, I am going to change it back so if you pick IPV6 or
    IPV4+IPV6 in Unix really it will only listen on IPV6 (which also should accept IPV4) and that will hopefully clean up those segfaults.

    That doesn't explain why I had the segfaults. I'm configured for IPv6 only, so there shouldn't be any conflict there. So far, only had then segfault storm once *touches wood*.

    Also, in the next pre-alpha I toned down the eventsignal log so that it shouldn't even fill up your hard drive like that if it does happen
    again.

    Thanks. :)


    ... A skydiving school is one in which you MUST be a dropout to graduate.
    ___ MultiMail/Win32 v0.49

    --- Mystic BBS/QWK v1.12 A36 2017/12/04 (Raspberry Pi/32)
    * Origin: The Bridge - bridge.vkradio.com (21:1/143)