irishjd

I finished reinstalling with the nvidia option and entered all of the required config settings, but I am still getting a lot off errors if I try enabling h/w acceleration: 2023-10-02 10:40:40.263887752 [2023-10-02 10:40:40] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:40:40.263918539 [2023-10-02 10:40:40] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-10-02 10:40:42.371988851 [2023-10-02 10:40:39] detector.coral INFO : Starting detection process: 2262 2023-10-02 10:40:42.371997559 [2023-10-02 10:40:39] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2023-10-02 10:40:42.382914475 [2023-10-02 10:40:42] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2023-10-02 10:40:47.289382996 [INFO] Starting go2rtc healthcheck service... 2023-10-02 10:40:59.420306333 [2023-10-02 10:40:59] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-10-02 10:40:59.436311048 [2023-10-02 10:40:59] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-10-02 10:40:59.436328655 [2023-10-02 10:40:59] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x55d8a9da1040] Cannot load libcuda.so.1 2023-10-02 10:40:59.436334006 [2023-10-02 10:40:59] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x55d8a9da1040] Could not dynamically load CUDA 2023-10-02 10:40:59.436346619 [2023-10-02 10:40:59] ffmpeg.birdcam.detect ERROR : Device creation failed: -1. 2023-10-02 10:40:59.436399051 [2023-10-02 10:40:59] ffmpeg.birdcam.detect ERROR : [h264 @ 0x55d8a9d9b4c0] No device available for decoder: device type cuda needed for codec h264. 2023-10-02 10:40:59.436405127 [2023-10-02 10:40:59] ffmpeg.birdcam.detect ERROR : Device setup failed for decoder on input stream #0:2 : Operation not permitted 2023-10-02 10:41:00.319363449 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.319389983 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.319397193 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.319404083 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.319410810 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.319416764 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.319422951 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.335891151 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:00.336886460 [2023-10-02 10:41:00] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-10-02 10:41:09.452729614 [2023-10-02 10:41:09] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-10-02 10:41:09.452943020 [2023-10-02 10:41:09] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-10-02 10:41:09.453094972 [2023-10-02 10:41:09] ffmpeg.birdcam.detect ERROR : [h264 @ 0x56496a9769c0] Missing reference picture, default is 0 2023-10-02 10:41:09.453317708 [2023-10-02 10:41:09] ffmpeg.birdcam.detect ERROR : [h264 @ 0x56496a9769c0] decode_slice_header error 2023-10-02 10:41:09.453526268 [2023-10-02 10:41:09] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x56496a9e6700] Cannot load libcuda.so.1 2023-10-02 10:41:09.453724545 [2023-10-02 10:41:09] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x56496a9e6700] Could not dynamically load CUDA 2023-10-02 10:41:09.453887118 [2023-10-02 10:41:09] ffmpeg.birdcam.detect ERROR : Device creation failed: -1. 2023-10-02 10:41:09.454082484 [2023-10-02 10:41:09] ffmpeg.birdcam.detect ERROR : [h264 @ 0x56496a9e1e00] No device available for decoder: device type cuda needed for codec h264. 2023-10-02 10:41:09.454317782 [2023-10-02 10:41:09] ffmpeg.birdcam.detect ERROR : Device setup failed for decoder on input stream #0:2 : Operation not permitted 2023-10-02 10:41:10.380691324 [2023-10-02 10:41:10] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:10.381545593 [2023-10-02 10:41:10] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:10.382056723 [2023-10-02 10:41:10] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-10-02 10:41:19.516829810 [2023-10-02 10:41:19] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-10-02 10:41:19.516840062 [2023-10-02 10:41:19] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-10-02 10:41:19.516842455 [2023-10-02 10:41:19] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x56157000a940] Cannot load libcuda.so.1 2023-10-02 10:41:19.516844550 [2023-10-02 10:41:19] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x56157000a940] Could not dynamically load CUDA 2023-10-02 10:41:19.516846341 [2023-10-02 10:41:19] ffmpeg.birdcam.detect ERROR : Device creation failed: -1. 2023-10-02 10:41:19.516848379 [2023-10-02 10:41:19] ffmpeg.birdcam.detect ERROR : [h264 @ 0x56156ff3a440] No device available for decoder: device type cuda needed for codec h264. 2023-10-02 10:41:19.516850369 [2023-10-02 10:41:19] ffmpeg.birdcam.detect ERROR : Device setup failed for decoder on input stream #0:2 : Operation not permitted 2023-10-02 10:41:20.379321927 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.379331894 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387038483 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387065073 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387070413 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387075330 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387080167 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387084457 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387088741 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387093004 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387097294 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387271005 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387276949 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387282942 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387287532 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387348991 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387354264 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387358844 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387363088 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387433363 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387438750 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387442976 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387447590 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387451933 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387456273 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387460714 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387464924 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387469120 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387541206 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387546396 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387550586 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387554699 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387559336 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387563543 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387567793 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387572046 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387656249 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387661495 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.387665705 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.389857922 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:20.390326728 [2023-10-02 10:41:20] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread... 2023-10-02 10:41:29.537778246 [2023-10-02 10:41:29] watchdog.birdcam ERROR : Ffmpeg process crashed unexpectedly for birdcam. 2023-10-02 10:41:29.537801219 [2023-10-02 10:41:29] watchdog.birdcam ERROR : The following ffmpeg logs include the last 100 lines prior to exit. 2023-10-02 10:41:29.537803624 [2023-10-02 10:41:29] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x561eb03a7840] Cannot load libcuda.so.1 2023-10-02 10:41:29.537805484 [2023-10-02 10:41:29] ffmpeg.birdcam.detect ERROR : [AVHWDeviceContext @ 0x561eb03a7840] Could not dynamically load CUDA 2023-10-02 10:41:29.537807339 [2023-10-02 10:41:29] ffmpeg.birdcam.detect ERROR : Device creation failed: -1. 2023-10-02 10:41:29.537809255 [2023-10-02 10:41:29] ffmpeg.birdcam.detect ERROR : [h264 @ 0x561eb03aac40] No device available for decoder: device type cuda needed for codec h264. 2023-10-02 10:41:29.537811060 [2023-10-02 10:41:29] ffmpeg.birdcam.detect ERROR : Device setup failed for decoder on input stream #0:2 : Operation not permitted 2023-10-02 10:41:30.413770640 [2023-10-02 10:41:30] frigate.video ERROR : birdcam: Unable to read frames from ffmpeg process. 2023-10-02 10:41:30.414111185 [2023-10-02 10:41:30] frigate.video ERROR : birdcam: ffmpeg process is not running. exiting capture thread...

I will need to reinstall it then as I didn't have the video card when I first set this up. Thanks for pointing me in the right direction!

Is there any documentation available for setting up a NVIDIA GPU for use with Frigate on unRAID? I installed a NVIDIA Quattro in my unRAID server and then installed the unRAID NVIDIA Driver package. Per the instructions, I then disabled Docker and then re-enabled Docker. According to the Frigate documentation, "Additional configuration is needed for the Docker container to be able to access the NVIDIA GPU", but their instructions appear to be for a linux host running Docker. I don't see anything specific for enabling it in unRAID. Anyway, if I turn on hardware acceleration via "hwaccel_args: preset-nvidia-h264". I get a bunch of errors, so I am pretty certain that the Docker Container can not talk to the NVIDIA GPU.

So it finally updated and posted one. It looks like there is a long delay between Frigate recording it and it showing up in WhosAtMyFeeder? There is about a two hour difference on the timestamps.

I did, I used the sample as a template. Here is what my frigate config.yml looks like: mqtt: host: mqtt port: 1883 topic_prefix: frigate # user: mqtt_username_here # password: mqtt_password_here stats_interval: 60 detectors: coral: type: edgetpu device: usb ffmpeg: global_args: -hide_banner -loglevel warning # hwaccel_args: -hwaccel_output_format qsv -c:v h264_qsv input_args: preset-rtsp-generic output_args: # Optional: output args for detect streams (default: shown below) detect: -threads 2 -f rawvideo -pix_fmt yuv420p # Optional: output args for record streams (default: shown below) record: preset-record-generic detect: width: 1920 height: 1080 objects: track: - bird snapshots: enabled: true cameras: birdcam: record: enabled: True events: pre_capture: 5 post_capture: 5 objects: - bird ffmpeg: # hwaccel_args: -hwaccel_output_format qsv -c:v h264_qsv inputs: - path: rtsps://192.168.100.1:7441/uN84YwyHVF8TCCd8?enableSrtp roles: - detect - record mqtt: enabled: True bounding_box: False #this will get rid of the box around the bird. We already know it is a bird. Sheesh. timestamp: False #this will get rid of the time stamp in the image. quality: 95 #default quality is 70, which will get you lots of compression artifacts I had to comment out the hardware acceleration settings as I still don't have a discrete GPU (on order).

I actually had to remove the "DATABASE_URL" label to get it to run. Leaving it blank, resulting in errors trying to connect to an undefined remote postgres server.

So I have one more issue. Frigate is working exactly as expected. It is capturing footage of the birds and recognizing them as a "bird". However, WhosAtMyFeeder is not logging anything. What is the best way to troubleshoot this issue?

Thank you for explaining this for me. I will did up an older card as I don't have many cameras.

Ahh, I completely missed that. Those errors are now gone. I also think I know why I get errors when trying to enable hw acceleration in frigate. The R820 uses: Intel® Xeon® CPU E5-4650 0 @ 2.70GHz processors (which are in the E5 family). According to Intel, only the E6 and newer chips support hw video acceleration. Would it be worth it to install a discrete video card for hw acceleration? If so, which would work best with UnRAID?

Thanks a lot! that got the WebUI working! I am still seeing these errors in the logs: "socket.gaierror: [Errno -2] Name or service not known Cannot assign requested address INFO: Created TensorFlow Lite XNNPACK delegate for CPU. Cannot assign requested address INFO: Created TensorFlow Lite XNNPACK delegate for CPU. Cannot assign requested address INFO: Created TensorFlow Lite XNNPACK delegate for CPU. Cannot assign requested address INFO: Created TensorFlow Lite XNNPACK delegate for CPU. WARNING: This is a development server. Do not use it in a production deployment. Use a production WSGI server instead. * Running on all addresses (0.0.0.0) * Running on http://127.0.0.1:7766 * Running on http://172.18.0.25:7766" One other issue I noticed was with Frigate in that I can not use the HW Acceleration lines for ffmpeg as all it does is generate a lot of errors. I am trying to use "hwaccel_args: preset-vaapi" as I am running Unraid on a Dell PowerEdge R820 with Intel Xeon processors.

So I removed the MQQT port number. As far as the config goes, it is really simple right now (I am trying to find documentation on which statements are required and which are available: frigate: frigate_url: http://192.168.100.69:1984 mqtt_server: 192.168.100.69 mqtt_auth: false mqtt_username: mqtt_password: main_topic: frigate camera: - "Remi_Cam" object: bird classification: model: model.tflite threshold: 0.7 webui: port: 7766 host: 192.168.100.69

So I have Frigate working with a Coral AI USB adapter. I have been trying to get the "WhosAtMyFeeder" app working with it, but I am not having any luck. I am seeing 2 errors in the logs, but I am not sure how to fix them: INFO: Created TensorFlow Lite XNNPACK delegate for CPU. Process Process-2: Traceback (most recent call last): File "/usr/local/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap self.run() File "/usr/local/lib/python3.8/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "./speciesid.py", line 239, in run_mqtt_client client.connect(config['frigate']['mqtt_server']) File "/usr/local/lib/python3.8/site-packages/paho/mqtt/client.py", line 914, in connect return self.reconnect() File "/usr/local/lib/python3.8/site-packages/paho/mqtt/client.py", line 1044, in reconnect sock = self._create_socket_connection() File "/usr/local/lib/python3.8/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source) File "/usr/local/lib/python3.8/socket.py", line 787, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): File "/usr/local/lib/python3.8/socket.py", line 918, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known Cannot assign requested address INFO: Created TensorFlow Lite XNNPACK delegate for CPU. Cannot assign requested address Process Process-2: Traceback (most recent call last): File "/usr/local/lib/python3.8/multiprocessing/process.py", line 315, in _bootstrap self.run() File "/usr/local/lib/python3.8/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "./speciesid.py", line 239, in run_mqtt_client client.connect(config['frigate']['mqtt_server']) File "/usr/local/lib/python3.8/site-packages/paho/mqtt/client.py", line 914, in connect return self.reconnect() File "/usr/local/lib/python3.8/site-packages/paho/mqtt/client.py", line 1044, in reconnect sock = self._create_socket_connection() File "/usr/local/lib/python3.8/site-packages/paho/mqtt/client.py", line 3685, in _create_socket_connection return socket.create_connection(addr, timeout=self._connect_timeout, source_address=source) File "/usr/local/lib/python3.8/socket.py", line 787, in create_connection for res in getaddrinfo(host, port, 0, SOCK_STREAM): File "/usr/local/lib/python3.8/socket.py", line 918, in getaddrinfo for res in _socket.getaddrinfo(host, port, family, type, proto, flags): socket.gaierror: [Errno -2] Name or service not known Calling Main Time: 2023-09-19 10:38:23.709 Python version 3.8.17 (default, Jun 13 2023, 16:09:51) [GCC 10.2.1 20210110] Version info. sys.version_info(major=3, minor=8, micro=17, releaselevel='final', serial=0) Starting threads for Flask and MQTT Starting flask app Starting MQTT client. Connecting to: 192.168.100.69:9001 * Serving Flask app 'webui' * Debug mode: off Calling Main Time: 2023-09-19 10:46:37.442 Python version 3.8.17 (default, Jun 13 2023, 16:09:51) [GCC 10.2.1 20210110] Version info. sys.version_info(major=3, minor=8, micro=17, releaselevel='final', serial=0) Starting threads for Flask and MQTT Starting flask app * Serving Flask app 'webui' * Debug mode: off Starting MQTT client. Connecting to: 192.168.100.69:1883 Any thoughts on what the issue is?

Thanks again! So far, everything is happy.

@JorgeBthanks for the quick response! I will give that a shot today. Any potential side effects that I should be aware of by making this change?

Ever since I updated all of my drives to ZFS (about a month ago), My Unraid server’s web interface becomes unresponsive every couple of days. The only way to recover it is to power-cycle the server. I have attached a diagnostic dump in hopes that someone can help me resolve this. v/r Jon unraid-1-smart-20230525-0701.zip unraid-1-diagnostics-20230916-1423.zip

That makes sense... I remember connect being updated just a day or two ago.

Definitely! I am having the same issue as well.

@lucahammer thanks for the catch in the error log. I stopped the container, deleted the data from appdata, and restart with v8. All is working fine now.

Ah Ha... somehow I completely missed that. Let me uninstall/reinstall as there is no persistent data that I need to keep.

Even after adding the labels and changing the perms, v8 still won't run: {"@timestamp":"2023-08-22T13:50:46.792Z", "log.level":"ERROR", "message":"fatal exception while booting Elasticsearch", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"main","log.logger":"org.elasticsearch.bootstrap.Elasticsearch","elasticsearch.node.name":"c02e0ef699aa","elasticsearch.cluster.name":"docker-cluster","error.type":"java.lang.IllegalStateException","error.message":"Cannot start this node because it holds metadata for indices created with version [6.6.2] with which this node of version [8.8.1] is incompatible. Revert this node to version [7.17.10] and delete any indices created in versions earlier than [7.0.0] before upgrading to version [8.8.1]. If all such indices have already been deleted, revert this node to version [7.17.10] and wait for it to join the cluster to clean up any older indices from its metadata.","error.stack_trace":"java.lang.IllegalStateException: Cannot start this node because it holds metadata for indices created with version [6.6.2] with which this node of version [8.8.1] is incompatible. Revert this node to version [7.17.10] and delete any indices created in versions earlier than [7.0.0] before upgrading to version [8.8.1]. If all such indices have already been deleted, revert this node to version [7.17.10] and wait for it to join the cluster to clean up any older indices from its metadata.\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.checkForIndexCompatibility(NodeEnvironment.java:537)\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.upgradeLegacyNodeFolders(NodeEnvironment.java:414)\n\tat [email protected]/org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:307)\n\tat [email protected]/org.elasticsearch.node.Node.<init>(Node.java:483)\n\tat [email protected]/org.elasticsearch.node.Node.<init>(Node.java:327)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch$2.<init>(Elasticsearch.java:216)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.initPhase3(Elasticsearch.java:216)\n\tat [email protected]/org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:67)\n"} V7 works fine...

Any chance that we can get native Wazuh agent support (or support for another NMS)? I found a Docker Wazuh agent that I was able to get working, but it is only exposing the docker env, and not the unraId env. Jon

I was reading through the docs and watching a couple of You Tubes on NUT. It appeared that the WebGUI provided more information than what is available in the plugin. Not really a big deal as it does everything Ineed it to. Guess I was more curious than anything. Jon

So, I am pretty sure that I am overlooking something. simple I have the NUT Plugin and configured. Its is communication with the UPS fine. NUT does have a Web GUI, correct? If so, how do I access it? Since it is running on my UnRAID server, Iknow the IP address, but what port is it listening on? v/r Jon

@kubed_zeroThanks for all of the work to figure this out!

Thanks @kubed_zero, that makes sense now.