Hi John:

Okay so I don't think it has to do with DHCP (I checked the conf file and it looks fine).

Yes I have definitely seen this problem before, the hard part now is figuring out what I did to fix it :-)

You don't really need to touch the pxeboot.0 fine.

This definitely have to do with the way OSCAR is passing information to Systemimager, right now off the top of my head is to check the outputs of mksimachine and /etc/hosts, if you can post those, maybe they will give us some hints as to what is going on.

Basically I think somewhere you have:

oscarnode2.blah.blah oscarnode2.blah1.blah1

or something like that, and Systemimager just parses that line but parsed it 'incorrectly', therefore it generated the output:

oscarnode2
oscarnode2.sh

Just need to figure out which file that is...

Cheers,

Bernard

[EMAIL PROTECTED] wrote:

It's attached.  I didn't modify it.  What seems to be happening is the
filenames that systemimager is using for its rsync commands are wrong.  I
ran the commands from the # prompt using the scriptname.sh name rather
than just scriptname and then executed the script that was copied
over...and it installed fine.  If I can figure out where the systemimager
is getting the commands, I can probably fix it.  The pxeboot.0 file is not
text so if that's the file I have to edit I'll need to figure out how.

Any info is appreciated...

John


Hi John:

I remember I encountered this problem before, but can't remember exactly
what I did to fix the problem.

Did you by any chance manually modify the /etc/dhcpd.conf file?

I think it has to do with having multiple domain-name entries for your
nodes, perhaps you can attach your /etc/dhcpd.conf and I can take a look.

Cheers,

Bernard

[EMAIL PROTECTED] wrote:


I'm having problems installing the client nodes.  They start the PXE
boot,
but then fail after "I will now try to get the autoinstall script:
oscarnode2
oscarnode2.sh
[: oscarnode2.sh: unknown operand
rsync -aL 192.168.30.1::scripts/oscarnode2
oscarnode2.sh /scripts
link_stat /oscarnode2 : No such file or directory
client: nothing to do: perhaps you need to specify some filenames or the
--recursive option?
rsync error: some files could not be transferred (code 23) at
main.c(636)

etc...

oscarnodes are at 192.168.30.2/16 and up. headnode is at 192.168.30.1.

I end up a at a # prompt.  I can see in the rsync log on my headnode
that
rsync is communicating with the client.  I'm running a RH9 headnode with
OSCAR 2.3.1.  The /var/lib/systemimager/scripts/oscarnode2.sh link is
there...I'm really at a loss for what's going wrong or how to fix it.
Any
ideas are welcome.  If there are any additional sites (other than those
mentioned on the main site) that you suggest for more info, please send
them.

Thanks,

John


------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Oscar-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-users




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users





-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Oscar-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-users

Reply via email to