vw-kombi

The unraid docker install for this has warnings about that. But you only see them on first install.

could not rollback - something above cant upgrade from the new to the old - I guess database changes ?

Restored config from yesterday - no need to re-do the rules. I am all working again.

Further and further to this - 7.3.76-ls173 is the overnight one that lost all config and nothing showing as adpoted at all - and never seems too. Rolled back to 7.3.76-ls172 - all working but USG went offline and stayed like that. Rolled back to 7.3.76-ls171 - and all is happy again......... - leaving that in the pull request now!!!!!! Now to re-do a load of FW rules !!!!!

Further to this, after a restore to 12/12 appdata - my version I am using seems to be 7.3.76 anyway. It is only what appeared today for install that killed it. But alas something is not quite right as the USG goes through its adopt cycle, then shows as offline. All other devices are all good.

I blindly (stupidly) clicked update on this without checking this forum. They have all been so good for years. This time though, nothing there, and no adopting of anything. No restore option to restore. Setting a previous version then through an erro saying cant upgrade from 7.3.76 so I guess somehting happened on it. I am restoring my appdata - but back to 12/12 unfortunately...... Have to look into individual container backup/restores going forward.

All working fine for remote use, ie when I turn wifi off in my phone. But while in wifi, on and off my wifi devices, so on same network, it does not work. Makes testing and checking a bit hard. Anything I should setup to make it work?

I want to add the geoip2 database stuff. It says to do this : In the container's docker arguments, set an environment variable DOCKER_MODS=linuxserver/mods:swag-maxmind However where does that go in the unraid cntainer setup ? Thanks.

does this (or can this) have/be updated to include the geoIP2 plugin stuff. I only want to allow connections from my own country.

I was hoping for the geoIP database plugin in nginx : https://www.nginx.com/products/nginx/modules/geoip2/

Thanks for this, I am new to the NPM - I have the 'old' manual method to date. I set this up alongside it or testing. What would be required to get the GEO blocking working with this container ?

Shouldn't the exclude folders option in this great tool NOT then stop the docker container ? I have tdarr running and converting, and I wanted to backup all the others, so i exceluded this one folder, mistakenly thinking that it would then not be stopped........ I often cant do a backup of all as on container is doing something and cant be stopped. Would be great if we have that capability.

I just came home to many things not working in unraid - even the console gui. was a 500 error. I found every CPU max 100%. I use cpu pinning and nothing is allowed them all like this except shinobi as it is new. I was able to telnet in and do a docker stop shinobipro and all was working again. Its not set to use its OWN CPU's and not the same as Unraid / primary dockers. Just a heads in in case it runs away on any of you like that.

+1

Ah, ok - I guess I was hoping to not have to restart the system.

Not sure if this was directed at me - i edited my post and added diagnostics.

I have a stuck drive ? It is a replacement under warranty from seagate. Worked OK for a few weeks, then it said there were a few uncorrectable errors, got up to 180 or something, then the consle just said 'FORMAT' next to it - yet I could still read and write to it. I pulled it out and re-connected it and now it just says this : In Change Disk UUID - nothing appears in the drop down. Disk log says this : Mar 2 11:54:57 Tower kernel: ata6: SATA max UDMA/133 abar m131072@0xf7480000 port 0xf7480380 irq 59 Mar 2 11:54:57 Tower kernel: ata6: SATA link down (SStatus 0 SControl 330) Mar 23 17:32:37 Tower kernel: sd 11:0:0:0: [sdm] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Mar 23 17:32:37 Tower kernel: sd 11:0:0:0: [sdm] 4096-byte physical blocks Mar 23 17:32:37 Tower kernel: sd 11:0:0:0: [sdm] Write Protect is off Mar 23 17:32:37 Tower kernel: sd 11:0:0:0: [sdm] Mode Sense: 00 3a 00 00 Mar 23 17:32:37 Tower kernel: sd 11:0:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 23 17:32:37 Tower kernel: sdm: sdm1 Mar 23 17:32:37 Tower kernel: sd 11:0:0:0: [sdm] Attached SCSI disk Mar 23 17:32:38 Tower unassigned.devices: Adding partition 'sdm1'... Mar 23 17:32:38 Tower unassigned.devices: Mounting partition 'sdm1' at mountpoint '/mnt/disks/8TB-HOTSPARE'... Mar 23 17:32:38 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdm1' '/mnt/disks/8TB-HOTSPARE' Mar 23 17:32:38 Tower kernel: XFS (sdm1): Filesystem has duplicate UUID af377034-9f75-4ffd-8bd1-e621f63dc0c6 - can't mount Mar 23 17:32:38 Tower unassigned.devices: Successfully mounted 'sdm1' on '/mnt/disks/8TB-HOTSPARE'. Mar 23 17:37:55 Tower kernel: sd 11:0:0:0: [sdm] Synchronizing SCSI cache Mar 23 17:37:55 Tower kernel: sd 11:0:0:0: [sdm] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Mar 23 17:37:55 Tower kernel: sd 11:0:0:0: [sdm] Stopping disk Mar 23 17:37:55 Tower kernel: sd 11:0:0:0: [sdm] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=0x00 Mar 23 17:42:22 Tower kernel: ata6: softreset failed (1st FIS failed) Mar 23 17:42:26 Tower kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 330) Mar 23 17:42:26 Tower kernel: ata6.00: ATA-10: ST8000DM004-2CX188, ZR11563Z, 0001, max UDMA/133 Mar 23 17:42:26 Tower kernel: ata6.00: 15628053168 sectors, multi 16: LBA48 NCQ (depth 32), AA Mar 23 17:42:26 Tower kernel: ata6.00: configured for UDMA/133 Mar 23 17:42:26 Tower kernel: sd 7:0:0:0: [sdm] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB) Mar 23 17:42:26 Tower kernel: sd 7:0:0:0: [sdm] 4096-byte physical blocks Mar 23 17:42:26 Tower kernel: sd 7:0:0:0: [sdm] Write Protect is off Mar 23 17:42:26 Tower kernel: sd 7:0:0:0: [sdm] Mode Sense: 00 3a 00 00 Mar 23 17:42:26 Tower kernel: sd 7:0:0:0: [sdm] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Mar 23 17:42:26 Tower kernel: sdm: sdm1 Mar 23 17:42:26 Tower kernel: sd 7:0:0:0: [sdm] Attached SCSI disk Mar 23 17:42:27 Tower unassigned.devices: Adding partition 'sdm1'... Mar 23 17:42:27 Tower unassigned.devices: Mounting partition 'sdm1' at mountpoint '/mnt/disks/8TB-HOTSPARE'... Mar 23 17:42:27 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'xfs' -o rw,noatime,nodiratime '/dev/sdm1' '/mnt/disks/8TB-HOTSPARE' Mar 23 17:42:27 Tower kernel: XFS (sdm1): Filesystem has duplicate UUID af377034-9f75-4ffd-8bd1-e621f63dc0c6 - can't mount Mar 23 17:42:27 Tower unassigned.devices: Successfully mounted 'sdm1' on '/mnt/disks/8TB-HOTSPARE'. But I cant mount it, unmount it, format it or anything. I cant send it away to get fixed, just its a data backup drive and that data was readable until I pulled it out, even though UD says FORMAT next to it. I would prefer to remove the data before sending, unless the disk is really gone. tower-diagnostics-20220324-0820.zip

I gave up on the motion detection inside shinobi. It was rubbish and I played with its settings for days to try and get reduced false positives, or actual motion events. In the end I instead followed the shinobi FTP event documentation online so now when the cams see motion, they drop anything via FTP to shinobi (i.e just a snapshot, no vid needed), which tells shinobi to do the recording. This is now working flawlessly. I tried using the smtp event firing but could not get that to work - could not find the smtp server (may have been my firewall config however). The only issues I am facing is that one cam fires a discord event and the other cam does not (always does it from the test screen with manual motion however). Unfortunately, the one that is not working is the primary one I want the discord event on (walking up to door). And finally, the discord event is being sent to quick - i.e I only get the motion object in the last half second. Yet the recorded video of the event is perfect (about 5 seconds pre event and 20 seconds after). I Googled the hell out of that but seems an issue with others also.

I have shinobi working well based on all this. Thanks heaps. One of my cams is a reolink E1 - cloud only, but there is a neolink docker that can act as a bridge to those - but i cant get it working as its on a different network - no matter what I do to the FW config (USG), it just cant connect. Having never heard of shinob before and doing some googling, I then find out all this 'object detection' stuff. I found sinobi-tensorflow on docker hub and installed that, pointed it all at the shinobi host/ip, went into shinobi for a camera feed and turned all that object detention stuff on - but I am stumped on what to do to enable the tensorflow plugin in shinobi. Online they are all standalone installs and not dockers. Would be great if you made a video to enhance all this with the tensorflow docker. I tried running INSTALL.sh from the docker terminal /plugins/tensorflow folder but get permission denied. I feel I have to make a json to match but I am out of my depth.

ahhhhhh - everything just came back to life. I stopped docker and vm, change the DNS from 1.1.1.1 to 8.8.8.8, and restarted - may have been a co-incidense however as CF is usually great. I again installed that test docker above and it then installed. I did a docker check for updates and they all came back with their expected statuses. So - was it an issue with CF DNS ? Or was it an issue with my system that managed to fix itself ? Or was it as issue with this error and someone remotely fixed their problem - docker: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: TLS handshake timeout.

I just tried to install a new docker from the apps - and I got this - which may relate to the issue ? Is there something wrong with registry-1.docker.io ?

Also - Just tried a restart of the server - same issue. tower-diagnostics-20220302-0831.zip

tower-diagnostics-20220302-0831.zip

If I try to update any of these :