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 To: debian-user@lists.debian.org Subject: Re: bind9 squeeze/oldstable
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 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 use ful 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-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130518133104.3be97...@jretrading.com
