| 25 Nov 2024 |
 @hexa:lossy.network | https://en.wikipedia.org/wiki/List_of_Intel_Celeron_processors#Tremont_based_Celerons | 17:46:57 |
 victorbjelkholm | Eh, it was cheap enough for my purposes so ain't complaining about it :) Had to upgrade the RAM and yeah, no AVX :P Besides Frigate>Tensorflow trying to use AVX (which can be worked around at least), haven't really come across any issues with it which I guess is the main point for me | 17:49:02 |
| @hexa:lossy.network | frigate doesn't pin tensorflow either, so it could require avx at any time | 17:50:59 |
| @hexa:lossy.network | https://github.com/blakeblackshear/frigate/issues/7035 | 17:51:22 |
| @hexa:lossy.network | they didn't care about this problem in 2021 and they sure as hell won't care going forward | 17:51:44 |
| @hexa:lossy.network | so they import tensorflow for the cpu detector | 17:53:21 |
| @hexa:lossy.network | you could be fine with configuring any other detector, maybe | 17:53:27 |
| @hexa:lossy.network | and also audio processing uses tensorflow | 17:53:42 |
|  Jalil David Salamé Messina joined the room. | 18:27:57 |
| Jalil David Salamé Messina | Hi, I'm running into a weird bug/interaction between hass and nginx: when I connect to it locally (over an ssh tunnel) it works, but when I turn on the proxy and connect through nginx, nginx pins a cpu core to 100% and stops working.
I'd like to have a minimal example of it failing, but because my cache and a few other vital services are running in the same service/nginx config, I am kinda hessitant to turn stuff off.
The journalctl and /var/log/nginx logs are unhelpful.
I tried looking around but I cannot find any references to this behaviour. | 20:02:35 |
| Jalil David Salamé Messina | So, I created a coredump of the nginx worker process, and apparently it is stuck during zstd compression. I am 90% this is the cause, but the harmonia cache needs zstd, so I will need to figure out how to turn it off for hass | 21:48:20 |
| Jalil David Salamé Messina | Yup, setting zstd off; in the extraConfig of the vhost fixed it 😅 I'll make a bug report on nixpkgs but I don't know if it is actionable | 21:53:16 |
 symphorien | does the journal contain kernel oops about io_uring ? if so it's a kernel bug | 21:54:42 |
| @hexa:lossy.network | I have the same issue with an nginx instance that proxies harmonia | 21:55:09 |
| @hexa:lossy.network | cc Mic92 | 21:55:12 |
 Mic92 | Well. Good that I just removed this requirement from harmonia yesterday! | 21:56:16 |
| Jalil David Salamé Messina | In reply to @symphorien:xlumurb.eu
does the journal contain kernel oops about io_uring ? if so it's a kernel bug I don't see any io_uring stuff, but I might be looking at the wrong place (journalctl -g io_uring) | 21:57:00 |
| Jalil David Salamé Messina | Nothing in dmesg either (sudo dmesg | rg -i 'oops|io_uring') | 22:00:27 |
