vw-kombi

Members
  • Posts

    256
  • Joined

  • Last visited

Everything posted by vw-kombi

  1. 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?
  2. 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.
  3. does this (or can this) have/be updated to include the geoIP2 plugin stuff. I only want to allow connections from my own country.
  4. I was hoping for the geoIP database plugin in nginx : https://www.nginx.com/products/nginx/modules/geoip2/
  5. 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 ?
  6. 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.
  7. 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.
  8. Not sure if this was directed at me - i edited my post and added diagnostics.
  9. 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
  10. 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.
  11. 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.
  12. 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.
  13. 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 ?
  14. Also - Just tried a restart of the server - same issue. tower-diagnostics-20220302-0831.zip
  15. This happened overnight. I did have a pre clear runnning..... Stopped that. I googled this and searched forums first. I dont use pihole or anything like that. I was using the cloudflare 1.1.1.2 provacy and thought that may be the issue so stopped docker and vms and change to 1.1.1.1, restarted them and not fixed. I am on unraid 6.9.2. As luck would have it, I need an update for the emby beta to keep live TV operating.......
  16. Thanks @squid. My system has been up for ages. I vaguely remember me issuing a chown for my recorded TV shows but accidentally did not include the target and I aborted it immediately. I suspect that was the cause at the time. i had a stork since then however so many memories are now gone, or garbled a bit.
  17. Am I right that if I restart unraid, the folders will get re-extracted from the USB stick in memory and then be all as shipped again ? It that is the case, I have a disk with 430 re-allocated sectors to be replaced soon, and I could do a restart at the same time.
  18. Thanks @squid. I did a chown -R root:root * on /etc I have checked other folders for this issue. The 'correct' ones with root:root are sbin, bin, var, boot, lir and run. /tmp has a mixture of both root and nobody proc has a mixture of both root and nobody sys has all folder in there as nobody:users Could I ask if I should do the chown -R root:root * on sys / proc / tmp
  19. I checked /etc, and this file is nobody:users. As are almost all of the files in /etc. I assume this is incorrect and these should all be root:root ?
  20. Here is the crontab stuff : root@Tower:~# crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null root@Tower:~# cat /etc/cron.d/root # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 45 3 * * * /usr/local/sbin/mover &> /dev/null # Generated parity check schedule: 30 0 1 * * /usr/local/sbin/mdcmd check NOCORRECT &> /dev/null || : # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Generated array status check schedule: 20 0,12 * * * /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null # Generated Unraid OS update check schedule: 11 0 * * 1 /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/unraidcheck &> /dev/null # Generated cron settings for plugin autoupdates 0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # CRON for CA background scanning of applications 35 * * * * php /usr/local/emhttp/plugins/community.applications/scripts/notices.php > /dev/null 2>&1 # Generated ssd trim schedule: 0 5 * * * /sbin/fstrim -a -v | logger &> /dev/null # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null # Generated schedules for parity.check.tuning 0 23 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "resume" &> /dev/null 0 10 * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "pause" &> /dev/null */7 * * * * /usr/local/emhttp/plugins/parity.check.tuning/parity.check.tuning.php "monitor" &>/dev/null # Generated cron schedule for user.scripts 45 23 * * * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/VW-Daily-FixPermissions-TVRecordings/script > /dev/null 2>&1 */5 * * * * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/VW-Sync-Home_Monitoring_to_Hiddeen_Laptop/script > /dev/null 2>&1 30 23 * * * /usr/local/emhttp/plugins/user.scripts/startCustom.php /boot/config/plugins/user.scripts/scripts/Weekly-unRAID-4TB-Backup/script > /dev/null 2>&1