Forums

Resolved
0 votes
Hi,

My server just went unresponsive for some reason. The webconfig was unresponsive and also I couldn't access my server over port 22 and there was no traffic on the WAN. The only thing I could do was a reset. I checked the messages log file to find out what happened.


Aug 28 19:55:01 gandalf systemd: Created slice user-0.slice.
Aug 28 19:55:01 gandalf systemd: Starting user-0.slice.
Aug 28 19:55:01 gandalf systemd: Started Session 8662 of user root.
Aug 28 19:55:01 gandalf systemd: Starting Session 8662 of user root.
Aug 28 19:55:01 gandalf systemd: Started Session 8663 of user root.
Aug 28 19:55:01 gandalf systemd: Starting Session 8663 of user root.
Aug 28 19:55:01 gandalf systemd: Started Session 8664 of user root.
Aug 28 19:55:01 gandalf systemd: Starting Session 8664 of user root.
Aug 28 19:55:01 gandalf systemd: Removed slice user-0.slice.
Aug 28 19:55:01 gandalf systemd: Stopping user-0.slice.


I saw a lot of the message above. Not sure if this is harmful. It's caused by systemd... I didn't noticed other weird things in messages. Are there other logs were I can find some clues?
Sunday, August 28 2016, 06:31 PM
Share this post:
Responses (6)
  • Accepted Answer

    Tuesday, August 30 2016, 01:47 PM - #Permalink
    Resolved
    0 votes
    Okay, thanks Nick! Did some further investigation but I can't find anything weird...
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 29 2016, 07:59 PM - #Permalink
    Resolved
    0 votes
    The ClearOS igb driver should be fine. It is the same version as the kmod one so I've gone back to using it.
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 29 2016, 05:51 PM - #Permalink
    Resolved
    0 votes
    I have 2 Intel I210 Gigabit NIC's

    Not sure what happened at the moment everything is running smoothly. Maybe just coincidence...
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, August 28 2016, 07:45 PM - #Permalink
    Resolved
    0 votes
    Have you checked your NIC drivers with
    lspci -k | grep Eth -A 3
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, August 28 2016, 07:35 PM - #Permalink
    Resolved
    0 votes
    Hmmm, my unRAID server also became unresponsive at the same time but that was due of a full system drive...
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, August 28 2016, 07:20 PM - #Permalink
    Resolved
    0 votes
    Did a bit of investigation and it seems that this are low priority "info"-level messages related to session and resource management.

    You can avoid this by changing the log level.


    systemd-analyze set-log-level notice


    So this has nothing that my server became unresponsive and the only solutions was a reset...
    The reply is currently minimized Show
Your Reply