| Click here to select a new forum. |
| For the record: Mac OS X Server 1.0 (Rhapsody) NetworkManager and HDNamer segfaults/sigbuses |
Posted by: cheesestraws on 2025-04-16 09:31:39
Indications:
- Fresh install of Mac OS X Server 1.x ("Rhapsody"). This does not apply to 10.x.
- When you try to run NetworkManager or HDNamer, they just die and dump you back to Workspace Manager.
- In the console (from the Workspace manager's Tools menu), you see these are from bus errors.
- During the Setup Assistant, you chose to obtain network information automatically (using BOOTP).
Solution:
- BOOTP seems to be broken. Rerun the Setup Assistant (in /System/Administration/Assistant.app) and set up a static IP and static router, then restart.
|
Posted by: adespoton on 2025-04-16 10:11:02
Is this specific to any particular hardware? Or does it look like this is the case for any PCI Power Mac that can run Rhapsody?
I've never seen this myself, as I always use a static IP and gateway. |
Posted by: cheesestraws on 2025-04-16 10:59:23
I don't know, I've only got one PCI machine with it on! But it was totally consistent for me across multiple installations on that hardware. Since the network driver abstraction layer is pretty decent, I'd expect it to be true across multiple hardware platforms. |
Posted by: lauland1 on 2025-05-14 06:27:39
I have it on a 7600 and haven't seen this. Might look in the system logs and see if more info on what it was doing before it crashed. Might also run one of them in gdb and could see where the crash is. |
Posted by: cheesestraws on 2025-05-14 06:37:17
I have it on a 7600 and haven't seen this. Might look in the system logs and see if more info on what it was doing before it crashed.
What BOOTP server are you using? I wouldn't rule out that mine is doing something wonky, since I didn't set it up for this.
Might also run one of them in gdb and could see where the crash is.
I'm afraid my dedication to the cause of finding stuff out was insufficient to crack out gdb, and I just gave it a static IP address in my static range instead... |
Posted by: lauland1 on 2025-05-14 08:13:33
Ah...sorry, I meant to specify that like adespoton, I just use static settings and have never tried BOOTP.
So, you are likely correct, in that it is broken.
Also, not that it matters, but it is on a B&W g3. I have an older pre-mosxs Rhapsody on my 7600. |
Posted by: cheesestraws on 2025-05-14 08:27:40
Ah, I misunderstood, I thought you had it working with BOOTP.
And yeah, I don't think this is worth spending a lot of time on - it may simply be broken. Just wanted to document it somewhere people could find it. |
Posted by: CC_333 on 2025-05-29 10:45:22
Why are you using BOOTP? Isn't DHCP an option, or does Server 1.x predate that particular feature?
Or do you have a specific need for it? You seem to know much more about networking than I do, so I'm sure you have your reasons....
c |
Posted by: cheesestraws on 2025-05-30 10:32:28
Isn't DHCP an option, or does Server 1.x predate that particular feature?
As far as I can see, BOOTP is the only option available. Which would be fine if it worked 🙂 |
Posted by: CC_333 on 2025-05-30 11:26:09
As far as I can see, BOOTP is the only option available. Which would be fine if it worked 🙂 Interesting.
c |
| 1 |