Quantcast
Channel: VMware Communities : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 180259

VDP not usable after reboot

$
0
0

Hi to everyone

I need some help to regain access to my VDP appliance.

Environment:

vCenter server 5.1 listening to port 444

ESXi hosts 5.0 build 623860

VDP appliance 5.1.1

 

After first installation the backup job runs with no issues, but I cannot access file level restore web client with error "Login failed. HostSession is NULL"

I tried both with domain administrator account (used during appliance registration) and with SSO admin account (SYSTEM-DOMAIN\admin).

 

 

After a reboot I cannot access the VDP appliance at all from vsphere web client. If I try to login I am presented with the following pop-up:

 

 

"The VDP appliance is not responding. Please try your request again.

Would you like to be directed to the VDP configuration screen to troubleshoot the issue?"

 

Then I tried to re-register the appliance, but nothing changes.

 

Accessing the appliance through ssh, I sniffed some packets and noticed that I see traffic to the vcenter server on port 443 instead of 444 as expected (please note that before the reboot traffic was correctly sent to port 444):

 

 

root@dataprotection:~/#: tcpdump src or dst vcenter-ip and not port 22 and not port 8543

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode

listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes

10:11:26.453654 IP dataprotection.33703 > vcenter.https: S 2574417830:2574417830(0) win 5840 <mss 1460,sackOK,timestamp 95863 0,nop,wscale 8>

10:11:26.453834 IP vcenter.https > dataprotection.33703: S 4065981307:4065981307(0) ack 2574417831 win 8192 <mss 1460,nop,wscale 8,sackOK,timestamp 20223503 95863>

10:11:26.453849 IP dataprotection.33703 > vcenter.https: . ack 1 win 23 <nop,nop,timestamp 95863 20223503>

10:11:26.457113 IP dataprotection.33703 > vcenter.https: P 1:152(151) ack 1 win 23 <nop,nop,timestamp 95864 20223503>

 

 

 

I see the following errors in /space/avamar/var/vdr/server_logs/vdr-server.log:

 

 

2013-04-28 11:26:18,980 INFO  [com.emc.vdr.server.VDRServer$1]-server.ConnectionService: Trying to establish connection with vCenter.
2013-04-28 11:26:18,980 INFO  [com.emc.vdr.server.VDRServer$1]-server.VDRExternalServerAccessConfig: loading default values forcefully: true
2013-04-28 11:26:18,980 INFO  [com.emc.vdr.server.VDRServer$1]-server.VDRExternalServerAccessConfig: Get mc access...
2013-04-28 11:26:18,989 INFO  [com.emc.vdr.server.VDRServer$1]-service.AdapterUtils: MCS Web Services URL: https://dataprotection:9444/services/mcService  MCUserId="MCUser"  MCUserPswd="*****************************"
2013-04-28 11:26:19,557 INFO  [com.emc.vdr.server.VDRServer$1]-service.ServiceInstance: ServiceInstanceMoref desc=Service Id: urn:uuid:2EAE11DCE6C69635E01367141180601 name=urn:uuid:2EAE11DCE6C69635E01367141180601 value=SERVICE
2013-04-28 11:26:19,691 ERROR [com.emc.vdr.server.VDRServer$1]-server.ConnectionService: Unable to get the vi access: VI SDK invoke exception:java.net.SocketException: Connection reset
2013-04-28 11:26:19,692 INFO  [com.emc.vdr.server.VDRServer$1]-server.ConnectionService: Retry after 5 seconds ...

 

 

 

 

Then followed these instructions:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2044826

 

but when I tried to restart mcs service I got the following error:

 

root@dataprotection:~/#: dpnctl start mcs

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)

dpnctl: INFO: Starting MCS...

dpnctl: INFO: To monitor progress, run in another window: tail -f /tmp/dpnctl-mcs-start-output-21179

dpnctl: ERROR: error return from "[ -r /etc/profile ] && . /etc/profile ; /usr/local/avamar/bin/mcserver.sh --start" - exit status 1

 

 

And the content of file vcenterinfo.cfg was yet correct:

 

vcenter-hostname=**************************

vcenter-port=444

vcenter-username=MYDOMAIN\Administrator

vcenter-password={AES}ZDAM9DqvJolBBEdCE5ha5g==

vcenter-sso-hostname=*************************

vcenter-sso-port=7444

I saw that a new version of dataprotection was released a couple of days ago... But I would like to know if there is a issue in running vcenter on a different port than 443 before trying to make another deploy.(the fifth exactly).

 

Many thanks

 

 

 


Viewing all articles
Browse latest Browse all 180259

Trending Articles