Profile Details

Toggle Sidebar
Recent updates
  • Thanks Nick for inquiring.

  • Hello Nick,

    Really really really nice to heard from you again. I hope all is well...

    I regards to your question: the server above is currently unavailable for me to do an update. Instead I ran a few cmds on a test vm. This is not an update but an install of mongodb-server showing similar issues with the same above 'nodejs-libs.x86_64' library. Note this time the library is not even installed ... that also can not be right?

  • Dependency issue: mongodb-server


    During my latest update of one of my servers, I am having a dependency issue:

    ---> Package openssl11-libs.x86_64 1:1.1.1k-2.el7 will be installed
    ---> Package v8.x86_64 1: will be obsoleted
    --> Processing Dependency: for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Finished Dependency Resolution
    --> Running transaction check
    ---> Package kernel.x86_64 0:3.10.0-1062.18.1.el7 will be erased
    ---> Package v8.x86_64 1: will be obsoleted
    --> Processing Dependency: for package: mongodb-server-2.6.12-6.el7.x86_64
    --> Finished Dependency Resolution
    Error: Package: mongodb-server-2.6.12-6.el7.x86_64 (@clearos-epel)
    Removing: 1:v8- (@clearos-epel)
    Obsoleted By: 1:nodejs-libs-16.13.2-3.el7.x86_64 (clearos-epel)[/code]

    It appears that the package mongodb-server requires a library that is being removed/obsolete with the install of the package: nodejs-libs

    I have had to exclude the nodejs-libs package to perform my update:

  • Finally found out from where this mysterious 'mcad' service message came from. It turns out that one of my Unifi AP appliances was the culprit and was configured to do remote Syslog server logging to my server gateway. Thanks Nick for your suggestions.

  • Hello Nick, this is so weird, same here I also can not find what is this 'mcad' process. Nothing pops out from your suggestions, B.T.W. thanks.

    I think I might have to change business and start growing potatoes instead.

  • Low memory; process mcad (xxxxx) killed

    I had a blip happen to my Gateway vm yesterday. This issue occurred between 2021-04-14 17:00:10 and 2021-04-14 20:55:51. I was notified by email of the issue, the server seem to respond appropriately. The issue stopped without my intervention.

    I ran the following cmd while the issue was happening with no results.

    I also restarted the vm during the event with no changes to the issue.

    Does any one know what is the 'mcad' service?

  • Dudley Ali wrote:

    Philippe Eveleigh wrote:

    I could be wrong about this but I do not think you can. I believe there is no connection on cable, you join the Ethernet Network of your ISP.

    If you had a PPP (ADSL, VDSL) you would have a better chance at doing this since you actually login for that protocol, you would still need to contact your ISP to see if they allow you to connect more than once. Note this does not provide more bandwidth since that is a feature of the line not the connection.

    Thank you I will give it a look

    Hello Dudley,

    My answer at the time might not be correct. I have learned over time that some ISP's may allow more than one connection by monitoring the MAC addresses used; anyways for ISP’s here in Canada. If you are allowed more than one connection and notice that you are denied your allocated number. You may be required to contact your ISP to clear the MAC addresses that are not in use anymore.


  • Agreed, as usual thank you for your input.

  • Hello Nick,

    Yes that is what I was concerned with. That this may cause me more grief then needed... as the saying: “if it works, don't touch it”.

    For the change of configuration on the ESXi side of things. Yes indeed I can configure the vm as requested to: Other 3.x Linux (64-bit) and that might be a better approach to the issue? I tried and I do not think this configuration will have any ill effect with ESXi since the status of the vm went from warning to normal. For both configuration the vm-tools service is acknowledge as running by ESXi. The only thing that I do not know is if ESXi does any specific type of optimization for a CentOS configuration that might have been beneficiary?

  • CLearOS ESXi vm-tools compatibility

    I wish to change the symbolic link:: /etc/centos-release in ClearOS for the following information: CentOS Linux release 7.8.1 (Core)

    I am receiving the following log message from ESXi on my setup with the ClearOS current configuration of /etc/centos-release: ClearOS release 7.8.1 (Final)

    The configured guest OS (CentOS 4/5/6 (64-bit)) for this virtual machine does not match the guest that is currently running (Other 3.x Linux (64-bit)). You should specify the correct guest OS to allow for guest-specific optimizations.

    It appears that this change seems to be relevant for optimizing the performance of ClearOS within an ESXi environment (both being Community Versions). Note that all my ClearOS vm's within my ESXi configuration are all set to CentOS... (which I believe to be the most accurate for ESXi ClearOS combination). I am assuming that vm-tools is providing CLearOS vm the Guest OS version that are set in /etc/centos-release. Having changed the information to the above seems satisfy my ESXI server. Now what I am wondering is if I have created myself future update release issues with CLearOS?

    Thank You

    For your information it appears that VMware is only looking at the first digit for the version: