johnnyfive

Hello I have been using Frigate for a while (CPU detector) and it has been working great for the most part. I have had high CPU usage which is expected and finally took the plunge and bought a coral USB. I plugged in the Coral USB and it was detected by Frigate. I can go to 'System Metrics' and see Coral there however after a minute or so it crashes. with this: frigate.watchdog INFO : Detection appears to have stopped... Exiting Frigate... Some errors other errors I see is the following, but that one is during boot [but frigate still loads after this error], so unsure if it is connected. 2024-12-02 08:08:23frigate.watchdog Detection appears to be stuck. Restarting detection process...info 2024-12-02 08:08:23detector.coral Starting detection process: 614info 2024-12-02 08:08:23frigate.detectors.plugins.edgetpu_tfl Attempting to load TPU as usbinfo 2024-12-02 08:08:25frigate.detectors.plugins.edgetpu_tfl TPU found 0-0bulk USB transfer error 1 [LibUsbDataOutCallback] 2024-12-02 08:08:25unknown Fatal Python error: Aborted I have tried increase the shm size and the tmpfs size. I have tried installing and uninstalling and reinstalling the coral drivers in the community apps. I have turned on privilege mode. I have also reinstalled frigate multiple times. I have also used a powered USB hub and tried various USB ports. I am using a Z68X-UD3H-B3 motherboard with a i5-3570 (unsure if this matters). I have included /dev/usb in my docker config and the detector in my config file I have done a lot searching but no answers/solutions. Currently reverting back to CPU detectors so my cameras are recording and detecting. Thanks in advance mqtt: host: [REDACTED] port: [REDACTED] user: [REDACTED] password: [REDACTED] detectors: coral: type: edgetpu device: usb cameras: yi2: ffmpeg: inputs: - path: [REDACTED] roles: - record record: enabled: true retain: days: 7 mode: all events: retain: default: 7 snapshots: enabled: false timestamp: true bounding_box: true retain: default: 10 detect: enabled: false width: 1920 height: 1080 yi1: zones: road: coordinates: 1920,615,1849,557,310,622,104,638,240,708 ffmpeg: inputs: - path: [REDACTED] roles: - record - detect record: enabled: true retain: days: 7 mode: all events: retain: default: 7 mode: active_objects snapshots: enabled: false timestamp: true bounding_box: true retain: default: 10 required_zones: - road detect: enabled: false width: 1920 height: 1080 review: alerts: required_zones: - road front: motion: mask: - 1876,996,1873,1080,1386,1080,1381,1001 zones: door: coordinates: 1920,0,1920,1080,0,1080,0,875,979,815,1517,810,1509,0 ffmpeg: inputs: - path: [REDACTED] roles: - detect - record record: enabled: true retain: days: 21 mode: all events: retain: default: 14 mode: active_objects snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 required_zones: - door detect: enabled: true width: 1920 height: 1080 review: alerts: required_zones: - door front2: motion: mask: - 1383,1080,1891,1080,1888,995,1375,1000 - 301,1080,0,1080,0,0,931,0,712,31,115,121,142,505 - 1920,1080,1522,1080,1754,634,1863,228,1182,55,374,0,1920,0 zones: door2: coordinates: 1920,132,1920,1080,316,1080,186,626,822,466,1188,370,1290,393,1541,462,1578,229 ffmpeg: inputs: - path: [REDACTED] roles: - detect - record record: enabled: true retain: days: 21 mode: all events: retain: default: 14 mode: active_objects snapshots: enabled: true timestamp: true bounding_box: true retain: default: 10 required_zones: - door2 detect: enabled: true width: 1920 height: 1080 fps: 5 objects: track: - person review: alerts: required_zones: - door2 version: 0.14

Yeah it didn't solve the problem afterwards though. Kept going back to unmountable after a restart. I copied everything over and put in a new SSD as I'm unsure if my SSD is dead as it couldn't even be reformatted in unraid. I took it to my other computer and reformatted it there though.. Seems to work.. but will use as a drive for not important things for now. Thanks

I was trying to 'view' files and I think delete things during that time before. I used terminal to remove my plex transcodes (so it cleared a lot of the cache space) and so far it's been 9 hours and good so far... I'll update if it crashes again. Thanks for looking into it.

Hello. My Cache drive recently crashed. I was able to recover the files and moved them to a new drive. I also noticed that my cache drive was 320gb used. Unsure what has been cached there as the only thing I have there at the moment is the appdata (might be plex). So after an hour ( I believe it has been running parity as well), it becomes unresponive and I have to do a hard reboot. tower-diagnostics-20240727-1412.zip

Yes thank you!!! This worked for me too 😃 btrfs rescue zero-log /dev/sdX1 Other searches just showed me to start 'copying' over files and reformatting the drive...

Hello. So I had a good long month of no crashes and unsure if I did anything other than update some dockers but it's crashing every day. Crashing as I know it, I cannot access it via the url nor my VMs. last crash I checked my log and last thing was the spin down of disks. So I disabled spin down and it crashed while I was out.... This one lasted for 2 days before crashing (after disabling spin down) Last thing for today's crash I see in syslog-previous is: Jan 8 18:35:00 Tower monitor: Stop running nchan processes Jan 8 21:20:38 Tower monitor: Stop running nchan processes Jan 9 00:00:46 Tower root: /etc/libvirt: xxxx trimmed on /dev/loop3 Jan 9 00:00:46 Tower root: /var/lib/docker: xxxxx on /dev/loop2 Jan 9 00:00:46 Tower root: /mnt/cache: xxxxx trimmed on /dev/sdg1 Jan 9 11:13:10 Tower kernel: md: sync done. time=67996sec Jan 9 11:13:10 Tower kernel: md: recovery thread: exit status: 0 Jan 9 22:24:56 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci Jan 9 22:25:00 Tower kernel: usb 2-1.2: reset full-speed USB device number 3 using ehci-pci Jan 10 00:00:20 Tower root: /etc/libvirt: xxxxx trimmed on /dev/loop3 Jan 10 00:00:20 Tower root: /var/lib/docker: xxxxx on /dev/loop2 Jan 10 00:00:20 Tower root: /mnt/cache: xxxxx trimmed on /dev/sdg1 Jan 10 01:30:15 Tower monitor: Stop running nchan processes Jan 10 09:52:22 Tower monitor: Stop running nchan processes Anyone know a possible issue?? Initially I also deleted a lot of plug ins trashed my old dockers that I wasn't using much. I have home assistant running and constantly have to hard reboot my computer. Likely bad for the hard drives. tower-diagnostics-20240110-1604.zip

I was given some slow 4gb ddr3 ram. I currently am using 16GB (2x8gb) ddr3 ram (this was my old gaming computer, don't remember the speed, but likely better than the 4gb modules I got for free). Current Idle use as I look is 25%. Is more ram worth it? or 16GB would be more stable/faster. 2nd Question. Currently without a graphics card installed, as I was using the 2500k without any passthrough. is it worth putting something old inside? I think I have a 4300 or a 7450 or a 8800 gt 512 Last Question... Is it possible to run a windows VM without an additional graphics card? and view the vm through a web browser (like remote desktop or something better...

Hello. I was wondering, if it's possible to setup a Guest AP using a ethernet card connected to my UNRAID and then a Access Point to the ethernet port. I want it not connected to my network. I was thinking of making that a VPN as well. I 'could' do something similar in my router... but it doesn't seem to be working as I still seem to be able to access files within my network.

Alright so I just deleted all my zoneminder files and restarted everything... I'm not sure all my previous configs. I'm getting this error though for one of my cameras Date/Time ComponentServerPIDLevelMessageFileLine 2020-01-22 16:30:14zma_m24620ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:30:14zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:29:13zmwatch976ERRMemory map file '/dev/shm/zm.mmap.2' should have been 1160 but was instead 0zmwatch.pl 2020-01-22 16:29:10zma_m24578ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:29:10zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:29:05zma_m24557ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:29:05zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:29:04zma_m24551ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:29:04zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:28:05zma_m24534ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:28:05zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:28:00zma_m24532ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:28:00zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:27:59zma_m24531ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:27:59zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:26:59zma_m24432ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:26:59zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:26:58zma_m24427ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:26:58zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:25:45zma_m24375ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:25:45zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:23:51zma_m24282ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:23:51zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:23:48zms_m24280ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:23:48zms_m24280ERRUnable to connect to monitor id 2 for streamingzm_stream.cpp48 2020-01-22 16:23:48zms_m24280ERRUnable to connect to zmc process for monitor 2zms.cpp259 2020-01-22 16:23:46zma_m24276ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:23:46zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:23:45zma_m24275ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:23:45zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:22:45zma_m24213ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:22:45zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:22:44zma_m24212ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:22:44zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 16:22:11web_js883ERRUncaught RangeError: Maximum call stack size exceededzm/tools/mootools/mootools-core.js1 2020-01-22 16:21:54zma_m24150ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 16:21:54zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:48:33zma_m23548ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:48:33zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:47:29zma_m23525ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 14:47:29zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:47:24zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:47:23zma_m23523ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 14:47:22zmwatch976ERRMemory map file '/dev/shm/zm.mmap.2' should have been 1160 but was instead 0zmwatch.pl 2020-01-22 14:47:22zma_m23522ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 14:47:22zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:47:18zma_m23514ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:47:18zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:47:13zma_m23513ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:47:13zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:47:12zma_m23512ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:47:12zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:46:03zma_m23493ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:46:03zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:46:02zma_m23492ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:46:02zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:45:01zma_m23471ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:45:01zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:44:07zma_m23451ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 14:44:07zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:44:02zma_m23449ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 14:44:02zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:44:01zma_m23448ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 14:44:01zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:44:00zmwatch976ERRMemory map file '/dev/shm/zm.mmap.2' should have been 1160 but was instead 0zmwatch.pl 2020-01-22 14:43:56zma_m23440ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:43:56zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:43:51zma_m23439ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:43:51zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:43:50zma_m23438ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:43:50zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:42:41zma_m23423ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:42:41zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:42:40zma_m23422ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:42:40zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 14:41:50zma_m23405ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 14:41:50zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:48:48zma_m21793ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:48:48zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:48:47zma_m21792ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:48:47zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:47:47zma_m21774ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:47:47zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:46:53zma_m21753ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 09:46:53zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:46:48zma_m21752ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 09:46:48zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:46:46zmwatch976ERRMemory map file '/dev/shm/zm.mmap.2' should have been 1160 but was instead 0zmwatch.pl 2020-01-22 09:46:46zma_m21751ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 09:46:46zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:46:42zma_m21743ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:46:42zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:46:37zma_m21742ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:46:37zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:46:36zma_m21741ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:46:36zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:45:37zma_m21726ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:45:37zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:45:36zma_m21725ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:45:36zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:44:25zma_m21708ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:44:25zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:43:31zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:43:31zma_m21687ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 09:43:26zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:43:26zma_m21686ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 09:43:25zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:43:25zma_m21685ERRShared data not initialised by capture daemon for monitor WyzePanzm_monitor.cpp498 2020-01-22 09:43:24zmwatch976ERRMemory map file '/dev/shm/zm.mmap.2' should have been 1160 but was instead 0zmwatch.pl 2020-01-22 09:43:20zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:43:20zma_m21677ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:43:15zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:43:15zma_m21676ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:43:14zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:43:14zma_m21673ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:42:05zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:42:05zma_m21655ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 09:42:04zmdc909ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 09:42:04zma_m21654ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 07:50:05zmdc909ERR'zma -m 1' exited abnormally, exit status 255zmdc.pl 2020-01-22 07:50:05zma_m1943ERRShared data not initialised by capture daemon for monitor RaspPizm_monitor.cpp498 2020-01-22 07:44:40zmdc861ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 07:44:40zma_m220534ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 07:44:39zmdc861ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 07:44:39zma_m220533ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 07:43:28zmdc861ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 07:43:28zma_m220514ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 07:41:27web_js20394ERRUncaught RangeError: Maximum call stack size exceededzm/tools/mootools/mootools-core.js1 2020-01-22 07:21:49zmdc861ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 07:21:49zma_m220236ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 07:21:48zmdc861ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl 2020-01-22 07:21:48zma_m220235ERRGot empty memory map file size 0, is the zmc process for this monitor running?zm_monitor.cpp574 2020-01-22 07:20:48zmdc861ERR'zma -m 2' exited abnormally, exit status 255zmdc.pl Most Common ones are: Got empty memory map file size 0, is the zmc process for this monitor running? zm_monitor.cpp 574 Shared data not initialised by capture daemon for monitor WyzePan zm_monitor.cpp 498 Uncaught RangeError: Maximum call stack size exceeded Memory map file '/dev/shm/zm.mmap.2' should have been 1160 but was instead 0 When this occurs the camera is getting disabled for a several minutes and then works again and after some times the errors occurs again. I have two cameras running. The camera that is having difficulty was running on record, just switched it to mocord. Other camera seems fine but is on modetect

didn't work same issue

I don't think so. Not sure how to use an external one so I'm going to say no...

1.34 isn't working for me.... Can't seem to load anything *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/05_set_the_time.sh... *** Running /etc/my_init.d/06_set_php_time.sh... *** Running /etc/my_init.d/10_syslog-ng.init... Jan 19 09:56:26 c6570ff7876c syslog-ng[16]: syslog-ng starting up; version='3.13.2' *** Running /etc/my_init.d/20_apt_update.sh... Hit:1 http://archive.ubuntu.com/ubuntu bionic InRelease Hit:2 http://ppa.launchpad.net/iconnor/zoneminder-1.34/ubuntu bionic InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... Using existing conf folder File zm.conf already moved File zmeventnotification.ini already moved File secrets.ini already moved Event notification server already moved Using existing ssmtp folder Using existing mysql database folder Copy /config/control/ scripts to /usr/share/perl5/ZoneMinder/Control/ Copy /config/conf/ scripts to /etc/zm/conf.d/ Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp Using existing data directory for cache no crontab for root Setting shared memory to : 50% of 16344776 bytes Starting services... * Starting MariaDB database server mysqld ...done. Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[733]: Upgrading MySQL tables if necessary. Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: Looking for 'mysql' as: /usr/bin/mysql Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[737]: This installation of MySQL is already upgraded to 10.1.43-MariaDB, use --force if you still need to run mysql_upgrade Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[744]: Checking for insecure root accounts. Jan 19 09:56:32 c6570ff7876c /etc/mysql/debian-start[748]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Initiating database upgrade to version 1.34.0 from version 1.32.3 Upgrading database to version 1.34.0 Loading config from DB 230 entries Saving config to DB 230 entries Upgrading DB to 1.33.0 from 1.32.3 Database successfully upgraded to version 1.33.0. Upgrading DB to 1.33.1 from 1.32.3 Database successfully upgraded to version 1.33.1. Upgrading DB to 1.33.2 from 1.32.3 Database successfully upgraded to version 1.33.2. Upgrading DB to 1.33.3 from 1.32.3 Database successfully upgraded to version 1.33.3. Upgrading DB to 1.33.4 from 1.32.3 Database successfully upgraded to version 1.33.4. Upgrading DB to 1.33.5 from 1.32.3 Database successfully upgraded to version 1.33.5. Upgrading DB to 1.33.6 from 1.32.3 Database successfully upgraded to version 1.33.6. Upgrading DB to 1.33.7 from 1.32.3 Database successfully upgraded to version 1.33.7. Upgrading DB to 1.33.8 from 1.32.3 Database successfully upgraded to version 1.33.8. Upgrading DB to 1.33.9 from 1.32.3 Database successfully upgraded to version 1.33.9. Upgrading DB to 1.33.10 from 1.32.3 Database successfully upgraded to version 1.33.10. Upgrading DB to 1.33.11 from 1.32.3 Database successfully upgraded to version 1.33.11. Upgrading DB to 1.33.12 from 1.32.3 ERROR 1932 (42S02) at line 15: Table 'zm.Logs' doesn't exist in engine Output: Command 'mysql -hlocalhost -uzmuser -p"zmpass" zm < /usr/share/zoneminder/db/zm_update-1.33.12.sql' exited with status: 1 Freshening configuration in database Migratings passwords, if any... Loading config from DB 230 entries Saving config to DB 230 entries * Starting Apache httpd web server apache2 * Starting ZoneMinder: Jan 19 09:56:35 c6570ff7876c zmpkg[847]: INF [Sanity checking States table...] DBD::mysql::st execute failed: Table 'zm.Logs' doesn't exist in engine at /usr/share/perl5/ZoneMinder/Logger.pm line 600. Jan 19 09:56:35 c6570ff7876c zmpkg[847]: ERR [Can't execute log entry 'INSERT INTO Logs ( TimeKey, Component, ServerId, Pid, Level, Code, Message, File, Line ) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, NULL )': Table 'zm.Logs' doesn't exist in engine] Jan 19 09:56:35 c6570ff7876c zmpkg[847]: INF [Command: start] Jan 19 09:56:35 c6570ff7876c zmpkg[847]: FAT [Version mismatch, system is version 1.34.0, database is 1.32.3, please run zmupdate.pl to update.] ZoneMinder failed to start *** /etc/my_init.d/40_firstrun.sh failed with status 255 *** Killing all processes... Jan 19 09:56:35 c6570ff7876c syslog-ng[16]: syslog-ng shutting down; version='3.13.2'

I just noticed that my torrents are slowed down for some reason. Is anyone using PIA and getting their download speed throttled? It seems I am limited to 600KBps-1MBps. Usually it hovers around 600KBps. Any additional torrent I add will lower the torrent speed so the total speed is only ~600KBps. I tested my download speeds without VPN on and it goes to about 25+MBps. If I pause and turn on ' forced proxy' (with none selected) it goes at normal speeds (25MBps+) ... which I think might be bypassing the VPN. If I turn on proxy and use sock5. It goes to the 600KBps speed... I also tested this in Windows Used PIA desktop APP and then used deluge for windows to download a torrent and with the VPN on I got ~600KBps and with it off I got 25MBps+. NO Settings were changed for the windows deluge (all were default) Anyone having this issue? It seems like a PIA thing... Not sure...