Re: newsyslog.conf and Apache log files
On 10/7/10 7:26 PM, Joe Auty wrote: Hi Joe, Unfortunately, this has created these big long log files such as the following: httpderror_log.2.bz2.2.bz2.2.bz2.1.bz2.1.bz2.1.bz2.0.bz2 How can I prevent these dumb log file names from being created? Like Lowell wrote, don't use wildcards in newsyslog.conf. :-) I just react to this, because I spent quite some time after a storage change on why my machine was hanging at bootup on the newsyslog trimming and creating logfiles line. There was no good Google result that pointed me in the direction, hence my post now. In my case I made the same mistake as you on my Asterisk logfiles (which also don't have any extention). So after troubleshooting NFS and filesystem problems, I ran truss on newsyslog and found out about the nice tree newsyslog had built on my Asterisk logfiles. It wasn't hanging afterall, it was quite busy. :-) I just wrote three lines with the three filenames I wanted to rotate and since then it's fine. /Robin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Deleting mail from a mail Queue
Joel Muia wrote: I need help on how to delete mail from deamons installed from in a freeBSD 5.5 I assume you mean that you just want to delete certain mails in a queue from a certain MTA. I use pfqueue for that, it's a pretty good util for queue management. You can tag mails (even if it's a lot of mails) and then perform a bulk action on them. If you mean something else, please explain. -- F/X Services Managed Hosting http://www.fx-services.com | http://www.fxs.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Server rebooting itself
Don O'Neil wrote: Don, This happens randomly every 3-20 days (no apparent pattern). Any suggestions on what to check next? As other wrote: it can be anything. I had a similair problem and it almost drove me mad. It was a webhosting machine running 5.4, later 6.1 and up. The machine was running Cpanel, a webhosting panel. I've tried everything (memory testing, stress testing, etc etc): kept rebooting. Just when I was at the point of actually stopping my webhosting business (I just have that as a hobby), I swapped the dual Xeon Supermicro that was giving problems with a really old dual P3 Dell 1650. It's been running stable since then. Stable but slow. :) Same for my backup machine, which was a self-built Dual Athlon MP (well, built by a computer supplier). Swapped that for an old dual P4 Dell 2550 and: all is fine. Doesn't help you much, except if you have some old Dell hardware laying around. :) /Robin -- F/X Services Managed Hosting http://www.fx-services.com | http://www.fxs.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Strange df output, including non-mounts
Hi guys, In the daily run output, the disk status always starts to look a bit strange on one of my machines. I think this starts after about three weeks of uptime. It never seems to cause any serious problems, but today I decided to find out why this happens. :) I couldn't find any answers on Google (or the list archives, which search function seems to be broken). df (both in the daily run and manual df -hi) starts showing mountpoints that are not mountpoints. Like var/spool and usr/local. Why these suddenly show up in the df output I'd like to know... :) The output looks like this: Disk status: df: libexec stats possibly stale df: lib stats possibly stale df: usr/lib stats possibly stale df: usr/sbin stats possibly stale df: usr/share stats possibly stale df: usr/bin stats possibly stale df: usr/man stats possibly stale df: usr/X11R6 stats possibly stale df: usr/libexec stats possibly stale df: usr/local/bin stats possibly stale df: usr/local/lib stats possibly stale df: var/spool stats possibly stale df: var/lib stats possibly stale df: var/run stats possibly stale df: var/log stats possibly stale df: jacco stats possibly stale df: tmp stats possibly stale df: dev stats possibly stale df: bin stats possibly stale df: proc stats possibly stale Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 5076307953238748817%/ devfs 11 0 100%/dev /dev/da0s1d 5076305877040825013%/tmp /dev/da0s1f 13694960 5729928 686943645%/usr /dev/da0s1e 1506190 124450014119690%/var_local devfs 11 0 100%/var/named/dev procfs 44 0 100%/proc /libexec 5076307953238748817%libexec /lib 5076307953238748817%lib /usr/lib13694960 5729862 686950245%usr/lib /usr/sbin 13694960 5729862 686950245%usr/sbin /usr/share 13694960 5729862 686950245%usr/share /usr/bin13694960 5729862 686950245%usr/bin /usr/man13694960 5729862 686950245%usr/man /usr/X11R6 13694960 5729862 686950245%usr/X11R6 /usr/libexec13694960 5729862 686950245%usr/libexec /usr/local/bin 13694960 5729862 686950245%usr/local/bin /usr/local/lib 13694960 5729862 686950245%usr/local/lib /var/spool 83886080 3969332 79916748 5%var/spool /var/lib83886080 3969332 79916748 5%var/lib /var/run83886080 3969332 79916748 5%var/run /var/log83886080 3969332 79916748 5%var/log /home/jail251658240 41213716 21044452416% jail /tmp 50763030598436422 7%tmp /dev 11 0 100%dev /bin 5076307953238748817%bin /proc 44 0 100%proc Anyone seen this or has any ideas? I'm thinking maybe some threshold is reached which makes those points show up (inode free% or something else). But I can't seem to find any info on that in the manpages for df or the handbook. -- F/X Services Managed Hosting http://www.fx-services.com | http://www.fxs.se ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
