asceticenergy

updated

12 years ago

0

1457

July 21st, 2014 10:00

Symstat froze management server !!

I ran   #symstat -sid xx -i 10 -c 1 -type requests -sa all  on my windows 2003 management server (VM).

After running this command cmd prompt froze and I cant get back into the VM now , its pingable but I think I've messed up something by running the symstat command .

Is tht command appropriate ?

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    765

    0

    Posted July 21st, 2014 10:00

    sorry it's your VM,  symstat has never caused a server to lock up for me.

  • 624

    0

    Posted July 21st, 2014 10:00

    I can see that ECC says "The security event log size(6309) exceeds the limit " . Another peer of mine who was on it was presented with  a blank blue screen  (didn't look like the bsod though )  .

    I have the VM team looking at it now , they haven't rebooted it as yet .

  • 392

    0

    Posted July 21st, 2014 10:00

    Yeah I've notified our clients reg the SE upgrade . we will upgrade soon

  • 765

    0

    Posted July 21st, 2014 10:00

    hey dynamox , thanks .. So this command is absolutely safe to run at anytime rt ?

    I'm kinda freaked out as it froze right after I ran symstat . I'm hoping it doesn't affect anything else .

  • M_Salem

    213 Posts

    765

    0

    Posted July 21st, 2014 10:00


    I agree with dynamox, however, let me ask you have you checked system event logs and storapid/symapi logs after rebooting the machine? Were there BSOD?

    HTH

    Mohammed Salem

  • 624

    0

    Posted July 21st, 2014 10:00

    yeah there is enough free space .  I wasn't redirecting it to a file . Just wanted to view the output in CLI and it didn't go well .

    But its ok to run the symstat at a director level rt ?

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    765

    0

    Posted July 21st, 2014 10:00

    you were not redirecting to a file, were you ? Enough free space in the VM ?

  • M_Salem

    213 Posts

    765

    0

    Posted July 21st, 2014 10:00

    7.2 went EOSL. The minimum supported is SE v7.4.

  • 765

    0

    Posted July 21st, 2014 10:00

    I'm on 7.2.2

  • M_Salem

    213 Posts

    765

    1

    Posted July 21st, 2014 10:00

    I am aware of a couple of similar issues  (not really with symstat. It is with the SE daemon) with very old SE releases like 6.x.. These versions went EOSL so if you are running SE 7.x (and you should!) then I doubt the issue is SE related.

    HTH

    Mohammed Salem