DSS does not start / Cannot connect¶
When DSS fails to properly start, the following symptoms can happen:
- dss start fails
- dss status indicates that some processes are not started
- “Could not connect to DSS server” banner when trying to connect using a browser (HTTP code: 502, type: Gateway error)
- “Connection refused” error when trying to connect using a browser
If you are using the Dataiku virtual machine, please see The dedicated documentation for troubleshooting instructions.
Check processes state¶
The first step is to check the state of the DSS process:
- Go to the DSS data directory
- Run
./bin/dss status
If all processes are indicated as RUNNING, proceed to the next step
If a process is not in RUNNING state, first try to restart DSS:
./bin/dss restart
If it does not help, and some processes are still failing, see “Diagnose process failures” below.
If all processes are now RUNNING and you still get errors when connecting, proceed to the next step
Verify local connectivity¶
From the DSS machine, run
curl http://127.0.0.1:DSS_PORT/
If you don’t see HTML code, and the nginx process is correctly running, you might have a local firewall issue
curl http://127.0.0.1:DSS_PORT/dip/api/get-configuration
If you don’t see a JSON result, check the status and logs of the backend process
If both of these tests are successful but you can’t connect from your browser, it indicates a network connectivity issue between DSS and your browser. Check for firewalls and proxies along the way. Try with another browser or another workstation if applicable.
DSS start (or stop) fails¶
It can happen that running ./bin/dss start fails
Server port already in use¶
Before starting, DSS checks that all TCP ports required are free. DSS requires up to 10 consecutive TCP ports, starting from the base port set at install time. Check that this whole range is available.
This error can also indicate that some stray DSS processes are still running, but are not controlled anymore by the DSS supervisor. See “Kill all DSS processes” below.
Server requires authentication¶
If you receive this message, it generally indicates that you ran the DSS installer or a dssadmin command while DSS was still running. It won’t be possible to stop DSS normally. See “Kill all DSS processes” below.
Kill all DSS processes¶
If some stray DSS processes are still running, you’ll need to kill them.
Run ps -u $USER -f to identify all processes running as the DSS service account, and use kill -9 PID to kill all DSS processes:
- Java processes
- Python processes
- nginx processes
Diagnose process failures¶
check which process is failing, and check the run/PROCESS.log file, where PROCESS is the name of the failing process.
In particular, if the backend process is failing, check run/backend.log for errors.
Common issues that can prevent DSS from starting include:
- Out of disk space (“No space left on device”) on the DSS data directory
- Permissions issues (all files must belong to the DSS service account)
© Copyright 2023, Dataiku
DSS Express Remote Access Setup via Port Forwarding
These instructions will show you how to setup your DSS Express server and network so you can remotely access the DSS Express server from the DSS Client or from the DSS Mobile App.
Prerequisites
- DSS Express
- IP Address of DSS Express
- User Name and Password to router or modem
Example of Port Forwarding Rules in Router
Port List for DSS Express Server
| Function Module | Listening Port | Application Protocol | Required Mapping |
|---|---|---|---|
| Client login | 80 (NGINX: HTTP) | HTTP | No |
| 443 (NGINX: HTTPS) | HTTPS | Yes | |
| 1883(MQ service connected by mobile app) | MQ-mqtt (encrypted) | Yes | |
| 61616 (MQ service connected by client) | MQ-openwire (encrypted) | Yes | |
| Live View | 9100 (MTS service: RTSP) | RTSP | Yes |
| 9102 (MTS service: RTSPS) | RTSP over TLS | No | |
| Playback | 9320 (SS service: RTSP) | RTSP | Yes |
| 9322 (SS service: RTSPS) | RTSP over TLS | No | |
| DeepXplore | 9910 (subOSS service) | HTTP | No |
| 9911 (subOSS service) | HTTPS | Yes | |
| ANPR | 8081 (PTS HTTP image server) | HTTP | No |
| 8082 (PTS HTTPS image server) | HTTPS | Yes | |
| 40000-50000 (PTS image stream) | RTP | Yes | |
| Video Intercom | 5080 (SC service) | SIP registration port (UDP) | Yes |
| 20000-30000 (SC service audio stream) | Intercom audio stream forwarding port |
If you want to use the SIP function of DSS Mobile for VDP, you need to map 20000-30000 ports
Port List for Remote Dahua IP Camera or Recorder
| Port | Server | Function |
|---|---|---|
| 80 | HTTP | Responsible for HTTP protocol client login |
| 37777 | HTTPS | Responsible for HTTPS protocol client and web login |
| 554 | RTSP |
Instructions
Identify & Set WAN and LAN IP Address of DSS Express Server
Video Instructions
Step by Step Instructions
1. Open the DSS Express Server configuration
2. Click the gear icon in the top right to change the IP information of the server
3. The Setting window will display the current IP information for the server
4. To find out the public IP for the network, start by opening a web browser and go to
5. The IP listed as «Your IP» will be the public IP as determined by the website
6. Enter this address into the «Mapping IP» field in the DSS Server Configuration
Be sure to note the CMS IP address, we will be using that IP address to forward the ports in the next step.
7. Click OK once the information has been entered
8. You will receive a prompt to confirm a restart of the server to make the network changes. Click OK to proceed
Forward Ports in Router or Modem
Please note the screenshots in this guide may not match identically to the modem/router being used with the DSS, but will be helpful as a reference in configuring the correct Port Forwarding rules.
If more direct instructions are required, please refer to www.PortForward.com to find a step by step guide for your specific make/model of modem/router
Video Instructions
Step by Step Instructions
1. Log into the router and navigate to the Firewall / Routing section
2. Create a new port forwarding rule
3. Enter all information for the port forwarding rule:
- Name — nickname for Port Forward Rule
- Port — desired port to be opened
- Forward IP — CMS IP , found in the previous steps in the DSS Server configuration
- Protocol — Both (TCP, UDP)
Click Save once the parameters have been entered
4. The created port forwarding rule will appear in the list.
Repeat the process to create new rules, for every port that is required for DSS functions (refer to above chart)
5. A full list of forwarded ports for the DSS Express
Verify Ports are Open
Video Instructions
CanYouSeeMe.org Test Table
| Port | Server | Test Result |
|---|---|---|
| 80 | HTTP | Success! Your ISP is not blocking port 80 |
| 443 | HTTPS | Success! Your ISP is not blocking port 80 |
| 9000 | CMS | Success! Your ISP is not blocking port 80 |
| 9320 | SS | Success! Your ISP is not blocking port 80 |
| 5080 | SIP | Error! |
| 8081 | PTS | Success! Your ISP is not blocking port 80 |
| 40000-49000 | RTP | Error! |
| 50000 | HTTP | Error! |
| 50001 | HTTPS | Error! |
| 9100 | MTS | Success! Your ISP is not blocking port 80 |
| 61616 | Openwire | Success! Your ISP is not blocking port 80 |
| 1886 | MQTT | Error! |
| 9090 | DSS_MGW | Success! Your ISP is not blocking port 80 |
| 8080 | DSS_MCDPos | Error! |
| 9500 | ARS | Error! |
Step by Step Instructions
1. Open a web browser and go to
2. Enter a Port number in «Port to Check» field to test
3. Click Check Port
4. The result will be displayed
Example of blocked port:
Server DSS Dahua cannot connect through Web y SQL
Log in to the DSS server and try to restart the Mysql service by the command startMysql.bat in the path C:/DSS Express/Server/bin/, the following error accured, according to the DAHUA engineer, the issue was cause by MAC address change;
Go to the below path and collect the information from the folder conf:
C:/DSS Express/Server/WEBCLIENT/webclient/apache-tomcat/conf/
After DAHUA engineer analyzed the license file, it’s found that the MAC address is as follows:
Root Cause
Checked the MAC address by the command ipconfig /all, it’s found that the MAC address is incorrect. Therefore, we asked the customer to change the MAC address to 00-15-5D-30-26-00, and then reboot the server;
Solution
After that we start the all the service, it was working fine.
The window was installed by Hyper-V, the MAC was changed by some unknow reason.
The solution is to change the MAC address of the VM to 00-15-5D-30-26-00 by hyper-V manager and restart all the services on the DDS.