Troubleshoot Installation

Check Server Status

The best place to check whether your Gateway, Media, or the recording management servers are running properly is the LiveSwitch Console → SERVERS page.

Services Failed to Start

If your servers don't start up properly or you need advanced investigation, use the LiveSwitch Hammer command-line tool. You can get it from the following links:

• https://hub.docker.com/r/frozenmountain/liveswitch-hammer
• https://github.com/liveswitch/liveswitch-hammer

The best resources for troubleshooting issues during installation are the logs. The logs provide information about why the services failed to start.

You can run the following in your Windows LiveSwitch Gateway Server installation location to retrieve console logs:

• FM.LiveSwitch.Gateway.Service.exe
• FM.LiveSwitch.MediaServer.Service.exe
• FM.LiveSwitch.RecordingMonitor.Service.exe
• FM.LiveSwitch.RecordingMover.Service.exe
• FM.LiveSwitch.RecordingMuxer.Service.exe

For most installations, you can find logs at:

• Windows
• Linux

%ProgramData%\Frozen Mountain Software\-service-\

If the logs aren't there, check your Logging Configuration.

For Linux installation, if the Gateway service can't start, you can manually run it on the console:

1. Stop the Gateway service:

   sudo systemctl stop gateway
   

2. Run the Gateway service:

   cd /opt/liveswitch/gateway
   dotnet FM.LiveSwitch.Gateway.Core.dll
   

Unable to Connect to Redis or PostgreSQL Server

If the service can't connect to the Redis or PostgreSQL server, check the following:

1. Confirm that the correct Redis or PostgreSQL connection string has been set in your Server-Specific Configuration.
2. Check that the Redis or PostgreSQL server is up and running.
3. Check that the LiveSwitch Gateway service can access the Redis or PostgreSQL server over the network.

Unable to Start Recording Management Services

If any of the recording management components can't start, check the following:

1. Confirm that the correct RabbitMQ or PostgreSQL connection string has been set in your Server-Specific Configuration.
2. Check that the RabbitMQ or PostgreSQL server is up and running.
3. Check that the LiveSwitch Recording Monitor, Muxer, and Mover services can access RabbitMQ or PostgreSQL server over the network.

Ports Are Already in Use

The LiveSwitch Gateway binds to ports 8080 and 9090 on the server by default. If another application uses those ports, the LiveSwitch services won't start. You can fix this by the following:

• Disable the other application or change the port it uses.

  Note

  We don't recommend running other services on the same server as LiveSwitch as it could adversely affect performance.

• If you are running multiple Gateways, access the LiveSwitch Console from a different Gateway and configure the HTTP Bindings with a different port.

• If you can't turn off the other application, then change the port that LiveSwitch uses. You can do this using the LiveSwitch command-line tool:

  • Windows
  • Linux

  & 'C:\Program Files\Frozen Mountain Software\LiveSwitch\Config Tool\FM.LiveSwitch.Cli.exe' reset http --sync=<sync_port--admin=<admin_port>
  

Restart all the services after running the tool. You can now access the LiveSwitch Console at http://localhost:<admin_port>/admin to complete your configuration.

Unable to Uninstall LiveSwitch

If you are unable to uninstall LiveSwitch, you can manually kill the services from Task Manager on Windows and then uninstall LiveSwitch.