fireplex

Hi, my server powered itself off in the middle of the night, no one near it. Is elogind-daemon part of the standard unRAID build please ? Jul 25 02:32:54 Tower emhttpd spinning down /dev/sdd Jul 25 03:01:11 Tower root /mnt/cache: 83.7 GiB (89874059264 bytes) trimmed Jul 25 03:04:06 Tower elogind-daemon Power key pressed. Jul 25 03:04:06 Tower elogind-daemon Powering Off... Jul 25 03:04:06 Tower elogind-daemon System is powering down.. Jul 25 03:04:06 Tower shutdown shutting down for system halt Jul 25 03:04:06 Tower init Switching to runlevel: 0 Jul 25 03:04:06 Tower flash_backup stop watching for file changes

So I have a share that I used some time ago and I deleted all files within it, and on the GUI deleted the share. All is good until I reboot, then the empty share reappears again. I have checked my individual disks /mnt/diskX and it's not there, I am guessing there is some config file somewhere that has not been updated, any ideas how I can resolve this please? unRAID 6.12.3

Could you elaborate on this at all, what specifics of ipvlan does the router need to support ? Thanks.

Just to follow up on the issue I had, in case it helps anyone, I realised that unRAID was being assigned IPv6 addresses by my router (even though I tried to disable it on my router). Changing the unRAID Network Settings from IPv4 to IPv4 + IPv6 fixed the intermittent connectivity issues I was having and I can access \\tower consistently every time now from all my PCs 😀

Hi, I removed data disks 4 & 5 from my array and now the disks are numbered 1,2,3,6 and 7 as per below. Any issues if I stop the array and assign 6 and 7 to 4 & 5 respectively ? (I know, just hate seeing things like that 😆) ?

Yes, I have unRAID running 24x7 and its the Local Master (according to Dynix plugin). I'll have a look but I'm a little hesitant to start chaning things on all my PCs when they used to work fine.

So, it seems if I await around 10 to 15 minutes after booting my PCs they can they connect to //TOWER OK. Bizarre

I deleted the credential and re-created it but still the same issue. The weird thing is, sometimes after trying multiple times to access it, it will eventually work and then typically stays working for a period of time then fails again. Just used to be rock solid, now very hit and miss. And on multiple PCs. I'm also seeing in the samba.log repeated lines like: [2022/12/21 15:58:01.698910, 1] ../../source3/winbindd/wb_queryuser.c:402(wb_queryuser_got_gid) Returning NT_STATUS_NO_SUCH_USER xid.type must be ID_TYPE_UID or ID_TYPE_BOTH. [2022/12/21 15:58:01.698943, 5] ../../source3/winbindd/wb_queryuser.c:466(wb_queryuser_recv) WB command queryuser end. state->info: struct wbint_userinfo domain_name : * domain_name : '' acct_name : * acct_name : 'root' full_name : NULL homedir : * homedir : '/home/%D/%U' shell : * shell : '/bin/false' uid : 0x0000000000000000 (0) primary_gid : 0x00000000ffffffff (4294967295) primary_group_name : NULL user_sid : S-1-5-21-1865665554-1384364343-2247375095-1000 group_sid : S-1-5-21-1865665554-1384364343-2247375095-513 [2022/12/21 15:58:01.699184, 1] ../../source3/winbindd/winbindd_getgroups.c:259(winbindd_getgroups_recv) Could not convert sid S-1-5-21-1865665554-1384364343-2247375095-1000: NT_STATUS_NO_SUCH_USER [2022/12/21 15:58:01.699225, 3] ../../source3/winbindd/winbindd.c:563(process_request_done) process_request_done: [nss_winbind(30222):GETGROUPS]: NT_STATUS_NO_SUCH_USER [2022/12/21 15:58:01.699733, 5] ../../source3/winbindd/wb_sids2xids.c:84(wb_sids2xids_send) WB command sids2xids start. Resolving 1 SID(s). [2022/12/21 15:58:01.699811, 5] ../../source3/winbindd/wb_sids2xids.c:775(wb_sids2xids_recv) WB command sids2xids end. [2022/12/21 15:58:01.699836, 5] ../../source3/winbindd/wb_sids2xids.c:779(wb_sids2xids_recv) 0: Found XID 4294967295 for SID S-1-5-21-1865665554-1384364343-2247375095-513 [2022/12/21 15:58:01.699864, 1] ../../source3/winbindd/wb_queryuser.c:402(wb_queryuser_got_gid) Returning NT_STATUS_NO_SUCH_USER xid.type must be ID_TYPE_UID or ID_TYPE_BOTH. [2022/12/21 15:58:01.699897, 5] ../../source3/winbindd/wb_queryuser.c:466(wb_queryuser_recv) WB command queryuser end. state->info: struct wbint_userinfo domain_name : * domain_name : '' acct_name : * acct_name : 'root' full_name : NULL homedir : * homedir : '/home/%D/%U' shell : * shell : '/bin/false' uid : 0x0000000000000000 (0) primary_gid : 0x00000000ffffffff (4294967295) primary_group_name : NULL user_sid : S-1-5-21-1865665554-1384364343-2247375095-1000 group_sid : S-1-5-21-1865665554-1384364343-2247375095-513 [2022/12/21 15:58:01.700123, 1] ../../source3/winbindd/winbindd_getgroups.c:259(winbindd_getgroups_recv) Could not convert sid S-1-5-21-1865665554-1384364343-2247375095-1000: NT_STATUS_NO_SUCH_USER [2022/12/21 15:58:01.700245, 3] ../../source3/winbindd/winbindd.c:563(process_request_done) process_request_done: [nss_winbind(30223):GETGROUPS]: NT_STATUS_NO_SUCH_USER

Everything was working fine with my system, but as some point something has changed and now I too, on multiple Windows PCs, have the: My settings looks ok here: and tower appears under File Explorer: If I access the array via \\192.168.1.25 everything is fine. Any ideas? I see lot's of different changes being done to various Windows settings but the thing is this all used to work OK, wish I could remember when/what has changed. Thanks!

Thanks for the help, did a reboot, came up stopped, did a start and all looks good with a new parity sync beginning

Ok great, thanks.

Yes, I normally use Firefox but as per my post I cleared cache and tried Edge, same issue. Am I safe to leave it like this, or should I reboot?

I have removed 2 data disks from my system by following https://wiki.unraid.net/Manual/Storage_Management#Removing_data_disk.28s.29 That all went well, I started the array but the GUI does not look correct and seems to believe the array is not started yet it does seem to be rebuilding parity as the % is changing and my dockers are running? What should I do, leave it, or reboot (but won't that cancel the parity sync?) ? Tried clearing browser cache, different browser etc Thanks for any help!!

Thank you!!

Hi, I guess when the TBS drivers can be compiled on 5.19 then there will be a newer release of the DVB plugin ?

I am getting "malformed password" in the logs, trying to use DNS-O-Matic, this is my config file: { "settings": [ { "provider": "dnsomatic", "domain": "updates.dnsomatic.com", "host": "@", "username": "something", "password": "something", "ip_version": "ipv4" } ] } Probably something obvious I've done wrong? EDIT: Figured it out, checked your github code for password validation and changed password appropriately. DNS-O-Matic now uses opendns.com login creds and my password was valid for that but not your code

Yes, bizarrely it appears that missing the MQTT username and password in the config.yml caused the problem - once I entered that it started to work again. Why it had previously worked for several weeks before without those entries I do not know...

Yes those icons, I forgot to also post a picture of them. Sorry, which port number? My config file: mqtt: host: 192.168.1.37 # homeassistant #logger: # default: debug detectors: cpu1: type: cpu cpu2: type: cpu # cpu3: # type: cpu # cpu4: # type: cpu cameras: low_drive: ffmpeg: inputs: - path: rtsp://192.168.1.43:554/12 roles: - detect - rtmp - path: rtsp://192.168.1.43:554/11 roles: - record motion: mask: - 0,0,389,0,345,153,0,179 detect: width: 640 height: 352 high_drive: ffmpeg: inputs: - path: rtsp://user:[email protected]:554/stream2 roles: - detect - rtmp - path: rtsp://user:[email protected]:554/stream1 roles: - record motion: mask: - 714,720,1280,720,1280,0,1101,0,916,0,911,124,810,169,717,275 detect: width: 640 height: 480 garden: ffmpeg: inputs: - path: rtsp://guest:[email protected]:554/h264Preview_01_sub roles: - detect - rtmp - path: rtsp://guest:[email protected]:554/h264Preview_01_main roles: - record motion: mask: - 1280,0,275,0,542,720,1280,720 detect: width: 640 height: 480 shed: ffmpeg: inputs: - path: rtsp://guest:[email protected]:80/ch0_1.264 roles: - detect - rtmp - path: rtsp://guest:[email protected]:80/ch0_0.264 roles: - record detect: width: 640 height: 360 objects: # Optional: list of objects to track from labelmap.txt (default: shown below) track: - person # Optional: filters to reduce false positives for specific object types filters: person: # Optional: minimum width*height of the bounding box for the detected object (default: 0) # min_area: 5000 # Optional: maximum width*height of the bounding box for the detected object (default: 24000000) # max_area: 100000 # Optional: minimum score for the object to initiate tracking (default: shown below) min_score: 0.5 # Optional: minimum decimal percentage for tracked object's computed score to be considered a true positive (default: shown below) threshold: 0.7 record: # Optional: Enable recording enabled: True # Optional: Number of days to retain retain_days: 7 # # Intel Quick Sync ffmpeg GPU acceleration # ffmpeg: hwaccel_args: - -hwaccel # - qsv # - -qsv_device # - /dev/dri/renderD128 - vaapi - -hwaccel_device - /dev/dri/renderD128 - -hwaccel_output_format - yuv420p

OK thanks, I thought because the toggles on the Web GUI no longer worked it may be an issue with the docker... I have also tried deleting everything on HA, ie removing the integration from HA AND HACS, re-downloading etc and the issue remains. Should I open a new Issue against the HASS integration on github https://github.com/blakeblackshear/frigate-hass-integration ?

For some reason my config has stopped working properly. In the Web GUI provided by the docker I can no longer toggle detect, snapshot or recordings on or off - clicking the icons simply hightlights the buttons and that's it. Also, in Home Assistant multiple entities now report as Unavailable or greyed out: I have tried deleting all my recordings and the appdata, deleting the container and re-downloading and starting from fresh but the problem strangely remains. Any ideas ? The frigate logs seem OK, from a fresh start: 022-01-11 19:58:52] frigate.app INFO : Starting Frigate (0.9.4-26ae608) [2022-01-11 19:58:52] frigate.app INFO : Creating directory: /media/frigate/recordings [2022-01-11 19:58:52] frigate.app INFO : Creating directory: /media/frigate/clips Starting migrations [2022-01-11 19:58:52] peewee_migrate INFO : Starting migrations Migrate "001_create_events_table" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "001_create_events_table" sql ('CREATE TABLE IF NOT EXISTS "event" ("id" VARCHAR(30) NOT NULL PRIMARY KEY, "label" VARCHAR(20) NOT NULL, "camera" VARCHAR(20) NOT NULL, "start_time" DATETIME NOT NULL, "end_time" DATETIME NOT NULL, "top_score" REAL NOT NULL, "false_positive" INTEGER NOT NULL, "zones" JSON NOT NULL, "thumbnail" TEXT NOT NULL)',) [2022-01-11 19:58:52] peewee_migrate INFO : sql ('CREATE TABLE IF NOT EXISTS "event" ("id" VARCHAR(30) NOT NULL PRIMARY KEY, "label" VARCHAR(20) NOT NULL, "camera" VARCHAR(20) NOT NULL, "start_time" DATETIME NOT NULL, "end_time" DATETIME NOT NULL, "top_score" REAL NOT NULL, "false_positive" INTEGER NOT NULL, "zones" JSON NOT NULL, "thumbnail" TEXT NOT NULL)',) sql ('CREATE INDEX IF NOT EXISTS "event_label" ON "event" ("label")',) [2022-01-11 19:58:52] peewee_migrate INFO : sql ('CREATE INDEX IF NOT EXISTS "event_label" ON "event" ("label")',) sql ('CREATE INDEX IF NOT EXISTS "event_camera" ON "event" ("camera")',) [2022-01-11 19:58:52] peewee_migrate INFO : sql ('CREATE INDEX IF NOT EXISTS "event_camera" ON "event" ("camera")',) Done 001_create_events_table [2022-01-11 19:58:52] peewee_migrate INFO : Done 001_create_events_table Migrate "002_add_clip_snapshot" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "002_add_clip_snapshot" add_column ('event', 'has_clip', <BooleanField: Event.has_clip>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'has_clip', <BooleanField: Event.has_clip>) add_column ('event', 'has_snapshot', <BooleanField: Event.has_snapshot>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'has_snapshot', <BooleanField: Event.has_snapshot>) Done 002_add_clip_snapshot [2022-01-11 19:58:52] peewee_migrate INFO : Done 002_add_clip_snapshot Migrate "003_create_recordings_table" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "003_create_recordings_table" Done 003_create_recordings_table [2022-01-11 19:58:52] peewee_migrate INFO : Done 003_create_recordings_table Migrate "004_add_bbox_region_area" [2022-01-11 19:58:52] peewee_migrate INFO : Migrate "004_add_bbox_region_area" add_column ('event', 'region', <JSONField: Event.region>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'region', <JSONField: Event.region>) add_column ('event', 'box', <JSONField: Event.box>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'box', <JSONField: Event.box>) add_column ('event', 'area', <IntegerField: Event.area>) [2022-01-11 19:58:52] peewee_migrate INFO : add_column ('event', 'area', <IntegerField: Event.area>) Done 004_add_bbox_region_area [2022-01-11 19:58:52] peewee_migrate INFO : Done 004_add_bbox_region_area [2022-01-11 19:58:52] frigate.mqtt INFO : MQTT connected [2022-01-11 19:58:52] detector.cpu1 INFO : Starting detection process: 216 [2022-01-11 19:58:52] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2022-01-11 19:58:52] frigate.app INFO : Output process started: 220 [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for low_drive: 223 [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for high_drive: 225 [2022-01-11 19:58:52] detector.cpu2 INFO : Starting detection process: 218 [2022-01-11 19:58:52] frigate.edgetpu WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes. [2022-01-11 19:58:52] ws4py INFO : Using epoll [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for garden: 226 [2022-01-11 19:58:52] frigate.app INFO : Camera processor started for shed: 228 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for low_drive: 229 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for high_drive: 231 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for garden: 235 [2022-01-11 19:58:52] frigate.app INFO : Capture process started for shed: 239 [2022-01-11 19:58:52] ws4py INFO : Using epoll [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: high_drive-20220111194745.mp4 [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: shed-20220111194745.mp4 [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: garden-20220111194745.mp4 [2022-01-11 19:58:57] frigate.record WARNING : Discarding a corrupt recording segment: low_drive-20220111194745.mp4 [2022-01-11 19:59:51] ws4py INFO : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:50020] [2022-01-11 20:00:51] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:50020] [2022-01-11 20:00:57] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:40060] [2022-01-11 20:01:03] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:40060] [2022-01-11 20:01:42] ws4py INFO : Managing websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:51260] [2022-01-11 20:01:43] ws4py INFO : Managing websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41224] [2022-01-11 20:01:46] ws4py INFO : Terminating websocket [Local => 127.0.0.1:8082 | Remote => 127.0.0.1:41224] [2022-01-11 20:03:48] ws4py INFO : Terminating websocket [Local => 127.0.0.1:5002 | Remote => 127.0.0.1:51260] Any ideas ?

Just needed to wait a number of hours I think before it started to log data - give it a day then check again.

I have the same issue with i915 driver and Plex HW transcoding causing a complete system hang, the only way I can get the system going again is the HW reset button. I have a Core i5 2390T which supports Quick Sync and I've tried the various methods mentioned previously to try and resolve the issue. For me I can play only a few seconds with Plex reporting HW transcoding then the system freezes, nothing displayed in any logs. I have an i5 2400 so will try that also just to rule out any issue with the CPU. Has anyone on this thread had any more joy with this issue ?

Hi, I installed the system stats plugin a few days ago and the real time function works fine, but if I select last day or any other selection in the drop down I don't get anything displayed. Do I need to carry out some additional work to get this historical data to show ? Thanks!! edit: I don't have a /var/log/sa folder, do I need to manually create that ?

Thanks, all working fine now. Love the new look, well done !