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
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]
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]
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]
