Re: /var/log/messages filling up with DHCPDISCOVER messages
On Monday 08 October 2007 16:24:22 Jeff Royle wrote: Stephen Allen wrote: /usr/local/etc/dhcpd.conf is configured with log-facility local7; and /etc/syslog.conf is also configured with local7.* /var/log/dhcpd.log However, /var/log/messages is filling up with DHCPDISCOVER / no free leases messages for those clients that are unknown to the DHCP server (eg. on a different subnet). I suspect that these messages are being caught by *.notice which is why they end up in /var/log/messages. Is there a way to prevent this happening? You could try filtering them out of syslog like so (in your syslogd.conf): local7.!=notice /var/log/dhcpd.log Which should log everything for local7 except notice. See man syslog.conf(5) Almost correct but he doesn't want /var/log/messages filling up, so add local7.none to the line that points to /var/log/messages, ie: --- /etc/syslog.conf2007-09-20 09:22:55.0 -0800 +++ /etc/syslog.conf.dhcpd 2007-10-09 14:32:18.0 -0800 @@ -6,7 +6,7 @@ # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit /dev/console -*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages +*.notice;local7.none;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info/var/log/auth.log mail.info /var/log/maillog -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /var/log/messages filling up with DHCPDISCOVER messages
Thanks to both of you... I'd already sussed out and used what Mel suggested, but I've learnt for the future, from Jeff's suggestion. It all makes sense going back through the man pages, when you get a couple of examples explained to you. Many thanks, Steve ;) -- Mel wrote: On Monday 08 October 2007 16:24:22 Jeff Royle wrote: Stephen Allen wrote: /usr/local/etc/dhcpd.conf is configured with log-facility local7; and /etc/syslog.conf is also configured with local7.* /var/log/dhcpd.log However, /var/log/messages is filling up with DHCPDISCOVER / no free leases messages for those clients that are unknown to the DHCP server (eg. on a different subnet). I suspect that these messages are being caught by *.notice which is why they end up in /var/log/messages. Is there a way to prevent this happening? You could try filtering them out of syslog like so (in your syslogd.conf): local7.!=notice /var/log/dhcpd.log Which should log everything for local7 except notice. See man syslog.conf(5) Almost correct but he doesn't want /var/log/messages filling up, so add local7.none to the line that points to /var/log/messages, ie: --- /etc/syslog.conf2007-09-20 09:22:55.0 -0800 +++ /etc/syslog.conf.dhcpd 2007-10-09 14:32:18.0 -0800 @@ -6,7 +6,7 @@ # may want to use only tabs as field separators here. # Consult the syslog.conf(5) manpage. *.err;kern.warning;auth.notice;mail.crit /dev/console -*.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages +*.notice;local7.none;authpriv.none;kern.debug;lpr.info;mail.crit;news.err /var/log/messages security.* /var/log/security auth.info;authpriv.info/var/log/auth.log mail.info /var/log/maillog ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /var/log/messages filling up with DHCPDISCOVER messages
Stephen Allen wrote: /usr/local/etc/dhcpd.conf is configured with log-facility local7; and /etc/syslog.conf is also configured with local7.* /var/log/dhcpd.log However, /var/log/messages is filling up with DHCPDISCOVER / no free leases messages for those clients that are unknown to the DHCP server (eg. on a different subnet). I suspect that these messages are being caught by *.notice which is why they end up in /var/log/messages. Is there a way to prevent this happening? You could try filtering them out of syslog like so (in your syslogd.conf): local7.!=notice /var/log/dhcpd.log Which should log everything for local7 except notice. See man syslog.conf(5) Cheers, Jeff Royle lists dot qwirky dot net ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/var/log/messages filling up with DHCPDISCOVER messages
/usr/local/etc/dhcpd.conf is configured with log-facility local7; and /etc/syslog.conf is also configured with local7.* /var/log/dhcpd.log However, /var/log/messages is filling up with DHCPDISCOVER / no free leases messages for those clients that are unknown to the DHCP server (eg. on a different subnet). I suspect that these messages are being caught by *.notice which is why they end up in /var/log/messages. Is there a way to prevent this happening? Many thanks, Steve ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filling up UDP socket buffers like mad
On Fri, Mar 24, 2006 at 06:03:47PM -0500, Charles Swiger wrote: On Mar 24, 2006, at 4:17 PM, Michael W. Lucas wrote: Running FreeBSD 6.1-PRERELEASE as a DNS, dhcp, and syslog server. I'm having trouble with DNS, DHCP, and syslogd locking up, and I think I've found what they all share in common. During the lockups, the box starts dropping UDP due to full socket buffers. I have a dumb little script to capture the rate of drops over 5 seconds, and it's about 45 a second. 168725 dropped due to full socket buffers 168958 dropped due to full socket buffers There is generally a cause behind the socket buffers filling up, whether that is some form of livelock due to an OS problem or a misconfiguration with a firewall/dummynet setup. You could look at the output of netstat -a(n) for insight as to where the packets are being queued up, but netstat -s would be useful to show to us as well. Thanks. I think you've shown me how to find the problem: # netstat -na ... udp4 0 0 127.0.0.1.57058127.0.0.1.53 udp4 0 0 127.0.0.1.61259127.0.0.1.53 udp4 0 0 127.0.0.1.54240127.0.0.1.53 udp4 0 0 127.0.0.1.52997127.0.0.1.53 udp4 0 0 *.67 *.* udp4 43414 0 *.514 *.* udp4 0 0 *.49661*.* ... We have no firewall on this machine; it's buried behind three layers of firewall. I've tried running syslogd in debug mode, but not found anything particularly useful yet. Syslogd is now set to restart every 15 minutes, and run in debug mode, so hopefully the next time this happens I'll have the debugging output. The problem happens even within fifteen minutes, but because of my timeouts nobody notices. I'm attaching the output of netstat -na and netstat -s for general informative purposes; if anyone has any further suggestions, I'm all ears. Thanks, ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ The cloak of anonymity protects me from the nuisance of caring. -Non Sequitur Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) tcp4 96 0 10.184.1.11.53 10.184.1.8.49838 ESTABLISHED tcp4 104 0 10.184.1.11.53 10.184.1.8.61719 ESTABLISHED tcp4 0 0 127.0.0.1.6011 *.*LISTEN tcp4 0 48 10.184.1.11.22 10.184.184.108.52392 ESTABLISHED tcp4 0 0 127.0.0.1.6010 *.*LISTEN tcp4 0 0 10.184.1.11.22 10.184.184.108.64567 ESTABLISHED tcp4 0 0 *.199 *.*LISTEN tcp4 0 0 *.80 *.*LISTEN tcp4 0 0 127.0.0.1.25 *.*LISTEN tcp4 0 0 *.22 *.*LISTEN tcp4 0 0 127.0.0.1.953 *.*LISTEN tcp4 0 0 127.0.0.1.53 *.*LISTEN tcp4 0 0 10.184.3.248.53*.*LISTEN tcp4 0 0 10.184.1.11.53 *.*LISTEN udp4 0 0 127.0.0.1.59578127.0.0.1.53 udp4 0 0 127.0.0.1.57058127.0.0.1.53 udp4 0 0 127.0.0.1.61259127.0.0.1.53 udp4 0 0 127.0.0.1.54240127.0.0.1.53 udp4 0 0 127.0.0.1.52997127.0.0.1.53 udp4 0 0 *.67 *.* udp4 43414 0 *.514 *.* udp4 0 0 *.49661*.* udp4 0 0 *.52767*.* udp4 0 0 *.63357*.* udp4 0 0 127.0.0.1.58915127.0.0.1.5680 udp4 0 0 127.0.0.1.62275127.0.0.1.5679 udp4 0 0 127.0.0.1.57431127.0.0.1.5678 udp4 0 0 *.63077*.* udp4 0 0 *.161 *.* udp4 0 0 *.57589*.* udp4 0 0 *.5681 *.* udp4 0 0 127.0.0.1.5680 *.* udp4 0 0 127.0.0.1.5679 *.* udp4 0 0 127.0.0.1.5678 *.* udp4 0 0 *.64486*.* udp4 0 0 *.53558*.* udp4 0 0 127.0.0.1.123 *.* udp4 0
Re: filling up UDP socket buffers like mad
Michael W. Lucas wrote: On Fri, Mar 24, 2006 at 06:03:47PM -0500, Charles Swiger wrote: [ ... ] udp4 43414 0 *.514 *.* udp4 0 0 *.49661*.* ... We have no firewall on this machine; it's buried behind three layers of firewall. Heh. :-) Well, it's pretty clear that the syslog traffic isn't being drained by the syslog daemon properly. I've seen syslogd get stuck like that if it was forwarding logs to another host specified by name and not IP, and it was having problems resolving it. [ I've got a MacOS X 10.2(.9?) machine where syslogd is frozen upon boot now due to using a non-local hostname to forward one specific type of traffic elsewhere, so I have to kill -9 it and restart it by hand once the resolver has gotten going, if I reboot that machine. ] -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filling up UDP socket buffers like mad
Michael, On 3/27/06, Michael W. Lucas [EMAIL PROTECTED] wrote: # netstat -na udp4 43414 0 *.514 *.* That's a big queue. I'm attaching the output of netstat -na and netstat -s for general informative purposes; if anyone has any further suggestions, I'm all ears. Try running syslogd with -n. Thanks, ==ml Frem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filling up UDP socket buffers like mad
On Mon, Mar 27, 2006 at 10:22:18AM -0500, Chuck Swiger wrote: Michael W. Lucas wrote: On Fri, Mar 24, 2006 at 06:03:47PM -0500, Charles Swiger wrote: [ ... ] udp4 43414 0 *.514 *.* udp4 0 0 *.49661*.* ... We have no firewall on this machine; it's buried behind three layers of firewall. Heh. :-) Well, it's pretty clear that the syslog traffic isn't being drained by the syslog daemon properly. I've seen syslogd get stuck like that if it was forwarding logs to another host specified by name and not IP, and it was having problems resolving it. This *is* the loghost other hosts are forwarding their logs to. So, I'm pretty sure that's not it. :-) ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ The cloak of anonymity protects me from the nuisance of caring. -Non Sequitur ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filling up UDP socket buffers like mad
On Mon, Mar 27, 2006 at 04:29:31PM +0100, Freminlins wrote: Michael, On 3/27/06, Michael W. Lucas [EMAIL PROTECTED] wrote: # netstat -na udp4 43414 0 *.514 *.* That's a big queue. Yep. Mine is bigger than yours. :-) I'm attaching the output of netstat -na and netstat -s for general informative purposes; if anyone has any further suggestions, I'm all ears. Try running syslogd with -n. Trying now, thanks! I'm also going to drop a line on hackers@, see if anyone over there is interested in syslogd problems. Thanks to everyone for the help. ==ml -- Michael W. Lucas[EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ The cloak of anonymity protects me from the nuisance of caring. -Non Sequitur ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filling up UDP socket buffers like mad
Could it be that you're under a DOS attack even though you're behind three layers of firewall? =/ Try configuring a firewall to block every UDP packet for every port except those needed by the services you run. On 3/27/06, Michael W. Lucas [EMAIL PROTECTED] wrote: On Fri, Mar 24, 2006 at 06:03:47PM -0500, Charles Swiger wrote: On Mar 24, 2006, at 4:17 PM, Michael W. Lucas wrote: Running FreeBSD 6.1-PRERELEASE as a DNS, dhcp, and syslog server. I'm having trouble with DNS, DHCP, and syslogd locking up, and I think I've found what they all share in common. During the lockups, the box starts dropping UDP due to full socket buffers. I have a dumb little script to capture the rate of drops over 5 seconds, and it's about 45 a second. 168725 dropped due to full socket buffers 168958 dropped due to full socket buffers There is generally a cause behind the socket buffers filling up, whether that is some form of livelock due to an OS problem or a misconfiguration with a firewall/dummynet setup. You could look at the output of netstat -a(n) for insight as to where the packets are being queued up, but netstat -s would be useful to show to us as well. Thanks. I think you've shown me how to find the problem: # netstat -na ... udp4 0 0 127.0.0.1.57058127.0.0.1.53 udp4 0 0 127.0.0.1.61259127.0.0.1.53 udp4 0 0 127.0.0.1.54240127.0.0.1.53 udp4 0 0 127.0.0.1.52997127.0.0.1.53 udp4 0 0 *.67 *.* udp4 43414 0 *.514 *.* udp4 0 0 *.49661*.* ... We have no firewall on this machine; it's buried behind three layers of firewall. I've tried running syslogd in debug mode, but not found anything particularly useful yet. Syslogd is now set to restart every 15 minutes, and run in debug mode, so hopefully the next time this happens I'll have the debugging output. The problem happens even within fifteen minutes, but because of my timeouts nobody notices. I'm attaching the output of netstat -na and netstat -s for general informative purposes; if anyone has any further suggestions, I'm all ears. Thanks, ==ml -- Michael W. Lucas [EMAIL PROTECTED], [EMAIL PROTECTED] http://www.BlackHelicopters.org/~mwlucas/ The cloak of anonymity protects me from the nuisance of caring. -Non Sequitur -- []'s, Luiz Eduardo ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filling up UDP socket buffers like mad
On Mar 24, 2006, at 4:17 PM, Michael W. Lucas wrote: Running FreeBSD 6.1-PRERELEASE as a DNS, dhcp, and syslog server. I'm having trouble with DNS, DHCP, and syslogd locking up, and I think I've found what they all share in common. During the lockups, the box starts dropping UDP due to full socket buffers. I have a dumb little script to capture the rate of drops over 5 seconds, and it's about 45 a second. 168725 dropped due to full socket buffers 168958 dropped due to full socket buffers There is generally a cause behind the socket buffers filling up, whether that is some form of livelock due to an OS problem or a misconfiguration with a firewall/dummynet setup. You could look at the output of netstat -a(n) for insight as to where the packets are being queued up, but netstat -s would be useful to show to us as well. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: filling up UDP socket buffers like mad
Michael W. Lucas wrote: Hi, Running FreeBSD 6.1-PRERELEASE as a DNS, dhcp, and syslog server. I'm having trouble with DNS, DHCP, and syslogd locking up, and I think I've found what they all share in common. During the lockups, the box starts dropping UDP due to full socket buffers. I have a dumb little script to capture the rate of drops over 5 seconds, and it's about 45 a second. 168725 dropped due to full socket buffers 168958 dropped due to full socket buffers Right now, named and syslogd are in cron to restart every 15 minutes. Once they restart, everything works fine. Immediately after the reload, the UDP drops cease. The script reveals no change in the number of drops... for a few minutes. I've turned kern.ipc.maxsockbuf to increase the number of UDP buffers, which Google tells me is correct. Mind you, I'd previously tuned it to 8388608. I've now doubled that again, to 16777216. I really don't want to just keep doubling this resource when something happens. The best thing to do here is to identify what's using all these sockets, but I'm stumped on how to do that. My bowels tell me it's syslogd, because that's the program that is most resistant to restarting, but that's a pretty crappy reason. Any thoughts? Thanks, ==ml Have you run netstat to determine what the culprit is? Try running netstat -f inet | grep udp | less; this will print out everything with a udp socket to a buffered screen, and maybe you can find out one of the socket file descriptors, then take lsof, for instance, and find out what the program/service is that is causing the issue with your system. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
clientmqueue filling up
I've turned off all my sendmail options, IIRC, but /var/spool/clientmqueue keeps getting filled up with messages about undelivered mail. How can I stop this? NOTE: Please CC me, as I am not currently subscribed. Thanks. jm -- My other computer is your windows box. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: clientmqueue filling up
On Sat, Feb 21, 2004 at 12:20:19PM +, Jonathon McKitrick wrote: I've turned off all my sendmail options, IIRC, but /var/spool/clientmqueue keeps getting filled up with messages about undelivered mail. How can I stop this? NOTE: Please CC me, as I am not currently subscribed. Thanks. Are there any sendmail processes running? If you've got: sendmail_enable=NONE in /etc/rc.conf no sendmail processes should be started at reboot. However, this doesn't prevent processes attempting to send e-mail by piping messages into the standard input of /usr/sbin/sendmail -- which will result in the messages being queued up in /var/spool/clientmqueue as you've discovered. What processes try and do this? Two contenders I can think of immediately are the periodic(8) scripts, and cron(8). To stop the periodic scripts sending e-mail, you need to tell the scripts to log their output to a file rather than e-mailing it to root. Do that by adding: daily_output=/var/log/daily.log weekly_output=/var/log/weekly.log monthly_output=/var/log/monthly.log to /etc/periodic.conf -- just create that file if it doesn't already exist. See /etc/defaults/periodic.conf for other options you can use there. You can, of course, choose whatever log files you prefer, but the files shown above are already set up for automatic log cycling in /etc/newsyslog.conf To prevent cron(8) sending e-mails, you simply need to set the MAILTO variable to an empty value in all of the various crontabs (/var/cron/tabs/*, /etc/crontab). Just add the line MAILTO= near the top of the various crontab files -- for best results, use the command 'crontab -e' to edit the stuff under /var/cron/tabs. There's possibly other commands that try and send e-mail, but I can't think of any right now. You should be able to work out what they are by inspecting the files that end up in /var/spool/clientmqueue. 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 pgp0.pgp Description: PGP signature
/ is filling up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hiya everyone. Using 5.2-REL, what could be filling up my / directory? Any ideas? - -- Best regards, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFADqs/D5P/gMAbw2MRAsctAJ46ism5zMJiL3TVB2itJ2RzaxyAHwCfeZfn Gpd6pwf4XMI65j96X+748Xs= =h7x5 -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: / is filling up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 21 January 2004 10:39 am, Chris wrote: Hiya everyone. Using 5.2-REL, what could be filling up my / directory? Any ideas? Negate this. Seems colortail cored in /root - Jeesh!!! - -- Best regards, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFADq25D5P/gMAbw2MRAkvOAJsEUoRZ8yYHGO9f6KzQpSfQ3Y55zwCeLhve ySP2k3fPOnWHQYZc8DBlaNA= =Tv1+ -END PGP SIGNATURE- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient filling up my logfile. Help needed. Solved
On Monday 14 July 2003 00.47, Lowell Gilbert wrote: Hasse [EMAIL PROTECTED] writes: I'm very satisfied with this way to solve it, cause I won't miss any important loginfo. Keep in mind that you *have* potentially removed some other messages from the log. What I will probably do eventually is create a periodic(8) script to check for this (probably with grep -v dhclient), but I haven't gotten around to it yet. ___ Thx again. When times come, I'll have a look into that too. But for now, I'm happy as is. :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient filling up my logfile. Help needed. Solved
On Sunday 13 July 2003 15.35, Lowell Gilbert wrote: Hasse [EMAIL PROTECTED] writes: Running FreeBSD 4.8, all files are up to date, cvsuped yesterday, and I'm connected to the net via ADSL. Dynamic IP, but hardly ever change. dhclient is filling up my /var/log/messages. Every 10th minute it makes a new request and logging it. That's a pretty annoying ISP you've got there. I've tried to request a longer lease time in my dhclient.conf without any luck, and I've tried to get it to log to another logfile named dhclient, resulting in it logging to two files. dhclient and /var/log/messages. Yep, that's what the !dhclient syntax is for... I've tried to talk to my ISP about this problem, without any luck. I think most of the computers connected to this network are win-boxes, and they don't seem to have this problem. ( Don't log this kind of info ) Right. The ISP is trying to be able to make major changes to their network without needing to plan ahead for it. How can I keep the program from logging all this info ? Not really a problem, but very annoying. What I did was to put all of the user.notice messages into a separate file from the main log. *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err;user.warning /var/log/messages user.notice /var/log/user.messages Remember to create user.messages first, and to set up some log rotation for it. ___ Thx a lot Lowell. That did the trick. I've been reading man-pages and googling to my eyes was bleeding, but couldn't get this one to play along. Found the same problem in the FreeBSD mailarchive, searching for dhclient too verbose , but no solution. I'm very satisfied with this way to solve it, cause I won't miss any important loginfo. Best regards Geir Svalland. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient filling up my logfile. Help needed. Solved
Hasse [EMAIL PROTECTED] writes: I'm very satisfied with this way to solve it, cause I won't miss any important loginfo. Keep in mind that you *have* potentially removed some other messages from the log. What I will probably do eventually is create a periodic(8) script to check for this (probably with grep -v dhclient), but I haven't gotten around to it yet. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient filling up my logfile. Help needed.
Hasse [EMAIL PROTECTED] writes: Running FreeBSD 4.8, all files are up to date, cvsuped yesterday, and I'm connected to the net via ADSL. Dynamic IP, but hardly ever change. dhclient is filling up my /var/log/messages. Every 10th minute it makes a new request and logging it. That's a pretty annoying ISP you've got there. I've tried to request a longer lease time in my dhclient.conf without any luck, and I've tried to get it to log to another logfile named dhclient, resulting in it logging to two files. dhclient and /var/log/messages. Yep, that's what the !dhclient syntax is for... I've tried to talk to my ISP about this problem, without any luck. I think most of the computers connected to this network are win-boxes, and they don't seem to have this problem. ( Don't log this kind of info ) Right. The ISP is trying to be able to make major changes to their network without needing to plan ahead for it. How can I keep the program from logging all this info ? Not really a problem, but very annoying. What I did was to put all of the user.notice messages into a separate file from the main log. *.notice;authpriv.none;kern.debug;lpr.info;mail.crit;news.err;user.warning /var/log/messages user.notice /var/log/user.messages Remember to create user.messages first, and to set up some log rotation for it. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
dhclient filling up my logfile. Help needed.
Hi everybody.
Need help.
Running FreeBSD 4.8, all files are up to date, cvsuped yesterday, and I'm
connected to the net via ADSL. Dynamic IP, but hardly ever change.
dhclient is filling up my /var/log/messages.
Every 10th minute it makes a new request and logging it.
I've tried to request a longer lease time in my dhclient.conf without any
luck, and I've tried to get it to log to another logfile named dhclient,
resulting in it logging to two files. dhclient and /var/log/messages.
I've tried to talk to my ISP about this problem, without any luck.
I think most of the computers connected to this network are win-boxes,
and they don't seem to have this problem. ( Don't log this kind of info )
How can I keep the program from logging all this info ?
Not really a problem, but very annoying.
snip from /var/log/messages
Jul 10 20:03:26 odin dhclient: DHCPREQUEST on xl0 to 10.0.113.1 port 67
Jul 10 20:03:26 odin dhclient: DHCPACK from 10.0.113.1
Jul 10 20:03:26 odin dhclient: New Network Number: 217.209.211.0
Jul 10 20:03:26 odin dhclient: New Network Number: 217.209.211.0
Jul 10 20:03:26 odin dhclient: New Broadcast Address: 217.209.211.255
Jul 10 20:03:26 odin dhclient: New Broadcast Address: 217.209.211.255
Jul 10 20:03:26 odin dhclient: bound to 217.209.211.129 -- renewal in 542
seconds.
Jul 10 20:12:28 odin dhclient: DHCPREQUEST on xl0 to 10.0.113.1 port 67
Jul 10 20:12:28 odin dhclient: DHCPACK from 10.0.113.1
Jul 10 20:12:28 odin dhclient: New Network Number: 217.209.211.0
Jul 10 20:12:28 odin dhclient: New Network Number: 217.209.211.0
Jul 10 20:12:28 odin dhclient: New Broadcast Address: 217.209.211.255
Jul 10 20:12:28 odin dhclient: New Broadcast Address: 217.209.211.255
Jul 10 20:12:28 odin dhclient: bound to 217.209.211.129 -- renewal in 495
seconds.
/snip
My dhclient.conf :
timeout 60;
retry 60;
reboot 10;
select-timeout 5;
initial-interval 2;
script /sbin/dhclient-script;
media -link0 -link1 -link2, link0 link1;
send host-name odin.swedehost.com;
send dhcp-client-identifier 00:01:02:f7:7d:e8;
send dhcp-lease-time 7200;
supersede domain-name swedehost.com;
prepend domain-name-servers 127.0.0.1;
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, host-name;
require subnet-mask, domain-name-servers;
My /var/db/dhclient.leases :
lease {
interface xl0;
fixed-address 217.209.211.129;
medium -link0 -link1 -link2;
option subnet-mask 255.255.255.0;
option time-offset 3600;
option routers 217.209.211.1;
option dhcp-lease-time 1200;
option dhcp-message-type 5;
option domain-name-servers 127.0.0.1,10.0.0.1,10.0.0.2;
option dhcp-server-identifier 10.0.113.1;
option broadcast-address 217.209.211.255;
option domain-name swedehost.com;
renew 4 2003/7/10 18:12:28;
rebind 4 2003/7/10 18:20:56;
expire 4 2003/7/10 18:23:26;
}
lease {
interface xl0;
fixed-address 217.209.211.129;
medium -link0 -link1 -link2;
option subnet-mask 255.255.255.0;
option time-offset 3600;
option routers 217.209.211.1;
option dhcp-lease-time 1200;
option dhcp-message-type 5;
option domain-name-servers 127.0.0.1,10.0.0.1,10.0.0.2;
option dhcp-server-identifier 10.0.113.1;
option broadcast-address 217.209.211.255;
option domain-name swedehost.com;
renew 4 2003/7/10 18:20:43;
rebind 4 2003/7/10 18:29:58;
expire 4 2003/7/10 18:32:28;
}
Regards
Geir Svalland.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient filling up my logfiles
On Thursday 19 June 2003 17.47, Hasse wrote:
Hi everybody.
Running FreeBSD 4.8-Stable.
I'm connected to the internet by ADSL and dynamic IP.
Dhcp-client keeps filling up my /var/log/messages.
Makes a log-entry every 10th minute.
snip
Jun 19 17:35:56 odin dhclient: New Network Number: 217.209.211.0
Jun 19 17:35:56 odin dhclient: New Broadcast Address: 217.209.211.255
Jun 19 17:44:48 odin dhclient: New Network Number: 217.209.211.0
Jun 19 17:44:48 odin dhclient: New Broadcast Address: 217.209.211.255
/snip
I'm running it with a practically empty dhclient.conf file.
Only added one line to preserve my resolv.conf file.
prepend domain-name-servers 127.0.0.1;
According to the man-page dhclient(8), it's possible to
add a -q switch to only log errors.
snip
The client normally prints a startup message and displays the protocol
sequence to the standard error descriptor until it has acquired
an address, and then only logs messages using the syslog (3) facility.
The -q flag prevents any messages other than errors from being printed to
the standard error descriptor.
/snip
I've tried to put it in rc.conf like this :
ifconfig_xl0=DHCP
dhcp_program=/sbin/dhclient
dhcp_flags=-q
But it still logs every connection.
--
Regards
Hasse
Webmaster @ Swedehost.com
-
Check the lease file you're receiving, if it has a rediculously short
lease time complain to your provider.
Or it may well be the case that their dhcpd server is way too chatty.
This often seems to be the case (possibly to make it work with windows,
I dunno). I just block that traffic from my cable ISP on my firewall
and keep state on outgoing connections, so that if the lease is going
to expire dhclient will ask the server and get its reply but only then,
not without the client asking. It also makes me feel a bit more secure.
(/var/log/messages):
Jun 2 23:26:31 gateway dhclient: New Network Number: 217.121.0.0
Jun 2 23:26:31 gateway dhclient: New Broadcast Address: 217.121.1.255
Jun 6 11:31:18 gateway dhclient: New Network Number: 217.121.0.0
Jun 6 11:31:18 gateway dhclient: New Broadcast Address: 217.121.1.255
Jun 9 23:58:28 gateway dhclient: New Network Number: 217.121.0.0
Jun 9 23:58:28 gateway dhclient: New Broadcast Address: 217.121.1.255
Jun 13 14:02:53 gateway dhclient: New Network Number: 217.121.0.0
Jun 13 14:02:53 gateway dhclient: New Broadcast Address: 217.121.1.255
Jun 17 02:03:22 gateway dhclient: New Network Number: 217.121.0.0
Jun 17 02:03:22 gateway dhclient: New Broadcast Address: 217.121.1.255
HTH,
--Dan
-
This excessive logging behavior started for about 4 days ago.
At least, thats when I got aware of it.
Everything is working just fine, except for this.
My IP-address hardly ever change. I've had the same one for nearly a year now.
There got to be a way to tell it to only log errors, not every connection,
but I don't know how.
I was looking for a way in the syslog.conf, but I have very little
understanding for that tool. ( not a clue ).
Any more hints or clues would be preciated.
This is a snip from my lease file :
lease {
interface xl0;
fixed-address 217.209.211.129;
option subnet-mask 255.255.255.0;
option time-offset 3600;
option routers 217.209.211.1;
option dhcp-lease-time 1200;
option dhcp-message-type 5;
option domain-name-servers 127.0.0.1,10.0.0.1,10.0.0.2;
option dhcp-server-identifier 10.0.113.1;
option broadcast-address 217.209.211.255;
renew 5 2003/6/20 12:18:03;
rebind 5 2003/6/20 12:26:08;
expire 5 2003/6/20 12:28:38;
}
--
Regards
Hasse
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient filling up my logfiles
Hasse [EMAIL PROTECTED] writes:
On Thursday 19 June 2003 17.47, Hasse wrote:
Hi everybody.
Running FreeBSD 4.8-Stable.
I'm connected to the internet by ADSL and dynamic IP.
Dhcp-client keeps filling up my /var/log/messages.
Makes a log-entry every 10th minute.
snip
Jun 19 17:35:56 odin dhclient: New Network Number: 217.209.211.0
Jun 19 17:35:56 odin dhclient: New Broadcast Address: 217.209.211.255
Jun 19 17:44:48 odin dhclient: New Network Number: 217.209.211.0
Jun 19 17:44:48 odin dhclient: New Broadcast Address: 217.209.211.255
/snip
I'm running it with a practically empty dhclient.conf file.
Only added one line to preserve my resolv.conf file.
prepend domain-name-servers 127.0.0.1;
According to the man-page dhclient(8), it's possible to
add a -q switch to only log errors.
No, that's not what the man page says the option does. That option
keeps anything but errors being sent to standard error; it has no
relationship to the system log.
snip
The client normally prints a startup message and displays the protocol
sequence to the standard error descriptor until it has acquired
an address, and then only logs messages using the syslog (3) facility.
The -q flag prevents any messages other than errors from being printed to
the standard error descriptor.
/snip
Read that again to see what I mean.
Check the lease file you're receiving, if it has a rediculously short
lease time complain to your provider.
This was obviously the situation.
This excessive logging behavior started for about 4 days ago.
At least, thats when I got aware of it.
Everything is working just fine, except for this.
My IP-address hardly ever change. I've had the same one for nearly a year now.
There got to be a way to tell it to only log errors, not every connection,
but I don't know how.
I was looking for a way in the syslog.conf, but I have very little
understanding for that tool. ( not a clue ).
Any more hints or clues would be preciated.
Pick the dhclient messages up in a different log file.
Something like (untested):
!dhclient
*.* /var/log/dhcpd
This is a snip from my lease file :
lease {
interface xl0;
fixed-address 217.209.211.129;
option subnet-mask 255.255.255.0;
option time-offset 3600;
option routers 217.209.211.1;
option dhcp-lease-time 1200;
Yep, your lease time is 10 minutes long.
option dhcp-message-type 5;
option domain-name-servers 127.0.0.1,10.0.0.1,10.0.0.2;
option dhcp-server-identifier 10.0.113.1;
option broadcast-address 217.209.211.255;
renew 5 2003/6/20 12:18:03;
rebind 5 2003/6/20 12:26:08;
expire 5 2003/6/20 12:28:38;
}
Try setting your dhclient.conf to ask for a longer lease. If that
fails, pull the dhclient messages into another file...
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: dhclient filling up my logfiles
On Friday 20 June 2003 21.55, Lowell Gilbert wrote:
Hasse [EMAIL PROTECTED] writes:
On Thursday 19 June 2003 17.47, Hasse wrote:
Hi everybody.
Running FreeBSD 4.8-Stable.
I'm connected to the internet by ADSL and dynamic IP.
Dhcp-client keeps filling up my /var/log/messages.
Makes a log-entry every 10th minute.
snip
Jun 19 17:35:56 odin dhclient: New Network Number: 217.209.211.0
Jun 19 17:35:56 odin dhclient: New Broadcast Address: 217.209.211.255
Jun 19 17:44:48 odin dhclient: New Network Number: 217.209.211.0
Jun 19 17:44:48 odin dhclient: New Broadcast Address: 217.209.211.255
/snip
I'm running it with a practically empty dhclient.conf file.
Only added one line to preserve my resolv.conf file.
prepend domain-name-servers 127.0.0.1;
According to the man-page dhclient(8), it's possible to
add a -q switch to only log errors.
No, that's not what the man page says the option does. That option
keeps anything but errors being sent to standard error; it has no
relationship to the system log.
snip
The client normally prints a startup message and displays the
protocol sequence to the standard error descriptor until it has
acquired an address, and then only logs messages using the syslog
(3) facility. The -q flag prevents any messages other than errors
from being printed to the standard error descriptor.
/snip
Read that again to see what I mean.
Ahh.. sorry :-)
Check the lease file you're receiving, if it has a rediculously short
lease time complain to your provider.
This was obviously the situation.
I'll stay put for a week or so, just to see if it goes back to normal due to
some upgrades or any other fishy stuff at my ISP.
It's not really a problem, just annoying.
This excessive logging behavior started for about 4 days ago.
At least, thats when I got aware of it.
Everything is working just fine, except for this.
My IP-address hardly ever change. I've had the same one for nearly a year
now. There got to be a way to tell it to only log errors, not every
connection, but I don't know how.
I was looking for a way in the syslog.conf, but I have very little
understanding for that tool. ( not a clue ).
Any more hints or clues would be preciated.
Pick the dhclient messages up in a different log file.
Something like (untested):
!dhclient
*.* /var/log/dhcpd
That did not work for me, if I did the right things.
Edited syslog.conf and added the above.
touch /var/log/dhcpd
added the following to newsyslog.conf
/var/log/dhcpd 644 3 100 @T00 Z
rebooted
This is a snip from my lease file :
lease {
interface xl0;
fixed-address 217.209.211.129;
option subnet-mask 255.255.255.0;
option time-offset 3600;
option routers 217.209.211.1;
option dhcp-lease-time 1200;
Yep, your lease time is 10 minutes long.
option dhcp-message-type 5;
option domain-name-servers 127.0.0.1,10.0.0.1,10.0.0.2;
option dhcp-server-identifier 10.0.113.1;
option broadcast-address 217.209.211.255;
renew 5 2003/6/20 12:18:03;
rebind 5 2003/6/20 12:26:08;
expire 5 2003/6/20 12:28:38;
}
Try setting your dhclient.conf to ask for a longer lease. If that
fails, pull the dhclient messages into another file...
Will do.
Thx everybody.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
--
Regards
Hasse
Webmaster @ Swedehost.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
dhclient filling up my logfiles
Hi everybody. Running FreeBSD 4.8-Stable. I'm connected to the internet by ADSL and dynamic IP. Dhcp-client keeps filling up my /var/log/messages. Makes a log-entry every 10th minute. snip Jun 19 17:35:56 odin dhclient: New Network Number: 217.209.211.0 Jun 19 17:35:56 odin dhclient: New Broadcast Address: 217.209.211.255 Jun 19 17:44:48 odin dhclient: New Network Number: 217.209.211.0 Jun 19 17:44:48 odin dhclient: New Broadcast Address: 217.209.211.255 /snip I'm running it with a practically empty dhclient.conf file. Only added one line to preserve my resolv.conf file. prepend domain-name-servers 127.0.0.1; According to the man-page dhclient(8), it's possible to add a -q switch to only log errors. snip The client normally prints a startup message and displays the protocol sequence to the standard error descriptor until it has acquired an address, and then only logs messages using the syslog (3) facility. The -q flag prevents any messages other than errors from being printed to the standard error descriptor. /snip I've tried to put it in rc.conf like this : ifconfig_xl0=DHCP dhcp_program=/sbin/dhclient dhcp_flags=-q But it still logs every connection. -- Regards Hasse Webmaster @ Swedehost.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
/ is filling up
My / partition is getting pretty full, 92%. Usually the culprit is something I'm not rotating in /var/log, but that's not the case this time. Does anyone have any suggestions to find out where this is? I'm guessing it's probably something using ls and sort but I'll be damned if I can put something together that helps this problem. David Daugherty ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: / is filling up
On Tue, 3 Jun 2003 11:07:36 -0700 David Daugherty [EMAIL PROTECTED] wrote: Howdy, My / partition is getting pretty full, 92%. Usually the culprit is something I'm not rotating in /var/log, but that's not the case this time. Does anyone have any suggestions to find out where this is? I'm guessing it's probably something using ls and sort but I'll be damned if I can put something together that helps this problem. How about: du -h | grep [0-9]M | sort -r Cheers, -- Miguel Mendez - [EMAIL PROTECTED] EnergyHQ :: http://www.energyhq.tk Tired of Spam? - http://www.trustic.com pgp0.pgp Description: PGP signature
Re: / is filling up
My / partition is getting pretty full, 92%. Usually the culprit is something I'm not rotating in /var/log, but that's not the case this time. Does anyone have any suggestions to find out where this is? I'm guessing it's probably something using ls and sort but I'll be damned if I can put something together that helps this problem. What have you tried? Usually I use successive runs of du(1) to track down overfilling culprits. Are you familiar with that? CD to your root (/) run du -sk * cd in to any suspiciously large directories and do another du, etc. By the way, I think it is good practice to make a separate file system for things like /var/log /var/spool and others that can fill up suddenly when you aren't looking. That way they won't trash the root file system and bring the system down (so easily). jerry David Daugherty ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: / is filling up
David: du -x -d N / where N is the number of levels deep you want to see. - Barry -- Barry Byrne, IT Manager, WBT Systems, Block 2, Harcourt Centre Harcourt Street, Dublin 2, Ireland -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Daugherty My / partition is getting pretty full, 92%. Usually the culprit is something I'm not rotating in /var/log, but that's not the case this time. Does anyone have any suggestions to find out where this is? I'm guessing it's probably something using ls and sort but I'll be damned if I can put something together that helps this problem. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: / is filling up
My / partition is getting pretty full, 92%. Usually the culprit is something
I'm not rotating in /var/log, but that's not the case this time. Does anyone
have any suggestions to find out where this is? I'm guessing it's probably
something using ls and sort but I'll be damned if I can put something
together that helps this problem.
cd /
du -xh -d 2
will print out the usage stats for everything that is in the /-partition
(mount points are not traversed). If you want to see more that 2 levels,
you can modify the command appropriately.
I usually use
du -xh -d 2 | grep M
and
du -xh -d 2 | grep G
to see directories that take more than 1 mega (giga) byte of space
(although these commands will print directories with an 'M' ('G') in
their names, too.
Simon
signature.asc
Description: Digital signature
Re: / is filling up
The usual solution I use would be (starting in the root directory) du -kx | sort -n. The x flag prevents crossing partitions when doing the recursive analysis that du is meant to do, while the k flag makes the output in kilobytes. I like this command enough that I have a shortcut to it in my .bashrc called dk. Check the man page for du for other options if you want. Hope this helps. Zev My / partition is getting pretty full, 92%. Usually the culprit is something I'm not rotating in /var/log, but that's not the case this time. Does anyone have any suggestions to find out where this is? I'm guessing it's probably something using ls and sort but I'll be damned if I can put something together that helps this problem. David Daugherty ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Disk filling up (was Re: Hell of a time, Cont'd)
John McClure wrote: Firstly, thanks for the help so far. My disk is an IBM 27G. The Disklabel config looks like this: Part Mount Size Newfs Part - - ad0s1a /1024MB UFS1Y ad0s1b swap 1024MB SWAP ad0s1d /var 256MB UFS1+S Y ad0s1e /tmp 256MB UFS1+S Y ad0s1f /usr23545MB UFS1+S Y Also, for the f partition I make sure that: newfs -f 2048 -b 16384 As far as my installation specs go, I choose All to install everything, including source, which I want, and I choose the ports collection as well because it feels me with a sense of divine power, and I also actually use it. As you can see, my /usr mount should have plenty o' space. What, exactly, was the error message again? You may want to post hardware details as well, because it might be an incompatible disk/controller. The error message is pretty important because it might not be what you think it is. Also ... didn't you say this was on 5.0? If so, -CURRENT may be a better list to post the question to, as this might be a problem specific to -CURRENT. When I specify mount points manually I enter / or /usr, not mnt/usr. During installation, the filesystems are mounted under /mnt ... when installation is complete and you reboot, they'll be /, /usr, /var, etc ... However, I've only, on most tries, been specifying the root partition and swap, so I can control those sizes, and letting the Auto config take over after that. Finally, when I create the initial slice, I allocate the whole space for freebsd, which I want, and I press S in order to ensure that it is bootable. Sounds like you're on track ... could be a hardware problem? -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Root filesystem 102% full (was: Disks filling up)
Hello, Searched everywhere which lead me to a prior posting about a similar problem. My file system is filling up again, but in different places. I initiated a rscync script that runs via cron which coincidently ran just before my system filling up. I'm sure the answer is obvious to anyone but myself. Any help would help divert my disaster. Thanks. My system: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad0s1a128990 127118-8446 107%/ /dev/ad0s1f257998 118 237242 0%/tmp /dev/ad0s1g 9092908 2060994 630448225%/usr /dev/ad0s1e257998 83548 15381235%/var /dev/ad2s1a128990 2 118670 0%/backup /dev/ad2s1f257998 2 237358 0%/backuptmp /dev/ad2s1g 18028798 2083266 1450323013%/backupusr /dev/ad2s1e257998 2 237358 0%/backuptmp procfs 4 40 100%/proc The script in question: #!/bin/sh /usr/local/bin/rsync -avx --delete --stats / /backup/ /usr/local/bin/rsync -av --delete --stats --exclude=/run/ /var/ /backupvar/ /usr/local/bin/rsync -av --delete --stats /usr/ /backupusr/ Thanks again for any help. David Radovanovic WhatsTheBigIdea.com, Inc. -- Bright ideas for the Web! 249 Partition Street Saugerties, New York 12477 (845) 247-0909, FAX: (845) 246-3880 http://www.WhatsTheBigIdea.com [-Original Message- [From: David Radovanovic [mailto:[EMAIL PROTECTED] [Sent: Thursday, February 13, 2003 8:57 AM [To: Giorgos Keramidas; [EMAIL PROTECTED] [Cc: [EMAIL PROTECTED] [Subject: RE: Root filesystem 102% full (was: Disks fillin up) [ [ [If I'm reading this right the most suspictious culprit in /dev: [ [-rw-r--r-- 1 rootwheel 68960256 Feb 9 04:04 st0 [ [Any ideas? [ [As far as CPAN is concerned, should I delete the files or create a symlink [like you, to another partition with more space? [ [Thanks for your time, I appreciate it :) [ [ [David Radovanovic [WhatsTheBigIdea.com, Inc. [-- Bright ideas for the Web! [249 Partition Street [Saugerties, New York 12477 [(845) 247-0909, FAX: (845) 246-3880 [http://www.WhatsTheBigIdea.com [ [ [[-Original Message- [[From: Giorgos Keramidas [mailto:[EMAIL PROTECTED] [[Sent: Thursday, February 13, 2003 8:22 AM [[To: [EMAIL PROTECTED] [[Cc: [EMAIL PROTECTED] [[Subject: Re: Root filesystem 102% full (was: Disks fillin up) [[ [[ [[Please don't remove the Cc: of the list when replying. I might not [[know the answer, or be too busy to read mail. If you Cc: the list [[too, someone else will have a change to reply too. Probably faster [[than me. [[ [[On 2003-02-13 07:19, David Radovanovic [[[EMAIL PROTECTED] wrote: [[ [Giorgos Keramidas [mailto:[EMAIL PROTECTED] wrote: [[ [ [[ [Start with: [[ [ [[ [ rsc-web1# du -kx / | sort -nr | head -20 [[ [ [[ [This will print the top-20 space consumers of your / filesystem. [[ [What's the output of this command on your system? [[ [[ rsc-web1# du -kx / | sort -nr | head -20 [[ 120903 / [[ 67460 /dev [[ [[This looks odd. Half of your / space is in /dev! Look in /dev with [[`ls -l' and see which part of /dev takes up so much space. [[ [[ 18464 /root [[ 17988 /root/.cpan [[ [[CPAN crap. This is why I don't use cpan at home, and if I absolutely [[have to use it, I symlink /root/.cpan - /home/giorgos/.cpan :-( [[ [[ 12228 /sbin [[ 10944 /root/.cpan/build [[ 5480/modules.old [[ 5480/modules [[ 4198/root/.cpan/sources [[ 4094/bin [[ 3446/root/.cpan/sources/authors [[ 3328/root/.cpan/sources/authors/id [[ 2514/root/.cpan/build/DBI-1.30 [[ 2176/stand [[ 1256/root/.cpan/sources/authors/id/J [[ 1246/root/.cpan/build/DBI-1.30/blib [[ 1232/etc [[ 1134/root/.cpan/build/Class-MakeMethods-1.005 [[ 966 /root/.cpan/sources/authors/id/J/JC [[ 964 /root/.cpan/sources/authors/id/J/JC/JCRISTY [[ [ [ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Root filesystem 102% full (was: Disks filling up)
My file system loooks like this: name# du -kx / | sort -nr | head -20 127117 / 73658 /backupvar 73620 /backupvar/db 71522 /backupvar/db/mysql 18416 /root 17932 /root/.cpan 12228 /sbin 10944 /root/.cpan/build 5480/modules.old 5480/modules 4142/root/.cpan/sources 4094/bin 3390/root/.cpan/sources/authors 3382/backupvar/db/mysql/rsci2 3330/root/.cpan/sources/authors/id 2918/backupvar/db/mysql/rsci 2514/root/.cpan/build/DBI-1.30 2198/backupvar/db/mysql/oldhome 2176/stand 1934/backupvar/db/mysql/database1 David Radovanovic WhatsTheBigIdea.com, Inc. -- Bright ideas for the Web! 249 Partition Street Saugerties, New York 12477 (845) 247-0909, FAX: (845) 246-3880 http://www.WhatsTheBigIdea.com [-Original Message- [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [Sent: Friday, February 28, 2003 12:31 PM [To: David Radovanovic [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [ [You know what - my eyeball slid - sorry.. [ [The only way I could help here would be to look at the root to see [ [Have you run a du to see if that doesnt flush out the disk hog spot? [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ Am I backing up the /backup files? Should I comment out the line: [ /usr/local/bin/rsync -avx --delete --stats / /backup/ in the [script? Maybe I [ don't understand FreeBSD's filesystem though you can see that [/backup is a [ separate 20 gig drive. Thanks for your time :) [ [ David Radovanovic [ WhatsTheBigIdea.com, Inc. [ -- Bright ideas for the Web! [ 249 Partition Street [ Saugerties, New York 12477 [ (845) 247-0909, FAX: (845) 246-3880 [ http://www.WhatsTheBigIdea.com [ [ [ [-Original Message- [ [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [ [Sent: Friday, February 28, 2003 12:15 PM [ [To: David Radovanovic [ [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [ [ [ [ [ [Your root partitions and your /backup are the same - so your [backing up to [ [overflowing. [ [ [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ [ [ Hello, [ [ Searched everywhere which lead me to a prior posting about a similar [ [ problem. My file system is filling up again, but in different [places. I [ [ initiated a rscync script that runs via cron which [coincidently ran just [ [ before my system filling up. I'm sure the answer is obvious [to anyone but [ [ myself. Any help would help divert my disaster. Thanks. My system: [ [ [ [ Filesystem 1K-blocksUsedAvail Capacity Mounted on [ [ /dev/ad0s1a128990 127118-8446 107%/ [ [ /dev/ad0s1f257998 118 237242 0%/tmp [ [ /dev/ad0s1g 9092908 2060994 630448225%/usr [ [ /dev/ad0s1e257998 83548 15381235%/var [ [ /dev/ad2s1a128990 2 118670 0%/backup [ [ /dev/ad2s1f257998 2 237358 0%/backuptmp [ [ /dev/ad2s1g 18028798 2083266 1450323013%/backupusr [ [ /dev/ad2s1e257998 2 237358 0%/backuptmp [ [ procfs 4 40 100%/proc [ [ [ [ The script in question: [ [ [ [ #!/bin/sh [ [ [ [ /usr/local/bin/rsync -avx --delete --stats / /backup/ [ [ /usr/local/bin/rsync -av --delete --stats --exclude=/run/ /var/ [ [/backupvar/ [ [ /usr/local/bin/rsync -av --delete --stats /usr/ /backupusr/ [ [ [ [ Thanks again for any help. [ [ [ [ [ [ David Radovanovic [ [ WhatsTheBigIdea.com, Inc. [ [ -- Bright ideas for the Web! [ [ 249 Partition Street [ [ Saugerties, New York 12477 [ [ (845) 247-0909, FAX: (845) 246-3880 [ [ http://www.WhatsTheBigIdea.com [ [ [ [ [ [ [-Original Message- [ [ [From: David Radovanovic [mailto:[EMAIL PROTECTED] [ [ [Sent: Thursday, February 13, 2003 8:57 AM [ [ [To: Giorgos Keramidas; [EMAIL PROTECTED] [ [ [Cc: [EMAIL PROTECTED] [ [ [Subject: RE: Root filesystem 102% full (was: Disks fillin up) [ [ [ [ [ [ [ [ [If I'm reading this right the most suspictious culprit in /dev: [ [ [ [ [ [-rw-r--r-- 1 rootwheel 68960256 Feb 9 04:04 st0 [ [ [ [ [ [Any ideas? [ [ [ [ [ [As far as CPAN is concerned, should I delete the files or [ [create a symlink [ [ [like you, to another partition with more space? [ [ [ [ [ [Thanks for your time, I appreciate it :) [ [ [ [ [ [ [ [ [David Radovanovic [ [ [WhatsTheBigIdea.com, Inc. [ [ [-- Bright ideas for the Web! [ [ [249 Partition Street [ [ [Saugerties, New York 12477 [ [ [(845) 247-0909, FAX: (845) 246-3880 [ [ [http://www.WhatsTheBigIdea.com [ [ [ [ [ [ [ [ [[-Original Message- [ [ [[From: Giorgos Keramidas [mailto:[EMAIL PROTECTED] [ [ [[Sent: Thursday, February 13, 2003 8:22 AM [ [ [[To: [EMAIL PROTECTED] [ [ [[Cc: [EMAIL PROTECTED] [ [ [[Subject: Re: Root filesystem 102% full (was: Disks fillin up) [ [ [[ [ [ [[ [ [ [[Please don't remove the Cc: of the list when replying. I might not [ [ [[know the answer, or be too busy to read mail. If you Cc: the list [ [ [[too, someone else will have a change to reply too. Probably faster [ [ [[than me
RE: Root filesystem 102% full (was: Disks filling up)
Thanks for your reply: name# du -s -h * 6.0KCOPYRIGHT 2.0Kbackup 2.0Kbackuptmp 2.0Gbackupusr 72Mbackupvar 4.0Mbin 542Kboot 2.0Kcdrom 0Bcompat 68Kdev 2.0Kdist 1.2Metc 2.0Kfdd 0Bhome 3.6Mkernel 0Bkernel.old 2.0Kmnt 5.4Mmodules 5.4Mmodules.old 37Kproc 18Mroot 12Msbin 2.1Mstand 0Bsys 2.0Ktar-e.log 0Btar.log 118Ktmp 2.0Gusr 82Mvar David Radovanovic WhatsTheBigIdea.com, Inc. -- Bright ideas for the Web! 249 Partition Street Saugerties, New York 12477 (845) 247-0909, FAX: (845) 246-3880 http://www.WhatsTheBigIdea.com [-Original Message- [From: Sean J. Countryman [mailto:[EMAIL PROTECTED] [Sent: Friday, February 28, 2003 12:32 PM [To: FreeBSD Questions; [EMAIL PROTECTED] [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [from the root directory (/) run: du -s -h * and post the [results. That [will tell us who the offendor is. That will show the disk usage du for [each of the directories in the / directory. If you wish to do a bit more [detective work, go into the largest directory and rerun du -s -h * on it [to find which subdirectory in that directory is oversized. In this manner [of drilling down, you can discover who the big offender is and then we can [figure out a good course of action. [ [I've seen this a bunch working tech support (for a large internet hosting [company :-) Everytime I drill down to find the problem, it turns out to be [something like an out of control log file, a grossly large mysql database, [or something similar. [ [Let me know if you need anything else [ [Sean Countryman [ [ [ [-Original Message- [From: [EMAIL PROTECTED] [[mailto:[EMAIL PROTECTED] Behalf Of David [Radovanovic [Sent: Friday, February 28, 2003 10:25 AM [To: Stephen Hovey [Cc: [EMAIL PROTECTED] [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [Am I backing up the /backup files? Should I comment out the line: [/usr/local/bin/rsync -avx --delete --stats / /backup/ in the [script? Maybe I [don't understand FreeBSD's filesystem though you can see that /backup is a [separate 20 gig drive. Thanks for your time :) [ [David Radovanovic [WhatsTheBigIdea.com, Inc. [-- Bright ideas for the Web! [249 Partition Street [Saugerties, New York 12477 [(845) 247-0909, FAX: (845) 246-3880 [http://www.WhatsTheBigIdea.com [ [ [[-Original Message- [[From: Stephen Hovey [mailto:[EMAIL PROTECTED] [[Sent: Friday, February 28, 2003 12:15 PM [[To: David Radovanovic [[Subject: RE: Root filesystem 102% full (was: Disks filling up) [[ [[ [[ [[Your root partitions and your /backup are the same - so your backing up to [[overflowing. [[ [[On Fri, 28 Feb 2003, David Radovanovic wrote: [[ [[ Hello, [[ Searched everywhere which lead me to a prior posting about a similar [[ problem. My file system is filling up again, but in different places. I [[ initiated a rscync script that runs via cron which [coincidently ran just [[ before my system filling up. I'm sure the answer is obvious to [anyone but [[ myself. Any help would help divert my disaster. Thanks. My system: [[ [[ Filesystem 1K-blocksUsedAvail Capacity Mounted on [[ /dev/ad0s1a128990 127118-8446 107%/ [[ /dev/ad0s1f257998 118 237242 0%/tmp [[ /dev/ad0s1g 9092908 2060994 630448225%/usr [[ /dev/ad0s1e257998 83548 15381235%/var [[ /dev/ad2s1a128990 2 118670 0%/backup [[ /dev/ad2s1f257998 2 237358 0%/backuptmp [[ /dev/ad2s1g 18028798 2083266 1450323013%/backupusr [[ /dev/ad2s1e257998 2 237358 0%/backuptmp [[ procfs 4 40 100%/proc [[ [[ The script in question: [[ [[ #!/bin/sh [[ [[ /usr/local/bin/rsync -avx --delete --stats / /backup/ [[ /usr/local/bin/rsync -av --delete --stats --exclude=/run/ /var/ [[/backupvar/ [[ /usr/local/bin/rsync -av --delete --stats /usr/ /backupusr/ [[ [[ Thanks again for any help. [[ [[ [[ David Radovanovic [[ WhatsTheBigIdea.com, Inc. [[ -- Bright ideas for the Web! [[ 249 Partition Street [[ Saugerties, New York 12477 [[ (845) 247-0909, FAX: (845) 246-3880 [[ http://www.WhatsTheBigIdea.com [[ [[ [[ [-Original Message- [[ [From: David Radovanovic [mailto:[EMAIL PROTECTED] [[ [Sent: Thursday, February 13, 2003 8:57 AM [[ [To: Giorgos Keramidas; [EMAIL PROTECTED] [[ [Cc: [EMAIL PROTECTED] [[ [Subject: RE: Root filesystem 102% full (was: Disks fillin up) [[ [ [[ [ [[ [If I'm reading this right the most suspictious culprit in /dev: [[ [ [[ [-rw-r--r-- 1 rootwheel 68960256 Feb 9 04:04 st0 [[ [ [[ [Any ideas? [[ [ [[ [As far as CPAN is concerned, should I delete the files or [[create a symlink [[ [like you, to another partition with more space? [[ [ [[ [Thanks for your time, I appreciate it :) [[ [ [[ [ [[ [David Radovanovic [[ [WhatsTheBigIdea.com, Inc. [[ [-- Bright ideas for the Web! [[ [249
RE: Root filesystem 102% full (was: Disks filling up)
Stephen, Since /backupvar is actually another drive and given my filesystem, where would you suggest? Thanks:) David Radovanovic WhatsTheBigIdea.com, Inc. -- Bright ideas for the Web! 249 Partition Street Saugerties, New York 12477 (845) 247-0909, FAX: (845) 246-3880 http://www.WhatsTheBigIdea.com [-Original Message- [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [Sent: Friday, February 28, 2003 12:53 PM [To: [EMAIL PROTECTED] [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [Your /backupvar is 73MB - over half of your root partition. I owuld move [that to some other place [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ My file system loooks like this: [ [ name# du -kx / | sort -nr | head -20 [ [ 127117 / [ 73658 /backupvar [ 73620 /backupvar/db [ 71522 /backupvar/db/mysql [ 18416 /root [ 17932 /root/.cpan [ 12228 /sbin [ 10944 /root/.cpan/build [ 5480/modules.old [ 5480/modules [ 4142/root/.cpan/sources [ 4094/bin [ 3390/root/.cpan/sources/authors [ 3382/backupvar/db/mysql/rsci2 [ 3330/root/.cpan/sources/authors/id [ 2918/backupvar/db/mysql/rsci [ 2514/root/.cpan/build/DBI-1.30 [ 2198/backupvar/db/mysql/oldhome [ 2176/stand [ 1934/backupvar/db/mysql/database1 [ [ [ David Radovanovic [ WhatsTheBigIdea.com, Inc. [ -- Bright ideas for the Web! [ 249 Partition Street [ Saugerties, New York 12477 [ (845) 247-0909, FAX: (845) 246-3880 [ http://www.WhatsTheBigIdea.com [ [ [ [-Original Message- [ [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [ [Sent: Friday, February 28, 2003 12:31 PM [ [To: David Radovanovic [ [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [ [ [ [ [ [You know what - my eyeball slid - sorry.. [ [ [ [The only way I could help here would be to look at the root to see [ [ [ [Have you run a du to see if that doesnt flush out the disk hog spot? [ [ [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ [ [ Am I backing up the /backup files? Should I comment out the line: [ [ /usr/local/bin/rsync -avx --delete --stats / /backup/ in the [ [script? Maybe I [ [ don't understand FreeBSD's filesystem though you can see that [ [/backup is a [ [ separate 20 gig drive. Thanks for your time :) [ [ [ [ David Radovanovic [ [ WhatsTheBigIdea.com, Inc. [ [ -- Bright ideas for the Web! [ [ 249 Partition Street [ [ Saugerties, New York 12477 [ [ (845) 247-0909, FAX: (845) 246-3880 [ [ http://www.WhatsTheBigIdea.com [ [ [ [ [ [ [-Original Message- [ [ [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [ [ [Sent: Friday, February 28, 2003 12:15 PM [ [ [To: David Radovanovic [ [ [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [ [ [ [ [ [ [ [ [ [Your root partitions and your /backup are the same - so your [ [backing up to [ [ [overflowing. [ [ [ [ [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ [ [ [ [ Hello, [ [ [ Searched everywhere which lead me to a prior posting about [a similar [ [ [ problem. My file system is filling up again, but in different [ [places. I [ [ [ initiated a rscync script that runs via cron which [ [coincidently ran just [ [ [ before my system filling up. I'm sure the answer is obvious [ [to anyone but [ [ [ myself. Any help would help divert my disaster. Thanks. My system: [ [ [ [ [ [ Filesystem 1K-blocksUsedAvail Capacity Mounted on [ [ [ /dev/ad0s1a128990 127118-8446 107%/ [ [ [ /dev/ad0s1f257998 118 237242 0%/tmp [ [ [ /dev/ad0s1g 9092908 2060994 630448225%/usr [ [ [ /dev/ad0s1e257998 83548 15381235%/var [ [ [ /dev/ad2s1a128990 2 118670 0%/backup [ [ [ /dev/ad2s1f257998 2 237358 0%/backuptmp [ [ [ /dev/ad2s1g 18028798 2083266 1450323013%/backupusr [ [ [ /dev/ad2s1e257998 2 237358 0%/backuptmp [ [ [ procfs 4 40 100%/proc [ [ [ [ [ [ The script in question: [ [ [ [ [ [ #!/bin/sh [ [ [ [ [ [ /usr/local/bin/rsync -avx --delete --stats / /backup/ [ [ [ /usr/local/bin/rsync -av --delete --stats --exclude=/run/ /var/ [ [ [/backupvar/ [ [ [ /usr/local/bin/rsync -av --delete --stats /usr/ /backupusr/ [ [ [ [ [ [ Thanks again for any help. [ [ [ [ [ [ [ [ [ David Radovanovic [ [ [ WhatsTheBigIdea.com, Inc. [ [ [ -- Bright ideas for the Web! [ [ [ 249 Partition Street [ [ [ Saugerties, New York 12477 [ [ [ (845) 247-0909, FAX: (845) 246-3880 [ [ [ http://www.WhatsTheBigIdea.com [ [ [ [ [ [ [ [ [ [-Original Message- [ [ [ [From: David Radovanovic [mailto:[EMAIL PROTECTED] [ [ [ [Sent: Thursday, February 13, 2003 8:57 AM [ [ [ [To: Giorgos Keramidas; [EMAIL PROTECTED] [ [ [ [Cc: [EMAIL PROTECTED] [ [ [ [Subject: RE: Root filesystem 102% full (was: Disks fillin up) [ [ [ [ [ [ [ [ [ [ [ [If I'm reading this right the most suspictious culprit in /dev: [ [ [ [ [ [ [ [-rw-r--r-- 1 rootwheel 68960256 Feb 9 04:04 st0 [ [ [ [ [ [ [ [Any ideas? [ [ [ [ [ [ [ [As far as CPAN
Re: Root filesystem 102% full (was: Disks filling up)
On 2003-02-28 12:06, David Radovanovic [EMAIL PROTECTED] wrote: Hello, Searched everywhere which lead me to a prior posting about a similar problem. My file system is filling up again, but in different places. Thank you for looking at the archives first. Honestly, thanks :-) I initiated a rscync script that runs via cron which coincidently ran just before my system filling up. I'm sure the answer is obvious to anyone but myself. Any help would help divert my disaster. Thanks. My system: Filesystem 1K-blocksUsedAvail Capacity Mounted on /dev/ad0s1a128990 127118-8446 107%/ /dev/ad0s1f257998 118 237242 0%/tmp /dev/ad0s1g 9092908 2060994 630448225%/usr /dev/ad0s1e257998 83548 15381235%/var /dev/ad2s1a128990 2 118670 0%/backup /dev/ad2s1f257998 2 237358 0%/backuptmp /dev/ad2s1g 18028798 2083266 1450323013%/backupusr /dev/ad2s1e257998 2 237358 0%/backuptmp procfs 4 40 100%/proc Note that there is no /backupvar mount point listed above... The script in question: #!/bin/sh /usr/local/bin/rsync -avx --delete --stats / /backup/ /usr/local/bin/rsync -av --delete --stats --exclude=/run/ /var/ /backupvar/ /usr/local/bin/rsync -av --delete --stats /usr/ /backupusr/ The second command will attempt to synchronise /var with /backupvar and effectively create a copy of the entire /var partition in your root filesystem. Since /dev/ad0s1e (your /var partition) is larger than /dev/ad0s1a (the root partition) this will quickly fill the root partition to 100% and start grabbing blocks from the reserved space (the default is 8% of the partition). You are running this as root and FreeBSD doesn't block you at 100% but goes on merrily with its job until both the partition and the reserved space are full (100 + 8 = 108%; this is why the usage percentage in / is listed as 107% and not as 100%). Thanks again for any help. You're welcome :) - Giorgos To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
RE: Root filesystem 102% full (was: Disks filling up)
its a backup of a different drive you mean or the /var partition of that same drive? Your backupusr partition is chubby - that would get my vote unless thats the same physical drive your tryin to get a backup of.. On Fri, 28 Feb 2003, David Radovanovic wrote: Stephen, Since /backupvar is actually another drive and given my filesystem, where would you suggest? Thanks:) David Radovanovic WhatsTheBigIdea.com, Inc. -- Bright ideas for the Web! 249 Partition Street Saugerties, New York 12477 (845) 247-0909, FAX: (845) 246-3880 http://www.WhatsTheBigIdea.com [-Original Message- [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [Sent: Friday, February 28, 2003 12:53 PM [To: [EMAIL PROTECTED] [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [Your /backupvar is 73MB - over half of your root partition. I owuld move [that to some other place [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ My file system loooks like this: [ [ name# du -kx / | sort -nr | head -20 [ [ 127117 / [ 73658 /backupvar [ 73620 /backupvar/db [ 71522 /backupvar/db/mysql [ 18416 /root [ 17932 /root/.cpan [ 12228 /sbin [ 10944 /root/.cpan/build [ 5480/modules.old [ 5480/modules [ 4142/root/.cpan/sources [ 4094/bin [ 3390/root/.cpan/sources/authors [ 3382/backupvar/db/mysql/rsci2 [ 3330/root/.cpan/sources/authors/id [ 2918/backupvar/db/mysql/rsci [ 2514/root/.cpan/build/DBI-1.30 [ 2198/backupvar/db/mysql/oldhome [ 2176/stand [ 1934/backupvar/db/mysql/database1 [ [ [ David Radovanovic [ WhatsTheBigIdea.com, Inc. [ -- Bright ideas for the Web! [ 249 Partition Street [ Saugerties, New York 12477 [ (845) 247-0909, FAX: (845) 246-3880 [ http://www.WhatsTheBigIdea.com [ [ [ [-Original Message- [ [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [ [Sent: Friday, February 28, 2003 12:31 PM [ [To: David Radovanovic [ [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [ [ [ [ [ [You know what - my eyeball slid - sorry.. [ [ [ [The only way I could help here would be to look at the root to see [ [ [ [Have you run a du to see if that doesnt flush out the disk hog spot? [ [ [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ [ [ Am I backing up the /backup files? Should I comment out the line: [ [ /usr/local/bin/rsync -avx --delete --stats / /backup/ in the [ [script? Maybe I [ [ don't understand FreeBSD's filesystem though you can see that [ [/backup is a [ [ separate 20 gig drive. Thanks for your time :) [ [ [ [ David Radovanovic [ [ WhatsTheBigIdea.com, Inc. [ [ -- Bright ideas for the Web! [ [ 249 Partition Street [ [ Saugerties, New York 12477 [ [ (845) 247-0909, FAX: (845) 246-3880 [ [ http://www.WhatsTheBigIdea.com [ [ [ [ [ [ [-Original Message- [ [ [From: Stephen Hovey [mailto:[EMAIL PROTECTED] [ [ [Sent: Friday, February 28, 2003 12:15 PM [ [ [To: David Radovanovic [ [ [Subject: RE: Root filesystem 102% full (was: Disks filling up) [ [ [ [ [ [ [ [ [ [ [ [Your root partitions and your /backup are the same - so your [ [backing up to [ [ [overflowing. [ [ [ [ [ [On Fri, 28 Feb 2003, David Radovanovic wrote: [ [ [ [ [ [ Hello, [ [ [ Searched everywhere which lead me to a prior posting about [a similar [ [ [ problem. My file system is filling up again, but in different [ [places. I [ [ [ initiated a rscync script that runs via cron which [ [coincidently ran just [ [ [ before my system filling up. I'm sure the answer is obvious [ [to anyone but [ [ [ myself. Any help would help divert my disaster. Thanks. My system: [ [ [ [ [ [ Filesystem 1K-blocksUsedAvail Capacity Mounted on [ [ [ /dev/ad0s1a128990 127118-8446 107%/ [ [ [ /dev/ad0s1f257998 118 237242 0%/tmp [ [ [ /dev/ad0s1g 9092908 2060994 630448225%/usr [ [ [ /dev/ad0s1e257998 83548 15381235%/var [ [ [ /dev/ad2s1a128990 2 118670 0%/backup [ [ [ /dev/ad2s1f257998 2 237358 0%/backuptmp [ [ [ /dev/ad2s1g 18028798 2083266 1450323013%/backupusr [ [ [ /dev/ad2s1e257998 2 237358 0%/backuptmp [ [ [ procfs 4 40 100%/proc [ [ [ [ [ [ The script in question: [ [ [ [ [ [ #!/bin/sh [ [ [ [ [ [ /usr/local/bin/rsync -avx --delete --stats / /backup/ [ [ [ /usr/local/bin/rsync -av --delete --stats --exclude=/run/ /var/ [ [ [/backupvar/ [ [ [ /usr/local/bin/rsync -av --delete --stats /usr/ /backupusr/ [ [ [ [ [ [ Thanks again for any help. [ [ [ [ [ [ [ [ [ David Radovanovic [ [ [ WhatsTheBigIdea.com, Inc. [ [ [ -- Bright ideas for the Web! [ [ [ 249 Partition Street [ [ [ Saugerties, New York 12477 [ [ [ (845) 247-0909, FAX: (845) 246-3880 [ [ [ http://www.WhatsTheBigIdea.com [ [ [ [ [ [ [ [ [ [-Original Message- [ [ [ [From: David Radovanovic [mailto:[EMAIL
RE: Root filesystem 102% full (was: Disks filling up)
Thank you. The problem was that backupvar was within the / partition instead of having its own partition on the second (backup) hard drive. As so clearly explained by Giorgos. Thank you all for our time, patience and wisdom :) David Radovanovic WhatsTheBigIdea.com, Inc. -- Bright ideas for the Web! 249 Partition Street Saugerties, New York 12477 (845) 247-0909, FAX: (845) 246-3880 http://www.WhatsTheBigIdea.com [-Original Message- [From: Giorgos Keramidas [mailto:[EMAIL PROTECTED] [Sent: Friday, February 28, 2003 4:13 PM [To: David Radovanovic [Cc: [EMAIL PROTECTED] [Subject: Re: Root filesystem 102% full (was: Disks filling up) [ [ [On 2003-02-28 12:06, David Radovanovic [[EMAIL PROTECTED] wrote: [ Hello, [ Searched everywhere which lead me to a prior posting about a similar [ problem. My file system is filling up again, but in different places. [ [Thank you for looking at the archives first. Honestly, thanks :-) [ [ I initiated a rscync script that runs via cron which coincidently [ ran just before my system filling up. I'm sure the answer is obvious [ to anyone but myself. Any help would help divert my disaster. [ Thanks. My system: [ [ Filesystem 1K-blocksUsedAvail Capacity Mounted on [ /dev/ad0s1a128990 127118-8446 107%/ [ /dev/ad0s1f257998 118 237242 0%/tmp [ /dev/ad0s1g 9092908 2060994 630448225%/usr [ /dev/ad0s1e257998 83548 15381235%/var [ /dev/ad2s1a128990 2 118670 0%/backup [ /dev/ad2s1f257998 2 237358 0%/backuptmp [ /dev/ad2s1g 18028798 2083266 1450323013%/backupusr [ /dev/ad2s1e257998 2 237358 0%/backuptmp [ procfs 4 40 100%/proc [ [Note that there is no /backupvar mount point listed above... [ [ The script in question: [ [ #!/bin/sh [ [ /usr/local/bin/rsync -avx --delete --stats / /backup/ [ /usr/local/bin/rsync -av --delete --stats --exclude=/run/ /var/ [/backupvar/ [ /usr/local/bin/rsync -av --delete --stats /usr/ /backupusr/ [ [The second command will attempt to synchronise /var with /backupvar [and effectively create a copy of the entire /var partition in your [root filesystem. Since /dev/ad0s1e (your /var partition) is larger [than /dev/ad0s1a (the root partition) this will quickly fill the root [partition to 100% and start grabbing blocks from the reserved space [(the default is 8% of the partition). You are running this as root [and FreeBSD doesn't block you at 100% but goes on merrily with its job [until both the partition and the reserved space are full [(100 + 8 = 108%; this is why the usage percentage in / is listed as [107% and not as 100%). [ [ Thanks again for any help. [ [You're welcome :) [ [- Giorgos [ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
/var filling up with X error logs
I've been having a nasty problem with my xserver log file being filled up with a strange message. Once /var gets to about 80% full the system really starts slowint down and I can't hardly X. At 90% it is unusable, as far as X is concnerned. Here is a sample of the output from xdm-errors log, which has gotten up to about 85mb: XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.6.2-RELEASE i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Tue Oct 22 00:36:26 2002 (==) Using config file: /etc/X11/XF86Config moutb(3CE, E) moutb(3CF, 20) moutl(40, 80) Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! minl(40) moutl(4, 0) moutl(C, 800) moutl(18, 40D00D0) minl(40) moutl(8, 55D) And this will continue on for 6.5 million lines. Any help would be greatly appreciated. Thanks, Mike ps my xfree86.0 log is about 85 mb too, but it has a lot more unique messages in it, if you need I can post it too. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
