vestacp open: /etc/named.conf: permission denied Rumi, August 1, 2022 This was the error I was getting after a doing a little change in the named.conf in my newly installed vesta control panel. While restarting the named, I was getting this error- [root@vesta2 ~]# systemctl status named.service ● named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2022-08-01 14:37:25 +06; 6s ago Process: 3478 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=1/FAILURE) Process: 3475 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS) Aug 01 14:37:25 vesta2.geospacehosting.com named[3480]: found 2 CPUs, using 2 worker threads Aug 01 14:37:25 vesta2.geospacehosting.com named[3480]: using 1 UDP listener per interface Aug 01 14:37:25 vesta2.geospacehosting.com named[3480]: using up to 21000 sockets Aug 01 14:37:25 vesta2.geospacehosting.com named[3480]: loading configuration from '/etc/named.conf' Aug 01 14:37:25 vesta2.geospacehosting.com named[3480]: open: /etc/named.conf: permission denied Aug 01 14:37:25 vesta2.geospacehosting.com named[3480]: loading configuration: permission denied Aug 01 14:37:25 vesta2.geospacehosting.com systemd[1]: named.service: control process exited, code=exited status=1 Aug 01 14:37:25 vesta2.geospacehosting.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS). Aug 01 14:37:25 vesta2.geospacehosting.com systemd[1]: Unit named.service entered failed state. Aug 01 14:37:25 vesta2.geospacehosting.com systemd[1]: named.service failed. Solution: Step-1: Execute the following command- restorecon -RFv /etc/named.conf Step-2: Setting permission- chmod 644 /etc/named.conf Related Configurations (Linux) Bindvesta cp
Vesta- How to set up master-slave DNS cluster January 28, 2019January 28, 2019 If you are looking for the options to avoid any DNS-related downtime or the way to manage dns across all server you have, you might consider to set up dns cluster. Create user dns-cluster on a server which will be used as dns slave On the second server (slave) with… Read More
Fix: Unable to start TLS: SSL connect attempt failed error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed when connecting to ldap master.Cannot determine services – exiting September 1, 2018 My ZImbra 8.6 was throwing the following error once after my letsencrypt SSL got expired: Unable to start TLS: SSL connect attempt failed error:14090086:SSL routines:ssl3_get_server_certificate:certificate verify failed when connecting to ldap master.Cannot determine services – exiting The Fix: In order to fix the problem you need to modify the following… Read More
Deploying a J2EE application behind an Apache server in a production environment April 20, 2012 You have created a Web application using a JBoss application server and you are going to put it in production. Great! But deploying your application with JBoss serving the Web requests directly may not be the optimal solution. First because the Tomcat web server embedded within JBoss is not the… Read More