similar to: Bind fails to start after update from 7.1 to 7.2

On 01/05/2016 02:00 PM, Alexander Dalloz wrote: > Am 05.01.2016 um 22:03 schrieb Emmett Culley: >> I am seeing these lines for each domain in the systemd journal: >> >> zone relationship123.com/IN: loading from master file relationship123.com.db failed: file not found >> zone relationship123.com/IN: not loaded due to errors. >> _default/relationship123.com./IN:

Am 05.01.2016 um 22:03 schrieb Emmett Culley: > I am seeing these lines for each domain in the systemd journal: > > zone relationship123.com/IN: loading from master file relationship123.com.db failed: file not found > zone relationship123.com/IN: not loaded due to errors. > _default/relationship123.com./IN: file not found here: relationship123.com > If I change the zone defs to

On 06/07/2016 05:05 AM, James Hogarth wrote: > On 7 Jun 2016 12:44, "Emmett Culley" <lst_manage at webengineer.com> wrote: >> >> I have a number of machines (hardware and VMs) running CentOS 7. I all > cases firewall-config is not functional. >> >> First, the service check boxes are not functional. When you click on > one, it don't change to

Am 06.01.2016 um 00:21 schrieb Emmett Culley: > On 01/05/2016 02:00 PM, Alexander Dalloz wrote: >> >Am 05.01.2016 um 22:03 schrieb Emmett Culley: >>> >>I am seeing these lines for each domain in the systemd journal: >>> >> >>> >>zone relationship123.com/IN: loading from master file relationship123.com.db failed: file not found >>>

I have a number of machines (hardware and VMs) running CentOS 7. I all cases firewall-config is not functional. First, the service check boxes are not functional. When you click on one, it don't change to "checked", and nothing changes on the firewall. However you do see a "Changes applied" Sometimes, f you go to permanent mode and attempt to edit a zone, the whole

On Jan 5, 2016, at 1:03 PM, Emmett Culley <lst_manage at webengineer.com> wrote: > > I am seeing these lines for each domain in the systemd journal: > > zone relationship123.com/IN: loading from master file relationship123.com.db failed: file not found > zone relationship123.com/IN: not loaded due to errors. > _default/relationship123.com./IN: file not found [snip] Just

I understand that the contents of /etc/sysctl.conf should be read and executed at system startup. However that never happens and I have to run sysctl -p after every reboot to get the settings I want. This is happening on every CentOS machine and VM I have. I can see in the startup scripts that "sysctl -e -p /etc/sysctl.conf >/dev/null 2>&1" is run at start up by the

After successfully updating three CentOS 6.3 VM guests to 6.4 I decided to update the host as well. And it failed to boot. Kernel panic - Not syncing: Attempted to kill init! Pid: 1, comm: init not tainted: 2.6.32-358.2.1.el6.x86_64 #1 Plus a call trace I couldn't see Luckily I was able to boot from the previous kernel and get my system back up. After booting to the previous kernel I

First system-config-network is not part of CentOS/RHEL 6, now I don't see system-config-bind either. Is there an alternative (GUI) way to manage the bind DNS server? Emmett

I finally decided to install the CR repo on one of my CentOS 6 machines that I use as a host for some VMs (also running CentOS 6). Before updating the host I updated a VM that was not critical to test the process and was able to boot that VM, so I went ahead with updating the host and the two VMs that were in use. When I rebooted the host none of the VM would start. Once I figured out that it

I have been using BackupPC via rsync daemons on the target machines and all has been working well. At least until about the time rsync went to version 3.0.6. Since then backups have been failing for some targets. The failure is a TCP ZeroWindow issue. It looks like the server rsync process cannot empty it's buffer soon enough and eventually the process fails. I really do not know if it is

https://bugzilla.samba.org/show_bug.cgi?id=9407 Summary: rsync transfers cause zero window packets Product: rsync Version: 3.0.9 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: emmett at webengineer.com

Have you found a solution? Did u allow master dns server to update the slave in /etc/named.conf ? -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of John R Pierce Sent: Monday, January 12, 2015 7:02 AM To: centos at centos.org Subject: Re: [CentOS] Zone file not written to slave DNS server On 1/11/2015 9:28 PM, Emmett Culley wrote:

On 14/01/2015 03:56, Emmett Culley wrote: > On 01/13/2015 12:10 PM, Mateusz Guz wrote: >> Have you found a solution? >> >> Did u allow master dns server to update the slave in /etc/named.conf ? >> >> >> >> -----Original Message----- >> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of John R Pierce >>

I have mostly succeeded in getting master and slave DNS servers operational. Mostly, because the zone file is not written when a zone is updated on the master server when the notify and transfer process happens. The slave DNS server gets the changes to the modified zone, but the slave zone file remains as before. I've found a few tutorials and lots of discussions, many of which talk about

I just noticed that when rebooting a CentOS 7 server the firewall comes back up with both interfaces set to REJECT, instead of the eth1 interface set to ACCEPT as defined in 'permanent' firewalld configuration files. All servers are up to date. By "just noticed" I mean that I finally investigated why a newly rebooted VM failed to allow NFS connections. Prior to doing that.

On 10/12/2015 10:17 AM, Gordon Messmer wrote: > On 10/11/2015 03:00 PM, Emmett Culley wrote: >> I just noticed that when rebooting a CentOS 7 server the firewall comes back up with both interfaces set to REJECT, instead of the eth1 interface set to ACCEPT as defined in 'permanent' firewalld configuration files. > > Rather than paraphrasing, could you show the specific

CentOS-5.5 # uname -a Linux inet05.hamilton.harte-lyne.ca 2.6.18-194.32.1.el5 #1 SMP Wed Jan 5 17:52:25 EST 2011 x86_64 x86_64 x86_64 GNU/Linux Can anyone tell me why I am seeing these error message? Specifically, why is TYPE=Bridge giving Unknown connection type 'Bridge'? Jan 13 08:25:31 inet05 nm-system-settings: Loaded plugin ifcfg-rh: (c) 2007 - 2008 Red Hat, Inc. To report bugs

On 7/15/20 2:39 AM, Gianluca Cecchi wrote: > On Wed, Jul 15, 2020 at 2:39 AM Emmett Culley via CentOS <centos at centos.org <mailto:centos at centos.org>> wrote: > > > Thanks for the info.? I hadn't seen that before nor many of the links.? I had seen the suggested systemd fix, but have never been able got them to work. And I've tried many combinations.? Still

> On 7/19/20 10:41 PM, Simon Matter via CentOS wrote: >>> On 7/13/20 6:40 PM, Emmett Culley via CentOS wrote: >>>> I need to set the umask for apache to 002.? I've tried every idea I've >>>> found on the internet, but nothing make a difference.? Most suggest >>>> that >>>> I put "umask 002" in /etc/sysconfig/httpd, but