CVSup and Building World
Earlier this evening I did a full CVSup on a FreeBSD 4.9 machine using RELENG_4, built and installed the kernel and world. My question is: are all the patches released since the last release came out included when I use CVSup? Or is it still necessary to patch the system after install? My guess is the CVSup will already include patches for known issues, but it's better safe than sorry so I'm asking anyway! Thanks. - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem Building World
-Original Message- From: Chris Hill [mailto:[EMAIL PROTECTED] Sent: Monday, November 15, 2004 6:49 PM To: Kevin D. Kinsey, DaleCo, S.P. Cc: Cyber Dog; [EMAIL PROTECTED] Subject: Re: Problem Building World On Mon, 15 Nov 2004, Kevin D. Kinsey, DaleCo, S.P. wrote: Cyber Dog wrote: Hello, I'm working with a server currently running FreeBSD 4.6. Clearly it hasn't been updated too recently, and I've made it my goal to bring it into the present. This would be my first time rebuilding a FreeBSD OS. I started out by clearing out /usr/src, and doing a fresh cvsup with the following supfile: snip [more snip] Stop in /usr/src. [EMAIL PROTECTED] src]# As you can see, something's amiss here. I don't understand why there would be any inconsistencies...as I said; I did a fresh CVSup (multiple times in fact). Any help would be greatly appreciated! - Matt Hi, Matt: I'm certainly not an expert here, but it seems like it's an awful long way from 4.6 to 4.10. Have you tried an intermediate update, say, 4.6 to 4.7 [or 4.8]? So many changes occur over time; and by the time 4.10 came out, 4.6 was very old*; so it's entirely possible that you might need to do a cvsup/buildworld routine to something a little closer to your box's date prior to attempting (and having any success) with 4.10. You might try changing the 'cvs tag' in your supfile to RELENG_4_7 or RELENG_4_8 and going again Kevin Kinsey *and probably past it's EOL. Whether or not, I'm sure it'd be nice if it _would_ build, but it's possible that the engineering team was under no compunction to test a migration from 4.6 directly to 4.10 at the time 4.10 was being tested for release, and therefore it wasn't (tested) ... like I said, I'm no expert, but a 'stepping stone' approach to the problem might work I did this exact upgrade (4.6 to 4.10) a while back, and I can endorse the 'stepping stone' procedure. I did a cvsup and rebuild from 4.6 to 4.7, 4.7 to 4.8, etc. until 4.10. It's tedious and time-consuming, but the whole thing went surprisingly smoothly. -- Chris Hill [EMAIL PROTECTED] ** [ Busy Expunging | ] I typo'd my original email, I'm starting with FreeBSD 4.7, not 6. Regardless, your suggestion made sense of stepping stoning the procedure... unfortunately I got the exact same results. I CVSup'd 4.6, cleared obj, and did a new build world. Same place, same error. - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Problem Building World
-Original Message- From: Kris Kennaway [mailto:[EMAIL PROTECTED] Sent: Monday, November 15, 2004 8:10 PM To: Chris Hill Cc: Kevin D. Kinsey, DaleCo, S.P.; Cyber Dog; freebsd- [EMAIL PROTECTED] Subject: Re: Problem Building World On Mon, Nov 15, 2004 at 06:49:22PM -0500, Chris Hill wrote: I did this exact upgrade (4.6 to 4.10) a while back, and I can endorse the 'stepping stone' procedure. I did a cvsup and rebuild from 4.6 to 4.7, 4.7 to 4.8, etc. until 4.10. It's tedious and time-consuming, but the whole thing went surprisingly smoothly. If you have access to the console, you can just avoid the hassle and do a binary upgrade from installation media. Kris This is true, of course. I do have access to the physical machine. The reason I'm hesitant is the research I've done on upgrading has turned up many recommendations that this is usually *not* the best way to go about an upgrade. As I've said, I've never done this before, so I don't know one way or another. Unfortunately this is a business machine, and I'm trying to take the course of least likely destruction. Massive downtime is not good. Of course, I'm making a full backup regardless. - Matt ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem Building World
Hello, I'm working with a server currently running FreeBSD 4.6. Clearly it hasn't been updated too recently, and I've made it my goal to bring it into the present. This would be my first time rebuilding a FreeBSD OS. I started out by clearing out /usr/src, and doing a fresh cvsup with the following supfile: # $FreeBSD: src/share/examples/cvsup/stable-supfile,v 1.19.2.4 2000/08/18 18:50:21 jkh Exp $ # Defaults that apply to all the collections # # IMPORTANT: Change the next line to use one of the CVSup mirror sites # listed at http://www.freebsd.org/handbook/mirrors.html. *default host=cvsup5.FreeBSD.org *default base=/usr *default prefix=/usr # The following line is for 4-stable. If you want 3-stable or 2.2-stable, # change RELENG_4 to RELENG_3 or RELENG_2_2 respectively. *default release=cvs tag=RELENG_4_10 *default delete use-rel-suffix # If your network link is a T1 or faster, comment out the following line. *default compress ## Main Source Tree. # # The easiest way to get the main source tree is to use the src-all # mega-collection. It includes all of the individual src-* collections. # Please note: If you want to track -STABLE, leave this uncommented. src-all ports-all tag=. As far as I can tell, all went well with that. I've been using the documentation at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html I cleared out /usr/obj as it describes. Then I cd /usr/src, and do a make buildworld. It churns along for awhile, but then we hit the problem area: === secure/lib/libcrypto ( echo #ifndef MK1MF_BUILD; echo /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */; echo #define CFLAGS \cc\; echo #define PLATFORM \`uname -s`-`uname -m`\; echo #define DATE \`LC_ALL=C date`\; echo #endif ) buildinf.h rm -f .depend mkdep -f .depend -a-I/usr/local/include -I/usr/local/lib -DTERMIOS -DANSI_SOURCE -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/engine -I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cpt_err.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cryptlib.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/ebcdic.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/ex_data.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/mem.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/mem_clr.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/mem_dbg.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/o_time.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/tmdiff.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/uid.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/aes/aes_cbc.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/aes/aes_cfb.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/aes/aes_core.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/aes/aes_ctr.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/aes/aes_ecb.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/aes/aes_misc.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/aes/aes_ofb.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_bitstr.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_bool.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_bytes.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_d2i_fp.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_digest.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_dup.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_enum.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_gentm.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_hdr.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_i2d_fp.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_int.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_mbstr.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_meth.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_object.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_octet.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_print.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_set.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_sign.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_strex.c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/asn1/a_strnid.c
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
Well, I guess we'll have to chalk this one up to forces of nature. I replaced the old syslog.conf with: # $FreeBSD: src/etc/syslog.conf,v 1.13.2.2 2001/02/26 09:26:11 phk Exp $ # # Spaces are NOT valid field separators in this file. # Consult the syslog.conf(5) manpage. # Purchasing database syslog local7.notice/var/log/purchasing # Postgres syslog local0.*/var/log/postgres local2.*/var/log/qmail/smtpd.log local3.*/var/log/qmail/send local4.*/var/log/qmail/masterlog *.err;kern.debug;mail.crit /dev/console *.notice;kern.debug;lpr.info;mail.crit /var/log/messages authpriv.* /var/log/authpriv security.* /var/log/security mail.info /var/log/maillog lpr.info/var/log/lpd-errs cron.* /var/log/cron *.emerg * # uncomment this to log all writes to /dev/console to /var/log/console.log console.info/var/log/console.log ...and low and behold the logs started working. As you said, it doesn't seem like it should have made a difference...but something changed. I still can't explain why it broke in the first place, but what's most important is that it started working again. Your explanation was extremely helpful, and I'm very appreciative. It's very admirable that you give of your time to help out complete strangers. If you have a PayPal account, I wouldn't mind sending over a little token of my appreciation. Thanks again, Matt -Original Message- From: JJB [mailto:[EMAIL PROTECTED] Sent: Saturday, May 15, 2004 10:42 PM To: Matt Cyber Dog LaPlante Subject: RE: FreeBSD 4.7 Syslogs Matt. You did not reboot system before you captured the requested data, but that is ok. I will write this reply in an teaching manner, so don't think I am talking down to you. The command ps ax displays all the tasks running on your system. 843 p0- S 0:00.03 syslogd -d 847 p0- I 0:00.03 syslogd -d 1214 p0- I 0:00.03 syslogd -dv from your posted data for ps ax display the above says you have 3 tasks running syslogd in debug mode. An reboot will get rid of this or you can kill the tasks by using the task number ie 843 for example. Enter on the command line killall 843 to kill that task then do ps ax to see that it's gone, then do same for the other 2 numbers 847 1214 *** Now lets cover how syslogs are defined and the control of auto rotate. This is very poorly described in man syslog and man newsyslog. The command man is the command for display to console the manual. So man newsyslog would display to the console screen the manual documentation for the newsyslog command. Be for warned the man documentation is very poorly written and conveys very little useful info. I will focus on the messages log file as an example to explain what is happening, but same process applies to all log files defined in /ect/syslog.conf. In FBSD all messages to syslog uses 2 elements to define the message, the facility and message level. In syslog.conf the left side on the line is the facility.level. The level describes the severity of the message, and is a keyword from the following ordered list (higher to lower): emerg, alert, crit, err, warning, notice, info and debug. Coding *.notice means all messages emerg through notice. With that info, looking at your syslog.conf it is obvious there are coding problems with some of the files, but nothing that would cause an log file not to work. As general rule messages file is reserved for FBSD system messages not application messages which have their own log files. Local0 and local7 should not be going to messages file as they have their own log files. !local0.*;!local7.*;*.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages this should be re-written as *.notice;kern.debug;lpr.info;mail.crit /var/log/messages !local0.*;*.err;kern.debug;auth.notice;mail.crit /dev/console !local0.*;*.notice;news.err /dev/console !local0.*;*.alert /dev/console This is an real mess, should be re-written as *.err;kern.debug;mail.crit/dev/console I did not see an news group server enabled in rc.conf so news.err is not necessary. You will only see these console messages when you are logged in as root, they are not saved in between logins. This local7.crit;local7.err;local7.notice/var/log/purchasing should be this local7.notice/var/log/purchasing as all the higher message levers are included, does the same thing as the original statement
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]
