[prev in list] [next in list] [prev in thread] [next in thread] 

List:       npaci-rocks-discussion
Subject:    Re: [Rocks-Discuss]Frontend network install gives "service busy"
From:       "Greg Bruno" <greg.bruno () gmail ! com>
Date:       2006-03-31 14:49:48
Message-ID: e572dbf60603310649k531c3847o1863eb5d626c357 () mail ! gmail ! com
[Download RAW message or body]

On 3/31/06, Eirik Thorsnes <eirik.thorsnes@bccs.uib.no> wrote:
> I have problem doing a frontend network install (from a 4.1 i386 central
> to 4.1 x86_64 if that matters). After starting insert-access --all on
> central and booting the new frontend with x86_64 base+kernel CD, I get
> to see the certificate of the central on the new frontend (but no
> information in the insert-access window).
> Upon pressing "proceed" I get an error message on the new frontend that
> it will retry getting kickstart file in X seconds. The ssl_access_log
> has 503 - service busy error for the URL
> /install/sbin/wan/public/kickstart.cgi?arch=x86_64&np=2&project=rocks
>
> Trying the https://central-fqdn/install/sbin/wan/public/kickstart.cgi
> URL in a regular browser on my desktop gives the same service busy error
> (as long as insert-access is running).
>
> Is there any additional logging from the kickstart.cgi program (except
> httpd access and error logs)?
> Is the problem the mix of i386 and x86_64?
> I did input the x86_64 rolls and OS discs on the central using the
> procedure in
> http://www.rocksclusters.org/rocks-documentation/4.1/cross.html.

on the central server, try resetting the rocks kickstart service:

    # service rocks-kickstart restart

then try to install your frontend.

on a related note, this issue has been addressed and will be fixed in
the next release.

 - gb

[prev in list] [next in list] [prev in thread] [next in thread]