Post

2 followers Follow
0
Avatar

DB Visit 8 on Windows 12R2

When I issue the command "dbvctl -f system_readiness" I run this error:
Example from Primary to secondary:
Error returned from running command: "C:\Program Files\Dbvisit\dbvnet\dbvnet.exe" -c
"C:\Program Files\Dbvisit\dbvnet\conf\dbvnetd.conf" -a DBVT -p 7890 -f "C:\Program
Files\Dbvisit\standby\doc\README.txt" -o "C:\Program
Files\Dbvisit\standby\doc\README.txt"
Error: connect: No connection could be made because the target machine actively refused  it

However on scondary system netstat -a  shows prooces are running an listening.

 TCP    [::]:49153             DBVT:0                 LISTENING
 TCP    [::]:49154             DBVT:0                 LISTENING
 TCP    [::]:49155             DBVT:0                 LISTENING
 TCP    [::]:49158             DBVT:0                 LISTENING
 TCP    [::]:49160             DBVT:0                 LISTENING
 TCP    [::]:49161             DBVT:0                 LISTENING
 TCP    [::1]:49156            DBVT:0                 LISTENING
 TCP    [fe80::b403:8d74:50b0:bfe0%12]:7890  DBVT:0                 LISTENING
 TCP    [fe80::b403:8d74:50b0:bfe0%12]:7891  DBVT:0                 LISTENING
 TCP    [fe80::b403:8d74:50b0:bfe0%12]:49159  DBVT:0                 LISTENING
 UDP    0.0.0.0:500            *:*
 UDP    0.0.0.0:4500           *:*
 UDP    0.0.0.0:5355           *:*
 UDP    192.168.50.202:137     *:*
 UDP    192.168.50.202:138     *:*
 UDP    [::]:500               *:*

The firewall has been disabled completely on both servers.

 

If I issue dbvctl -f system_readiness an set primary and secondary system to local server things run fine.

Any Ideas?

 

Thx

Christian

 

 

 

 

Christian Floreck Answered

Please sign in to leave a comment.

1 comment

0
Avatar

This is part of the Communication config and testing section - please refer to the online document link: https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+Networking+-+Dbvnet#DbvisitStandbyNetworking-Dbvnet-7.TroubleshootingDbvnet

 

1. Ensure the hostnames of the two Windows servers and their IP addresses are present in the hosts file on both servers - c:\Windows\System32\Drivers\etc\hosts.


2. You may have to adjust the "metric" for the specific network interface to make sure ipv4 gets higher priority.
Example see attached - 3 steps to get to the metric.

Adjust the automatic setting to something like 20, then retry - restart of dbvnet will be required 
You can do this on your test system standby server first - the metric change might require a windows restart to take affect.


See attached screen print

3. Once you have carried out the steps run the netstat command on both primary and standby servers.

C:\Users\Administrator> netstat -ano|findstr 7890

With expected output as :

TCP    0.0.0.0:7890           0.0.0.0:0              LISTENING       2396
TCP    172.16.1.92:7890       172.16.1.91:61319      ESTABLISHED     2396

Check the status of the ports on Primary Server 
================================================ 
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7890 
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7891

Check the status of the ports on Standby Server 
================================================ 
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7890 
C:\Program Files\Dbvisit\Standby>netstat -ano|findstr 7891

4. Finally run the System Readiness test  :

C:\Program Files\Dbvisit\Standby>dbvctl.exe -f system_readiness

 

 

 

 

 

 

Charmaigne Bezuidenhout 0 votes
Comment actions Permalink