Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - bentsea

Pages: [1]
How to / Cron job works from command line but not in cron
« on: July 22, 2019, 04:11:45 PM »

The following works for me from the command line:

/usr/local/bin/php /home/tetra/help/public_html/api/cron.php

However, I've tried the following cron jobs and none of them have produced any results:

* * * * * tetra /usr/local/bin/php /home/tetra/help/public_html/api/cron.php
* * * * * nobody /usr/local/bin/php /home/tetra/help/public_html/api/cron.php
* * * * * /usr/local/bin/php /home/tetra/help/public_html/api/cron.php
* * * * * /opt/alt/php-fpm70/usr/bin/php /home/tetra/help/public_html/api/cron.php

The permissions for that file are 755. I've checked my cron logs, and I'm not 100% sure it is being run at all, but honestly I do not know how to identify for sure. This is for the past hour and I've had 1 minute crons in this queue for over an hour and this is the only output from tail (I wasn't able to do this as the user, I had to do it as root):

Code: [Select]
Jul 22 14:10:01 server3 CROND[24716]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 14:20:01 server3 CROND[25605]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 14:30:01 server3 CROND[28042]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 14:40:01 server3 CROND[21551]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 14:50:01 server3 CROND[7167]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 15:00:01 server3 CROND[4888]: (root) CMD (/usr/share/clamav/freshclam-sleep)
Jul 22 15:00:01 server3 CROND[4889]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 15:01:01 server3 CROND[4969]: (root) CMD (run-parts /etc/cron.hourly)
Jul 22 15:01:01 server3 run-parts(/etc/cron.hourly)[4969]: starting 0anacron
Jul 22 15:01:01 server3 run-parts(/etc/cron.hourly)[4978]: finished 0anacron
Jul 22 15:10:01 server3 CROND[6247]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 15:20:01 server3 CROND[6985]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 15:30:01 server3 CROND[7756]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 15:40:01 server3 CROND[10443]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 15:50:02 server3 CROND[14263]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 16:00:01 server3 CROND[15617]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Jul 22 16:01:01 server3 CROND[15689]: (root) CMD (run-parts /etc/cron.hourly)
Jul 22 16:01:01 server3 run-parts(/etc/cron.hourly)[15689]: starting 0anacron
Jul 22 16:01:01 server3 run-parts(/etc/cron.hourly)[15698]: finished 0anacron
Jul 22 16:10:01 server3 CROND[16183]: (root) CMD (/usr/lib64/sa/sa1 1 1)

CentOS 7 Problems / Changing Hostname Inserts Junk into Hostname
« on: April 01, 2019, 12:19:23 AM »
From the change hostname menu (Server Settings -> Change Hostname) I am experiencing an error when clicking the change hostname button. No matter what I set my hostname to, the server appends "" to the hostname when it moves to the next screen.

Example, if I try to set my hostname to the server sets it to server5.bentsea.net127.0.0.1.

THis obviously causes SSL generation to fail and causes the "You do not have a valid hostname set" error.

Can anyone recommend any kind of troubleshooting for this?

CentOS 7 Problems / AutoSSL Hangs and Fails
« on: March 30, 2019, 10:44:32 AM »
I just reinstalled CWP from scratch and AutoSSL is not issuing an SSL for the hostname, in addition to this when attempting to enable autossl for any domains installed on the server causes the install process to hang and not complete. I'm not sure where to troubleshoot this because no error is generated, any use of Autossl just hangs for forever. Any recommendations for how to troubleshoot?

DNS / BIND DNS / Nameservers are unreachable
« on: December 29, 2018, 11:41:46 PM »

While trying to rollback an update using yum history undo, I accidentally rolled back the wrong update and it broke bind. I'm not sure which one. It would not start, but I was able to fix it by reinstalling BIND with
Code: [Select]
yum install bind bind-utils. At this time BIND will start and run normally, however, none of the domains using my custom name servers will resolve. Leaf DNS returns the following error:

"FAIL: Nameserver is unreachable."

Here are zone files for the two domains that will not load:

Code: [Select]
; Generated by CWP
; Zone file for
$TTL 14400
@    86400        IN      SOA (
2018071600      ; serial, todays date+todays
3600            ; refresh, seconds
7200            ; retry, seconds
1209600         ; expire, seconds
86400 )         ; minimum, seconds

@ 86400 IN NS
@ 86400 IN NS
@ IN MX 0
mail 14400 IN CNAME
smtp 14400 IN CNAME
pop  14400 IN CNAME
pop3 14400 IN CNAME
imap 14400 IN CNAME
webmail 14400 IN A
cpanel 14400 IN A
cwp 14400 IN A
www 14400 IN CNAME
ftp 14400 IN CNAME
_dmarc 14400 IN TXT "v=DMARC1; p=none"
@ 14400 IN TXT "v=spf1 +a +mx +ip4: ~all"

default._domainkey 14400 IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDeyZLcuYMlLXr2kN0C6q/aSK8WltaHIzoGgGed1yrc2BlQmpmvb6fU5PtPtHxDXhVRK5xNH8xe6gJSeVqoUDcMZGICY5VMjrS0b4RCZ7NlPl1MWY9hCoke09iDe7khzNE8UEQyf+Yu+5lKCgRyRUNZGdABrFE3h7N0ALtO95tkywIDAQAB"

Code: [Select]
; Generated by CWP
; Zone file for
$TTL 14400      86400        IN      SOA (
2013071600      ; serial, todays date+todays
86400           ; refresh, seconds
7200            ; retry, seconds
3600000         ; expire, seconds
86400 )         ; minimum, seconds 86400 IN NS 86400 IN NS IN A IN A IN MX 0

; Add additional settings below this line
_dmarc 14400 IN TXT "v=DMARC1; p=none"

I've tried recreating the name servers, removing and re-adding the domains. All the records appear to be correct to me. BIND service is running... I'm at a complete loss for why the name servers are not responding and for what can resolve this.

CentOS 6 Problems / Blank White Screen
« on: January 28, 2017, 05:19:41 AM »
My CWP control panel has suddenly started to display a blank white screen, both on the secure and unsecure ports. Nothing was changed on the server (Manually) since the last time I accessed it, which was some months ago. I'm not even sure where to start troubleshooting this one. This looks like a PHP error that I've seen with other scripts but I have no idea, really. The control panel URL:

Any ideas how to resolve this? I'm using CentOS 6

Apache appears to still be resolving:

SSL / Error Restarting cwpsrv Service for Servername SSL
« on: January 21, 2017, 05:40:40 PM »
Hello, I am attempting to install an SSL for my server name using the Tutorial available here:

I am using CentOS 7 with the default apache only configuration.

I am successful through step one and two, and my host name can be reached via HTTPS:

When I perform step 3 to enable HTTPS access via port 2031,  there is no cwp-ssl.conf file. So I have created one with the following code:

Code: [Select]
Listen 2031

        SSLEngine on
 SSLCertificateFile /etc/letsencrypt/live/
 SSLCertificateKeyFile /etc/letsencrypt/live/
 SSLCertificateChainFile /etc/letsencrypt/live/
 SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown

When restarting the cwpsrv, I get the following error:

Code: [Select]
Redirecting to /bin/systemctl restart  cwpsrv.service
Job for cwpsrv.service failed because the control process exited with error code. See "systemctl status cwpsrv.service" and "journalctl -xe" for details.

The ouput for "journalctl -xe" yields the following error:
Code: [Select]
Jan 21 11:31:46 server3 systemd[1]: Starting CentOS Web Panel service (daemon)...
-- Subject: Unit cwpsrv.service has begun start-up
-- Defined-By: systemd
-- Support:
-- Unit cwpsrv.service has begun starting up.
Jan 21 11:31:46 server3 cwpsrv[30103]: nginx: [emerg] unexpected end of file, expecting ";" or "}" in /usr/local/cwpsrv/conf.d/cwp-ssl.conf:10
Jan 21 11:31:46 server3 cwpsrv[30103]: nginx: configuration file /usr/local/cwpsrv/conf/cwpsrv.conf test failed

I have been unable to locate any alternative cwp-ssl.conf code given that the error appears to be potentially with syntax or alternative directions for configuring correct use of an SSL for service over port 2031 with the letsencrypt issues SSL. Any help resolving this issue or with alternative directions for configuring for use on port 2031 would be greatly appreciated.

Pages: [1]