Checking service status and logs

This section will describe general procedure to follow and things to check when troubleshooting Navixy platform issues. It covers basic troubleshooting of Java services, Web server and Database server.

Java service status

On Linux, Navixy use runit supervisor, which is an alternative to traditional init.d scripts. Use the following command to check all services status:

sv status {api-server,sms-server,navixyserver}

When everything is normal, it should output something like:

run: api-server: (pid 454) 173771s; run: log: (pid 432) 173772s
run: sms-server: (pid 1341) 173742s; run: log: (pid 433) 173772s
run: navixyserver: (pid 8049) 167738s, normally down; run: log: (pid 434) 173772s

On Linux, navixyserver is an alias for tcp-server

NOTE: On Windows, the services work like regular NT services, so you can check their status, as well as control them, using standard Windows services manager

When any service is down, it will show with down status. Example:

down: navixyserver: 1s; run: log: (pid 434) 173829s

In this case we need to look into the logs for this service. By default, all services are located in /home/java/<service_name>, and each service have a log folder. For example, to look into the logs of navixyserver (which is an alias for tcp-server), we need to open file /home/java/tcp-server/log/log.txt.

If the service can’t start, usually you can find the reason in the logs.

To restart Navixy services manually, first, order them to stop:

sv stop {api-server,sms-server,navixyserver}

If any service can’t shutdown, just kill the process using it’s pid (the pid is shown in sv output):

kill -KILL <pid>

Then start all services:

sv start {api-server,sms-server,navixyserver}

To restart all Navixy services in one action, use command restart-navixy
If you don’t have this command, you probably have old version of Navixy, it will appear after update.

Web server status

If Java services are runnig, but you still can’t get access to the interface, you should check if the web server is running:

/etc/init.d/nginx status

Also, ensure that web server is listening on port 80 (in a standard configuration):

netstat -an | grep :80

If that’s correct but you still can’t access the platform, refer to admin panel or user interface respective guides.

Database troubleshooting

Navixy use MySQL, so, first of all, ensure MySQL server is running:

/etc/init.d/mysql status

Try to connect to MySQL using the same account as Java services. For example, open /home/java/api-server/conf/ file, get database login and password from there, and use them to connect to MySQL from the shell:

mysql -u<username> -p<password> google

Ensure other Java services can connect too. If you have a database issue, usually you can see related error in respective Navixy service’s log.

Contact technical support

Those are the basic steps to check. If you can’t fix the issue, please contact us at [email protected], and describe the issue in detail. We’ll do our best to help.

If you have more questions please contact our support team


USA: +1 858 815 9045

Mexico: +52 334 1642158

UK: +44 808 1641499

Germany: +49 1573 5988250

Russia: +7 495 317 1622

Log in


We use сookies to improve our website, products and related services, analyze site traffic, and serve targeted advertisements. If you continue to use our services, you consent to our use of сookies. Read more