Danuel

what i see, if i manage to start 1-2 containers the 3 one will spin and if i try to acces log from UI i have blank also sometime after a fresh boot when i navigate on UI TOOLS tabs, or settings it takes time to load

those are the latest logs, i dont know what happen, but i came back and unraid UI and started again to have a parity and all containers were off now i see something regarding CPU not supported seven-diagnostics-20231231-1207.zip

Does the unradUi is getting slow after you start a container ? My problem is a bit similar

Is there any way or tool that i can check for hardware faults ? I dont know what is with my server, sometimes work ok, sometimes work like a very old system or freezes, need some help please some ideas on what to try

any news regarding those diagnostics ?

from what is see, is behaving like a slow system, even with docker off, Unraid homepage still take a bit to refresh or load i wonder if is a corrupted docker image ? and downgrading to 6.12.4 does not help, another thing i noticed is that sometime when i am trying to start a container i get execution error, or takes up to 5 min to start a container

ZFS 100% ? can that be the problem ?

just happen to notice that sometimes server shut down itself when trying to start a container, it take like 5 minutes anyway does take long time to start or stop a container

now after all this restarting and trying to understand what happens i see a container that i dont know what it is, i dont remember installing it, this just showed up

here are the diagnostics 1942 are the latest seven-diagnostics-20231228-1942.zip seven-diagnostics-20231228-1726.zip seven-diagnostics-20231228-1751.zip

hi, guys, need some help, problem i have started in the last hour, docker containers are taking to long time to start, this happen after trying to manually update a container then server got stuck, so i did a restart then the array did not want to come back or having problem to start, so i entered in safe mode and disabled docker then array started as normal, now i started docker and all docker containers taking forever to start , any help please, i am with almost 2 hours and still not all containers started Ulogs.txt

if your container does not have a variable where to add GPU ID, you have to created that VAraible then in extra parameters: add this line -e NVIDIA_DRIVER_CAPABILITIES=all -e NVIDIA_VISIBLE_DEVICES=all --gpus all

ctrl+c , ctrl+v not working on a SSH i just stared using this trying to replace a terminal that i have installed this is critical since i am not able to use the commands above not sure if this is a bug or not, or maybe i am doing something wrong

hi, just updated to 27.0.0 i do get a message in nextcloud `Some files have not passed the integrity check. Further information on how to resolve this issue can be found in the documentation ↗. (List of invalid files… / Rescan…)` pressing rescan does nothing, any fix for this ?

can HDD temp influence a crash early my HDD were 46c and around 10 am server froze

a update regarding my server after updated to 6.12.0 server froze after 3-4 day of running here are logs syslog-10.10.10.6.log

use the File manager Plugin in uNRAid and edit permision from there

this is a guide on how to upgrade from terminal you might find it more easy if you have problem This version of Nextcloud is not compatible with PHP>=8.2.<br/>You are currently running 8.2.6 what i have did i revert back to 25.0.3 then started the upgrade from terminal 1. open terminal from nextcloud container 2. Turn on maintenance mode cd /config/www/nextcloud/ sudo -u abc php occ maintenance:mode --on 3. Backup current nextcloud install cd /config/www/ mv nextcloud nextcloud-backup if you get a error regarding backup delete `nextcloud-backup` and try again to backup 4. Grab newest nextcloud release and unpack it wget https://download.nextcloud.com/server/releases/nextcloud-26.0.2.tar.bz2 or whatever version, "you can see latest version on https://download.nextcloud.com/server/releases" tar -xvf nextcloud-26.0.2.tar.bz2 5. Copy across old config.php from backup cp nextcloud-backup/config/config.php nextcloud/config/config.php ##Now Restart docker container via Unraid WebGUI 6. Open terminal in container 7. Perform upgrade cd /config/www/nextcloud/ sudo -u abc php occ upgrade (if you get error you might have to enable permision) 8.Turn off maintenance mode sudo -u abc php occ maintenance:mode --off 9. Now Restart docker container via Unraid WebGUI and upgrade your container to latest version 26.0.2 in my case ###fixes after installation### *if you get error "sudo: ./occ command not found" (run chmod 777 occ) then run the fix sudo -u abc ./occ db:add-missing-indices sudo -u abc ./occ db:convert-filecache-bigint **Other fixes you have to stop the nextcloud container and proxymanager go to appdata\nextcloud\nginx\site-confs and edit the line add_header X-Robots-Tag "noindex, nofollow" always; add_header X-Frame-Options "SAMEORIGIN" always; also if you still have problem with apps after updating nextcloud, you have to change ownership to apps nextcloud\www\nextcloud\apps i use the plugin `file manager` from unraid to achieve that and i set owner to nobody

i can confirm, that foce update fix the problem

logs + screenshot if i roll back to 2.16.1-3-01 is working binhex-hexchat-2023-05-10T11-53-02.log

now the app is starting but i get `failed to connect to server` to VNCserver

is just me or the latest update broke the app ? because for me latest is not working downgrading to 2.16.1-3-01 is working ` Traceback (most recent call last): File "/usr/sbin/websockify", line 33, in <module> sys.exit(load_entry_point('websockify==0.10.0', 'console_scripts', 'websockify')()) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/sbin/websockify", line 22, in importlib_load_entry_point for entry_point in distribution(dist_name).entry_points ^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 981, in distribution return Distribution.from_name(distribution_name) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 565, in from_name raise PackageNotFoundError(name) importlib.metadata.PackageNotFoundError: No package metadata was found for websockify 2023-05-07 11:45:57,217 DEBG 'start' stderr output: _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. 2023-05-07 11:45:57,217 DEBG 'start' stderr output: Xvnc TigerVNC 1.13.1 - built Mar 10 2023 21:57:50 Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst) See https://www.tigervnc.org for information on TigerVNC. Underlying X server release 12101006 Sun May 7 11:45:57 2023 vncext: VNC extension running! 2023-05-07 11:45:57,217 DEBG 'start' stderr output: vncext: Listening for VNC connections on all interface(s), port 5900 vncext: created VNC server for screen 0 2023-05-07 11:45:57,266 DEBG 'start' stderr output: [mi] mieq: warning: overriding existing handler (nil) with 0x563e1a18b920 for event 2 [mi] mieq: warning: overriding existing handler (nil) with 0x563e1a18b920 for event 3 2023-05-07 11:46:01,157 DEBG 'start' stdout output: [info] tint2 not running 2023-05-07 11:46:01,167 DEBG 'start' stderr output: tint2: Using glib slice allocator (default). Run tint2 with environment variable G_SLICE=always-malloc in case of strange behavi 2023-05-07 11:46:01,167 DEBG 'start' stderr output: or or crashes 2023-05-07 11:46:01,172 DEBG 'start' stderr output: t 2023-05-07 11:46:01,173 DEBG 'start' stderr output: int2: xRandr: Found crtc's: 1 tint2: xRandr: Linking output VNC-0 with crtc 0, resolution 1024x768, DPI 96 2023-05-07 11:46:01,199 DEBG 'start' stderr output: (hexchat:93): Gtk-WARNING **: 11:46:01.198: Unable to locate theme engine in module_path: "adwaita", 2023-05-07 11:46:01,338 DEBG 'start' stderr output: (hexchat:93): Gtk-WARNING **: 11:46:01.338: Unable to locate theme engine in module_path: "murrine", 2023-05-07 11:46:01,349 DEBG 'start' stderr output: (hexchat:93): Gtk-WARNING **: 11:46:01.349: Unable to locate theme engine in module_path: "adwaita", 2023-05-07 11:46:16,178 DEBG 'start' stderr output: tint2: warning : WM doesn't respect NETWM specs. tint2 default to 1 desktop. 2023-05-07 11:46:16,178 DEBG 'start' stderr output: tint2: No XSETTINGS manager, tint2 uses config option 'launcher_icon_theme'. tint2: Loading config file: /home/nobody/.config/tint2/theme/tint2rc 2023-05-07 11:46:16,181 DEBG 'start' stderr output: tint2: real transparency on... depth: 32 2023-05-07 11:46:16,182 DEBG 'start' stderr output: tint2: panel items: TSC tint2: Systray composited rendering on 2023-05-07 11:46:16,182 DEBG 'start' stderr output: tint2: nb monitors 1, nb monitors used 1, nb desktops 1 tint2: panel 1 uses scale 1 2023-05-07 11:46:16,215 DEBG 'start' stderr output: tint2: Kernel uevent interface initialized... 2023-05-07 11:46:16,215 DEBG 'start' stderr output: tint2: systray window 4194317 tint2: systray started `

Hi, i thought to come with a update regarding my posting. i can confirm that server is looking stable, no freeze in past 48 hours

here are the diagnostics requested seven-diagnostics-20230416-1106.zip