January 1, 20242 yr Author Im not sure but giving the unraid docker the same ip as the old ubuntu server if you turn it off might help adoption of you did a restore.
January 6, 20242 yr seeing this error now. I had it running for sometime normally. # Problematic frame: # V [libjvm.so+0xce766b][thread 158 also had an error] [thread 141 also had an error] RuntimeService::record_safepoint_begin(long)+0x1b # # 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: # Unknown # [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x0000151d4e589941] # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0x7) at pc=0x000014a02887c9f2, pid=1, tid=21 # # JRE version: OpenJDK Runtime Environment (17.0.9+9) (build 17.0.9+9-Ubuntu-120.04) # Java VM: OpenJDK 64-Bit Server VM (17.0.9+9-Ubuntu-120.04, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64) # Problematic frame: # V [libjvm.so+0xc7c9f2] 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: # Unknown # [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x000014a0290cd941]
January 6, 20242 yr Author 33 minutes ago, ssjucrono said: seeing this error now. I had it running for sometime normally. # Problematic frame: # V [libjvm.so+0xce766b][thread 158 also had an error] [thread 141 also had an error] RuntimeService::record_safepoint_begin(long)+0x1b # # 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: # Unknown # [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x0000151d4e589941] # # A fatal error has been detected by the Java Runtime Environment: # # SIGBUS (0x7) at pc=0x000014a02887c9f2, pid=1, tid=21 # # JRE version: OpenJDK Runtime Environment (17.0.9+9) (build 17.0.9+9-Ubuntu-120.04) # Java VM: OpenJDK 64-Bit Server VM (17.0.9+9-Ubuntu-120.04, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, parallel gc, linux-amd64) # Problematic frame: # V [libjvm.so+0xc7c9f2] 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: # Unknown # [error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x000014a0290cd941] Not sure. Could you restart the docker or not? Check you had disk space available. Edited January 6, 20242 yr by PeteAsking
January 8, 20242 yr Thank you! Duh yes I was messing around with some large dockers and ran out of space a few times. Thank you!
January 8, 20242 yr Author New controller tag has been released and is tested for home use: 11notes/unifi:8.0.26-unraid
January 8, 20242 yr 5 minutes ago, PeteAsking said: New controller tag has been released and is tested for home use: 11notes/unifi:8.0.26-unraid Is this now the new recommended tag for home usage?
January 8, 20242 yr Author 21 minutes ago, Ruato said: Is this now the new recommended tag for home usage? Yes this is correct.
January 9, 20242 yr Moved over from the LSIO docker yesterday following the instructions in the first post and no issues with the changeover. Only question I have is there a plan to enable a "latest" tag so we can just hit the update button in Unraid rather than modifying the tag to each release number to update? Also thank you for your work on getting this up and running to replace the current LSIO docker
January 9, 20242 yr Author 31 minutes ago, fat said: Moved over from the LSIO docker yesterday following the instructions in the first post and no issues with the changeover. Only question I have is there a plan to enable a "latest" tag so we can just hit the update button in Unraid rather than modifying the tag to each release number to update? Also thank you for your work on getting this up and running to replace the current LSIO docker No this tag will not/does not exist and there are no plans to include it.
January 9, 20242 yr How do you upgrade a version just stop the docker replace the repository line with the new one and start it back up?
January 9, 20242 yr 2 minutes ago, chclark said: How do you upgrade a version just stop the docker replace the repository line with the new one and start it back up? With a suitable backup in between yes.
January 9, 20242 yr 13 minutes ago, chclark said: How do you upgrade a version just stop the docker replace the repository line with the new one and start it back up? You don't actually need to stop the docker. You can just change the repository field and click "Apply".
January 9, 20242 yr Just now, wgstarks said: You don't actually need to stop the docker. You can just change the repository field and click "Apply". Thanks for confirming just wanted to make sure I knew the process as I couldn't see it mentioned.
January 10, 20242 yr 3 hours ago, fat said: is there a plan to enable a "latest" tag It is very wise that this has not been implemented. You do not want an automatic update to whatever controller version Ubiquiti just released. They tend to be in a beta state at best and sometimes have been more like alpha software. Admittedly, Ubiquiti had gotten much better over the last year or so in releasing more stable controller software; however, it is still best to let any new release stew for a week or two and see what the more adventurous users discover and post in the Ubiquiti forums. If there are no major problems, @PeteAsking will create a tag for that release which usually means it is safe (mostly) to proceed with the update.
January 10, 20242 yr Author 8 minutes ago, Hoopster said: It is very wise that this has not been implemented. You do not want an automatic update to whatever controller version Ubiquiti just released. They tend to be in a beta state at best and sometimes have been more like alpha software. Admittedly, Ubiquiti had gotten much better over the last year or so in releasing more stable controller software; however, it is still best to let any new release stew for a week or two and see what the more adventurous users discover and post in the Ubiquiti forums. If there are no major problems, @PeteAsking will create a tag for that release which usually means it is safe (mostly) to proceed with the update. The expand on this there is a testing process that we undertake on the new container prior to deployment and after before announcing it here on the forum so it has at leased passed a basic quality control check.
January 10, 20242 yr 21 minutes ago, wgstarks said: You don't actually need to stop the docker. You can just change the repository field and click "Apply". But for safety, stop docker, do a backup (appdata backup/restores, zfs snapshot, manual or whatever), then change it.
January 11, 20242 yr i've just seen the reddit post about the current installs expiring 1/1/24. i'm running controller 5.14.23 with 12 or so sites on it. can i migrate to this reborn or do i need to do something else? edit - went for it to 8.0.24. it went without a hitch and is working great. thank you. Edited January 11, 20242 yr by Jammy B
January 11, 20242 yr Author 4 hours ago, Jammy B said: i've just seen the reddit post about the current installs expiring 1/1/24. i'm running controller 5.14.23 with 12 or so sites on it. can i migrate to this reborn or do i need to do something else? edit - went for it to 8.0.24. it went without a hitch and is working great. thank you. No problem. If you always take a backup before changes you should be fine no matter what.
January 14, 20242 yr On 1/1/2024 at 3:04 PM, DWomack said: Thank you for your help on this New Years Day. Your suggestion above does stop it on the Ubuntu box. Likewise sudo service unifi start will start it back up. I am still having issues with adopting. It doesn’t want to adopt. I think the fly in the ointment is the meshing ability. When it is trying to adopt it is trying to get there through an AP that hasn’t been adopted. How in UniFi can you force wired only? No meshing at all. I know meshing can provide some redundancy if wired fails but this ridiculous. Dennis I have been having issues adopting devices in this controller as well. The solution for me has been to ssh into each device and manually set the inform address: set-inform http://ip-of-controller:8080/inform I just noticed though my switch was once again in the adopting loop and I had to do this a second time, which was weird.
January 14, 20242 yr Author 1 hour ago, Tunatron said: I have been having issues adopting devices in this controller as well. The solution for me has been to ssh into each device and manually set the inform address: set-inform http://ip-of-controller:8080/inform I just noticed though my switch was once again in the adopting loop and I had to do this a second time, which was weird. Dont forget to check the inform host override is set correctly on the controller.
January 14, 20242 yr 4 hours ago, PeteAsking said: Dont forget to check the inform host override is set correctly on the controller. Discovered that a little while ago and had come back to edit my post to add, ha. Seems like everything is working as it should for me now.
January 15, 20242 yr Thank you for the image. I am running this on unraid and have found all the versions are exiting with code 143 after a certain amount of hours (not sure how long yet). I can't find anything wrong though, no errors or issues. Any ideas?
January 15, 20242 yr Author 2 minutes ago, Annih said: Thank you for the image. I am running this on unraid and have found all the versions are exiting with code 143 after a certain amount of hours (not sure how long yet). I can't find anything wrong though, no errors or issues. Any ideas? Are you running out of resources or something? How much ram is in use typically that sort of thing.
January 16, 20242 yr No other containers are stopping, average RAM I can see is max 1GB for this container, overall memory is 20GB free. I can't see any obvious reason for the shutdown.
January 16, 20242 yr Author Not sure but that error means the OS told it to stop for some reason. Could be anything that causes it from a backup to low resources or so on.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.