Re: [expert] syslog restarts and other wierdness
Phil Connor wrote:
I don't understand, dhcpd should just use the address of the NIC. How
does it know "the address is already in use"?
Nope! try setting the ipaddress for DHCPD as .0 example 192.168.20.0 and
then set your range to start with your nic address like 192.168.20.20 -
192.168.20.40
Yes, the subnet is declared as the network addresss - not the machine.
But dhcpd was still responding that it couldn't bind to the machine
address. Here is my dhcpd.conf.
# Dynamic Host Configuration Protocol
# DHCPd Daemon Configuration File
# dlt=600sec=10min, mlt=43200sec=12hours
#
default-lease-time 600;
max-lease-time 43200;
option domain-name-servers 10.8.1.7, 207.73.196.250;
option domain-name "forestview.edu";
subnet 10.33.1.0 netmask 255.255.255.0 {
range 10.33.1.10 10.33.1.250;
option subnet-mask 255.255.255.0;
option broadcast-address 10.33.1.255;
option routers 10.33.1.251;
}
Perhaps there is more that one dhcpd running on the box. What does the
log file say? What does the output from ifconfig say? What does your
dhcpd.conf file say?
Only if he has several or virtual address's which will all have to have an
entry/declaration even if their not used to give address out.
ifconfig shows only eth0 and lo. Nothing appears abnormal in any way.
Even the routing table looked normal and the server itself was able to
surf the web as normal. dhcpd just insisted on pukeing whenever I tried
to launch it. As I've said elsewhere though, I think there must be
something going on either with the server or the network as we're
getting sharing violations with Samba that shouldn't be happening. I
don't know what else on the network would cause this. Immediately after
I changed the server IP I pinged the original IP to see what I'd find.
Ping said there was nothing there.
?
--
Mike Rambo
[EMAIL PROTECTED]
Keep in touch with http://mandrakeforum.com:
Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] syslog restarts and other wierdness
Bill Shirley wrote: I don't understand, dhcpd should just use the address of the NIC. How does it know "the address is already in use"? Perhaps there is more that one dhcpd running on the box. What does the log file say? What does the output from ifconfig say? What does your dhcpd.conf file say? Bill I don't understand either and I don't know why it's giving that message. Maybe I'll check with the dhcp mail list that ISC has. I checked for the dhcpd pid. There was none. Nothing showed with ps ax either. ifconfig showed only the single ethernet card and lo and displayed nothing out of the ordinary. The dhcpd.conf file was unchanged from it's initial setup (and was checked for correctness too - it was/is ok). As I said before ... totally baffled! Something does appear to be going on with this server though. We've got what appear to be sharing violations with Samba shares that shouldn't be occuring. I haven't been back on location yet so I don't know for sure. That's for later this afternoon. -- Mike Rambo [EMAIL PROTECTED] Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] syslog restarts and other wierdness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 19 Oct 2000, Mike Rambo wrote: the box refused to start the dhcp server daemon with the error that it couldn't bind to the IP address because it was already in use. There is and was nothing else on the same IP address as the server but the only way I found to resolve that problem was to put the server on a different IP address. That's a wierd one I've never seen before. There was probably another computer on the subnet with the same IP address. Now this morning I'm starting to get more complaints that the access problem has returned to some degree. Only a few computers in the school can access one of the important programs. Start by looking at what's changed since the system last worked. Did you accidentally break something while trying to fix things yesterday? Do all of the clients know the new address of the server? After that, start working on network troubleshooting. Make sure your underlying communications between the server and clients works. Once you are confident of this, look at software specific problems like record locking. - -- Jim Holthaus (pronunciation: HOLT house) [EMAIL PROTECTED] PGP Public Key at http://www.holthaus.com/jim/pgpkey.html Learn about PGP at http://www.holthaus.com/jim/pgp.html -BEGIN PGP SIGNATURE- Version: PGP 6.5.1 iQA/AwUBOe8u9n3IcJJ+eC/CEQI4OQCgyfdSZ5PZVStjA0MWc4zkUYrsGMsAnAoe eUaqhVeCzzFj/022U/mHeeCR =Zwu6 -END PGP SIGNATURE- Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
Re: [expert] syslog restarts and other wierdness
Jim Holthaus wrote: On Thu, 19 Oct 2000, Mike Rambo wrote: the box refused to start the dhcp server daemon with the error that it couldn't bind to the IP address because it was already in use. There is and was nothing else on the same IP address as the server but the only way I found to resolve that problem was to put the server on a different IP address. That's a wierd one I've never seen before. There was probably another computer on the subnet with the same IP address. That was my first thought. We ended up getting a new hub out of the van and hooking the server up to that hub on the table which went nowhere. Rebooting the server yielded the same results - dhcpd still found the address already in use. We then put the server back into the building network and reset the IP address. After a reboot dhcpd worked fine. We pinged the original IP. Nothing was there. I don't know what this was but it definitely appeared to be something in the server itself to me. Now this morning I'm starting to get more complaints that the access problem has returned to some degree. Only a few computers in the school can access one of the important programs. Start by looking at what's changed since the system last worked. Did you accidentally break something while trying to fix things yesterday? Do all of the clients know the new address of the server? After that, start working on network troubleshooting. Make sure your underlying communications between the server and clients works. Once you are confident of this, look at software specific problems like record locking. The only thing we changed was the server IP address. It appears the last day the server really worked right was three (now four) days ago. At least that was when the complaints started and it coincided with when the log files started to show syslog restarts every 15 seconds or so. We haven't changed anything on the server for almost a month and even then the work was only to install some new software (math blaster or something) in a shared folder. I'll look into the underlying network when I next get out there - we did have a switch go down a couple of weeks ago in another building. Possibility I guess. Thanks for the response. -- Mike Rambo [EMAIL PROTECTED] Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
RE: [expert] syslog restarts and other wierdness
I don't understand, dhcpd should just use the address of the NIC. How does it know "the address is already in use"? Perhaps there is more that one dhcpd running on the box. What does the log file say? What does the output from ifconfig say? What does your dhcpd.conf file say? Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Rambo Sent: Thursday, October 19, 2000 4:37 PM To: [EMAIL PROTECTED] Subject: Re: [expert] syslog restarts and other wierdness Jim Holthaus wrote: On Thu, 19 Oct 2000, Mike Rambo wrote: the box refused to start the dhcp server daemon with the error that it couldn't bind to the IP address because it was already in use. There is and was nothing else on the same IP address as the server but the only way I found to resolve that problem was to put the server on a different IP address. That's a wierd one I've never seen before. There was probably another computer on the subnet with the same IP address. That was my first thought. We ended up getting a new hub out of the van and hooking the server up to that hub on the table which went nowhere. Rebooting the server yielded the same results - dhcpd still found the address already in use. We then put the server back into the building network and reset the IP address. After a reboot dhcpd worked fine. We pinged the original IP. Nothing was there. I don't know what this was but it definitely appeared to be something in the server itself to me. Now this morning I'm starting to get more complaints that the access problem has returned to some degree. Only a few computers in the school can access one of the important programs. Start by looking at what's changed since the system last worked. Did you accidentally break something while trying to fix things yesterday? Do all of the clients know the new address of the server? After that, start working on network troubleshooting. Make sure your underlying communications between the server and clients works. Once you are confident of this, look at software specific problems like record locking. The only thing we changed was the server IP address. It appears the last day the server really worked right was three (now four) days ago. At least that was when the complaints started and it coincided with when the log files started to show syslog restarts every 15 seconds or so. We haven't changed anything on the server for almost a month and even then the work was only to install some new software (math blaster or something) in a shared folder. I'll look into the underlying network when I next get out there - we did have a switch go down a couple of weeks ago in another building. Possibility I guess. Thanks for the response. -- Mike Rambo [EMAIL PROTECTED] Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
RE: [expert] syslog restarts and other wierdness
I don't understand, dhcpd should just use the address of the NIC. How does it know "the address is already in use"? Nope! try setting the ipaddress for DHCPD as .0 example 192.168.20.0 and then set your range to start with your nic address like 192.168.20.20 - 192.168.20.40 Perhaps there is more that one dhcpd running on the box. What does the log file say? What does the output from ifconfig say? What does your dhcpd.conf file say? Only if he has several or virtual address's which will all have to have an entry/declaration even if their not used to give address out. Phil Connor [EMAIL PROTECTED] Registered Linux User #189889 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike Rambo Sent: Thursday, October 19, 2000 4:37 PM To: [EMAIL PROTECTED] Subject: Re: [expert] syslog restarts and other wierdness Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
