Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
06-30-2008, 02:43 PM
|
#1
|
LQ Newbie
Registered: Jun 2008
Posts: 4
Rep:
|
problm in PXE configuration needed for network installation through systemimager
I installed systemimager-4.0.2 and retrieved image from golden client
Installed a pxe-1.4.2
when I ran si_mkbootsever I got the error:
[root@ccpc167 ~]# si_mkbootserver
WARNING: this script may modify the following files:
--> /etc/services
--> /etc/inetd.conf
--> /etc/xinetd.d/tftp
And can restart inetd, xinetd or tftp servers.
Do you wish to continue (y/[n])? y
Ok, continuing...
/var/lib/tftpboot exists and is a symlink to /usr/share/systemimager/boot.
Checking for a tftp server... found.
Checking if tftp server is H. Peter Anvin's tftp server... yup - right on!
Checking for a running inetd... 5471.
Checking for a running xinetd... 18134.
Looking for update-inetd... not found.
Restaring xinetd ...
Stopping xinetd: [ OK ]
Starting xinetd: [ OK ]
done.
Looking for a tftp client... found.
Checking for loopback interface... up.
Does tftp server work... yes.
Looking for a pxe daemon... found.
Backing up /etc/pxe.conf...
Moving /etc/pxe.conf to /etc/pxe.conf.si_mkbootserver.bak36...done.
What network interface should pxe run on? ([eth0])?
Checking to make sure eth0 exists... yeah.
Checking to make sure eth0 is up... yup.
Will the DHCP server be running on this machine? ([y]/n)?
Restarting pxe daemon...
/usr/sbin/si_mkbootserver: line 755: 21690 Segmentation fault /etc/init.d/pxe stop
/usr/sbin/si_mkbootserver: line 755: 21691 Segmentation fault /etc/init.d/pxe start
done.
Checking to see if pxe daemon exited silently... it did.
it looks like pxe is misconfigured.
ERROR: pxe daemon configuration failed
if I manually start PXE daemon I get the error
[root@ccpc167 Desktop]# /etc/init.d/pxe
Segmentation fault
[root@ccpc167 Desktop]# /etc/init.d/pxe restart
Segmentation fault
plz help me out!!!!
|
|
|
06-30-2008, 02:58 PM
|
#2
|
Senior Member
Registered: Jul 2003
Location: Silicon Valley, USA
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
|
What are the contents of /ect/pxe.conf
|
|
|
06-30-2008, 03:16 PM
|
#3
|
LQ Newbie
Registered: Jun 2008
Posts: 4
Original Poster
Rep:
|
my pxe.conf reads:
# ******* PXE CONFIGURATION FILE *******
# Any Line starting with a '#" is treated as a comment line
# and ignored. However, '#' must be the first character on
# a line and no spaces before that are allowed.
# The following entry is the name of the interface on which pxe is going
# to operate. We use this interface to get the ip address automatically.
[Network_Interface_Name]
eth0
# The following entry will be queried if PXE fails to get
# the IP address automatically through 'ifconfig' like code built-in. This
# is only needed if the above interface name is not present in the system
[OurIpAddress]
#192.215.100.202
# This entry shows the base directory of the mtftpd. All file names/paths
# will be relative to this directory. This is the same name that should
# be used as the start up argument to the mtftpd daemon.
[Mtftpd_Root_Directory]
/var/lib/tftpboot
# Set the following entry to 0 if you have a DHCP server running on this
# system.
[UseDHCPPort]
0
# Set the entry below to zero if you don't want this system to act
# as a PXE proxyDHCP
[StartProxy]
1
# Set the entry below to zero if you don't want this system to act as a
# PXE boot server
[startBootService]
1
[MasterProxy]
1
# 0 - broadcast discovery is enabled; 1 - broadcast discovery is disabled
[Discovery_BCast_Disabled]
0
# 0 - multicast discovery is enabled; 1 - multicast discovery is disabled
[Discovery_MCast_Disabled]
0
# Multicast Discovery address. The boot server would listen on this address
# for multicast boot server packets.
[Discovery_MCast_Addr]
224.0.1.2
# Prompt to display on the user screen
# format of this entry: timeout,<string>
[Prompt]
10,Press F8 to view menu ...
# This entry is set to 1 if the client should accept only responses
# from servers in this list
[Discovery_Server_List_Only]
0
# the format of the discovery_list entry is as follows
# type of the server, # of entries, Ip address of each entry
# separated by commas
[Discovery_List]
#3,2,192.215.100.49,192.215.100.99
#65535,1,192.215.100.45
# In some systems, the all '1' broadcast address 255.255.255.255
# won't work as the system will fail with a network unreachable message.
# In those cases, you can use the 'route add -host 255.255.255.255 eth0'
# command to add a route. Or else, you can define the host portion of the
# address alone as '1' in the following entry. This entry is not
# required if your system is set up to transmit
# broadcast packets on 255.255.255.255
[Broadcast_ip_address]
#192.215.100.255
# Architectures supported
# format : <arch-type>,<arch-string>
[PROC_ARCH]
0,X86PC
# Boot server types supported
[Service_Types]
0,BStrap
13,linux-install
# 14,linux-boot
# Menu string that will be displayed on the client screen
# after F8 is pressed.
[X86PC/UNDI/MENU]
0,Local Boot
13,Remote Install Linux
# 14,Remote Boot Linux
# Image file name for Linux install boot server type
# format : <min layer #> <max layer #> <base file name>
[X86PC/UNDI/linux-install/ImageFile_Name]
0
2
linux
# Image file name for Linux boot server type
# format : <min layer #> <max layer #> <base file name>
# [X86PC/UNDI/linux-boot/ImageFile_Name]
# 0
# 2
# linux
# Image file name for BStrap boot server
# format : <min layer #> <max layer #> <base file name>
[X86PC/UNDI/BStrap/ImageFile_Name]
0
0
bstrap
# List of plug-ins. The PXEClientTester is the plug-in that
# validates received packets for PXE compliance. By default, this
# plug-in is DISBALED. Remove the '#" in front of it, if you want
# packet validation to happen
[Parsers]
# PXEClientTester
PxeParser
[Parsers/PxeParser/MainFunction]
PxeParser
[Parsers/PxeParser/DllPath]
/usr/lib/libpxeParser.so
[Parsers/PXEClientTester/MainFunction]
PXEClientTester
[Parsers/PXEClientTester/DllPath]
/usr/lib/libpxeTester.so
# Even if the PXEClientTester is loaded, you still need to
# turn this flag to '1' for packet validation.
[TestOn]
1
# Directory where the results of the packet validation by PXEClientTester
# will be written to. Under this directory, there will be
# sub-directories with the last 8 digits of the MAc address of
# each client.
[TestPath]
/tmp
# Option DLL for BStrap
[X86PC/UNDI/BStrap/Vendor_Dll]
/usr/lib/libBstrapOpts.so
# Fill in a NT server name that will be contacted by the client
# to log back in for APitest
[ServerName]
#vviswana-desk2
# Specify whether the above server is in a domain or a workgroup
[IsDomain]
0
# specify the name of the workgroup or domain of the server
[Domain]
cc
# All debug related stuff here
# If this entry is set to 1, pxe services will write
# more debug info to the system log using syslog()
[DEBUG/PxeServices_DebugOutToWindow_On]
0
# If this entry is set to 1, pxe parser will write
# more debug info to the system log using syslog()
[DEBUG/PxeParsers_DebugOutToWindow_On]
0
# If this entry is set to 1, pxe services will write
# more debug info to the file mentioned
# under the entry [DEBUG/PxeServices_Debug_FileName]
[DEBUG/PxeServices_DebugOutToFile_On]
0
# If this entry is set to 1, pxe parser will write
# more debug info to the file mentioned
# under the entry [DEBUG/PxeParsers_Debug_FileName]
[DEBUG/PxeParsers_DebugOutToFile_On]
0
[DEBUG/PxeServices_Debug_FileName]
/PxeServiceLog.txt
[DEBUG/PxeParsers_Debug_FileName]
/PxeParserLog.txt
[End]
|
|
|
All times are GMT -5. The time now is 02:00 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|