From owner-freebsd-questions Wed May 29 11:16:14 2002 Delivered-To: freebsd-questions@freebsd.org Received: from sage-one.net (adsl-65-71-135-137.dsl.crchtx.swbell.net [65.71.135.137]) by hub.freebsd.org (Postfix) with ESMTP id 490F737B403 for ; Wed, 29 May 2002 11:16:09 -0700 (PDT) Received: from SAGEONE (sageone [192.168.0.5]) by sage-one.net (8.11.6/8.11.6) with SMTP id g4TIFu800606; Wed, 29 May 2002 13:16:01 -0500 (CDT) (envelope-from jackstone@sage-one.net) Message-Id: <3.0.5.32.20020529131555.01c02c38@mail.sage-one.net> X-Sender: jackstone@mail.sage-one.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 29 May 2002 13:15:55 -0500 To: Kent Stewart From: "Jack L. Stone" Subject: Re: Logs stopped Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <3CF51648.6000402@owt.com> References: <3.0.5.32.20020529122854.03a78220@mail.sage-one.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:56 AM 5.29.2002 -0700, Kent Stewart wrote: > > >Jack L. Stone wrote: > >> Using FBSD 4.5-RELEASE >> >> About an hour ago, several of my critical logs stopped... messages, >> security and FTPD. I've tried resetting the logs by trimming with the usual >> newsyslog. That didn't work Then restarted/rehashed syslog and still >> nothing logged... >> >> What is likely to have caused this....???? I don't really want to reboot.... > > >Make sure you have a proper line feed at the EOF. I had a + left over >from when I copied the text instead of letting mergemaster merge the >fixes. The last character in /etc/newsyslog.conf was a left over + and >it would not log. > >Kent > > >> >> .... our website: http://www.sage-one.net/ >> >> Best regards, >> >> Jack L. Stone >> Server Admin >-- >Kent Stewart >Richland, WA Kent: Thanks for the tip, but I don't think I have that problem. I haven't messed with the newsyslog.conf file for a while and all logs have been working fine untial an hour ago. In fact, all of the logs didn't stop, just those three.... maillog for instance was still chugging along. very strange.... it is possible that some of the trimming all hit at once and did something, but I thought the rehash of the syslog would take care of it.... I monitor my logs constantly and especially those that quit. So, dadblast it, I rebooted and now all works again.... this is a production box with pretty heavy web traffic, so reboots... not very polite thing to do..... .... our website: http://www.sage-one.net/ Best regards, Jack L. Stone Server Admin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message