Discussion between Rilindo and stevether - 2011-09-22

« first day last day (14 days later) »

12:00 AM

And while you are at it, do a ls -la on /var/log? I want to see if named is writing to a separate file or not.

zone "rayhawkoffices.com" {
type master;
file "/var/named/forward.rayhawkoffices.com";
};
zone "patientacquisitionsystems.com" {
type master;
file "/var/named/forward.patientacquisitionsystems.com";
};
zone "patientacquisitionsystem.org" {
type master;
file "/var/named/forward.patientacquisitionsystem.org";
};
zone "patientacquisitionsystems.org" {
type master;
file "/var/named/forward.patientacquisitionsystems.org";
};
zone "patientacquisitionsystem.com" {
type master;
file "/var/named/forward.patientacquisitionsystem.com";

Okay, so we won't disable that file, then.

[root@ip-184-168-86-185 var]# ls -la log
total 87128
drwxr-xr-x 6 root root 4096 Sep 21 14:53 .
drwxr-xr-x 22 root root 4096 Sep 21 14:39 ..
-rw------- 1 root root 0 Sep 20 18:32 boot.log
-rw-r--r-- 1 root root 591803 Sep 21 17:01 brcm-iscsi.log
-rw------- 1 root utmp 81204480 Sep 21 15:31 btmp
-rw------- 1 root root 152246 Sep 21 11:38 cron
-rw-r--r-- 1 root root 0 Feb 1 2011 dmesg
-rw------- 1 root root 13440 Sep 21 12:54 faillog

Okay, it doesn't look like that named is logging to a separate file. But unless you are in the different time zone, messages file has not been updated yet. :(

for giggles, can you tail -50 on the message file again?

there's this if it helps [root@ip-184-168-86-185 log]# ls -la messages
-rw------- 1 root root 969 Sep 21 11:38 messages
[root@ip-184-168-86-185 log]# cd ../../../
[root@ip-184-168-86-185 /]# /usr/sbin/named -u named -t /var/named/chroot -g
21-Sep-2011 17:03:40.039 starting BIND 9.3.6-P1-RedHat-9.3.6-16.P1.el5 -u named -t /var/named/chroot -g
21-Sep-2011 20:03:40.128 found 8 CPUs, using 8 worker threads
21-Sep-2011 20:03:40.128 using up to 4096 sockets
21-Sep-2011 20:03:40.134 loading configuration from '/etc/named.conf'

12:04 AM

Okay. . .

Alright . .

That is progress

can you do ls -la /etc/named*

[root@ip-184-168-86-185 /]# ls -la /etc/named*
lrwxrwxrwx 1 root named 52 Sep 21 14:40 /etc/named.caching-nameserver.conf -> /var/named-chroot//etc/named.caching-nameserver.conf
lrwxrwxrwx 1 root named 32 Feb 1 2011 /etc/named.conf -> /var/named-chroot/etc/named.conf
lrwxrwxrwx 1 root named 40 May 23 16:23 /etc/named.conf.tpsave -> /var/named-chroot//etc/named.conf.tpsave
lrwxrwxrwx 1 root named 42 Sep 21 14:40 /etc/named.rfc1912.zones -> /var/named-chroot//etc/named.rfc1912.zones

do "cat /etc/sysconfig/named "

Make sure that this line:

ROOTDIR=/var/named/chroot

is not commented out.

or this case:

it's not

ROOTDIR=/var/named-chroot

Can you see if anything else is not commented out in that file?

[root@ip-184-168-86-185 /]# cat /etc/sysconfig/named
# Currently, you can use the following options:
# ROOTDIR="/some/where" -- will run named in a chroot environment.
# you must set up the chroot environment before
# doing this.
# OPTIONS="whatever" -- These additional options will be passed to named
# at startup. Don't add -t here, use ROOTDIR instead.
ROOTDIR=/var/named-chroot

nothing important

12:10 AM

*looking at my DNS setup.

lets cd back to /var/named-chroot/etc

and give read permissions to named.conf with:

chmod 644 named.conf

and then restart named

ugh, still no

do tail /var/log/messages

and then ls -la /var/named-chroot/etc/

[root@ip-184-168-86-185 /]# tail /var/log/messages
2011-09-20T18:32:37.322626-07:00 ip-184-168-86-185 rsyslogd: [origin software="rsyslogd" swVersion="3.22.1" x-pid="3127" x-info="http://www.rsyslog.com"] (re)start
2011-09-20T18:32:37.321006-07:00 ip-184-168-86-185 rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically generated config directives may interfer with your rsyslog.conf settings. We suggest upgrading your config and adding -c3 as the first rsyslogd option.
2011-09-20T18:32:37.322354-07:00 ip-184-168-86-185 rsyslogd: Warning: backward compatibility layer adde…

[root@ip-184-168-86-185 /]# ls -la /var/named-chroot/etc/
total 48
drwxr-xr-x 2 root root 4096 Sep 21 15:43 .
drwxr-xr-x 6 root root 4096 Feb 1 2011 ..
-rw-r--r-- 1 root root 2819 May 6 02:53 localtime
-rw-r--r-- 1 root named 5572 Sep 21 12:55 named-turbopanel.conf
-rw-r----- 1 root named 1230 Dec 13 2010 named.caching-nameserver.conf
-rw-r--r-- 1 root named 821 Feb 1 2011 named.conf
-rw-r--r-- 1 root named 47 Feb 1 2011 named.conf.tpsave
-rw-r----- 1 root named 955 Dec 13 2010 named.rfc1912.zones

Okay, re-looking back, I thought that file error you posted was an output from messages.

For some reason, we are not getting any messages back from named back into the messages file.

do

service rsyslog restart

shutdown failed

12:17 AM

and then tail /var/log/messages

start ok

?

Ah, okay.

That was the output from rsyslog It wasn't running.

Now lets see what does /var/log/messages with

tail /var/log/messages

[root@ip-184-168-86-185 /]# tail /var/log/messages
2011-09-20T18:32:37.321006-07:00 ip-184-168-86-185 rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically generated config directives may interfer with your rsyslog.conf settings. We suggest upgrading your config and adding -c3 as the first rsyslogd option.
2011-09-20T18:32:37.322354-07:00 ip-184-168-86-185 rsyslogd: Warning: backward compatibility layer added to following directive to rsyslog.conf: ModLoad imuxsock
2011-09-21T11:38:21.437308-07:00 ip-184-168-86-185 shutdown[16303]: shutting down for system reboot

Alright, let's make sure that rsyslog is running with:

ps -ef | grep rsyslog

are you running centoss 5 or 6?

[root@ip-184-168-86-185 /]# ps -ef | grep rsyslog
root 3272 1 0 17:16 ? 00:00:00 /sbin/rsyslogd -m 0
root 3289 1927 0 17:18 pts/0 00:00:00 grep rsyslog

12:19 AM

Alright.

don't know, how can I check?

cat /etc/redhat-release

Anyway, looks like it is running now, so do a restart of named once again.

and then tail /var/log/messages

[root@ip-184-168-86-185 /]# tail /var/log/messages
Sep 21 17:16:51 ip-184-168-86-185 rsyslogd: WARNING: rsyslogd is running in compatibility mode. Automatically generated config directives may interfer with your rsyslog.conf settings. We suggest upgrading your config and adding -c3 as the first rsyslogd option.
Sep 21 17:16:51 ip-184-168-86-185 rsyslogd: Warning: backward compatibility layer added to following directive to rsyslog.conf: ModLoad imuxsock
Sep 21 17:20:09 ip-184-168-86-185 named[3363]: starting BIND 9.3.6-P1-RedHat-9.3.6-16.P1.el5 -u named -t /var/named-chroot

permission denied

Okay, we back to permissions.

Let me take a look to see what the permissions should be:

CentOS release 5.6 (Final) fyi

12:21 AM

can you do this:

Ah, excellent. That is my version of my DNS setup too.

ls -la /var | grep named

do this:

let's make sure that we have the right permissions on /var/named.

ls -la var/named

[root@ip-184-168-86-185 /]# ls -la /var/named
total 20
drwxr-x--- 5 root named 4096 Sep 21 14:40 .
drwxr-xr-x 22 root root 4096 Sep 21 14:39 ..
drwxr-x--- 5 root named 124 Sep 21 14:40 chroot
drwxrwx--- 2 named named 4096 Sep 21 14:40 data
lrwxrwxrwx 1 root named 45 Sep 21 14:40 localdomain.zone -> /var/named-chroot//var/named/localdomain.zone
lrwxrwxrwx 1 root named 43 Sep 21 14:40 localhost.zone -> /var/named-chroot//var/named/localhost.zone
lrwxrwxrwx 1 root named 44 Sep 21 14:40 named.broadcast -> /var/named-chroot//var/named/named.broadcast

Let's try giving reading permissions for other with:

chmod o+r /var/named

And then restart

If it doesn't work, do "tail /var/log/messages" and see what was the output again.

While we are at it, let's do:

ls -la /var/named-chroot/var/

[root@ip-184-168-86-185 /]# /sbin/service named restart
Stopping named: [ OK ]
Starting named: [FAILED]
[root@ip-184-168-86-185 /]# tail /var/log/messages
Sep 21 17:20:09 ip-184-168-86-185 named[3363]: using up to 4096 sockets
Sep 21 17:20:09 ip-184-168-86-185 named[3363]: loading configuration from '/etc/named.conf'
Sep 21 17:20:09 ip-184-168-86-185 named[3363]: /etc/named.conf:2: change directory to '/var/named' failed: permission denied

[root@ip-184-168-86-185 /]# ls -la /var/named-chroot/var/
total 16
drwxr-xr-x 4 root root 4096 Feb 1 2011 .
drwxr-xr-x 6 root root 4096 Feb 1 2011 ..
drwxr-x--- 3 root root 4096 Sep 21 12:54 named
drwxr-xr-x 4 root root 4096 Feb 1 2011 run
[root@ip-184-168-86-185 /]#

It like something or somebody is trying to restart the machine.

But at this point, its still a permissions problem.

And it looks like the ownership is wrong.

do:

chown named:named /var/named-chroot/var/named

Do

service rsyslog restart

and then

restart named

!!

[root@ip-184-168-86-185 /]# chown named:named /var/named-chroot/var/named
[root@ip-184-168-86-185 /]# /sbin/service named restart
Stopping named: [ OK ]
Starting named: [ OK ]

12:32 AM

Yay!!!!

Looks like the problem is gone. I might suggest that you reach out to your ISP, as it appears to be other issues with the VPS account.

Yeah I've had several permissions issues lately

not sure what started it

Can't thank you enough

No problem. Glad to be of help!

« first day last day (14 days later) »

Transcript for

Sep '1122

Discussion between Rilindo and stevether

Imported from a comment discussion on serverfault.com/question...

centos linux nameserver service

join this room
about this room

00:00

06:00

12:00

18:00

all times are UTC

site design / logo © 2024 Stack Exchange Inc; legal

mobile