Troubleshooting data server

Checking process

vitalsigns@vitalsigns1:~$ ps aux | grep -i dataserver

The important one is vitalsigns-1.0

vitalsi+ 28597  [...] confdir=/home/vitalsigns/vitalsigns-1.0/conf

If there is one, check if it's stuck.
Otherwise, just start it

Checking if data server is stuck

Check in the logs folder, sorted by most recent

vitalsigns@vitalsigns1:~/vitalsigns-1.0/logs$ ls -alht | grep dataserver
-rw-rw-r--  1 vitalsigns vitalsigns 1.7G Feb 24 03:30 dataserver_20220912_205951165.log
[...]

Pick the first one to follow it

vitalsigns@vitalsigns1:~/vitalsigns-1.0/logs$ tail -f dataserver_20220912_205951165.log

If there's no activity, even after you attempt to login in VS, the data server is stuck. Restart it

Restarting data server

Stopping stuck data server

vitalsigns@vitalsigns1:~/vitalsigns-1.0/bin$ ./stopDataServer.sh

If the process is still running after this, then:

kill [pid]

If it persists:

kill -9 [pid]

Starting data server

vitalsigns@vitalsigns1:~/vitalsigns-1.0/bin$ ./startDataServer.sh

NOTE: Press enter afterwards, it's not stuck

Then check the logs to make sure it started properly.

vitalsigns@vitalsigns1:~/vitalsigns-1.0/logs$ ls -alht | grep dataserver
-rw-rw-r--  1 vitalsigns vitalsigns 1.7G Feb 24 15:30 dataserver_20220912_205951165.log
[...]

vitalsigns@vitalsigns1:~/vitalsigns-1.0/logs$ tail -f dataserver_20220912_205951165

If you can't login now, check the postgres service or just call Melky.