RE: DHCP Server Offline.
The du command is your friend. Have a look at 'man du' Maybe something like: du -d2 /var Cheers, Paul -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephan Weaver Sent: Friday, 15 July 2005 10:25 PM To: [EMAIL PROTECTED]; freebsd-questions@freebsd.org Subject: Re: DHCP Server Offline. I Found out the Problem, The /var partation is full. How do i find out where is taking up all the space? Thanks From: Ean Kingston [EMAIL PROTECTED] To: freebsd-questions@freebsd.org CC: [EMAIL PROTECTED] Subject: Re: DHCP Server Offline. Date: Fri, 15 Jul 2005 10:18:09 -0400 On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server Offline.
On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server Offline.
I Found out the Problem, The /var partation is full. How do i find out where is taking up all the space? Thanks From: Ean Kingston [EMAIL PROTECTED] To: freebsd-questions@freebsd.org CC: [EMAIL PROTECTED] Subject: Re: DHCP Server Offline. Date: Fri, 15 Jul 2005 10:18:09 -0400 On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DHCP Server Offline.
du /var | sort -rn | more This will sort the output with the largest directories at the top. Then you can examine what is in the directories that is taking up the space. David http://freebsd.vangeyn.net/ I Found out the Problem, The /var partation is full. How do i find out where is taking up all the space? Thanks From: Ean Kingston [EMAIL PROTECTED] To: freebsd-questions@freebsd.org CC: [EMAIL PROTECTED] Subject: Re: DHCP Server Offline. Date: Fri, 15 Jul 2005 10:18:09 -0400 On July 15, 2005 10:11 am, Stephan Weaver wrote: Hello folks, I have a Stand Alone FreeBSD Firewall / Nat / Dhcp Server. Everything seems to work fine, up until this morning. Users seem to complain they could not get on the network anymore. Further investigation revealed the dhcp server could not be contacted. Further more, only some of the users were online. I am guessing that these clients who were online had an ip address from the dhcp server at a previous time and the lease didnt expire as yet. And users who were not online, the lease expired and attempted to contact the dhcp server and failed. I Would appreciate any help or suggestions. Set the lease expire time to at least 5 days (7 to 10 is better) and the renewal time to between 4 and 12 hours. Then setup a dhcp monitoring process that will alert you if it fails to get an address or renewal. Make sure you have more addresses available than you ever expect to give out. I go with 50% more. I've known some admins that want at least double. Like what to do in the future incase this happens again. Setup 2 dhcp servers on the network. If one fails, the other will hopefully continue to serve addresses. Monitor this one as well. I Would like to find out what had happened. Start reading logs. The last thing that i had done to the server was setup, configure and install 'ntop'; dont know if this would cause a problem. Thank you in advance. Stephan Weaver P.S. Please reply to my Directly at @ [EMAIL PROTECTED] -- Ean Kingston E-Mail: ean AT hedron DOT org URL: http://www.hedron.org/ I am currently looking for work. If you need competent system/network administration please feel free to contact me directly. _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
