Please could someone assist here! I can find anyone on other mailing lists who knows. On Tuesday 31 August 2004 01:08, Heinz Meulke wrote:
On Mon, 2004-08-30 at 12:57, Chadley Wilson wrote:
Greetings
I urgently need some advise My nfs server is failing to start It has something to do with the exports file. If the exports file is empty nfs starts. If it has and entry it won't I have restarted portmap and nfs several times. I have also started nfs then exported the files with exportfs -r but that also hangs.
What can be done to find the root of this evil?
check /var/log/messages
nfs logs any error messages
also check /var/log/dmesg
I am not getting any problems from my logs at all, The strange thing here is that if I run "service named stop" then nfs works. I manufacture PCs and you will be happy to know that I have already built approx 4000 systems loaded with FC1 / 2 Linux this year. To speed up the installations via the network I setup a dns server and a dhcp to assign IPs and host names to the computers. The problem I am faced with is possibly a config problem in my dhcp file. The server is not assigning the host names, I also can't use mac address statements because the PCs are always new. In other words I want the dhcp to assign an IP on a random basis, if for example the IP is 192.168.2.1 then make that PCs hostname station1.domainname. If a PC is unplugged from the network then it must make that IP immediatley available again. Here is my dhcpd.conf file could someone please give me a hint: +++++++++++++++++++++++++++++++++++++++++++++++ ddns-update-style ad-hoc; default-lease-time 30; # 30 seconds max-lease-time 7200; # 2 hours option domain-name "teq.pinteq"; option domain-name-servers 192.168.2.1; option broadcast-address 192.168.2.255; option routers 192.168.2.1; option subnet-mask 255.255.255.0; subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.10 192.168.2.50; } +++++++++++++++++++++++++++++++++++++++++++++++++++ -------------------------------------------------------
On Tuesday 31 August 2004 15:03, Chadley Wilson wrote:
I am not getting any problems from my logs at all,
The strange thing here is that if I run "service named stop" then nfs works.
I manufacture PCs and you will be happy to know that I have already built approx 4000 systems loaded with FC1 / 2 Linux this year. To speed up the installations via the network I setup a dns server and a dhcp to assign IPs and host names to the computers. The problem I am faced with is possibly a config problem in my dhcp file. The server is not assigning the host names, I also can't use mac address statements because the PCs are always new. In other words I want the dhcp to assign an IP on a random basis, if for example the IP is 192.168.2.1 then make that PCs hostname station1.domainname. If a PC is unplugged from the network then it must make that IP immediatley available again.
Here is my dhcpd.conf file could someone please give me a hint:
+++++++++++++++++++++++++++++++++++++++++++++++ ddns-update-style ad-hoc; default-lease-time 30; # 30 seconds max-lease-time 7200; # 2 hours
option domain-name "teq.pinteq"; option domain-name-servers 192.168.2.1; option broadcast-address 192.168.2.255; option routers 192.168.2.1; option subnet-mask 255.255.255.0;
subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.10 192.168.2.50; } +++++++++++++++++++++++++++++++++++++++++++++++++++
------------------------------------------------------- This is ridiculous; OK so I decided to setup http based installations out of desperation, I copied the install dir fc1 to my http folder . I forgot to edit the ks.cfg (kickstart file) which is set to nfs, the line is: nfs --server=192.168.2.1 --dir=/fc1
Booting from cdrom I use the option: linux ks=http://192.168.2.1/fc1/ks.cfg and then it mounts my nfs share /fc1 and the install rocks on. So I figured that nfs has mysteriously decided to work so I try linux ks=nfs:192.168.2.1:/fc1/ks.cfg and it fails to mount the share. So I know it is a problem between named and dhcp but what is the problem. Please can someone give me a clue PS:clues do not include man pages or google I have read and can't see the light.
Chadley Wilson wrote:
<SNIP>
Here is my dhcpd.conf file could someone please give me a hint:
+++++++++++++++++++++++++++++++++++++++++++++++ ddns-update-style ad-hoc; default-lease-time 30; # 30 seconds max-lease-time 7200; # 2 hours
option domain-name "teq.pinteq"; option domain-name-servers 192.168.2.1; option broadcast-address 192.168.2.255; option routers 192.168.2.1; option subnet-mask 255.255.255.0;
subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.10 192.168.2.50; } +++++++++++++++++++++++++++++++++++++++++++++++++++
-------------------------------------------------------
<SNIP>
You're providing a domain name in DHCP. Is this domain properly set up in DNS? I would be interested in seeing the zone file for this domain as well as named.conf. I think your machine has an identity crisis ;-) Louis
On Tuesday 31 August 2004 13:19, Louis Richards wrote:
Chadley Wilson wrote:
<SNIP>
Here is my dhcpd.conf file could someone please give me a hint:
+++++++++++++++++++++++++++++++++++++++++++++++ ddns-update-style ad-hoc; default-lease-time 30; # 30 seconds max-lease-time 7200; # 2 hours
option domain-name "teq.pinteq"; option domain-name-servers 192.168.2.1; option broadcast-address 192.168.2.255; option routers 192.168.2.1; option subnet-mask 255.255.255.0;
subnet 192.168.2.0 netmask 255.255.255.0 { range 192.168.2.10 192.168.2.50; } +++++++++++++++++++++++++++++++++++++++++++++++++++
-------------------------------------------------------
/etc/exports: /fc1 192.168.2.0/255.255.255.0(ro,sync,no_root_squash) =========================================== /etc/named.conf options { directory "/var/named"; }; zone "localhost" IN { type master; file "localhost.zone"; allow-update { none; }; }; zone "0.0.127.in-addr.arpa" IN { type master; file "named.local"; allow-update { none; }; }; zone "teq.pinteq" IN { type master; file "pinteq.zone"; }; zone "2.168.192.in-addr.arpa" IN { type master; file "pinteq.rev"; }; =============================== /var/named/pinteq.zone: $TTL 86400 @ SOA preload.teq.pinteq. root.preload.teq.pinteq. ( 200408290 ;serial 28800 ;Refresh 14400 ;Retry 3600000 ;Expire 0) ;Negative @ IN NS preload.teq.pinteq. @ IN A 192.168.2.1 preload.teq.pinteq. IN A 192.168.2.1 www IN A 192.168.2.1 ftp IN A 192.168.2.1 teq2.pinteq IN A 192.168.2.1 chadlin.teq.pinteq. IN A 192.168.2.2 peter.teq.pinteq. IN A 192.168.2.3 pinpreload.teq.pinteq. IN A 192.168.2.4 testbench01.teq.pinteq. IN A 192.168.2.10 testbench02.teq.pinteq. IN A 192.168.2.11 testbench03.teq.pinteq. IN A 192.168.2.12 testbench04.teq.pinteq. IN A 192.168.2.13 testbench05.teq.pinteq. IN A 192.168.2.14 testbench06.teq.pinteq. IN A 192.168.2.15 snipped =================================== /var/named/pinteq.rev $TTL 86400 @ IN SOA preload.teq.pinteq. root.preload.teq.pinteq. ( 4 10800 3600 604800 86400 ) @ IN NS preload.teq.pinteq. 1.2.168.192.IN-ADDR.ARPA. IN PTR preload.teq.pinteq. 1.2.168.192.IN-ADDR.ARPA. IN PTR ftp.teq.pinteq. 1.2.168.192.IN-ADDR.ARPA. IN PTR www.teq.pinteq. 1.2.168.192.IN-ADDR.ARPA. IN PTR teq2.pinteq. 2.2.168.192.IN-ADDR.ARPA. IN PTR chadlin.teq.pinteq. 3.2.168.192.IN-ADDR.ARPA. IN PTR peter.teq.pinteq. 4.2.168.192.IN-ADDR.ARPA. IN PTR pinpreload.teq.pinteq. 10.2.168.192.IN-ADDR.ARPA. IN PTR testbench01.teq.pinteq. 11.2.168.192.IN-ADDR.ARPA. IN PTR testbench02.teq.pinteq. 12.2.168.192.IN-ADDR.ARPA. IN PTR testbench03.teq.pinteq. 13.2.168.192.IN-ADDR.ARPA. IN PTR testbench04.teq.pinteq. 14.2.168.192.IN-ADDR.ARPA. IN PTR testbench05.teq.pinteq. 15.2.168.192.IN-ADDR.ARPA. IN PTR testbench06.teq.pinteq. 16.2.168.192.IN-ADDR.ARPA. IN PTR testbench07.teq.pinteq. 17.2.168.192.IN-ADDR.ARPA. IN PTR testbench08.teq.pinteq. ================================================= Have a look at these and see.
You're providing a domain name in DHCP. Is this domain properly set up in DNS?
I would be interested in seeing the zone file for this domain as well as named.conf.
I think your machine has an identity crisis ;-)
Louis
-- Chadley Wilson Production Line Supervisor Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
Chadley Wilson wrote:
Have a look at these and see.
You're providing a domain name in DHCP. Is this domain properly set up in DNS?
I would be interested in seeing the zone file for this domain as well as named.conf.
I think your machine has an identity crisis ;-)
Louis
My thoughts of an identity crisis may not have been far off. There were multiple entries for the same address in both the forward and reverse files. I also would suggest removing "teq2.pinteq". This would be another domain in another zone file. Back up your original files and try with these. =============================== /var/named/pinteq.zone: $TTL 86400 teq.pinteq IN SOA preload.teq.pinteq. root.preload.teq.pinteq. ( 200408310 ;serial 28800 ;Refresh 14400 ;Retry 3600000 ;Expire 0) ;Negative NS preload.teq.pinteq. $ORIGIN ldrinteractive.com. preload A 192.168.2.1 www CNAME preload ftp CNAME preload chadlin A 192.168.2.2 peter A 192.168.2.3 pinpreload A 192.168.2.4 testbench01 A 192.168.2.10 testbench02 A 192.168.2.11 testbench03 A 192.168.2.12 testbench04 A 192.168.2.13 testbench05 A 192.168.2.14 testbench06 A 192.168.2.15 =================================== /var/named/pinteq.rev $TTL 86400 2.168.192.in-addr.arpa IN SOA preload.teq.pinteq. root.preload.teq.pinteq. ( 200408310 10800 3600 604800 86400 ) NS preload.teq.pinteq. $ORIGIN 50.168.192.in-addr.arpa. 1 PTR preload.teq.pinteq. 2 PTR chadlin.teq.pinteq. 3 PTR peter.teq.pinteq. 4 PTR pinpreload.teq.pinteq. 10 PTR testbench01.teq.pinteq. 11 PTR testbench02.teq.pinteq. 12 PTR testbench03.teq.pinteq. 13 PTR testbench04.teq.pinteq. 14 PTR testbench05.teq.pinteq. 15 PTR testbench06.teq.pinteq. 16 PTR testbench07.teq.pinteq. 17 PTR testbench08.teq.pinteq. HTH Louis
On Tuesday 31 August 2004 18:58, Louis Richards wrote:
Chadley Wilson wrote:
Have a look at these and see.
You're providing a domain name in DHCP. Is this domain properly set up in DNS?
I would be interested in seeing the zone file for this domain as well as named.conf.
I think your machine has an identity crisis ;-)
Louis
My thoughts of an identity crisis may not have been far off. There were multiple entries for the same address in both the forward and reverse files. I also would suggest removing "teq2.pinteq". This would be another domain in another zone file.
Hi Louis and fellow SUSErs Firstly thank you! Just one question? My network is internal with no internet access (www), do I need the $ORIGIN statement and if so, why?
Back up your original files and try with these.
=============================== /var/named/pinteq.zone:
$TTL 86400 teq.pinteq IN SOA preload.teq.pinteq. root.preload.teq.pinteq. ( 200408310 ;serial 28800 ;Refresh 14400 ;Retry 3600000 ;Expire 0) ;Negative
NS preload.teq.pinteq. $ORIGIN ldrinteractive.com.
preload A 192.168.2.1 www CNAME preload ftp CNAME preload chadlin A 192.168.2.2 peter A 192.168.2.3 pinpreload A 192.168.2.4 testbench01 A 192.168.2.10 testbench02 A 192.168.2.11 testbench03 A 192.168.2.12 testbench04 A 192.168.2.13 testbench05 A 192.168.2.14 testbench06 A 192.168.2.15
=================================== /var/named/pinteq.rev $TTL 86400 2.168.192.in-addr.arpa IN SOA preload.teq.pinteq. root.preload.teq.pinteq. ( 200408310 10800 3600 604800 86400 )
NS preload.teq.pinteq. $ORIGIN 50.168.192.in-addr.arpa.
1 PTR preload.teq.pinteq. 2 PTR chadlin.teq.pinteq. 3 PTR peter.teq.pinteq. 4 PTR pinpreload.teq.pinteq. 10 PTR testbench01.teq.pinteq. 11 PTR testbench02.teq.pinteq. 12 PTR testbench03.teq.pinteq. 13 PTR testbench04.teq.pinteq. 14 PTR testbench05.teq.pinteq. 15 PTR testbench06.teq.pinteq. 16 PTR testbench07.teq.pinteq. 17 PTR testbench08.teq.pinteq.
HTH Louis
-- Chadley Wilson Production Line Supervisor Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
Chadley Wilson wrote:
<SNIP>
Hi Louis and fellow SUSErs Firstly thank you! Just one question? My network is internal with no internet access (www), do I need the $ORIGIN statement and if so, why?
Well ... you certainly don't need the ones I put in there. ;-) When I made the changes to the files, part of what I did was to copy and paste from a known working setup. I must be getting old. I forgot to edit the $ORIGIN lines in *both* zone files. Change the forward to: $ORIGIN teq.pinteq. And the reverse to: $ORIGIN 2.168.192.in-addr.arpa. HTH, Louis P.S. Once you get this up and running, backup these files as well as your dhcpd.conf file. Read the man page for dhcpd.conf and scroll down to the "Dynamic DNS Updates" section. Then you don't have to enter all those workstation addresses manually.
On Wednesday 01 September 2004 16:41, Louis Richards wrote:
Chadley Wilson wrote:
<SNIP>
Hi Louis and fellow SUSErs Firstly thank you! Just one question? My network is internal with no internet access (www), do I need the $ORIGIN statement and if so, why?
Well ... you certainly don't need the ones I put in there. ;-)
When I made the changes to the files, part of what I did was to copy and paste from a known working setup. I must be getting old. I forgot to edit the $ORIGIN lines in *both* zone files.
Change the forward to: $ORIGIN teq.pinteq.
And the reverse to: $ORIGIN 2.168.192.in-addr.arpa.
Aha now I understand ! -- Chadley Wilson Production Line Supervisor Pinnacle Micro Manufacturers of Proline Computers ==================================== Exercise freedom, Use LINUX =====================================
participants (2)
-
Chadley Wilson
-
Louis Richards