if the update has failed you can try one of the following
run the update script again from terminal. Navigate to the shinobi directory and run the following command.
sudo chmod +x UPDATE.sh&&sudo ./UPDATE.sh
download the repo again and overwrite your current files. conf.json file and videos folder should not be affected in an overwrite.
use git clone to get a fresh copy then move over your conf.json, videos, and super.json files into the new directory.
Check out this link here https://shinobi.video/docs/start#content-updating-shinobi
If you used git then i suggest running git checkout dev then i think git pull and restart shinobi pm2 restart camera.js
Sleeping connections are idle connections, so normal case if there is currently nothing to do. I think to avoid "too many connections" you could call sql.destroy (maybe in a try-catch-block) at start of s.disc so the old connection is definitely closed. (btw. the name s.disc is really odd for a function initializing sql connections).
At the top of the Windows install instructions there is blip noting this issue. http://shinobi.video/docs/start#content-windows--the-hard-way
Currently Shinobi is not a native Windows application and requires more attention in this regard. So far I have just got it to run in Windows (mostly). I haven't ironed out the asethetics... I welcome any input on how to make a script for a windows daemon.
Since this is noted in the docs i will close this thread Thanks!
That is right. The reason I don't is because not everyone uses motion, so not everyone has the libs for it.
Attempting to run that without the libs may halt the entire package.json install.
I leave it to user discretion with this being the case.