I cannot replicate the issue:

The only thing I can think to suggest without more info is to please make sure that your eno8 is completely unconfigured.

When you get your error, can you post the 'tail -n 50 /var/log/messages'

[root@download-test network-scripts]# cat ifcfg-enp0s8.509
DEVICE=enp0s8.509
TYPE="VLAN"
ONBOOT="yes"
USERCTL="no"
BOOTPROTO="static"
IPADDR="10.100.9.1"
NETMASK="255.255.255.0"
VLAN="yes"
[root@download-test network-scripts]# cat ifcfg-enp0s8.501
DEVICE=enp0s8.501
TYPE="VLAN"
ONBOOT="yes"
USERCTL="no"
BOOTPROTO="static"
IPADDR="10.100.1.1"
NETMASK="255.255.255.0"
VLAN="yes"
[root@download-test network-scripts]# cat ifcfg-enp0s8.512
DEVICE=enp0s8.512
TYPE="VLAN"
ONBOOT="yes"
USERCTL="no"
BOOTPROTO="static"
IPADDR="10.100.12.1"
NETMASK="255.255.255.0"
VLAN="yes"

Do you have any snippets of the mad logging?

It is possible that the db is trying to do a recovery, hence the proc spike.

Awesome feedback everyone.

I've compiled your answers here and have given some feedback:

https://docs.google.com/document/d/14QllNp5OjRTyC9ejlf1gEGme6mmUCCinRJFOaZl6KO4/edit?usp=sharing

Please give us more.

What features or changes would you like to see around here

As we are working to provide on ClearOS 8 we are looking to see what features and functions that you find lacking with ClearOS, the portals, and this website. What would you like improved and what would you like changed. We are working on building our roadmap for 8 and need to know what is key for you. We also want to allow for greater community involvement and if you have an interest in 'owning' or leading within the community.

Tony,

There is a specific security bug being fixed involved that is holding things up. I'm not going to go into details but we are withholding releases until it is resolved. We are keenly aware that updates are slow and are working to resolve the issue so things can get back to normal. As for the EOL for 6, our link that Nick shared is accurate still but we may extend 6 or push security patches if deemed necessary. That being said, our goal is to also produce a DVD sometime this quarter for 6.x so that we have a more recent media for 6.x... a sort of last hurrah before it goes EOL.

We are also working on ClearOS 8 topics as well. If you have suggestions for 8, let us know what they are. I will start a thread on that topic so we can better gauge community interest.

You may have a driver that is specifically tuned to an old ABI. What ClearOS media are you using to install? You need to make sure that you are using ClearOS 7.5 release media (or later). You can also pass parameters to make your install text only as well as simply scripting the install with a .ks file. Here is an example of one I've used before on a system where the recovery partition contained the ISO and the ks file here:

ClearVM 1.0 starts VMs as a qemu-img. It has to start it or it won't know about it. In ClearVM 2.0 we use libvirtd so the whole libvirt stack and tools are compatible.

From command line you should be able to determine if your block devices are present. Run the following and see what is available and what is mounted:

blkid
mount

One way to mitigate this, even as a defensive strategy is to install MultiWAN even for LAN boxes. This will prevent a misconfigured, multiple-external configuration from causing issues with the routing tables because it will place the routing under dynamic management and start to employ iproute2-style routes for traffic.

My 2 cents.

What you need is type 0x10000002 rules in /etc/clearos/fiirewall.conf



You can use WinSCP to directly edit the file but be careful in creating rule so that you don't make a typo.

In the example, I use 'Test' as the firewall rule name (don't recommend spaces but use underscores and dashes). I used 1.1.1.1 for the IP address to be blocked.

You can and should use CIDRs where possible, for example:



If you have a really long list, you should investigate calling an ipset list and creating your own ipset rules.

Marcel,

You can turn up logging in Webconfig by modifying the following:

/var/webconfig/common/Config.inc.php



Then this will give us more info about what is going on in /var/log/system

Be sure to back up the file and remove the extra logging when you have your error snippet.