Community Forum

Resolved
0 votes
Hello all, ClearOS arbitrarily make unplanned RESTART, What could be the fault?
Thanks in advance for your replies.
In Gateway
Saturday, December 02 2017, 08:09 PM
Share this post:
Responses (18)
  • Accepted Answer

    Thursday, December 07 2017, 02:16 PM - #Permalink
    Resolved
    0 votes
    Problem fixed - hardware broken.
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, December 06 2017, 10:38 AM - #Permalink
    Resolved
    0 votes
    Today, Hardaware refused to work restarting all the time. Was done: sdd was connected in an analogous system, currently the system is working, time will show.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 06:35 PM - #Permalink
    Resolved
    0 votes
    Thanks a lot for the suggestion, it was done.

    [root@gateway ~]# lspci -k | grep Eth -A 3
    01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
    Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
    Kernel driver in use: r8168
    Kernel modules: r8168
    02:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 41)
    03:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
    Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
    Kernel driver in use: e1000
    Kernel modules: e1000



    Package kmod-r8169-6.020.00-2.v7.x86_64 already installed and latest version
    Package kmod-r8168-8.045.08-1.el7_4.elrepo.x86_64 already installed and latest version
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 06:11 PM - #Permalink
    Resolved
    0 votes
    Please can you do a "yum install kmod-r816*" and reboot. There is a much better NIC driver for the RTL8111/8168/8411, but I've never seen the r8169 driver causing reboots before. It is worth doing the change. If you do install the kmod drivers, please note this post. It *may* not apply to you as CleearOS is providing these two files but they have yet to work out the best route to transition to the new drivers for people like you (and me as I use the kmod-r8168 as well)
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 05:58 PM - #Permalink
    Resolved
    0 votes
    [root@gateway ~]# lspci -k | grep Eth -A 3
    01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
    Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet
    Kernel driver in use: r8169
    Kernel modules: r8169
    02:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 41)
    03:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
    Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
    Kernel driver in use: e1000
    Kernel modules: e1000
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 05:52 PM - #Permalink
    Resolved
    0 votes
    You are missing the top 3 lines of the output. Can you repost?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 05:12 PM - #Permalink
    Resolved
    0 votes
    [root@gateway ~]# ^M[root@gateway ~]# lspci -k | grep Eth -A 3
    Kernel modules: r8169
    02:00.0 PCI bridge: Integrated Technology Express, Inc. Device 8892 (rev 41)
    03:00.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controll
    er (rev 05)
    Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
    Kernel driver in use: e1000
    Kernel modules: e1000
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 04:03 PM - #Permalink
    Resolved
    0 votes
    I did not want all the logs. Just the bit near the end which could be relevant! They should easily go between code tags on the forum. No need for syswatch.

    I see you have virtual NIC's. What is the output of:
    lspci -k | grep Eth -A 3
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 02:47 PM - #Permalink
    Resolved
    0 votes
    Sorry but I can't get to the files. Blocked by NOD32 AV. Can you paste the relevant bits between code tags on the forum?
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 12:49 PM - #Permalink
    Resolved
    0 votes
    ClearOS restarted time: 14:32

    Logs file in annex

    Title
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 11:56 AM - #Permalink
    Resolved
    0 votes
    Did you do a fresh installation on the new machine or move the disk across?

    Can you install the resources report? It will need to run for a time before it shows any data.

    Also install lm-sensors and set it up by running "sensors-detect" and let it create the configuration file. Immediately after a crash, check the CPU temperature with the command "sensors".
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, December 05 2017, 09:41 AM - #Permalink
    Resolved
    0 votes
    Changing the RAM did not change anything, Clearos today again Restart =(
    The reply is currently minimized Show
  • Accepted Answer

    Monday, December 04 2017, 08:40 PM - #Permalink
    Resolved
    0 votes
    Today changed the RAM to the tested, will see how it will be. I use DDR4 8 gb, ssd120gb, i3cpu
    The reply is currently minimized Show
  • Accepted Answer

    Monday, December 04 2017, 07:12 PM - #Permalink
    Resolved
    0 votes
    Hi Edgars,
    Bring your message back public. If you have just changed servers by moving the disk across, you could try reinstalling the kernel to regenerate initramfs. Also, if it is very modern hardware, there could be a question of support as RedHat does not live at the cutting edge of technology. Your processor is probably OK, though.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, December 03 2017, 09:27 PM - #Permalink
    Resolved
    0 votes
    From your output, you should have plenty of memory and have a lot of disk space free. Have you looked at the Resource report and do your logs give any indication?

    Are you able to monitor CPU temperature. You can use lm-sensors as a command line monitor and it is available in the clearos-centos repo.

    Do you have any third-party apps installed?

    Have you tried taking your server off-line and doing any hardware tests such as the memory test, memtest86? Also available on other discs such as the Ultimate Boot CD which comes with all sorts of other utilities.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, December 03 2017, 08:30 PM - #Permalink
    Resolved
    0 votes
    Recently, ClearOS was restarted
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, December 03 2017, 08:25 PM - #Permalink
    Resolved
    0 votes
    Webconfig > Reports > Performance and Resources > System Report
    Attachments:
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, December 03 2017, 07:35 PM - #Permalink
    Resolved
    0 votes
    These are hard to diagnose. Does it always happen at the same time each day? In the Resource Reports, do you see anything like full memory usage or high system load before the restart? Note the acceptable system load depends on the number of cores or virtual cores the CPU has, so, for example, my CPU has two hyperthreaded cores so full utilisation would show 400% i.e 4 effective cores @ 100% each.

    Have you checked your logs around the time of the crash e.e /vat/log/messages or /var/log/system or, perhaps, /var/log/dmesg?

    Can you copy and paste the info from the Webconfig > Reports > Performance and Resources > System Report?
    The reply is currently minimized Show
Your Reply