daninet

Hi, Every 1-2 days the container stops with java error. It runs perfectly fine for a while which is strange. My flag is 11notes/unifi:9.3.43-unraid I see this is log: {"time":"2025-07-29T16:37:12.000Z","type":"INF","msg":"starting unifi v9.3.43"} # # A fatal error has been detected by the Java Runtime Environment: # # [thread 32927 also had an error] SIGBUS (0x7) at pc=0x000014ae728192de, pid=1, tid=111 # # JRE version: OpenJDK Runtime Environment (17.0.15+6) (build 17.0.15+6-Ubuntu-0ubuntu120.04) # Java VM: OpenJDK 64-Bit Server VM (17.0.15+6-Ubuntu-0ubuntu120.04, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64) # Problematic frame: # V [libjvm.so+0xc192de] ObjectMonitor::EnterI(JavaThread*)+0x27e # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /usr/lib/unifi/hs_err_pid1.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-17 # [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x000014ae7316d941] {"time":"2025-08-02T08:17:44.000Z","type":"INF","msg":"starting unifi v9.3.43"} # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0x7) at pc=0x000015360d47d412, pid=1, tid=30 # # JRE version: OpenJDK Runtime Environment (17.0.15+6) (build 17.0.15+6-Ubuntu-0ubuntu120.04) # Java VM: OpenJDK 64-Bit Server VM (17.0.15+6-Ubuntu-0ubuntu120.04, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64) # Problematic frame: # V [libjvm.so+0xc7d412] PerfLongVariant::sample()+0x22 # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /usr/lib/unifi/hs_err_pid1.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-17 # [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x000015360dda7941]I have attached the file from the container that the error log refers to. hs_err_pid1.log

I feel like it is actually slow not just underreporting. Anyway, what alternative i can use while on phone? MC is very hard to manage on touch screen, total commander SMB plugin does not seem to bypass when copying from share to share. I'm looking for gui option here just to be on the same page but i guess its clear 🙂

Im using linux so i dont have that fancy graph windows explorer has but the copy speed is indeed ok. So is this an issue with Dynamix File Manager?

Hello, As title says I have issues with copy speed. It tops out at 20-25Mb/s. I'm initiating the copy over the web interface so it should not be limited by any network speed. Files are around 1Gb so it is sequential writing to the HDD. I have WD Red 2Tb drives and Samsung nvme SSD for cache. File is cached, mover not yet run. While copy is running dashboard shows high CPU usage. Not sure if it includes iowait. Once copy over CPU usage goes back to normal idle. Diagnostics made during copy operation. Any help about what to check appreciated. Thanks tevenas-diagnostics-20250117-1924.zip

indeed when im stopping docker service it looks good. My only new docker in the setup is immich. The rest of my dockers are running for years no issue. I will test the setup now without immich, I already have all my images indexed and the thumbnails generated im not sure why it should be an issue

Hello! I recently did some upgrades on my system, I added more ram, added a new disk, added a new ssd (this one only stores immich thumbnails). Now with this combination something happened to my server any I'm getting 100% CPU usage a lot. It is so bad that I need 2-3minutes just to ssh into my server. htop and docker stats show very weird things, processes are fighting for CPU cycles. For example when did you see htop process itself uses 45% CPU last time? Then I see lsof on top a lot, then qemu and docker service as well. Basically anything I invoke on the interface goes up with high CPU usage and very hard to tell what exactly is throttling my cpu. In docker stats every container randomly goes between 0-20% CPU usage even the inactive ones like mysql for my websites that I'm not using. Very weird. Everything still works, I can access my dockers, access my server but it is super slow. Crazy slow. The config is HP Elitedesk PC with i5-7500 and 16Gb RAM. I also have an older nvidia card for plex encoding. I have attached the diagnostics, any help appreciated. tevenas-diagnostics-20250110-0944.zip

Circling back to my original question from the first post, can i somehow replace the IDs so i dont have to copy all my data somewhere to redo the array? I dont have that much free space.

Here you go. The IDs are same as my first screenshot in the post, IDs are not changing. tevenas-diagnostics-hotplug.zip tevenas-diagnostics-normal-boot.zip

Hi, I recently acquired an icy box usb jbod. I have a microserver and while i'm aware rebuilding it in a new case with sata card and such would be a better option, at the moment i cannot justify the price. It would mean a brand new server for me. So i'm using it for now and honestly i dont have much complaint with it. Speed is fine for media and downloads. It holds no irreplaceable data. The issue is i didnt know unraid handles is weirdly when i set it up. So right now it has a single drive. My server was running, i have stopped the array, plugged in the usb, added the new disk to the array and was happy. Until i had to restart the server and I noticed that the drive is not mounted, it said missing. Unplug, replug usb and I was able to select the drive and start the array. But the issue is my server is now unable to start automatically I have to babysit it. What I noticed is when I start unraid os with the usb jbod plugged in it gets a very normal looking HDD serial number, however when you hot plug it in while the os is running it gets a very generic 00000003 serial. Obviously i should have done the first option then i would have no trouble but here I am. So..: Now I need to know how I can replace a disk while content is 100% the same but different serial. I know it might be a weird edge case but it happens as you see. I dont have parity drive, its a media server.

Hi! I have a GreenCell Micropower 1500VA UPS and it was working great with for quite some time with the blaze usb driver. However something happened and the battery charge percentage no longer updates. This results in my system not shutting down gracefully upon power outage. I can see the UPS load and the battery voltage indicator still updating. If someone can look on it please do. Thank you. nut-debug-20241219105328.zip nut-ups.dev

Hi, I'm using this container for some time without much issue. Where I live I have internet access with CGNAT only so I dont have my own IP. I'm using cloudflare tunnel to access my nextcloud instance running on my server. CF provides me an SSL so all good. However when I'm trying to access locally through IP I cannot, connection not secure. My localhost and domain is added to the config. 'trusted_domains' => array ( 0 => '192.168.1.200:8666', 1 => 'mydomain.xyz', ), 'trusted_proxies' => array ( 0 => '77.221.43.251', 1 => '172.17.0.6', 2 => '192.168.1.200', ), 'overwriteprotocol' => 'https', 'overwrite.cli.url' => 'http://192.168.1.200:8666', I want to know if there is some easy to understand description on how to attach certificate to the container and config it to be used by the container even locally. Unfortunately most of the help in this topic is to setup reverse proxy like traefik or swag and add certificate there but its not an option for me as far as I can understand or it would just add extra complexity for little to no benefit.

Seems like it worked. I'm left with this error now: WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) {"time":"2024-12-02T19:53:49.000Z","type":"INF","msg":"starting unifi (8.5.6)"} quick search in this thread told me it might be something related to ports, but i get the same error on br0 and Bridge as well 🤔

I have the default settings, same as yours: Here is my docker run: docker run -d --name='unifi-controller-reborn' --net='bridge' --pids-limit 2048 --privileged=true -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="TEVENAS" -e HOST_CONTAINERNAME="unifi-controller-reborn" -e 'MEM_LIMIT'='4096' -e 'MEM_STARTUP'='2048' -e 'UMASK'='002' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://[IP]:[PORT:8443]' -l net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg' -p '8443:8443/tcp' -p '3478:3478/udp' -p '10001:10001/udp' -p '8080:8080/tcp' -p '1900:1900/udp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '6789:6789/tcp' -p '5514:5514/udp' -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw' --memory=8G '11notes/unifi:8.5.6-unraid' WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. 61e179a0b46c22815a0f4fb9bb7ec9f41d686715348634ca6f838bc01e168dec The command finished successfully! I'm assuming the last warning is default as unraid does not have swap. Memory is limited to user memory, I have 7.4Gb free in this system. htop:

I updated to the latest stable 6.12.14 yesterday. I used to have mongoDB coz the linuxserver unifi controller needs mongoDB to work. But I no longer have that container nor the content of the appdata folder. That is past time.

Hello, I have issues getting this docker running after updating my unraid OS. I have the unifi backup, I have wiped the appdata so it is considered a new installation. Version: 11notes/unifi:8.5.6-unraid All ports and docker settings are default. I have tried with bridge (i dont have any clashing ports) as well on br0 with dedicated IP. This is the error I'm getting when running it on bridge: WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) Exception in thread "mongo-db" java.lang.OutOfMemoryError: unable to create native thread: possibly out of memory or process/resource limits reached at java.base/java.lang.Thread.start0(Native Method) at java.base/java.lang.Thread.start(Thread.java:809) at java.base/java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:945) at java.base/java.util.concurrent.ThreadPoolExecutor.ensurePrestart(ThreadPoolExecutor.java:1593) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:346) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:562) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:715) at java.base/java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:748) at com.ubnt.service.trace.logerror.AnalyticsAppender.int(Unknown Source) at com.ubnt.service.trace.logerror.AnalyticsAppender.append(Unknown Source) at ch.qos.logback.core.AppenderBase.doAppend(AppenderBase.java:83) at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:51) at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:272) at ch.qos.logback.classic.Logger.callAppenders(Logger.java:259) at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:426) at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:386) at ch.qos.logback.classic.Logger.error(Logger.java:563) at com.ubnt.ace.OOoo.ôO0000(Unknown Source) at com.ubnt.ace.OOoo.ôo0000(Unknown Source) at com.ubnt.service.db.null.ö00000(Unknown Source) at com.ubnt.service.db.null.Óo0000(Unknown Source) at com.ubnt.service.db.null.ÔO0000(Unknown Source) at com.ubnt.service.db.null.run(Unknown Source) WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) WARN Unable to load properties from '/usr/lib/unifi/data/system.properties' - /usr/lib/unifi/data/system.properties (No such file or directory) {"time":"2024-12-02T07:44:33.000Z","type":"INF","msg":"starting unifi (8.5.6)"} [6116.156s][warning][os,thread] Failed to start thread "Unknown thread" - pthread_create failed (EAGAIN) for attributes: stacksize: 1024k, guardsize: 4k, detached. [6116.157s][warning][os,thread] Failed to start the native thread for java.lang.Thread "crash-reporter" When running it on br0 I only get the first line of the above warning. Regarding the memory warning I have about 16Gb free RAM and the docker image has space also. Any help appreciated.

Hi, Can someone give some guidence how to restore VM? I have the backup from the plugin and the img disk file. I tried the following: create a generic linux VM virsh edit the settings paste the config I get error that the VM already exists with the same uuid. Not sure what to do EDIT: I have resolved the issue by generating a new uuid on some website and replacing it in the config. It might not be the correct solution but it works just fine. Prerequisites: the original qcow or img file of the VM in the original location restored. 1. create a new linux VM, leave everything on default, does not matter. You will need to define an image location but that is all. Dont start the new VM just create it. 2. Go to uuidgenerator.net and create a new uuid, replace it in the backup xml 3. SSH into your unraid (copy paste works funky in the web console) and virsh edit new_VM_name 4. It will open the the config in vim editor. Replace all the config text with your config text (esc, ggVG, d, esc, i, right click to paste, esc, :wq) 5. Now if you refresh the VM page in unraid you will see your old VM and you can start is as usual, You will also see your temporary linux VM that you can remove. If you are confortable with virsh (provided you are reading this step-by-step you are not) you can create your own VM with the existing config from scratch.

Same issue for me. I have re-downloaded the docker image and started working again

Solved. So data folder has to be nobody:users And despite what they are saying online the cron shouldnt be run as www-data user. I just removed the --user flag and it works: this is my cron script #!/bin/bash docker exec Nextcloud php /var/www/html/cron.php

../ is /mnt/user/Private ./ is /mnt/user/Private/nextcloud nextcloud dir is already 770 root@TEVENAS:/mnt/user/Private# stat -c "%a" ./nextcloud 770 Ok this might not be obvious for me I'm not really good with the understanding of linux permissions: if the Private dir is not owned by 33:33 will it not work? /mnt/user is owned by nobody:users so I guess it should work, everything else works on my system.

Hi @Kilrah thanks for your answer. Are you sure my permission on nextcloud is not 770? For me it seems to be. Here I redo everything from scratch: root@TEVENAS:~# getent passwd sshd #Making sure sshd:sshd is the 33:33 id user on my unraid sshd:x:33:33:sshd:/:/bin/false root@TEVENAS:~# chown -R sshd:sshd /mnt/user/Private/nextcloud #Make sshd:sshd the owener of nextcloud folder recursively root@TEVENAS:~# chmod -R 770 /mnt/user/Private/nextcloud #Chmod 770 the entire folder and its contents recursively root@TEVENAS:~# cd /mnt/user/Private root@TEVENAS:/mnt/user/Private# ls -ld ./nextcloud #Check folder permission and owner, seems to be correct drwxrwx--- 1 sshd sshd 142 May 6 13:20 ./nextcloud/ root@TEVENAS:/mnt/user/Private# cd nextcloud root@TEVENAS:/mnt/user/Private/nextcloud# ls -l -a #List all the stuff to see its users and permissions total 1108 drwxrwx--- 1 sshd sshd 142 May 6 13:20 ./ drwxrwx--- 1 daninet users 6 May 7 12:46 ../ -rwxrwx--- 1 sshd sshd 542 May 6 13:06 .htaccess* -rwxrwx--- 1 sshd sshd 0 May 6 13:06 .ocdata* drwxrwx--- 1 sshd sshd 130 May 6 15:33 appdata_ock2dw0o714w/ drwxrwx--- 1 sshd sshd 76 May 7 09:09 daninet/ drwxrwx--- 1 sshd sshd 27 May 6 13:20 files_external/ -rwxrwx--- 1 sshd sshd 0 May 6 13:06 index.html* -rwxrwx--- 1 sshd sshd 1129157 May 9 21:00 nextcloud.log* root@TEVENAS:/mnt/user/Private/nextcloud# cd .. root@TEVENAS:/mnt/user/Private# stat -c "%a" ./nextcloud #check chmod as a numeric value 770 After all this i still have this on my start screen:

Hi! I'm having trouble with the user data folder. I could not found solution so far. These are my allocations: /var/www/html /mnt/user/appdata/nextcloud/html /var/www/html /custom_apps/mnt/user/appdata/nextcloud/apps /var/www/html/config /mnt/user/appdata/nextcloud/config /var/www/html/data /mnt/user/Private/nextcloud/ Inside the container there is a user called www-data:www-data (33:33) running the cron jobs. In my unraid the 33:33 user is sshd:sshd I made the owner of the dir /mnt/user/Private/nextcloud/ the sshd user and the cron job suggested me to make the permission 770. I did. If I make the permission 770 this is what I get on the frontpage (and the cronjob runs on the same error saying it has no permission): The data directory is invalid. Ensure that there is a ".ocdata" file in the root of the data directory. The data directory is not writable. Permissions can typically be fixed by giving the web server write access to the root directory. See https://docs.nextcloud.com/server/29/go.php?to=admin-dir_permissions. Ok so 770 is not enough? Make it 777. Then I get this: Your data directory is readable by other people. Please change the permissions to 0770 so that the directory cannot be listed by other people. Welp.. maybe 775? The data directory is not writable. Permissions can typically be fixed by granting write access to the web server on the root directory. See https://docs.nextcloud.com/server/29/go.php?to=admin-dir_permissions. This is a bit comical.. :)) where is the issue now? root@TEVENAS:/mnt/user/Private/nextcloud# ls -ld drwxrwx--- 1 sshd sshd 142 May 6 13:20 ./ root@TEVENAS:/mnt/user/Private/nextcloud# ls -l -a total 1104 drwxrwx--- 1 sshd sshd 142 May 6 13:20 ./ drwxrwx--- 1 nobody users 18 May 7 12:46 ../ -rwxrwx--- 1 sshd sshd 542 May 6 13:06 .htaccess* -rwxrwxrwx 1 sshd sshd 0 May 6 13:06 .ocdata* drwxrwx--- 1 sshd sshd 130 May 6 15:33 appdata_ock2dw0o714w/ drwxrwx--- 1 sshd sshd 76 May 7 09:09 daninet/ drwxrwx--- 1 sshd sshd 27 May 6 13:20 files_external/ -rwxrwx--- 1 sshd sshd 0 May 6 13:06 index.html* -rwxrwx--- 1 sshd sshd 1123780 May 9 20:50 nextcloud.log*

working, thanks😊

I'm having trouble with the setup and not sure why. I have tried to follow the instructions. The unifi web interface is not reachable. These are the steps I took: 1. backup the deprecated ls.io unifi container. 2. Install mongodb with the init script init-mongo.js db.getSiblingDB("unifi").createUser({user: "daninet", pwd: "pwd", roles: [{role: "dbOwner", db: "unifi"}]}); db.getSiblingDB("unifi_stat").createUser({user: "daninet", pwd: "pwd", roles: [{role: "dbOwner", db: "unifi_stat"}]}); docker run docker run -d --name='MongoDB' --net='bridge' -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="TEVENAS" -e HOST_CONTAINERNAME="MongoDB" -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='https://raw.githubusercontent.com/jason-bean/docker-templates/master/jasonbean-repo/mongo.sh-600x600.png' -p '27017:27017/tcp' -v '/mnt/user/appdata/mongodb/':'/data/db':'rw' -v '/mnt/user/appdata/mongodb/mongo_init/init-mongo.js':'/docker-entrypoint-initdb.d/init-mongo.js':'rw' 'mongo' 53b1599bcd21ae9bca1461eb19327e5e4a4952ee6df196f2025fe28c26cd325a Then setup the new unifi container: docker run -d --name='unifi-network-application' --net='bridge' -e TZ="Europe/Budapest" -e HOST_OS="Unraid" -e HOST_HOSTNAME="TEVENAS" -e HOST_CONTAINERNAME="unifi-network-application" -e 'MONGO_USER'='daninet' -e 'MONGO_PASS'='pwd' -e 'MONGO_HOST'='unifi-db' -e 'MONGO_PORT'='27017' -e 'MONGO_DBNAME'='unifi' -e 'MEM_LIMIT'='1024' -e 'MEM_STARTUP'='1024' -e 'MONGO_TLS'='' -e 'MONGO_AUTHSOURCE'='' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://192.168.1.200:8443/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/unifi-network-application-icon.png' -p '8443:8443/tcp' -p '3478:3478/udp' -p '10001:10001/udp' -p '8080:8080/tcp' -p '1900:1900/udp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '6789:6789/tcp' -p '5514:5514/udp' -v '/mnt/user/appdata/unifi-network-application':'/config':'rw' 'lscr.io/linuxserver/unifi-network-application' aaa2d5762f3f99c50def5ef5a419972aba766006c1351c58382cfe57347f8bf5 Now the container log is telling me the following: *** Waiting for MONGO_HOST unifi-db to be reachable. *** *** Defined MONGO_HOST unifi-db is not reachable, cannot proceed. *** What is exactly unifi-db? I did not define it anywhere but the documentation says use this. They are both on the same subnet. My other DBs are working on this subnet.

Hi, Thank you for your replies. I think I have cracked it and it is related to inodes and unraid's cache. The file inode changes when unraid moves the file from cache to hdd and the share unmounts. Adding noserverino flag to the smb mount resolves the problem. This is the proper config for unraid cached shares with fstab: //server_address/share_name /mount/path cifs credentials=/home/username/.smbcredentials,uid=1000,gid=1000,vers=3.0,noserverino,nounix,_netdev 0 0 Thank you for all the help it was really useful and have learnt a lot.

Thank you for the detailed answer. There is a lot to unpack and I will dig myself through the settings. As for some of your questions: I initially thought xdg-desktop-portal is somehow responsible (the window that lets you pick or save a file). Very often the following happens: I download a file (any file really, pdf, image etc) from the internet, save the file to my share with the xdg-desktop-portal and when I open dolphin the share is no longer reachable. Edit: I'm really happy now, I was able to trigger it with xdg-desktop-portal and record it also. See video attached. This is an SMB mount. This also happens if I just let it be for an hour. 2024-01-16_10-54-59.mkv