Can't get NetBoot service started.

[haggan]

I was playing around with the NetSUS today, it looks really great. But... I can't seem to get the NetBoot service started in the sense that the green light never turns on, stays red which I assume mean the service is not running.

I trashed my installation and made it all over again, same thing happens. I've been trying the setup in both Virtual Box 4.1.2 and VMware Fusion 3.1.2.

NetSUS let me choose the newly created .nbi, and I can add subnet, but when I press "Enable Netboot" nothing happens.

Any ideas? I was thinking maybe there is a terminal command you can use verbose to see what really happens under the shell.

Cheers
Matt

[jarednichols]

Two things:
1. Are there spaces in your NetBoot .nbi image? If so, it doesn't support them. You'll need to remove them.
2. I forgot to add a subnet in the settings initially and ran into the exact same thing. So, make sure you've got the subnet the server sits on defined there.

[haggan]

Hi, thanks for quick reply

1. No space in either .nbi or .dmg within
2. Im adding subnet in the form of xxx.xxx.xxx.0/24 255.255.255.0. I tried adding just an IP, i tried without IP, the result is the same though.

[aurica]

It appears that the NetSUS doesn't like underscores in the .nbi file name either. I fixed mine by renaming the .nbi in /srv/NetBoot/NetBootSP0/ and editing the Name string in it's NBImageInfo.plist to match.

[jarednichols]

Interesting. I've used underscores without an issue.

[yadin]

I'd love to know how you put in the syntax of the subnet in the end to get this working. I can't get the netboot service to start, as you say the button does nothing, the light stays red. The apache2 log tells me what the UI fails to, that it doesn't like the syntax in some way, but I can't figure out what it does want. The UI should be telling me what format to use, and kick back errors explaining why it's doing nothing, and the documentation should say what format to use as well. I know it's free, but this is pretty poorly put together and apparently has zero updates so the longevity seems highly questionable.

This thing desperately needs an update with bug fixes like above, good complete documentation, Ubuntu 12 LTS based, and a VHD format for download (converting from vmdk to vhd was insane...)