Unsolved
This post is more than 5 years old
14 Posts
0
7273
September 23rd, 2014 04:00
Networker 8.1117 NMC problem: gstd.exe service don't start after mmrecov
Hello,
I'm doing some recovery tests. We have Networker 8.1117 on Windows 2008 R2 sever.
For recovery tests, I have installed networker on my test server on the same version than my production one. It was running fine, I was able to access the NMC without problem.
So I have start my recover just as I was doing with Networker 7.6 :
Load my tape without mounting, run a scanner -B \\.\Tape0\ to get the bootstrap id and the file number.
Run the "mmrecov" to restore the "res" folder
Then I have stopped the networker services, renamed the original "res" folder as "res.old" and the "res.R" as "res"
An finally restart the Networker services.
But this time the "EMC GST Service" failed to start. So the Management Console is not available.
Networker is running fine. I was able to recreate my index using "nsrck -L7" command and I am able to restore data using Networker Client.
I have tried to remove and reinstall the NMC but I still have the same problem.
I have tried to upgrade networker to version 8.1118 : no change.
When I run the gstd.exe program and the apache server on dos windows it works... but they failed to start as services.
Any idea ?
bingo.1
2.4K Posts
0
September 23rd, 2014 09:00
Yes - for debug mode simply run "gstd -D#". Start with D2 and increase it until you see a valuableinfo.
Do not forget that you should first make sure that you "Screen Buffer Size - Height" for the Command Prompt windows can take huge amount of messages.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 23rd, 2014 11:00
I think old debug method still might work: gstd -D9 1>gstd.log 2>&1 (then open another cmd to view the log)
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 23rd, 2014 11:00
I can't see why if you would have fresh NMC unless your NMC DB is located under res (custom setting) and in that way might be affected by DR. However, that should still not affect startup of fresh new NMC which has no idea about NSR db on that box.
CarlosRojas
1.7K Posts
0
September 23rd, 2014 23:00
Hi pclement
This could be also a peer information related issue.
Have you tried removing the peer information on NW and NMC servers?
To do it so run these commands:
on NW server:
nsradmin -p nsrexec
nsradmin>. type: nsr peer information
nsradmin>delete
(if there are not too many clients delete all, but if there are then run this command instead of delete):
nsradmin>delete name:NMC_SERVER_NAME
delete?y
nsradmin>quit
Now run on NMC server:
nsradmin -p nsrexec
nsradmin>. type: nsr peer information
nsradmin>delete
delete?y
nsradmin>quit
Type "y" as many times as peer information you have.
Anyway, using debug will definitely help you to get to the root cause, so please follow the advice already given.
Thank you,
Carlos
CarlosRojas
1.7K Posts
0
September 24th, 2014 04:00
Hi pclement
Did you try deleting the peer information and then try to start the service normally?
On the other hand, please start the service and check if you can open NMC, if you cannot, then in the window where you started the service from, copy all the output and save as gstd.raw, then render it and check the output, that should indicate you where the problem is (or any other underlying problems).
Thank you,
Carlos
pclement
14 Posts
0
September 24th, 2014 04:00
I have tested the variation 1 (stop gstd service before running nsrdr...) -> Same problem when I want to restart it.
About the debug option, I can run gstd in debug mode in a console window, but, as I told you before, in a console it works ! So it creates a nice log but I can't find my problem in... Is there a way to force te gstd service in debug mode ?
pclement
14 Posts
0
September 24th, 2014 05:00
Carlos,
I have deleted all the peer informations, but anyway my NMC is on my NW server.... No change on my problem.
Finally I have found in the NW admin documentation the way to force the debug mode for gstd service : GST_DEBUG in environment variables. But nothing change... The service does not start at all.
pclement
14 Posts
0
September 24th, 2014 06:00
Solved !
I have looked back the problem from the begining: the key was the timeout (Event ID: 7009 in windows even viewver). So I have search at microsoft how to increase this timeout...
I found the solution at http://support.microsoft.com/kb/922918
I created the "ServicesPipeTimeout" entry in the registery, set the value to "60000" (60 seconds instead of 30 s). Reboot the server, and IT WORKS ! !
Thanks guys, Sorry for the time lost. I had doubt on Networker, and the weak link was Windows...
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 24th, 2014 13:00
So how does the res story fit then?
bingo.1
2.4K Posts
0
September 25th, 2014 00:00
IMHO the size does not really matter.
And you must be very specific when you talk about the resource directories.
We are running NW 8.1.1.4 on Win2008R2 with about 600 client resources. Our /nsr/res directory is about 1GB in size.
However, the /nsr/res/jobsdb alone keeps 775MB (we keep entries for 30 days) followed by /nsr/res/statistics (240MB).
/nsr/res/nsrdb only uses 4.2MB, /nsr/res/nsrladb is 2.9MB in size.
pclement
14 Posts
0
September 25th, 2014 00:00
well, I think it's just a queston of size... The restored res weight is 60 MB while the installed original is only 400KB. I never faced this problem when my server (the same box) was running Win2003 and Networker 7.6, but maybe the startup timing was not limited to 30 seconds on Win2003.
pclement
14 Posts
0
September 25th, 2014 02:00
Yes Bingo, sure, 60 MB (mainly statistics in our case) is not a big deal... But on our DR Test server, it seems that it made the difference on the gstd service start speed.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
September 25th, 2014 03:00
That's what most men say
bingo.1
2.4K Posts
1
September 25th, 2014 05:00
Hi Hrovje - of course I expected such comment.
Wait until we'll meet us again ... LOL