MothyTim

Members
  • Posts

    308
  • Joined

  • Last visited

Everything posted by MothyTim

  1. Hi, I suddenly have this exact issue! A VM caused unRAID to crash (AGAIN!!!) and now it won't boot!! I've tried 4 different sticks (1 Intenseo blue USB2, 2 Sandisk Cruzer Blades USB2 and 1 Kingston Datatraveller USB3) no idea what caused this, it's not happened before and not sure what to try next? ☹️ now stuck without a server!
  2. Hi all, Time Machine has decided that it needs to start a new backup, it's been running fine for a couple of years so has probably become too fragmented! The only issue I've noticed lately is that whenever Time Machine was running all disks would stay spun up, even though the TM share is set to disk 3 only! Annoyingly I didn't manage to work out why! So first question is, is it a good idea to reformat disk 3 in the array as zfs so I use the extra features? And will this maybe fix the spinning up all disks issue? Or better to make a separate single disk pool? If separate pool then zfs or stick to xfs? What is everone elsedoing these days for Time Machine? Thanks Tim
  3. Forgot syslog, incase that's more useful!! syslog-10.19.64.2.log
  4. I've tried rebooting the server, but it just says docker service failed to start!!! It was working fine, I just stopped it to change something but realised I couldn't so started back up! It seems every new version of unRAID gets worse! Had a frustrating weekend changing the cache drive to zfs and now this! tower-diagnostics-20230905-1503.zip
  5. Hi, I was trying to move everything off the cache drive following the video by @SpaceInvaderOne to change it to zfs and failed at the first stage! I set all the relavant shares to move to array and shut docker and vm manager down, then set mover running! This was around 13:30 on 2nd Sept. After about 4 hours I noticed that it had only moved around 1gb and had stopped, in fact all disks in the array had spun down so nothing happening at all! so I stopped mover and tried the to stop the array and check drive settings, but that crash unRAID!! So I've reverted share settings for now and am running mover again to hopefully put the few files it moved back again! Hoping someone can spot the problem before I have another go! Thanks Tim syslog-10.19.64.2.log tower-diagnostics-20230902-1947.zip
  6. Fixed by changing to preset-vaapi Thanks for your help!
  7. Ok thanks, it seems to start now but no video? text error warn system array login s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service frigate-log successfully stopped s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped s6-rc: info: service s6rc-fdholder: starting s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service fix-attrs: starting s6-rc: info: service s6rc-fdholder successfully started s6-rc: info: service fix-attrs successfully started s6-rc: info: service legacy-cont-init: starting s6-rc: info: service legacy-cont-init successfully started s6-rc: info: service log-prepare: starting s6-rc: info: service log-prepare successfully started s6-rc: info: service nginx-log: starting s6-rc: info: service go2rtc-log: starting s6-rc: info: service frigate-log: starting s6-rc: info: service go2rtc-log successfully started s6-rc: info: service go2rtc: starting s6-rc: info: service nginx-log successfully started s6-rc: info: service frigate-log successfully started s6-rc: info: service go2rtc successfully started s6-rc: info: service go2rtc-healthcheck: starting s6-rc: info: service frigate: starting s6-rc: info: service go2rtc-healthcheck successfully started s6-rc: info: service frigate successfully started s6-rc: info: service nginx: starting s6-rc: info: service nginx successfully started s6-rc: info: service legacy-services: starting s6-rc: info: service legacy-services successfully started 2023-07-26 14:04:37.237186960 [2023-07-26 14:04:37] frigate.events INFO : Exiting event processor... 2023-07-26 14:04:37.237336666 [2023-07-26 14:04:37] peewee.sqliteq INFO : writer received shutdown request, exiting. 2023-07-26 14:04:37.363424991 [2023-07-26 14:04:37] watchdog.garden INFO : Terminating the existing ffmpeg process... 2023-07-26 14:04:37.363606904 [2023-07-26 14:04:37] watchdog.garden INFO : Waiting for ffmpeg to exit gracefully... 2023-07-26 14:04:38.106242071 [2023-07-26 14:04:38] frigate.video INFO : garden: exiting subprocess 2023-07-26 14:04:38.610580154 [2023-07-26 14:04:38] frigate.output INFO : exiting output process... 2023-07-26 14:04:39.772871076 [INFO] Service Frigate exited with code 0 (by signal 0) 2023-07-26 14:04:39.774703307 exit OK 2023-07-26 14:04:39.779776206 [INFO] The go2rtc service exited with code 0 (by signal 0) 2023-07-26 14:04:44.391396692 [INFO] Preparing go2rtc config... 2023-07-26 14:04:44.391695179 [INFO] Starting Frigate... 2023-07-26 14:04:44.392108765 [INFO] Starting NGINX... 2023-07-26 14:04:44.573084091 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually 2023-07-26 14:04:44.602014979 [INFO] Starting go2rtc... 2023-07-26 14:04:44.691108723 14:04:44.691 INF go2rtc version 1.2.0 linux/amd64 2023-07-26 14:04:44.691318689 14:04:44.691 INF [api] listen addr=:1984 2023-07-26 14:04:44.691553194 14:04:44.691 INF [rtsp] listen addr=:8554 2023-07-26 14:04:44.691721525 14:04:44.691 INF [srtp] listen addr=:8443 2023-07-26 14:04:44.691897569 14:04:44.691 INF [webrtc] listen addr=:8555 2023-07-26 14:04:45.234227247 2023/07/26 14:04:45 [error] 134#134: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.19.64.2, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001/stats", host: "10.19.64.2:5000" 2023-07-26 14:04:45.234284155 10.19.64.2 - - [26/Jul/2023:14:04:45 +0100] "GET /api/stats HTTP/1.1" 502 157 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:04:45.236579481 [2023-07-26 14:04:45] frigate.app INFO : Starting Frigate (0.12.1-367d724) 2023-07-26 14:04:45.261038558 [2023-07-26 14:04:45] peewee_migrate INFO : Starting migrations 2023-07-26 14:04:45.264231849 [2023-07-26 14:04:45] peewee_migrate INFO : There is nothing to migrate 2023-07-26 14:04:45.281407489 [2023-07-26 14:04:45] detector.coral INFO : Starting detection process: 578 2023-07-26 14:04:47.895672929 [2023-07-26 14:04:45] frigate.app INFO : Output process started: 580 2023-07-26 14:04:47.895748882 [2023-07-26 14:04:45] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2023-07-26 14:04:47.895844847 [2023-07-26 14:04:45] frigate.app INFO : Camera processor started for garden: 587 2023-07-26 14:04:47.895891692 [2023-07-26 14:04:45] frigate.app INFO : Capture process started for garden: 588 2023-07-26 14:04:47.898251146 [2023-07-26 14:04:47] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2023-07-26 14:04:50.247608605 [2023-07-26 14:04:50] frigate.util ERROR : Unable to poll intel GPU stats: Failed to initialize PMU! (Operation not permitted) 2023-07-26 14:04:50.247612478 2023-07-26 14:04:53.432538517 10.19.64.2 - - [26/Jul/2023:14:04:53 +0100] "GET /api/stats HTTP/1.1" 200 2350 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:04:54.391625798 [INFO] Starting go2rtc healthcheck service... 2023-07-26 14:05:01.419456965 10.19.64.2 - - [26/Jul/2023:14:05:01 +0100] "GET /api/stats HTTP/1.1" 200 2351 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:05.321489373 [2023-07-26 14:05:05] watchdog.garden INFO : No frames received from garden in 20 seconds. Exiting ffmpeg... 2023-07-26 14:05:05.321561589 [2023-07-26 14:05:05] watchdog.garden INFO : Waiting for ffmpeg to exit gracefully... 2023-07-26 14:05:05.361204284 [2023-07-26 14:05:05] frigate.video ERROR : garden: Unable to read frames from ffmpeg process. 2023-07-26 14:05:05.361255931 [2023-07-26 14:05:05] frigate.video ERROR : garden: ffmpeg process is not running. exiting capture thread... 2023-07-26 14:05:09.463968091 10.19.64.2 - - [26/Jul/2023:14:05:09 +0100] "GET /api/stats HTTP/1.1" 200 2320 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:15.362735085 [2023-07-26 14:05:15] watchdog.garden ERROR : Ffmpeg process crashed unexpectedly for garden. 2023-07-26 14:05:15.362816156 [2023-07-26 14:05:15] watchdog.garden ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-07-26 14:05:15.362882375 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : [h264_qsv @ 0x5557e0a3ab00] video_get_buffer: image parameters invalid 2023-07-26 14:05:15.362936534 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : [h264_qsv @ 0x5557e0a3ab00] get_buffer() failed 2023-07-26 14:05:15.362985810 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : Error while decoding stream #0:0: Invalid argument 2023-07-26 14:05:15.363027753 [2023-07-26 14:05:15] ffmpeg.garden.detect ERROR : Finishing stream 1:0 without any data written to it. 2023-07-26 14:05:17.419589443 10.19.64.2 - - [26/Jul/2023:14:05:17 +0100] "GET /api/stats HTTP/1.1" 200 2351 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 14:05:25.427323740 10.19.64.2 - - [26/Jul/2023:14:05:25 +0100] "GET /api/stats HTTP/1.1" 200 2383 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" config.yml
  8. Hi, thanks for all that. I've changed the things that you've suggested, but unfortunatly it doesn't work? Here is the log and new config. text error warn system array login Traceback (most recent call last): File "/usr/local/go2rtc/create_config.py", line 27, in <module> config: dict[str, any] = yaml.safe_load(raw_config) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 125, in safe_load return load(stream, SafeLoader) File "/usr/local/lib/python3.9/dist-packages/yaml/__init__.py", line 81, in load return loader.get_single_data() File "/usr/local/lib/python3.9/dist-packages/yaml/constructor.py", line 49, in get_single_data node = self.get_single_node() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 36, in get_single_node document = self.compose_document() File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 55, in compose_document node = self.compose_node(None, None) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node node = self.compose_mapping_node(anchor) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 133, in compose_mapping_node item_value = self.compose_node(node, item_key) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node node = self.compose_mapping_node(anchor) File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node while not self.check_event(MappingEndEvent): File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event self.current_event = self.state() File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 428, in parse_block_mapping_key if self.check_token(KeyToken): File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 116, in check_token self.fetch_more_tokens() File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 223, in fetch_more_tokens return self.fetch_value() File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 577, in fetch_value raise ScannerError(None, None, yaml.scanner.ScannerError: mapping values are not allowed here in "<unicode string>", line 180, column 15: input_args: preset-rtsp-restream-low-latency ^ s6-rc: info: service legacy-services: stopping s6-rc: info: service legacy-services successfully stopped s6-rc: info: service nginx: stopping s6-rc: info: service go2rtc-healthcheck: stopping s6-rc: info: service go2rtc-healthcheck successfully stopped s6-rc: info: service nginx successfully stopped s6-rc: info: service nginx-log: stopping s6-rc: info: service frigate: stopping s6-rc: info: service frigate successfully stopped s6-rc: info: service go2rtc: stopping s6-rc: info: service frigate-log: stopping s6-rc: info: service nginx-log successfully stopped s6-rc: info: service go2rtc successfully stopped s6-rc: info: service go2rtc-log: stopping s6-rc: info: service frigate-log successfully stopped s6-rc: info: service go2rtc-log successfully stopped s6-rc: info: service log-prepare: stopping s6-rc: info: service s6rc-fdholder: stopping s6-rc: info: service log-prepare successfully stopped s6-rc: info: service legacy-cont-init: stopping s6-rc: info: service s6rc-fdholder successfully stopped s6-rc: info: service legacy-cont-init successfully stopped s6-rc: info: service fix-attrs: stopping s6-rc: info: service fix-attrs successfully stopped s6-rc: info: service s6rc-oneshot-runner: stopping s6-rc: info: service s6rc-oneshot-runner successfully stopped 2023-07-26 12:15:22.225758077 File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 84, in compose_node 2023-07-26 12:15:22.225759078 node = self.compose_mapping_node(anchor) 2023-07-26 12:15:22.225760116 File "/usr/local/lib/python3.9/dist-packages/yaml/composer.py", line 127, in compose_mapping_node 2023-07-26 12:15:22.225761077 while not self.check_event(MappingEndEvent): 2023-07-26 12:15:22.225762094 File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 98, in check_event 2023-07-26 12:15:22.225762944 self.current_event = self.state() 2023-07-26 12:15:22.225763977 File "/usr/local/lib/python3.9/dist-packages/yaml/parser.py", line 428, in parse_block_mapping_key 2023-07-26 12:15:22.225781265 if self.check_token(KeyToken): 2023-07-26 12:15:22.225782421 File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 116, in check_token 2023-07-26 12:15:22.225783244 self.fetch_more_tokens() 2023-07-26 12:15:22.225784245 File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 223, in fetch_more_tokens 2023-07-26 12:15:22.225785210 return self.fetch_value() 2023-07-26 12:15:22.225786212 File "/usr/local/lib/python3.9/dist-packages/yaml/scanner.py", line 577, in fetch_value 2023-07-26 12:15:22.225787070 raise ScannerError(None, None, 2023-07-26 12:15:22.225788017 yaml.scanner.ScannerError: mapping values are not allowed here 2023-07-26 12:15:22.225788879 in "<unicode string>", line 180, column 15: 2023-07-26 12:15:22.225789793 input_args: preset-rtsp-restream-low-latency 2023-07-26 12:15:22.225790624 ^ 2023-07-26 12:15:22.225791363 2023-07-26 12:15:22.225792311 ************************************************************* 2023-07-26 12:15:22.225807173 *** End Config Validation Errors *** 2023-07-26 12:15:22.225808212 ************************************************************* 2023-07-26 12:15:22.233284544 2023/07/26 12:15:22 [error] 134#134: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 10.19.64.2, server: , request: "GET /api/stats HTTP/1.1", upstream: "http://127.0.0.1:5001/stats", host: "10.19.64.2:5000" 2023-07-26 12:15:22.233334360 10.19.64.2 - - [26/Jul/2023:12:15:22 +0100] "GET /api/stats HTTP/1.1" 502 157 "-" "HomeAssistant/2023.7.3 aiohttp/3.8.5 Python/3.11" "-" 2023-07-26 12:15:22.527162273 [INFO] Preparing go2rtc config... 2023-07-26 12:15:22.727177322 [INFO] The go2rtc service exited with code 1 (by signal 0) 2023-07-26 12:15:23.348278290 [INFO] Service Frigate exited with code 1 (by signal 0) 2023-07-26 12:15:23.360410949 [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15) 2023-07-26 12:15:23.395323650 [INFO] Service NGINX exited with code 0 (by signal 0) config.yml
  9. Thanks for the tips! I put my calm head on and had another go yesterday while watching the Grand Prix! All worked straight away! I copied the newer Reolink config over and switched off RTMP and left everthing else mostly the same! One question! Do you think its better to change the FFMEG settings to one of the presets? Cheers, Timconfig.yml
  10. Ok, did that for hours! I'll stick with v11 as it works! Whilst I appreciate all the work people put into these programs, I find the breaking changes very frustrating, especially when there are so many to work out at once! So I'll move to Unifi Protect as soon as I can afford the cameras, as it has a GUI. Thanks again for your efforts bringing this to Unraid!
  11. Hi, I had a frustrating day yesterday trying to upgrade to v0.12 gave up in the end and rolled back to v0.11.1! I went through the release notes and changed the things I thought and while the docker image was running I had no acces the the gui and the logs wouldn't even open! It was like the log window would crash as soon as it opened! So without a log to see what the errors were I was stuck! Please if someone has time to look at my current config file and point out the bits I need to change, then I'll have another go at it! Cheers Tim config.yml
  12. Hi @KluthR, yes looks like its now working well and backing up NC! Log attached for your info! Thanks again for your work on this plugin! Cheers, Tim ab.debug.log
  13. Ok, yes of course, happy to test! Let me know when available, I’m away for the weekend, back on Monday so can test from then! 😄
  14. Hi @KluthR, Installed new beta as requested and the backup completed successfully! The only thing I noticed is that it skipped the Nextcloud appdata directory I don't want it to do that as that were all the config is! It can and should skip the nextcloud user share directory though! Thanks for you work on this! ab.debug (1).log
  15. Thanks, yes need to map appdata to access config files? Can I stop backing up that bit? I don't think the old plugin did that? But this version has a lot more options, which is great! Thanks for your work! Same with Tautulli i guess? It'd be nice to be able to group apps I guess, so they stop and start together? Also to check for updates while each app/container is stopped for backup, rather than at the end? Thanks again, this is a great upgrade!
  16. Hi, not sure what the problem is but since installing all 3 backups done so far say failed on them! Looks like its a couple of containers that are failing, hoping someone can help me work out the issue? Cheers Tim ab.debug.log
  17. I have this problem on 10 of my docker containers and I'm on 6.12rc-2 so it seems not fixed?
  18. Hi, had a complete system crash! I think its the same issue that has plaged me with all 6.11 releases, the system becomes unstable after shutting down a VM, this time Ubuntu! It only ever crashes after running a VM but not always! On a plus though it seems that rc2 switches off the gpu on shutdown and the monitor now goes into standby! syslog-10.19.64.2 (1).log tower-diagnostics-20230406-1820.zip
  19. Hi, I'd like to know this too? Did you work it out? Cheers, Tim
  20. I don't know what caused this and the amount of crashes since upgrading to 6.11 is very concerning! I wasn't trying to start/stop a VM. The docker apps all seemed to be running ok and I was watching something on Plex. But noticed the GUI was unresponsive and so I pushed the off button, this worked and did a clean shutdown! So something killed the GUI and samba, but not docker or small VM that runs headless for my phone system. Hopefully someone could shed some light? Maybe a plugin of course? Cheers, Tim tower-diagnostics-20230306-1345.zip syslog-10.19.64.2.log
  21. Hi, I have a strange problem, neither of my Linux VM's switch off my GPU, so my monitor stays on! They are ChromeOS (Cloudready) and Ubuntu 22.04. Both worked fine in 6.10, but haven't in any version of 6.11, Windows 11 is fine! I shut Ubuntu down at 16:29 and see errors in the logs? Diagnosics attached. Anybody any ideas? Or is it a known bug? Thanks, Tim tower-diagnostics-20230227-1716.zip
  22. Hi, I keeping thinking/hoping that this bug is fixed! Tried to start a Ubuntu VM and the system crashed! Had to hard reset and I hate doing that! Logs attached, hopefully they point to something? Restarted at around 12:05. Cheers, Tim syslog-10.19.64.2.log tower-diagnostics-20230221-1225.zip
  23. Hi, I would post your diagnostics? The guys at Limetech can't check for bugs if you don't! And no one else can help if its not a bug and some sort of config issue!
  24. I would post your diagnosics so that someone from Limetech can look and see if it's a bug that needs addressing! Don't assume they know about it!