IIS Server Dropdout

Discussion in 'Virtual and Cloud Computing' started by Fergal1982, Feb 20, 2009.

  1. Fergal1982

    Fergal1982 Petabyte Poster

    4,196
    172
    211
    We have a VMWare Server running Server 2k3 as a web host. Within IIS, there is a defined website for one of our applications, and an associated Application Pool for the applications under that website.

    This morning (about 30 mins after we told users about the server actually), the server effectively dropped off the radar. Although it was responding to pings, we were unable to use MSTC to connect to it, webpages failed to load/respond, and the performance logs in the VMWare manager dropped to zero for everything (even the 'allocated memory' bar dropped to zero.

    Not sure if its an issue, but the machine performed a snapshot at 1100 (the dropout occurred about 2-3 mins after this).

    After 15 minutes, the server resumed normal operation.

    I cant really seem to see anything that might have caused it. The website is a direct copy of what is currently running on the live (and ancient) box. Do any VMWare gurus have any ideas about how to pin down the error?
     
    Certifications: ITIL Foundation; MCTS: Visual Studio Team Foundation Server 2010, Administration
    WIP: None at present
  2. zebulebu

    zebulebu Terabyte Poster

    3,748
    330
    187
    What version of VMWare are you running (Server 1.x, server 2.0, ESX etc)?
     
    Certifications: A few
    WIP: None - f*** 'em
  3. Fergal1982

    Fergal1982 Petabyte Poster

    4,196
    172
    211
    ESX apparently.
     
    Certifications: ITIL Foundation; MCTS: Visual Studio Team Foundation Server 2010, Administration
    WIP: None at present
  4. Taita

    Taita Nibble Poster

    78
    0
    18
    Don't know anything about this really. But how long does it usually take to do a snapshot?

    If you do another snapshot, does this issue happen again?
     
    Certifications: A+ N+ MCP
    WIP: MCSE
  5. zebulebu

    zebulebu Terabyte Poster

    3,748
    330
    187
    ESX what? You'll have to ask your server guys to be more specific. I've seen plenty of VMs become unresponsive during or after snapshotting. it isn't the wonderful feature VMWare would like you to believe. Its much better in 3.5 than it was prior to this, and there were a lot of bugs fixed by update 2 - so if you're running an older version it would be worth your while telling the infrastructure team to get off their arses and upgrade :)

    I've had a VM unresponsive for 24 hours before after a snapshot wasn't deleted properly when our backup software (ESX Ranger) didn't remove it correctly. The only way I could resolve it was to run a manual delete and reboot the VM from the ESX CLI.
     
    Certifications: A few
    WIP: None - f*** 'em
  6. Fergal1982

    Fergal1982 Petabyte Poster

    4,196
    172
    211
    Ah right, ESX 3.5.0, 110268
     
    Certifications: ITIL Foundation; MCTS: Visual Studio Team Foundation Server 2010, Administration
    WIP: None at present

Share This Page

Loading...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.