Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
Solved!
Go to SolutionA
ahmed_amin
13 Posts
0
3796
November 26th, 2014 22:00
Rename Networker Server Error
Hi,
I was trying to change the hostname for my Networker server 7.6 SP3 using the EMC atricle 000193979 in the following link:
https://emc--c.na5.visual.force.com/apex/KB_HowTo?id=kA0700000004VwO
I followed the steps exactly and now i'm stuck at Task 2: Step 4. I have changed the hostname in both the local hosts file and DNS and rebooted the server. I was expecting it to automatically create a new client resource in the Networker server with the new hostname.
What happened is that the Networker Backup and Recover service will not start and i opened the daemon.raw file and found the following error:
Networker is unable to continue its startup due to a server hostname change to "%s". Please verify that the server's hostname and it's aliases are properly represented in the local host database (eg. /etc/hosts) and DNS.
I have configured the hosts file correctly and here how it looks like:
127.0.0.1 localhost loopback
#10.70.0.20 original_name.domain.com original_name
10.70.0.20 new_temp_name.domain.com new_temp_name
Also the DNS is resolving the new temp name correctly.
Please advise.
Thanks,
Ahmed
ahmed_amin
13 Posts
1807
0
Posted November 26th, 2014 23:00
Thanks a lot. It works for this step and the Networker Backup and Recover service is now up, but i cannot access the NMC and i get the error:
Problem contacting server new_temp_name.domain.com: Connection reset.
What could be the reason for that?
ahmed_amin
13 Posts
1807
0
Posted November 27th, 2014 00:00
No it's installed on the same machine
Before your reinstall NMC may I suggest that you first try to connect via "http://localhost:9000".
ahmed_amin
13 Posts
1807
1
Posted December 4th, 2014 00:00
I found the solution for the NMC. you must run the command gstconfig from the NMC installation path and the hostname for the NMC will be updated. without that even if you connect with http://localhost:9000 it will not work.
Thanks all for the support
crazyrov
6 Operator
•
1319 Posts
1807
1
Posted November 26th, 2014 22:00
Hi Ahmed,
Have seen this do it more than often. You will have to create the temp client instance manually using the nsradmin command with the NetWorker services down. Or you could put the old name back, create the client instance for the temp name and do the renaming of the server again. I assume you would choose the first option easier i.e. creating the temp client instance using nsradmin, here are the steps.
- assuming you are on windws - nsradmin -d path_where_networker_is_installed/nsr/res/nsrdb
- create type: nsr client; name: new_temp_name; aliases: new_temp_name.domain.com
- yes
- quit
- start the services.