Troubleshooting

Contents

1. Sublime
2. Node-sass

Sublime, rsub, server login trouble

Sometimes rsub, msub, ysub etc. won't open a file. This can be due to several things, eg. Sublime not being open, or busy ports or hanging login sessions:

Things to try:

1. Check that Sublime is open.
2. Log out of all sessions with exit (not just closing window), and log back in.
3. Check active sessions on server with netstat -tulpn. Look for your port number:

Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
tcp        0      0 127.0.0.1:52694         0.0.0.0:*               LISTEN      18908/5
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      13659/sshd
tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN      1314/postgres

...eg. first line (:52694). You'll then see which session keeps that port open to the far right (/5). When you've found which sshd session is keeping the port open (5 in this example), you can go open htop and kill this session. (select line with arrows, then press k and 9.
4. Restart your computer and try again...

Node-sass

Getting the dreaded >> Error: libsass bindings not found. Try reinstalling node-sass?

1. this is because node-sass is built with different version of nodeJS. Thing is, the sx server (for example) has one version of node, but the wu-container has another one. Solution: rebuild node-sass inside container.
2. quick fix: add npm rebuild node-sass to server.sh

Other npm build problems

1. remember to always build in container context, not outside. lots of packages check their env and install accordingly. env is NOT the same in outside as in container.

srs, srs_settings.js

Error: Cannot find module '/var/www/wu/node_modules/srs/lib/binding/node-v11-linux-x64/srs_settings.js'
Solution:

1. go inside container docker exec -it dev_wu_1 bash
2. rm node_modules -r
3. npm install
   usually works fine.

general GDAL build errors

Usually this is due to nodeJS version mismatch. Try 0.10.40 or 0.12.