This post is more than 5 years old
80 Posts
0
1372
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 ?
No Events found!
dynamox
9 Legend
•
20.4K Posts
0
July 21st, 2014 10:00
sorry it's your VM, symstat has never caused a server to lock up for me.
asceticenergy
80 Posts
0
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 .
asceticenergy
80 Posts
0
July 21st, 2014 10:00
Yeah I've notified our clients reg the SE upgrade . we will upgrade soon
asceticenergy
80 Posts
0
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
0
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
asceticenergy
80 Posts
0
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
9 Legend
•
20.4K Posts
0
July 21st, 2014 10:00
you were not redirecting to a file, were you ? Enough free space in the VM ?
M_Salem
213 Posts
0
July 21st, 2014 10:00
7.2 went EOSL. The minimum supported is SE v7.4.
asceticenergy
80 Posts
0
July 21st, 2014 10:00
I'm on 7.2.2
M_Salem
213 Posts
1
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
asceticenergy
80 Posts
0
July 21st, 2014 12:00
The VM cambe back on its own , the symcli session terminated itself .
asceticenergy
80 Posts
0
July 24th, 2014 07:00
Does GPO play any role in upgrading SE ?
I was proposing an upgrade to my client to upgrade SE to 7.6.1 .. and the response was "someone changed the GPO "
Is he referrning to the Group policy objects or is it something else in the storage world ?
dynamox
9 Legend
•
20.4K Posts
0
July 24th, 2014 07:00
group policy object, can do a lot of stuff to a windows box. I would still schedule the time and upgrade to the latest SE. In addition to new features there were some serious OpenSSL fixes (yes even on Windows), update will not hurt.
dynamox
9 Legend
•
20.4K Posts
2
July 24th, 2014 08:00
there you go
1 Attachment
docu52739_Solutions-Enabler-Version-7.6.2-Release-Notes.pdf
asceticenergy
80 Posts
0
July 24th, 2014 08:00
ok cool will schedule an upgrade .
Do you have the latest SE release notes with you please ?
My powerlink profile is messed up and they cant seem to fix it . I always get a not authorized message to certain links .