tictoc

Okay, so I've re-read the Crowdsec docs a bit more carefully and Crowdsec can actually parse the logs directly from docker so a log file isn't necessary. I haven't actually go this to work yet but it seems it should. I will raise it as a question to the Crowdsec folks. Edit: In case anyone else needs this for Immich or any other docker logs a quick write up follows. Pr-requisites: - the dockersocket app from CA to proxy the docker socket - a custom docker network that dockersocket and Crowdsec are on. Possibly Immich too as that is where I have it. - Immich collection installed on Crowdsec To enable Crowdsec to read from dockersocket you need to add the variable `INFO: 1` to the dockersocket container. Source. In your Crowdsec aquis.yaml add: source: docker container_name: - immich labels: type: immich docker_host: tcp://dockersocket:2375 Source. You will also need to whitelist some of the api calls. Create a new yaml file in /crowdsec/parsers/s02-enrich/ name: crowdsecurity/immich-whitelists description: "Whitelist false positive from Immich-api" filter: "evt.Meta.service == 'http' && evt.Meta.log_type in ['http_access-log', 'http_error-log']" whitelist: reason: "Whitelist false positive from Immich-api" expression: - evt.Parsed.traefik_router_name == 'immich@docker' && evt.Meta.http_verb == 'POST' && evt.Meta.http_status == '403' && evt.Parsed.request contains '/asset/upload' - evt.Parsed.traefik_router_name == 'immich@docker' && evt.Meta.http_verb == 'GET' && evt.Meta.http_status == '429' && evt.Parsed.request contains '/api/asset/thumbnail/' - evt.Parsed.traefik_router_name == 'immich@docker' && evt.Meta.http_verb == 'GET' && evt.Meta.http_status == '200' && evt.Parsed.request contains '/api/asset/thumbnail/' - evt.Parsed.traefik_router_name == 'immich@docker' && evt.Meta.http_verb == 'GET' && evt.Meta.http_status == '304' && evt.Parsed.request contains '/api/asset/thumbnail/' Source. Restart Crowdsec and Immich logs should be being parsed with no bans from using the mobile app.

That seemed to work for me too!

I'm trying to connect Immich to Crowdsec however I'm missing the immich_server.log from /mnt/user/appdata/immich/. It does appear to be in /mnt/user/system/docker/docker/containers/containerid/ though with the name containerid-json.log. I assume something is not right there? Any ideas how can I get it show in appdata/immich?

Hey @jude. Yes, everything is still working for me!

I've been having this issue too. Mobo is Asus x470-f Gaming. Currently on Unraid 6.12.10. With fans on auto detect in bios, DC fans would switch off and PWM would spin up to max after an hour or so from start up. Setting the PWM fans to PWM in bios stopped them from maxing out but instead ramped to ~1000rpm which was weird. Applying the `blacklist asus_wmi_sensors` fix per @BomB191's post stopped the fans from deviating from the bios settings. Interestingly, then installing @ich777 plugin *ITE IT87 Driver* exposed the fans again to *System Temp* for monitoring. It's been 12 hours now and fan speeds are still behaving as set in bios. Not sure why all that works but hopefully it helps someone else.

Just to close this out, it was the CPU. New CPU installed and everything is running as normal. Thanks for your help @JorgeB.

Thanks. I had that all set up already except for disabling global c-states but enabling that didn't resolve anything. Hardware testing so far is pointing to the CPU.

Thanks @JorgeB. I've ruled out all the add-on cards now. I've got another Ryzen system I can cannibalise and will report back.

A few days a ago my Unraid server hung during a parity check. This wasn't scheduled so I assume it was after a crash. The system continued to hang each time it attempted to run a parity check. I removed the parity disks and started in maintenance mode and ran check disks but the server crashed and rebooted. I tried starting all docker containers and the system hung. I suspected the PSU given it was only happening during high load and it was over 10 years old so swapped that out and removed all sata splitters from the build. Still crashed/hung. Then during a couple of boots the boot sequence hung so I tried a new USB port with no luck. Checked the drive on my windows system and it found and repaired errors but Unraid still crashed. Tried a new USB drive restored from a backup. Crashed. Booting into safe mode failed the first time then crashed during a disk check. I've tried booting with UEFI and BIOS. System is Ryzen and is configured per FAQ. I also tried disabling global C-states with no luck. Currently running memtest but has passed twice so far. System has been up and running for a few months now. Last change was a bios update from ASUS a couple of weeks ago and the update to Unraid 6.12.10. System details : AMD 2700x | ASUS x470-F | 32gb RAM | Nvidia GTX1070 | 9211-8i controller card | 7x 4TB HDD (dual parity) | 2x 500GB SSD | 2x 500GB NVMe | Corsair RM850x | Intel Dual port ethernet card I am new to Unraid and this is the first issue I've had so I think my troubleshooting has been a bit haphazard so any help is appreciated! Anyone have any thoughts on what might be going on? Syslogs are from the last couple of crashes / system hangs. syslog-previous-20140425-0831.zip syslog-20240425-0835.zip unraidserver-diagnostics-20240425-0824.zip