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.
Ok that fixed it, now I can record but holy smokes CPU gets eaten up, I'm running 390% while using the default x264 processing agent at 2048x1536, 10fps. Going to mp4/copy fixed that though, and file sizes aren't that bad, yet.
So on OS X, Shinobi is installed in the root home folder (alongside Desktop, Documents, Pictures, etc. folders). When you open Terminal should load the proper pathway to start, and so the cd /home command is not needed, at least not on my machine.
Got another problem... on my test machine/laptop, I didn't have this error, but on a brand new OS X install (got a dedicated Mini for this, fresh erase/install of 11.4), when opening Terminal and running the
git clone https://github.com/ShinobiCCTV/Shinobi Shinobi
command, Terminal reports a permissions error at the end:
Cloning into 'Shinobi'...
remote: Counting objects: 1336, done.
remote: Compressing objects: 100% (86/86), done.
remote: Total 1336 (delta 70), reused 90 (delta 37), pack-reused 1211
Receiving objects: 100% (1336/1336), 4.14 MiB | 2.95 MiB/s, done.
Resolving deltas: 100% (763/763), done.
warning: unable to access '/Users/osxusernamehere/.config/git/attributes': Permission denied
Any ideas on what the hidden config folder does and how to fix it?
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.
i think the easiest way is the "easier way". I use ninja way just for the giggles of using npm. git is better because it is more likely to be up to date.
I am not sure where you are at now.. but if you have the web page and cant login then you probably need to add the sql files.
the error above is about not having ffmpeg, but you figured that out yay!
Looks like your connection to Shinobi Forum was lost, please wait while we try to reconnect.