TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools


troubleshooting:diagnosing_connection_problems

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
troubleshooting:diagnosing_connection_problems [2021/09/02 00:06] – [Check TapeTrack is listening on port 5000.] Scott Cunliffetroubleshooting:diagnosing_connection_problems [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 42: Line 42:
 If the Framework Server is not running, attempt to [[server:start_stop|start the Framework Server]] and then check your connection again.    If the Framework Server is not running, attempt to [[server:start_stop|start the Framework Server]] and then check your connection again.   
  
 +If the Framework Server wont start see [[troubleshooting:Rebuild Database Environment Files]].
 +
 +If the Framework Server still wont start see [[server:reload|Reloading Server]]
 ==== Linux  ==== ==== Linux  ====
    
Line 66: Line 69:
 =====Ping with TMSS10Ping===== =====Ping with TMSS10Ping=====
  
-If the TapeTrack Framework Server is running, use TMSS10Ping to check the connection to the server.+If the TapeTrack Framework Server is running, use [[cli:tmss10ping|TMSS10Ping]] to check the connection to the server.
  
-Ping the TapeTrack Framework Server with TMSS10Ping, using localhost on the server that TapeTrack Framework Server is installed on with:+Ping the TapeTrack Framework Server with [[cli:tmss10ping|TMSS10Ping]], using localhost on the server that TapeTrack Framework Server is installed on with:
  
 <code> <code>
troubleshooting/diagnosing_connection_problems.1630541169.txt.gz · Last modified: 2025/01/21 22:07 (external edit)