Bug 78155 - pxe daemon crashes after each request
pxe daemon crashes after each request
Product: Red Hat Linux
Classification: Retired
Component: pxe (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2002-11-19 09:56 EST by Tim Verhoeven
Modified: 2007-04-18 12:48 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-01 15:48:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Verhoeven 2002-11-19 09:56:05 EST
Description of problem:
The pxe daemon will crash each time after it has served a request to a client.
Tested with multiple clients. There is no information in the logs.

Version-Release number of selected component (if applicable): pxe-0.1-

How reproducible:

Steps to Reproduce:
1.service pxe start -> OK
2.let client start using pxe
3.service pxe status -> pxe dead but pid file exists

Actual Results:  pxe process is gone, but pid file still exists.

Expected Results:  pxe process should still be running.

Additional info:

The server is a IBM xSeries 230. The clients are IBM Thinkpads and Blades. The
server with the pxe daemon has all updates on it.
Comment 1 Joe Orton 2002-12-09 11:44:01 EST
I've seen the daemon crashing regularly with the 8.0 pxe package too.
Comment 2 Elliot Lee 2002-12-10 15:53:36 EST
If you could use 'tcpdump -w badpxe.packets' to capture the network traffic that causes the 
problem, and then attach that file to this bug report, that would help immensely.
Comment 3 Tim Verhoeven 2002-12-11 06:52:18 EST
I've just tried it on our regular network but the daemon didn't crash. I'll have
to reconstructed a private LAN where I can run the Red Hat dhcp daemon.

I'll let you know as soon as I have some time to set it all up.

Note You need to log in before you can comment on or make changes to this bug.