dianasta

I have the lifetime Pro account, nothing to worry about, this is just the new onboarding screen, just click Get Started, and click all the the defaults presented for you, so next , next, next, complete, that's it all done.

Very weird, I just shutdown and start the server and is now fine !

Hello, Everything was working fine for many days on version 7, and now I'm sudenly getting these in the log, curl is failing to check every service, and Parts of the UI is not functioning? Feb 21 09:32:13 Tower2 publish: curl to parity failed Feb 21 09:32:13 Tower2 publish: curl to paritymonitor failed Feb 21 09:32:14 Tower2 publish: curl to fsState failed Feb 21 09:32:14 Tower2 publish: curl to mymonitor failed Feb 21 09:32:14 Tower2 publish: curl to devices failed Feb 21 09:32:14 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:14 Tower2 publish: curl to temperature failed Feb 21 09:32:15 Tower2 publish: curl to devices failed Feb 21 09:32:15 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:16 Tower2 publish: curl to devices failed Feb 21 09:32:16 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:17 Tower2 publish: curl to parity failed Feb 21 09:32:17 Tower2 publish: curl to paritymonitor failed Feb 21 09:32:17 Tower2 publish: curl to fsState failed Feb 21 09:32:17 Tower2 publish: curl to mymonitor failed Feb 21 09:32:17 Tower2 publish: curl to devices failed Feb 21 09:32:17 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:18 Tower2 publish: curl to devices failed Feb 21 09:32:18 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:19 Tower2 publish: curl to temperature failed Feb 21 09:32:19 Tower2 publish: curl to devices failed Feb 21 09:32:19 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:20 Tower2 publish: curl to parity failed Feb 21 09:32:20 Tower2 publish: curl to paritymonitor failed Feb 21 09:32:20 Tower2 publish: curl to fsState failed Feb 21 09:32:20 Tower2 publish: curl to mymonitor failed Feb 21 09:32:20 Tower2 publish: curl to devices failed Feb 21 09:32:20 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:21 Tower2 publish: curl to devices failed Feb 21 09:32:21 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:23 Tower2 publish: curl to devices failed Feb 21 09:32:23 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:23 Tower2 publish: curl to parity failed Feb 21 09:32:23 Tower2 publish: curl to paritymonitor failed Feb 21 09:32:23 Tower2 publish: curl to fsState failed Feb 21 09:32:23 Tower2 publish: curl to mymonitor failed Feb 21 09:32:24 Tower2 publish: curl to devices failed Feb 21 09:32:24 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:24 Tower2 publish: curl to temperature failed Feb 21 09:32:25 Tower2 publish: curl to devices failed Feb 21 09:32:25 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:26 Tower2 publish: curl to devices failed Feb 21 09:32:26 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:26 Tower2 publish: curl to parity failed Feb 21 09:32:26 Tower2 publish: curl to paritymonitor failed Feb 21 09:32:26 Tower2 publish: curl to fsState failed Feb 21 09:32:26 Tower2 publish: curl to mymonitor failed Feb 21 09:32:27 Tower2 publish: curl to devices failed Feb 21 09:32:27 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:28 Tower2 publish: curl to devices failed Feb 21 09:32:28 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:29 Tower2 publish: curl to devices failed Feb 21 09:32:29 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:29 Tower2 publish: curl to parity failed Feb 21 09:32:29 Tower2 publish: curl to paritymonitor failed Feb 21 09:32:29 Tower2 publish: curl to fsState failed Feb 21 09:32:29 Tower2 publish: curl to mymonitor failed Feb 21 09:32:29 Tower2 publish: curl to temperature failed Feb 21 09:32:30 Tower2 publish: curl to devices failed Feb 21 09:32:30 Tower2 publish: curl to arraymonitor failed Feb 21 09:32:31 Tower2 publish: curl to devices failed Feb 21 09:32:31 Tower2 publish: curl to arraymonitor failed

I see the same on Unraid 6.12.14, cannot update the plugin getting the error below (Update Incompatible).

I found it, it was the OpenVINO Object Detection for Scrypted, in the Scrypted Docker container. Interesting though, I was not geting these errors before! hhmmmm.....

Looks like this is the NPU Device as described below and this link (https://docs.openvino.ai/2024/openvino-workflow/running-inference/inference-devices-and-modes/npu-device.html). Anyone have any idea which plugin is that, and is causing all these errors? Nov 27 15:40:41 Tower kernel: traps: python3[1330] trap invalid opcode ip:153d4cc4e9d7 sp:7ffde264b860 error:0 in libopenvino_intel_npu_plugin.so[153d4cc2f000+1f1000] Nov 27 15:41:46 Tower kernel: traps: python3[4545] trap invalid opcode ip:1466c124e9d7 sp:7ffc04608690 error:0 in libopenvino_intel_npu_plugin.so[1466c122f000+1f1000] Nov 27 15:42:50 Tower kernel: traps: python3[7635] trap invalid opcode ip:14f4dee4e9d7 sp:7ffc822895c0 error:0 in libopenvino_intel_npu_plugin.so[14f4dee2f000+1f1000] Nov 27 15:43:54 Tower kernel: traps: python3[10908] trap invalid opcode ip:14d54424e9d7 sp:7ffe17f3fb20 error:0 in libopenvino_intel_npu_plugin.so[14d54422f000+1f1000] Nov 27 15:44:59 Tower kernel: traps: python3[14029] trap invalid opcode ip:14e7c484e9d7 sp:7ffcb1e1abb0 error:0 in libopenvino_intel_npu_plugin.so[14e7c482f000+1f1000] Nov 27 15:46:03 Tower kernel: traps: python3[17257] trap invalid opcode ip:14a75104e9d7 sp:7ffefbde0230 error:0 in libopenvino_intel_npu_plugin.so[14a75102f000+1f1000] Nov 27 15:47:07 Tower kernel: traps: python3[20796] trap invalid opcode ip:14f64d04e9d7 sp:7ffedc2fe2c0 error:0 in libopenvino_intel_npu_plugin.so[14f64d02f000+1f1000] Nov 27 15:48:11 Tower kernel: traps: python3[24024] trap invalid opcode ip:14597c44e9d7 sp:7ffee64afa70 error:0 in libopenvino_intel_npu_plugin.so[14597c42f000+1f1000] Nov 27 15:49:16 Tower kernel: traps: python3[27169] trap invalid opcode ip:154b2824e9d7 sp:7ffe716fc2f0 error:0 in libopenvino_intel_npu_plugin.so[154b2822f000+1f1000] Nov 27 15:50:20 Tower kernel: traps: python3[30277] trap invalid opcode ip:1552e8c4e9d7 sp:7ffe1b18bec0 error:0 in libopenvino_intel_npu_plugin.so[1552e8c2f000+1f1000] Nov 27 15:51:24 Tower kernel: traps: python3[946] trap invalid opcode ip:15015444e9d7 sp:7ffdbf06b8d0 error:0 in libopenvino_intel_npu_plugin.so[15015442f000+1f1000] Nov 27 15:52:28 Tower kernel: traps: python3[4087] trap invalid opcode ip:14e66504e9d7 sp:7ffd5a43c160 error:0 in libopenvino_intel_npu_plugin.so[14e66502f000+1f1000] Nov 27 15:53:32 Tower kernel: traps: python3[7228] trap invalid opcode ip:14a50d04e9d7 sp:7fffcd5edcd0 error:0 in libopenvino_intel_npu_plugin.so[14a50d02f000+1f1000] Nov 27 15:54:37 Tower kernel: traps: python3[10382] trap invalid opcode ip:151271c4e9d7 sp:7ffeaa968db0 error:0 in libopenvino_intel_npu_plugin.so[151271c2f000+1f1000] Nov 27 15:55:41 Tower kernel: traps: python3[13717] trap invalid opcode ip:15037c84e9d7 sp:7ffefade28e0 error:0 in libopenvino_intel_npu_plugin.so[15037c82f000+1f1000] Nov 27 15:56:45 Tower kernel: traps: python3[16910] trap invalid opcode ip:15337c84e9d7 sp:7ffc5c565da0 error:0 in libopenvino_intel_npu_plugin.so[15337c82f000+1f1000] NPU Device The Neural Processing Unit is a low-power hardware solution, introduced with the Intel® Core™ Ultra generation of CPUs (formerly known as Meteor Lake). It enables you to offload certain neural network computation tasks from other devices, for more streamlined resource management. NPU Plugin is now available through all relevant OpenVINO distribution channels. Supported Platforms: Host: Intel® Core™ Ultra (former Meteor Lake) NPU device: NPU 3720 OS: Ubuntu* 22.04 64-bit (with Linux kernel 6.6+), MS Windows* 11 64-bit (22H2, 23H2) NPU Plugin needs an NPU Driver to be installed on the system for both compiling and executing a model.

Upgraded from 6.12.12 to 6.12.14 and getting the errors below. Nov 27 10:15:24 Tower kernel: traps: python3[15621] trap invalid opcode ip:15029c24e9d7 sp:7ffc1aae7d80 error:0 in libopenvino_intel_npu_plugin.so[15029c22f000+1f1000] Nov 27 10:16:28 Tower kernel: traps: python3[17272] trap invalid opcode ip:14e5f144e9d7 sp:7ffd7975d760 error:0 in libopenvino_intel_npu_plugin.so[14e5f142f000+1f1000] Nov 27 10:17:33 Tower kernel: traps: python3[19079] trap invalid opcode ip:14d5bd04e9d7 sp:7fffe4d61430 error:0 in libopenvino_intel_npu_plugin.so[14d5bd02f000+1f1000] Nov 27 10:18:37 Tower kernel: traps: python3[21496] trap invalid opcode ip:1491e964e9d7 sp:7fff100edc40 error:0 in libopenvino_intel_npu_plugin.so[1491e962f000+1f1000] Nov 27 10:19:41 Tower kernel: traps: python3[23108] trap invalid opcode ip:15480824e9d7 sp:7ffdaea17f20 error:0 in libopenvino_intel_npu_plugin.so[15480822f000+1f1000] Nov 27 10:20:45 Tower kernel: traps: python3[24745] trap invalid opcode ip:1481bc84e9d7 sp:7ffe211b6dd0 error:0 in libopenvino_intel_npu_plugin.so[1481bc82f000+1f1000]

Hello, I would also like to report the same issue as above. Mar 30 03:31:09 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 000000005aa165ea Mar 30 03:31:09 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 0000000075e8eda5 Mar 30 03:31:10 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 00000000b887951d Mar 30 03:31:10 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 000000005c37aaa9 Mar 30 03:31:11 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 00000000b590034f Mar 30 03:31:11 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 0000000062194ea4 Mar 30 03:31:11 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 000000002bfc4cc1 Mar 30 03:31:11 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 00000000b9a86e54 Mar 30 03:31:11 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 000000004f283bd6 Mar 30 03:31:11 Tower kernel: CIFS: VFS: directory entry name would overflow frame end of buf 000000003879e2fc Regards.

Hello, Could you please let us know if the below interesting change is in the plans ? - Login with device enabled for self-host Thanks!

Hello, Could you please update the container to include the following new feature? * Version 2023.7.0 Latest Password Manager - Login with device enabled for self-host Thanks!

Excellent thanks works great!

yes thanks all good !

Hello, Does anyone know how to solve this php error in the container "PHP executable not found. Install PHP 7 and add it to your PATH or set the php.executablePath" ?

Hello, Does anyone know how to solve this php error in the container "PHP executable not found. Install PHP 7 and add it to your PATH or set the php.executablePath" ?

Thank you will do!