Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
bind9 squeeze/oldstable
3 views
Skip to first unread message
george cox
May 18, 2013, 7:40:02 AM5/18/13
to
I haven't had a chance to upgrade this system yet.
I needed to update my bind configuration and now it will not start. In the past bind would write errors to the syslog (or messages file, i forget which), but it isn't doing so. Is there another way to get the error messages? All the info I get is a "failed" when trying to restart the daemon, but no clue as to what is causing the problem.
I noticed my syslog and messages files are totally empty, Going back a few version numbers there was always useful info there, but not any more. Is there a way to increase the level of logging?
I needed to update my bind configuration and now it will not start. In the past bind would write errors to the syslog (or messages file, i forget which), but it isn't doing so. Is there another way to get the error messages? All the info I get is a "failed" when trying to restart the daemon, but no clue as to what is causing the problem.
I noticed my syslog and messages files are totally empty, Going back a few version numbers there was always useful info there, but not any more. Is there a way to increase the level of logging?
george cox
May 18, 2013, 8:00:03 AM5/18/13
to
I found named-checkconf search-engining, and this found my bind syntax error, yeah!
Is there anything I can do about the logging issue? I was thinking of doing a dist-upgrade to wheezy on my server, but could the logging issue remain after the upgrade? Maybe I should just do a fresh install of wheezy instead? Any advice? Far as I know that messages and syslog not containing info (filesystem not full BTW) is the only problem.
Is there anything I can do about the logging issue? I was thinking of doing a dist-upgrade to wheezy on my server, but could the logging issue remain after the upgrade? Maybe I should just do a fresh install of wheezy instead? Any advice? Far as I know that messages and syslog not containing info (filesystem not full BTW) is the only problem.
----- Original Message -----
From: george cox
Sent: 05/18/13 07:25 AM
Subject: bind9 squeeze/oldstable
Joe
May 18, 2013, 8:40:01 AM5/18/13
to
On Sat, 18 May 2013 07:57:08 -0400
"george cox" <gc...@mail.com> wrote:
> I found named-checkconf search-engining, and this found my bind
> syntax error, yeah!
>
> Is there anything I can do about the logging issue? I was thinking of
> doing a dist-upgrade to wheezy on my server, but could the logging
> issue remain after the upgrade? Maybe I should just do a fresh
> install of wheezy instead? Any advice? Far as I know that messages
> and syslog not containing info (filesystem not full BTW) is the only
> problem.
No experience here, but my feeling is that a server upgrade should be
"george cox" <gc...@mail.com> wrote:
> I found named-checkconf search-engining, and this found my bind
> syntax error, yeah!
>
> Is there anything I can do about the logging issue? I was thinking of
> doing a dist-upgrade to wheezy on my server, but could the logging
> issue remain after the upgrade? Maybe I should just do a fresh
> install of wheezy instead? Any advice? Far as I know that messages
> and syslog not containing info (filesystem not full BTW) is the only
> problem.
approached in a state of great peace of mind, not in an attempt to
solve a problem. I wouldn't attempt it without getting the old system
running perfectly first. Especially logging.
Bind should also be logging as 'named' to daemon.log, by the way. But
the default logging seems oriented towards problems with name serving
rather than problems in bind itself. I've found Google/guesswork to be
more useful than the logs with bind.
But syslog should contain much more, cron and iptables at least should
leave logs here. If it is empty, I would start looking at syslogd,
bearing in mind there is more than one possible version, though they
should all log to the same place.
--
Joe
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20130518133...@jretrading.com
george cox
May 18, 2013, 9:00:02 AM5/18/13
to
I checked debug and it was empty too. I'll take a look at syslogd, I can't think of ever touching its config though.
I think that is sound advice about the upgrade. My thinking was perhaps debian in general or various package maintainers had decided to reduce the amount of message logging, but I think you are right saying that something has broken with syslog. My laptop is a fresh wheezy/stable and it has lots of useful stuff adding to the logs. I know the syslog issue has been that way for a long time on the system in question. I've had some issues in the past and noticed the logs were empty then too. Thanks.
----- Original Message -----
From: Joe
Sent: 05/18/13 08:31 AM
Subject: Re: bind9 squeeze/oldstable
0 new messages