PDA

View Full Version : Server is "stuck" - how to force removal??


andybrucenet
12-12-2011, 07:53 AM
Hi Forum,

I am just trying to add a new server to a test grid. I set the server up for PXE boot and it Booted Fine into the inventory image and that the server showed up in the BFC server list. I went into my test grid configuration (within the BFC UI) and modified my "Target Servers" to be 2 instead of 1. I then saw the new server was rebooted and had the standard boot system deployed to it. I walked away from the server for a while and came back to a screen that continually displayed the word "GRUB" thousands of times. Hmm. That's not good!

In the BFC, the server status "Deploying image to host". What I want to do is pull this server out of the grid and the BFC! However, everytime I try to do this I get:

"Operation denied because the server is busy or is in use.
No further details available."

In my test grid, I am unable to force a removal of that grid. In fact, from a grid shell "srv list" returns only the single server that I already had in the grid.

As a matter of interest, would 3tctl help here? I can't find any documentation on this command.

PeterNic
12-13-2011, 05:14 PM
Andy,

I think the grid doesn't yet know the server will become part of it, which is why it is showing only 1 server in "srv list". Once BFC completes the imaging and preparation to the server, it will tell AppLogic that the server should be part of it. (The consequence is that 3tctl or any other grid controller command or utility will not help, this should be resolved in the fabric controller first.)

I will forward this to a BFC team member. If this issue is urgent, please contact support. (Also, please IM me your contact info so if someone needs to contact you, they will know how - thanks!)

Best regards,
- Peter

BobH
12-14-2011, 06:29 AM
Andy,

In 3.0, we have a two-hour timeout when a server is being booted into a grid due to some issues with ESX. At the end of that timeout, the server should fail. You can then select it and remove it via the grid actions menu (be sure to select the "force removal" flag). Like Peter said, the grid does not know about this server yet as we are not done imaging the box and have not handed it to the grid yet.

Definitely let us know if you are unable to remove this server once it has failed.

Bob

tonyjun
12-17-2011, 10:28 AM
I has same case:confused: