RE: Keep log_in_vain Value
-Original Message- From: Bill Moran [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 2:59 PM To: Matt Cyber Dog LaPlante Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Keep log_in_vain Value Matt \Cyber Dog\ LaPlante [EMAIL PROTECTED] wrote: -Original Message- From: David Fuchs [mailto:[EMAIL PROTECTED] Matt Cyber Dog LaPlante wrote: Ah, grep saves the day again. It was being turned on in rc.network. Thanks. You sure it wasn't being turned on in rc.conf instead? Anything else would mean that someone was messing with rc.network or /etc/default/rc.conf, which really should be left alone. I'm positive...there is no log_in_vain entry in rc.conf. It only appears in rc.network, where both tcp and udp were set to 1. That's really strange ... is you rc.network customized? It really shouldn't be. The stock one only sets log_in_vain if /etc/rc.conf tells it to. -- Bill Moran Potential Technologies http://www.potentialtech.com Couldn't tell you, I didn't build this system. It got dumped on me when I took over a sysadmin job. I guess it's just another checkmark on my list of really strange things that have been done to this network. :) - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Keep log_in_vain Value
Right now on a FreeBSD 4.7 box, net.inet.tcp.log_in_vain and net.inet.udp.log_in_vain are both turned on. I know they can be disabled using sysctl, but this only fixes the problem until the machine is rebooted, at which point they both come back on. Due to our network configuration, it's constantly displaying blocked port 53 from one of the other servers, and I want UDP log_in_vain disabled permanently. Where can I do this in the configuration? Thanks. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Keep log_in_vain Value
-Original Message- From: Bill Moran [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 1:04 PM To: Matt Cyber Dog LaPlante Cc: [EMAIL PROTECTED] Subject: Re: Keep log_in_vain Value Matt \Cyber Dog\ LaPlante [EMAIL PROTECTED] wrote: Right now on a FreeBSD 4.7 box, net.inet.tcp.log_in_vain and net.inet.udp.log_in_vain are both turned on. I know they can be disabled using sysctl, but this only fixes the problem until the machine is rebooted, at which point they both come back on. Due to our network configuration, it's constantly displaying blocked port 53 from one of the other servers, and I want UDP log_in_vain disabled permanently. Where can I do this in the configuration? Thanks. /etc/sysctl.conf -- Bill Moran Potential Technologies http://www.potentialtech.com I already tried: == # $FreeBSD: src/etc/sysctl.conf,v 1.1.2.2 2001/12/19 17:52:17 ru Exp $ # # This file is read when going to multi-user and its contents piped thru # ``sysctl'' to adjust kernel values. ``man 5 sysctl.conf'' for details. # net.inet.udp.log_in_vain=0 == But that had no effect upon reboot: # sysctl -ae net.inet | grep vain net.inet.tcp.log_in_vain=1 net.inet.udp.log_in_vain=1 - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Keep log_in_vain Value
-Original Message- From: Chuck Swiger [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 1:22 PM To: Matt Cyber Dog LaPlante Cc: [EMAIL PROTECTED] Subject: Re: Keep log_in_vain Value Matt Cyber Dog LaPlante wrote: Right now on a FreeBSD 4.7 box, net.inet.tcp.log_in_vain and net.inet.udp.log_in_vain are both turned on. I know they can be disabled using sysctl, but this only fixes the problem until the machine is rebooted, at which point they both come back on. These default to off, so I would suggest you check /etc/sysctl.conf and see whether they are being turned on there, and then change that. :-) Otherwise, something like grep log_in_vain /etc/* might give a hint... -- -Chuck Ah, grep saves the day again. It was being turned on in rc.network. Thanks. - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Keep log_in_vain Value
-Original Message- From: David Fuchs [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 15, 2004 2:07 PM To: Matt Cyber Dog LaPlante Cc: [EMAIL PROTECTED] Subject: Re: Keep log_in_vain Value Matt Cyber Dog LaPlante wrote: Ah, grep saves the day again. It was being turned on in rc.network. Thanks. You sure it wasn't being turned on in rc.conf instead? Anything else would mean that someone was messing with rc.network or /etc/default/rc.conf, which really should be left alone. -- Thanks, -David Fuchs BCIS ([EMAIL PROTECTED]) WWW:http://www.davidfuchs.ca/ MSN:[EMAIL PROTECTED] PGP:http://www.davidfuchs.ca/aboutme/433EEC91.pgp I'm positive...there is no log_in_vain entry in rc.conf. It only appears in rc.network, where both tcp and udp were set to 1. - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 4.7 Syslogs
I tried the logger command, but it didn't reach the messages file (which is
still empty). Here is the output from the syslogd -d command:
syslogd: bind: Address already in use
logmsg: pri 53, flags 4, from , msg syslogd: bind: Address already in use
Logging to CONSOLE /dev/console
syslogd: bind: Address already in use
logmsg: pri 53, flags 4, from , msg syslogd: bind: Address already in use
Logging to CONSOLE /dev/console
can't open /dev/klog (16)
off running
init
cfline(local7.crit;local7.err;local7.notice
/var/log/purchasing, f, *, *)
cfline(local0.*/var/log/postgres,
f, *, *)
cfline(local2.*
/var/log/qmail/smtpd.log, f, *, *)
cfline(local3.*
/var/log/qmail/send, f, *, *)
cfline(local4.*
/var/log/qmail/masterlog, f, *, *)
cfline(authpriv.* /var/log/authpriv,
f, local0, *)
cfline(security.* /var/log/security,
f, local0, *)
cfline(mail.info /var/log/maillog,
f, local0, *)
cfline(lpr.info/var/log/lpd-errs,
f, local0, *)
cfline(cron.* /var/log/cron, f,
local0, *)
cfline(*.emerg *, f, local0,
*)
cfline(console.info
/var/log/console.log, f, local0, *)
X X X X X X X X X X X X X X X X X X X X X X X 5 X FILE: /var/log/purchasing
X X X X X X X X X X X X X X X X 8 X X X X X X X X FILE: /var/log/postgres
X X X X X X X X X X X X X X X X X X 8 X X X X X X FILE:
/var/log/qmail/smtpd.log
X X X X X X X X X X X X X X X X X X X 8 X X X X X FILE: /var/log/qmail/send
X X X X X X X X X X X X X X X X X X X X 8 X X X X FILE:
/var/log/qmail/masterlog
X X X X X X X X X X 8 X X X X X X X X X X X X X X FILE: /var/log/authpriv
(local0)
X X X X X X X X X X X X X 8 X X X X X X X X X X X FILE: /var/log/security
(local0)
X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog
(local0)
X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/log/lpd-errs
(local0)
X X X X X X X X X 8 X X X X X X X X X X X X X X X FILE: /var/log/cron
(local0)
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: (local0)
X X X X X X X X X X X X X X 6 X X X X X X X X X X FILE: /var/log/console.log
(local0)
logmsg: pri 56, flags 4, from compname, msg syslogd: restart
syslogd: restarted
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Matthew Seaman
Sent: Saturday, May 15, 2004 4:56 AM
To: Matt Cyber Dog LaPlante
Cc: [EMAIL PROTECTED]
Subject: Re: FreeBSD 4.7 Syslogs
On Sat, May 15, 2004 at 01:51:40AM -0400, Matt Cyber Dog LaPlante wrote:
I've inherited a FreeBSD 4.7 server as part of a system administration
job.
Recently I noticed that the syslog files had stopped collecting data.
This
includes /var/log/messages and /var/log/console among others. Up until
some
time last week, they'd been full of data, but after some unknown event,
all
data collection stopped. I did not build/configure the system, nor am I
very fluent in the ways of BSD, so I do not know where else to begin
looking
for answers. I ran the newsyslog program to regenerate all the log files.
It created them, with the single line stating a new log file was created,
but aside from that one line they remain empty. I tried manually
restarting
syslogd, as well as rebooting the whole machine, neither of which have had
any effect. I have not manually altered any syslog configuration info,
and
I basically have no idea what to try next. I'm a relative noob when it
comes to FreeBSD, so I'd appreciate answers in a simple format. Thanks in
advance...
Hmmm... that doesn't sound good. Can you use logger(1) to write a
test message into the log files?
% logger -p daemon.info -t TEST Some test message
which should appear in /var/log/messages. If it doesn't, look at
/etc/syslog.conf and verify that it is sensible. Then try killing
syslogd and starting it up in debug mode:
# syslogd -d {other syslog flags}
this will not daemonize itself or go into the background and will
print out various debugging information as log messages come in.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: FreeBSD 4.7 Syslogs
- S 0:00.03 syslogd -d 847 p0- I 0:00.03 syslogd -d 1214 p0- I 0:00.03 syslogd -dv 4530 p0 Is 0:00.03 -bash (bash) 4534 p0 S 0:00.05 su (bash) 4657 p0 R+ 0:00.00 ps ax 754 v0 Is+0:00.01 /usr/libexec/getty Pc ttyv0 241 v1 Is+0:00.01 /usr/libexec/getty Pc ttyv1 242 v2 Is+0:00.00 /usr/libexec/getty Pc ttyv2 243 v3 Is+0:00.01 /usr/libexec/getty Pc ttyv3 244 v4 Is+0:00.01 /usr/libexec/getty Pc ttyv4 245 v5 Is+0:00.00 /usr/libexec/getty Pc ttyv5 246 v6 Is+0:00.01 /usr/libexec/getty Pc ttyv6 247 v7 Is+0:00.00 /usr/libexec/getty Pc ttyv7 214 con- I 0:00.07 /usr/local/pgsql/bin/postmaster (postgres) 221 con- I 0:00.00 postmaster: stats buffer process(postgres) 222 con- I 0:00.00 postmaster: stats collector process(postgres) 231 con- S 0:00.39 /usr/local/bin/svscan /var/service 232 con- I 0:00.00 /usr/local/bin/readproctitle service errors: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JJB Sent: Saturday, May 15, 2004 4:04 PM To: Matt Cyber Dog LaPlante; 'Matthew Seaman'; [EMAIL PROTECTED] Subject: RE: FreeBSD 4.7 Syslogs Well since you are new to FBSD and since the syslogd -d commands shows that you do not have logging specified in /etc/syslog.conf for the messages file. You just do not know what you are looking at. Who ever was sysadmin before you probably commented it out for what ever reason. By the way I tried using the logger command on my 4.9 system and it did not write any messages at all. So it is no help in debugging this problem. I read the man logger info and as usual the man page is useless. Who ever writes those must work real hard at writing sentences that convey no meanings. To verify the conclusion that no logging is enabled for messages file, first do halt command, power off box, wait 1 minute, power back on to boot system, then, post the complete contents of these files. /var/run/dmesg.boot /etc/rc.conf /etc/syslog.conf /etc/newsylog.conf /etc/crontab The output of this command ls -l /var/log/* to see all the details about your log files. The output of this command ps ax -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Matt Cyber Dog LaPlante Sent: Saturday, May 15, 2004 1:34 PM To: 'Matthew Seaman'; [EMAIL PROTECTED] Subject: RE: FreeBSD 4.7 Syslogs I tried the logger command, but it didn't reach the messages file (which is still empty). Here is the output from the syslogd -d command: syslogd: bind: Address already in use logmsg: pri 53, flags 4, from , msg syslogd: bind: Address already in use Logging to CONSOLE /dev/console syslogd: bind: Address already in use logmsg: pri 53, flags 4, from , msg syslogd: bind: Address already in use Logging to CONSOLE /dev/console can't open /dev/klog (16) off running init cfline(local7.crit;local7.err;local7.notice /var/log/purchasing, f, *, *) cfline(local0.* /var/log/postgres, f, *, *) cfline(local2.* /var/log/qmail/smtpd.log, f, *, *) cfline(local3.* /var/log/qmail/send, f, *, *) cfline(local4.* /var/log/qmail/masterlog, f, *, *) cfline(authpriv.* /var/log/authpriv, f, local0, *) cfline(security.* /var/log/security, f, local0, *) cfline(mail.info /var/log/maillog, f, local0, *) cfline(lpr.info /var/log/lpd-errs, f, local0, *) cfline(cron.* /var/log/cron, f, local0, *) cfline(*.emerg *, f, local0, *) cfline(console.info /var/log/console.log, f, local0, *) X X X X X X X X X X X X X X X X X X X X X X X 5 X FILE: /var/log/purchasing X X X X X X X X X X X X X X X X 8 X X X X X X X X FILE: /var/log/postgres X X X X X X X X X X X X X X X X X X 8 X X X X X X FILE: /var/log/qmail/smtpd.log X X X X X X X X X X X X X X X X X X X 8 X X X X X FILE: /var/log/qmail/send X X X X X X X X X X X X X X X X X X X X 8 X X X X FILE: /var/log/qmail/masterlog X X X X X X X X X X 8 X X X X X X X X X X X X X X FILE: /var/log/authpriv (local0) X X X X X X X X X X X X X 8 X X X X X X X X X X X FILE: /var/log/security (local0) X X 6 X X X X X X X X X X X X X X X X X X X X X X FILE: /var/log/maillog (local0) X X X X X X 6 X X X X X X X X X X X X X X X X X X FILE: /var/log/lpd-errs (local0) X X X X X X X X X 8 X X X X X X X X X X X X X X X FILE: /var/log/cron (local0) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 X WALL: (local0) X X X X X X X X X X X X X X 6 X X X X X X X X X X FILE: /var/log/console.log (local0) logmsg: pri 56, flags 4, from compname, msg syslogd: restart syslogd: restarted -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthew Seaman Sent: Saturday, May 15, 2004 4:56 AM To: Matt Cyber Dog LaPlante Cc: [EMAIL PROTECTED] Subject: Re: FreeBSD 4.7 Syslogs On Sat, May 15, 2004 at 01:51:40AM -0400, Matt Cyber Dog LaPlante wrote: I've inherited a FreeBSD 4.7 server as part
FreeBSD 4.7 Syslogs
I've inherited a FreeBSD 4.7 server as part of a system administration job. Recently I noticed that the syslog files had stopped collecting data. This includes /var/log/messages and /var/log/console among others. Up until some time last week, they'd been full of data, but after some unknown event, all data collection stopped. I did not build/configure the system, nor am I very fluent in the ways of BSD, so I do not know where else to begin looking for answers. I ran the newsyslog program to regenerate all the log files. It created them, with the single line stating a new log file was created, but aside from that one line they remain empty. I tried manually restarting syslogd, as well as rebooting the whole machine, neither of which have had any effect. I have not manually altered any syslog configuration info, and I basically have no idea what to try next. I'm a relative noob when it comes to FreeBSD, so I'd appreciate answers in a simple format. Thanks in advance... - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
