Difference between revisions of "Common Errors When Starting Server"

From Vital Soft Wiki
Jump to: navigation, search
(VsrvTcp Listener service not started on the host)
(VsrvTcp Listener service not started on the host)
Line 7: Line 7:
 
Possible causes:
 
Possible causes:
 
* The VsrvTcp listener is not running.  
 
* The VsrvTcp listener is not running.  
**To verify, run the following command on the server:
+
:*To verify, run the following command on the server:
 
   $ps -ef | grep vsrvtcp
 
   $ps -ef | grep vsrvtcp
 
   root    1436088      1  0 09:30 pts/0    00:00:00 ./vsrvtcp -a
 
   root    1436088      1  0 09:30 pts/0    00:00:00 ./vsrvtcp -a
Line 13: Line 13:
 
* Invalid IP address.
 
* Invalid IP address.
 
* Invalid port number.  
 
* Invalid port number.  
**To verify the default port used by VsrvTcp, issue the following command on the server:
+
:*To verify the default port used by VsrvTcp, issue the following command on the server:
 
   $grep askplus /etc/services
 
   $grep askplus /etc/services
 
   askplus        29500/tcp    # vsrvTCP listener
 
   askplus        29500/tcp    # vsrvTCP listener
** The port can also be specified when starting VsrvTcp using the -n parm
+
:*The port can also be specified when starting VsrvTcp using the -n parm
{{{
 
 
   /ASKPLUS/vsrvtcp -a -n29500
 
   /ASKPLUS/vsrvtcp -a -n29500
}}}
+
*Invalid sTunnel configuration.
 +
:*When the 2nd part of the error is "No connection could be made because the target machine actively refused it." it usually indicates an invalid sTunnel setup.

Revision as of 17:56, 5 June 2023

Errors When Starting Server

VsrvTcp Listener service not started on the host

This error message is usually following by a second message that includes more details about why the connection failed.

Possible causes:

  • The VsrvTcp listener is not running.
  • To verify, run the following command on the server:
 $ps -ef | grep vsrvtcp
 root     1436088       1  0 09:30 pts/0    00:00:00 ./vsrvtcp -a
 root     1436089 1436088  0 09:30 pts/0    00:00:00 ./vsrvtcp -a
  • Invalid IP address.
  • Invalid port number.
  • To verify the default port used by VsrvTcp, issue the following command on the server:
 $grep askplus /etc/services
 askplus        29500/tcp    # vsrvTCP listener
  • The port can also be specified when starting VsrvTcp using the -n parm
 /ASKPLUS/vsrvtcp -a -n29500
  • Invalid sTunnel configuration.
  • When the 2nd part of the error is "No connection could be made because the target machine actively refused it." it usually indicates an invalid sTunnel setup.