I tried that with little success.
If i run the df -h command, then I see that the /dev/mapper.clearos-root is using 781Gb of the drive.
If i then run the du -h --max-depth=1 / it points me to the /var/flexshare folder.
However i have moved the data for /var/flexshare/shares/photos, /var/flexshare/shares/development and /var/flexshare/shares/backups to the 2Tb drive mounted on /Backups with bind mounts to the /var/flexshare/shares folder. Have I done something wrong in the fstab file?
Thanks for the responses. No, I have not completely resolved this. I moved my flexshares to an external drive and then used bind mounts for them. This brought my disc usage down from 100% to <90%. It's not ideal, but at least I can change/modify configuration without the Ooops message. The disc usage tool shows I'm only using <40Gb where the system report shows I'm using 780Gb. I think i may get a replacement solid state and do a fresh install. Then I can check the drive without hampering the live server.
My system (ClearOS V7.3.0) has started popping up with the message
Ooooops: Server is running low on available disk space - preventing further modifications via API until disk space issues are resolved..
My system summary shows the /dev/mapper/clearos-root as being 100% used. This is a 1Tb solid state drive. The biggest directory is my VAR at 165Gb, but the next biggest is the USR at only 2.3Gb. In total, i shouldn't be using more than 200Gb.
I ran the command below, but this didn't highlight anything other than my flexshare folders.
I just can't seem to see where 916Gb is being used. Any ideas?
I'm running the business version of ClearOS 7 and am having issues recently with the content filter. Recently we are receiving allot of emails regarding weight loss and diet pills. I have selected all the relevant phrase lists in the content filter, but it's not picking up these emails. For the most part, the SPAM filter is picking them up, but the level is not enough for them to be automatically discarded by the antispam. My content filter is updating as it should - i'm just guessing these these are new phrases and yet to be added to the content filter.
Is there a way to manually add phrases to the content filter? Or is there a way to suggest additions to the content filter moderators to add to the next update?
Thanks in advance.
Is there any permanent fix to using SSL on the clearOS7 system? I have SSL on multiple virtual sites running on ClearOS7, but it's a pain as each time there is an update, the flex-80.conf file is autocreated and I have to manually remove the section below from the file. Is there specific folder permissions i need to apply or something?
Options +Indexes +FollowSymLinks -IncludesNOExec
Require all granted
I found out that the <Directory....</Directory> in the flex-80.conf file is what is breaking the system. No matter what options you select in the webconfig, this just stops the pointing. I have deleted this and my site is working and the SSL is working too. It's just a pain that this is an autocreated file so I have no idea how long it's going to work for.
Options +Indexes -FollowSymLinks -IncludesNOExec
Require all granted
Little checking since my last post. The httpd service failed due to SSL certificate (Unable to configure RSA server private key). If I don't use SSL, then the httpd server starts up. However it does not direct to virtual sites. I see that webconfig has now created a file /etc/http/conf.d/flex-80.conf as well as flex-443.conf files. However they don't seem to have any affect. If I copy my old virtual.website.com.conf file into the /etc/httpd/conf.d directory then the directing to the virtual website works again. However I'm back at square one where I can't use the SSL.
Manually did the update. I no longer get the error message in webconfig. I however cannot start the httpd service.
Mar 22 13:05:18 server systemd: Started ProFTPD FTP Server.
Mar 22 13:05:21 server webconfig: Redirecting to /bin/systemctl start httpd.service
Mar 22 13:05:21 server systemd: Starting The Apache HTTP Server...
Mar 22 13:05:21 server systemd: httpd.service: main process exited, code=exited, status=1/FAILURE
Mar 22 13:05:21 server kill: kill: cannot find process ""
Mar 22 13:05:21 server systemd: httpd.service: control process exited, code=exited status=1
Mar 22 13:05:21 server systemd: Failed to start The Apache HTTP Server.
Mar 22 13:05:21 server systemd: Unit httpd.service entered failed state.
Mar 22 13:05:21 server systemd: httpd.service failed.