[[Support] spaceinvaderone - Shinobi Pro]

On 8/15/2020 at 3:14 PM, rojarrolla said:

I agree with you, Shinobi is way difficult to setup. What CPU usage do you get with that setup? And what resolution are you using?

I am using an old gaming box. i7 4790k with 32gb ram. 2x500gb SSD's in extended volume for the boot disk and storage for the "Current, New and alerts" folders. a 4TB mechanical drive for the stored folder and a final 6TB for long term. 

 

Other than some "fun" getting my head around crossing zones for camera triggering to cut down on the moth activation problem at night, it's working without a fault. I haven't tried out the GPU support yet, but the box has a GTX 970 in it that I will get around to messing with when I have time.

 

CPU utilisation wise it floats from 50'ish to 100% but averages arround a solid 70%. That is with the local client running over remote desktop. Closing blueiris and letting it run as a service drops 15-20% off the utilisation figures for me.

 

When connecting via the web interface just to monitor the camera's it sits around 50% and moves up to 95%'ish when recording the hi quality streams with them all activated. 

 

I am recording at Max resolution for each camera, with audio (5 x Reaolink 520's and 1 x SV3C PTZ camera).

 

And the 5 FPS noted on the screen is the FPS for the multi view monitor screen. The camera's are all recording happily when triggered at 15 FPS.

 

I am using pfsense with its own dedicated interface for the cameras and the cameras on their own VLAN to keep traffic problems down. Switch wise they are connected together with a Cisco SG300 series POE switch.

 

 

EDIT:

I was being real dumb and left encoding on in BluieIris. Not needed as the cameras already encode. I changed it to direct to disc recording and CPU usage has dropped to 21%

 

 

 

[[Support] spaceinvaderone - Shinobi Pro]

On 9/19/2020 at 4:16 AM, sota said:

trying to figure out how to prove/disprove this, but apparently the following combination causes some issues:

Shinobi Pro

Reolink RLC-520

main (clear) stream at 25fps 2560x1920 8192kB max data rate

monitor set up to record, with same monitor up on screen.

I get tearing/ghosting issues.

 

been fighting with this problem for the past couple days, which is weird since the cameras have been online for almost 2 weeks without issue.

it's not just shinobi that's showing the problem either; the cameras record locally on an SD Card, and those files are corrupted as well.

i'm thinking, the strain of recording the clear stream locally, the sub-stream (fluent) locally (640x480 7fps 160kB), shinobi recording and monitoring the clear stream, is overloading the camera's internal capabilities? I changed shinobi to watch only on one set of monitors (fluent), record on another set (clear), seems to have maybe calmed things down?

I have the same camera's and would get this randomly on 2 of the 6. For me I think it was bandwidth related in the end as the data transfer off the box coupled with high network use (6 other heavy users on the LAN) caused them to drop out like your are. Putting them on their own VLAN with a high VLAN priority sorted it sorted it. Well for me. I haven't had the problem anymore but I only have about a week of testing that fix as I switched to Blue Iris. :-)

[[Support] spaceinvaderone - Shinobi Pro]

I have given up on shinobi. It's all too flaky. What is working well for me is Blue Iris 5. Well worth £60. It is even running well with 6 camera's in a Windows 10 VM on an unraid box with an I7 4790k. 

[[Support] spaceinvaderone - Shinobi Pro]

19 hours ago, jevan23 said:

Thought I'd expand on this as it took some time for me to figure out what changes were needed in the shinobi container, and it might help out someone else:

 

Created a mariadb database as follows:

CREATE USER ‘shinobi’ IDENTIFIED by ‘password’;

CREATE DATABASE IF NOT EXISTS shinobi;

GRANT ALL PRIVILAGES ON shinobi.* TO ‘shinobi’ IDENTIFIED BY ‘password’;

 

now you can edit the shinobipro container and make the following changes based on the new mariadb database created above:

 

MYSQL_USER: shinobi

MYSQL_DATABASE: shinobi

MYSQL_HOST: IP address of unraid

maria db database location, change it to: /mnt/user/appdata/mariadb/databases/shinobi/

MYSQL_PASSWORD: password

 

Many thanks. That looks like it has got it all going. Just in time too, camera's arrive tomorrow. 

[[Support] spaceinvaderone - Shinobi Pro]

I hope this is the correct spot to post this, my apologies if it isn't.

 

I have just installed ShinobiPRO on unraid and ti all looks right with no errors in any logs. However, when I login as super/admin I get the following error (Screenshot), "Database is not running or unreachable. Please ensure it is started then restart Shinobi. By default Shinobi uses MariaDB, an SQL server, as the database engine."

 

 

However the suggested fix on the link doesn't appear to help as I cannot find the mysql terminal application anyplace and paths are different. I have removed and reinstalled ShinobiPRO and gone into the appdata/ShinobiPro folder and removed all content left behind there, and then reinstalled and I get the same error. 

 

My unraid system has only ever been used for file sharing and this is the first docker container it has had. I am on Unraid 6.8.3 and so far this is my first problem. 

 

Does anyone have any pointers to get this going?