MothyTim

So it stayed up for 2 days this time and suddenly crashes!! Nothing unusual running only noticed because the programme I was watching on Plex stopped! tower-diagnostics-20220805-1845.zip syslog-10.19.64.2.log

Thanks for the link, done that and everything seems to have come back-up ok! Fingers crossed that's it for now! I'm suspisious that the Windows 11 VM is possibly causing this because it's the only thing I can think of that I've run just before one of these events happens and I don't use it very often! I also installed USB Manager last week hoping that would help, but it seems not. I think its a problem with USB somehow though, I have a Coral TPU, could that be overloading the USB bus? Although its been there a couple of years now! Thanks again for your quick responses and help! Cheers, Tim

Ok ran first aid on stick on my mac and its booted up, the attached screen shows an error though: XFS (md3): Metadata corruption detected at xfs_dinode_verify+0xa4/0x56f [xfs], inode 0x5c1bf6 dinode XFS (md3): Unmount and run xfs_repair Then lines of hex code! What do I do about that? Thanks, Tim

I've got a bad feeling that the USB on the motherboard has failed/is failing as the mouse doesnt light up! Could be a port failed just trying it with minimal stuff plugged in! Unraid USB stick mounts and is brouseable on my Mac, do you think it might be corupted? Should I reflash it? Thanks for your help again. Cheers, Tim

Ok, so it stayed up for a whole month and has crashed again this morning! So bad this time that it won't boot back up again!!!! This is beyond frustrating now, I should have guessed a problem was looming as CA Backup has failed to restart my docker containers for 2 days on the trot. I ran diagnostics before reboot as all the USB derices had disappeared from USB Manager! Really hope something shows in the logs this time. Cheers, Tim tower-diagnostics-20220803-1238.zip

Ok thanks

And this mornings. root@Tower:~# df -h / Filesystem Size Used Avail Use% Mounted on rootfs 16G 980M 15G 7% / root@Tower:~# Cheers, Tim

Ok thanks for the info, just run it again. root@Tower:~# df -h / Filesystem Size Used Avail Use% Mounted on rootfs 16G 953M 15G 6% / root@Tower:~# Cheers, Tim

root@Tower:~# df -h / Filesystem Size Used Avail Use% Mounted on rootfs 16G 959M 15G 7% / root@Tower:~#

root@Tower:~# df -h / Filesystem Size Used Avail Use% Mounted on rootfs 16G 953M 15G 6% / root@Tower:~#

Ok thanks for looking, annoying that it’s not more specific! cheers, Tim

Ok so again a problem I think the GUI crashed as all dockers etc seemed to still be working but no GUI, system wouldn't restart so had to hit the oh shit button! Logs attached! I'm wondering if I'll have to give up on 6.10 and go back to 6.9? Cheers, Tim tower-diagnostics-20220701-1811.zip syslog-10.19.64.2.log

Ok, thanks for looking so quickly. I think it was something with docker as Plex became unresponsive and I tried to restart its container but it through a server error and the container wouldn't start. I guess I could have restarted the docker service but opted to restart the whole machine! Cheers, Tim

It crashed again last night, so sadly it seems that hasn't fixed the issue? It happened at around 20:30 - 20:45, the system wasn't totally hung like before though and I was able to restart properly! Logs attached, hopefully there is something there? Cheers, Tim syslog-10.19.64.2.log tower-diagnostics-20220630-0839.zip

Ok, thanks for that, I've changed the Plex docker back to host as that was the only one with a static IP, hopefully that'll fix it! I'll keep an eye on the RAM it's probably when I'm running Windows 11 VM, if so I'm not worried, but I'll check that it's nothing else! Thanks again for your help! Cheers, Tim

Already enabled here is the log! Sorry should have thought of including that! syslog-10.19.64.2.log

Hi, I had the occasional crash with the RC releases, but it seems to have become more unstable with the stable releases! Not sure whats going on but it crashed on friday and nothing was working, no GUI and no respons on command line! So unclean shutdown! And same again this morning! I was suspicious of CA Backup because the crashes seemed to happen at 6:00am on the RC's which is when it runs but this morning it wasn't that time! So hoping someone cleverer than me can spot something? I've attached diagnostics from Friday and today. Thanks, Tim tower-diagnostics-20220624-1452.zip tower-diagnostics-20220627-1114.zip

Hi, I haven'y used code-server for a few months and went to use it the other day and it wouldn't start! I can see some errors in the log but not sure if they are causing the issue? I'm guessing that an update broke it at somepoint? Here is part of the log, if you need more please shout! Cheers, Tim ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... setting up sudo access setting sudo password using SUDO_PASSWORD env var New password: Retype new password: passwd: password updated successfully setting permissions::configuration setting permissions::workspace [cont-init.d] 30-config: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 95-apt-get: executing... Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Get:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease [114 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-security InRelease [114 kB] Hit:4 https://dl.yarnpkg.com/debian stable InRelease Get:5 http://archive.ubuntu.com/ubuntu focal-updates/universe Sources [267 kB] Get:6 http://archive.ubuntu.com/ubuntu focal-updates/restricted Sources [38.2 kB] Get:7 http://archive.ubuntu.com/ubuntu focal-updates/main Sources [574 kB] Get:8 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages [1,814 kB] Hit:9 https://deb.nodesource.com/node_14.x focal InRelease Get:10 http://archive.ubuntu.com/ubuntu focal-updates/universe amd64 Packages [1,118 kB] Get:11 http://archive.ubuntu.com/ubuntu focal-updates/restricted amd64 Packages [859 kB] Get:12 http://archive.ubuntu.com/ubuntu focal-security/universe Sources [101 kB] Get:13 http://archive.ubuntu.com/ubuntu focal-security/restricted Sources [36.2 kB] Get:14 http://archive.ubuntu.com/ubuntu focal-security/main Sources [242 kB] Get:15 http://archive.ubuntu.com/ubuntu focal-security/universe amd64 Packages [837 kB] Get:16 http://archive.ubuntu.com/ubuntu focal-security/restricted amd64 Packages [790 kB] Get:17 http://archive.ubuntu.com/ubuntu focal-security/main amd64 Packages [1,385 kB] Fetched 8,289 kB in 1s (6,239 kB/s) Reading package lists... [cont-init.d] 95-apt-get: exited 0. [cont-init.d] 98-python3: executing... **** installing python3 dev environment **** Reading package lists... Building dependency tree... Reading state information... libffi-dev is already the newest version (3.3-4). python3-dev is already the newest version (3.8.2-0ubuntu2). python3-venv is already the newest version (3.8.2-0ubuntu2). build-essential is already the newest version (12.8ubuntu1.1). libssl-dev is already the newest version (1.1.1f-1ubuntu2.10). python3-pip is already the newest version (20.0.2-5ubuntu1.6). 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. [cont-init.d] 98-python3: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] 99-home-assistant: executing... Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-security InRelease Hit:4 https://deb.nodesource.com/node_14.x focal InRelease Hit:5 https://dl.yarnpkg.com/debian stable InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Package bsdtar is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source However the following packages replace it: libarchive-tools E: Package 'bsdtar' has no installation candidate Generating locales (this might take a while)... en_US.UTF-8... done Generation complete. /var/run/s6/etc/cont-init.d/99-home-assistant: line 28: uuidgen: command not found Installing vscode extension: LogFileHighlighter by emilast @ 2.11.0 https://marketplace.visualstudio.com/_apis/public/gallery/publishers/emilast/vsextensions/LogFileHighlighter/2.11.0/vspackage % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed Warning: Transient problem: HTTP error Will retry in 60 seconds. 5 retries Warning: left. Throwing away 483 bytes /var/run/s6/etc/cont-init.d/99-home-assistant: line 44: bsdtar: command not found [cont-init.d] 99-home-assistant: exited 1. [cont-init.d] code-server.sh: executing... [cont-init.d] code-server.sh: exited 0. [cont-init.d] mosquitto.sh: executing... ln: failed to create symbolic link '/root/.config/mosquitto_pub': File exists ln: failed to create symbolic link '/root/.config/mosquitto_rr': File exists [cont-init.d] mosquitto.sh: exited 1. [cont-init.d] user.sh: executing... ln: failed to create symbolic link '/config/.ssh/.ssh': File exists ln: failed to create symbolic link '/config/.gitconfig': File exists [cont-init.d] user.sh: exited 1. [cont-init.d] done. [services.d] starting services [services.d] done. Starting the code server... [2022-01-08T17:57:41.235Z] error Unknown option --extra-builtin-extensions-dir [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.

Hi, I'm also getting this error: Fatal error: Cannot redeclare _() (previously declared in /usr/local/emhttp/plugins/parity.check.tuning/Legacy.php:6) in /usr/local/emhttp/plugins/dynamix/include/Translations.php on line 20 But I have just upgraded my parity drive to a larger one! Everything seems to be working though and I've tried removing and reinstalling the plugin. I'm running Unraid 6.10.0rc1. Cheers, Tim

Ok weird! Attached a new one! tower-diagnostics-20210901-1606.zip

Server just crashed, don’t know why! It’s 10 at night and was watching something on Plex when it just stopped playing, I checked and nothing was reachable! So I went into the office and tried to shut down via command line using the monitor and keyboard but that was frozen too, so had to hit the oh shit button! Attached diagnostics so maybe you can see what happened? tower-diagnostics-20210831-2238.zip

Hi, I'm using Authelia and everything works as it should. I have a problem with LMS, I only proxied it to use Alexa skill and wanted to use Authelia instead of basic auth, but it seems Alexa can't/won't use 2-factor auth for this skill! Can I set somewhere in the config to use single-factor just for this container? Thanks, Tim

Hi, hoping for some help with my config! All seems to work, I have recording 24/7 and clips when it detects. Intel gpu is working and using cpu at the moment for object detection (Coral USB on order). I only want it to detect people which it does about half the time, which is disappointing and I get constant false positives! At night it doesn't detect anything at all, I can stand in front of the camera and wave, nothing! Will the Coral improve this? Camera is S3VC 5mp super HD. Here's my config, please let me know if anything could be changed? Thanks, Tim mqtt: # Required: host name host: 192.168.xxx.xxx # Optional: port (default: shown below) port: 1883 # Optional: topic prefix (default: shown below) # WARNING: must be unique if you are running multiple instances topic_prefix: frigate # Optional: client id (default: shown below) # WARNING: must be unique if you are running multiple instances client_id: frigate # Optional: user user: XXXXXXXXXX # Optional: password # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {}. # eg. password: '{FRIGATE_MQTT_PASSWORD}' password: XXXXXXXXXX # Optional: interval in seconds for publishing stats (default: shown below) stats_interval: 60 cameras: # Required: name of the camera garden: # Required: ffmpeg settings for the camera ffmpeg: # Required: A list of input streams for the camera. See documentation for more information. inputs: # Required: the path to the stream # NOTE: Environment variables that begin with 'FRIGATE_' may be referenced in {} - path: rtsp://XXXXX:[email protected]:554/stream1 # Required: list of roles for this stream. valid values are: detect,record,clips,rtmp # NOTICE: In addition to assigning the record, clips, and rtmp roles, # they must also be enabled in the camera config. roles: - detect - record - path: rtsp://XXXXX:[email protected]:554/stream0 roles: - clips - rtmp # Required: width of the frame for the input with the detect role width: 704 # Required: height of the frame for the input with the detect role height: 576 # Optional: desired fps for your camera for the input with the detect role # NOTE: Recommended value of 5. Ideally, try and reduce your FPS on the camera. # Frigate will attempt to autodetect if not specified. fps: 5 # Optional: camera level motion config motion: # Optional: motion mask # NOTE: see docs for more detailed info on creating masks mask: 446,370,428,576,0,576,0,296,232,259,255,359 # Optional: timeout for highest scoring image before allowing it # to be replaced by a newer image. (default: shown below) best_image_timeout: 60 # Optional: zones for this camera zones: # Required: name of the zone # NOTE: This must be different than any camera names, but can match with another zone on another # camera. path: # Required: List of x,y coordinates to define the polygon of the zone. # NOTE: Coordinates can be generated at https://www.image-map.net/ coordinates: 545,1077,747,939,788,805 # Optional: Zone level object filters. # NOTE: The global and camera filters are applied upstream. filters: person: min_area: 5000 max_area: 100000 threshold: 0.7 # Optional: Camera level detect settings detect: # Optional: enables detection for the camera (default: True) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: Number of frames without a detection before frigate considers an object to be gone. (default: 5x the frame rate) max_disappeared: 25 # Optional: save clips configuration clips: # Required: enables clips for the camera (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: Number of seconds before the event to include in the clips (default: shown below) pre_capture: 10 # Optional: Number of seconds after the event to include in the clips (default: shown below) post_capture: 10 # Optional: Objects to save clips for. (default: all tracked objects) objects: - person # Optional: Restrict clips to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 60 # Optional: Per object retention days objects: person: 90 # Optional: 24/7 recording configuration record: # Optional: Enable recording (default: global setting) enabled: True # Optional: Number of days to retain (default: global setting) retain_days: 30 # Optional: RTMP re-stream configuration rtmp: # Required: Enable the live stream (default: True) enabled: True # Optional: Configuration for the jpg snapshots written to the clips directory for each event snapshots: # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: print a timestamp on the snapshots (default: shown below) timestamp: False # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: False # Optional: crop the snapshot (default: shown below) crop: False # Optional: height to resize the snapshot to (default: original size) height: 175 # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 10 # Optional: Per object retention days objects: person: 15 # Optional: Configuration for the jpg snapshots published via MQTT mqtt: # Optional: Enable publishing snapshot via mqtt for camera (default: shown below) # NOTE: Only applies to publishing image data to MQTT via 'frigate/<camera_name>/<object_name>/snapshot'. # All other messages will still be published. enabled: True # Optional: print a timestamp on the snapshots (default: shown below) timestamp: True # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: True # Optional: crop the snapshot (default: shown below) crop: True # Optional: height to resize the snapshot to (default: shown below) height: 270 # Optional: Restrict mqtt messages to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera level object filters config. objects: track: - person # Optional: mask to prevent all object types from being detected in certain areas (default: no mask) # Checks based on the bottom center of the bounding box of the object. # NOTE: This mask is COMBINED with the object type specific mask below mask: 0,0,1000,0,1000,200,0,200 filters: person: min_area: 5000 max_area: 100000 min_score: 0.5 threshold: 0.7 # Optional: mask to prevent this object type from being detected in certain areas (default: no mask) # Checks based on the bottom center of the bounding box of the object mask: 0,295,234,258,251,359,454,373,434,576,0,576 detectors: cpu1: type: cpu cpu2: type: cpu clips: # Optional: Maximum length of time to retain video during long events. (default: shown below) # NOTE: If an object is being tracked for longer than this amount of time, the cache # will begin to expire and the resulting clip will be the last x seconds of the event. max_seconds: 600 # Optional: Retention settings for clips (default: shown below) retain: # Required: Default retention days (default: shown below) default: 60 # Optional: Per object retention days objects: person: 90 ffmpeg: # Optional: global ffmpeg args (default: shown below) global_args: -hide_banner -loglevel warning # Optional: global hwaccel args (default: shown below) # NOTE: See hardware acceleration docs for your specific device hwaccel_args: - -hwaccel - vaapi - -hwaccel_device - /dev/dri/renderD128 - -hwaccel_output_format - yuv420p # Optional: global input args (default: shown below) input_args: -avoid_negative_ts make_zero -fflags +genpts+discardcorrupt -rtsp_transport tcp -stimeout 5000000 -use_wallclock_as_timestamps 1 # Optional: global output args output_args: # Optional: output args for detect streams (default: shown below) detect: -f rawvideo -pix_fmt yuv420p # Optional: output args for record streams (default: shown below) record: -f segment -segment_time 60 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an # Optional: output args for clips streams (default: shown below) clips: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c copy -an # Optional: output args for rtmp streams (default: shown below) rtmp: -c copy -f flv 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

Oh ok, thanks for clarifying! Also thanks for all you do, providing these excellent containers!

It’s also showing here? So a bit puzzled!