Profile Details

Toggle Sidebar
Loading cover... Drag cover to reposition
Recent updates
  • Thanks Nick for undertaking these updates...

    I could accept that if there are concrete plans to implement the replacement within say the next three months, and announced within the next week or two. As yet there hasn't been a single append by anyone from Clear management as to *when* it will happen and *what* the replacement will be. So other than an indication that we *might* move to Discourse , and no indication whatsoever of timing - we are still in much the same situation as 8 1/2 years ago. This change could be two years away or more for all we know...

    Perhaps we should change the bug to something like "no viable procedure or willingness to fix problems, performance issues, bugs etc affecting the Clear Forums". :p If after the move to Discourse. or whatever the replacement, is - we still have the same crappy support and reluctance to fix issues, we will still have the same basic problem as currently experienced. Discourse looks nice, but will there be continuous competent and expeditious support?

  • Just to confirm that automatic updates with certbot-0.31.0-2.el7.noarch work OK here
    yum log

    Successful update early this morning, 30 days before expiry...

  • As suspected flip-flop is a result of both interfaces connected to the same subnet - don't do it as Nick indicates... (bridge would be the exception).

    The bacteria growth in water cooling systems is a result of mismanagement. There are various anti-fungal additives available that prevent this, as well as corrosion inhibitors to reduce hardware damage. The world is full of water cooling systems from cooling towers to automobiles and the technology mature. A quick check on using Google would have shown what is required - here are two excellent references...
    Part I Part II

    That power supply is a decent one... Re. IPMI memory error - can you please quote the error verbatim...

  • Tony Ellis
    Tony Ellis replied to a discussion, ClearOS Crashing

    The Vendor id for the NICs suggest this is a Dell PowerEdge 860 Server of about 2006 vintage. Is this correct? If so, then hardware that old could be developing all sorts of problems. Electrolytic Capacitors drying out, memory issues, power supply starting to fail, CPU heat transfer paste between CPU and heat-sink going bad, fans running too slow as bearings worn, case full of dust, CPU head-sink clogged, hard disk errors etc...

    Completely agree with Nick. If you want a response the you must make it easy to get the information. I read the first screen with the NIC information, sorry not going to struggle any further If you must use a camera/phone then at least hold it in a position where the lens points straight at and is level with the centre of the screen and you get a square screen snapshot with all of it mostly in focus, not one where the lines go out of focus and diminish in length as they become further away from the lens. A photo is necessary to capture the panic output - this could help us. The rest should be a copy and paste as Nick detailed - between code tags.

    Have you performed some of the simple checks such as running memory tests for a few hours, or running the S.M.A.R.T disk monitoring tool long test (install the smartmontools package if not already installed) to verify the disk drive(s) are not having problems? Inspected the interior of the server?

  • One further thought... on re-reading your appends came across the reference to water cooling. One disadvantage to water cooling is a hotter running mother board. Reason? There is no CPU fan moving the air near the mother-board - especially with a down-facing CPU fan pushing air through the heat-sing to the CPU. The power control circuitry on the mother board for the CPU and memory generates significant heat which quickly builds up if there is static stale air in that area. Some water cooling builders actually install a fan blowing on the mother-board to combat this problem. This also helps the memory to run cooler...


  • 've detect a quite high system temp in my IPMI monitoring I guess related to North & South Bridge. at idle 61°C whit heavy load in raise up to 105°C but system is still responding...

    Seems too high to me - you would not want even the CPUs to run that hot... Is the case cooling working OK? Fans spinning, any filters clean, grills clean. Is there a dust build up on the fan blades reducing their efficiency... poor case location - needs to be resolved. Fan orientation such that air is pulled in from one side and expelled the other. What case, how many fans and where?

    You indicated two NICs. What is the network mode configuration? Gateway? standalone etc... connected to what.. Network addresses... static, dhcp? Details please...

    Mac addresses 0c:c4:7a:33:07:8a and 0c:c4:7a:33:07:8b are the two NICs on the ClearOS server? If so, makes me wonder if they are on the same sub-net getting dhcp addresses to flip-flop like that, but without any information on your network can on;y guess...

    Make and model of the new power supply?

  • I didn't say you had a full file system or disk - just suggesting reducing the excessive logging and consequent disk activity. As for disks, would recommend running the long smart tests as well. See nothing obviously wrong with the rsyslog.conf file.

    You might get some ideas regarding the hang here Could you please provide a short summary of the system components and their age so we know what we are dealing with.. Using raid? One prime suspect, if hardware, would be the power supply. External sources could include interference, dips in the mains power supply or mains wiring fault. Do you use a UPS? Can you reboot after a hang using Ctl-Alt-Del - or is it necessary to press the Reset or Power Off Switch?

  • ClearCenter Marketplace: [SSL: CERTIFICATE_VERIFY_FAILED]

    Am I the only one? Seeing this on all the ClearOS machines here using yum...

  • Two suggestions :-
    1) arpwatch
    Suggest at least temporarily stop logging arpwatch messages by adding a file to /etc/rsyslog.d (see below ). This will stop the clutter in /var/log/messages and and prevent the excessive disk activity as well as saving disk space in /var/log directory (Nowhere near full I hope)...
    2) rsyslog
    As I understand it the "actions" are numbered sequentially from the start of the "#### RULES ####" section in /etc/syslog.conf (if this is incorrect please indicate how they are numbered). Can you please show us your /etc/rsyslog.conf from "#### RULES ####" to the end (in code tags please).

    Create a file named, for example, /etc/rsyslog.d/arpwatch.conf with the following contents similar to the following

    See previous discussion in these forums regarding these files...