ssjucrono

Members
  • Posts

    95
  • Joined

  • Last visited

Everything posted by ssjucrono

  1. Thank you! Duh yes I was messing around with some large dockers and ran out of space a few times. Thank you!
  2. 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]
  3. upgrade went well! container is working great once I got my issues sorted out!
  4. ok Great! Glad I got this all working! now excited about version 8.0.x Thank you for all this work!
  5. Ok that worked! when i click webui it shows blocked? but when I type it in manually it works! thank you very odd
  6. I agree something might be wrong with my network setup on unraid but not sure where to even start looking. I did type an IP in the template Also My old unifi controller works fine still so that seems confusing
  7. I have not done the set inform. I will try that. I did the set inform host but when I use custom:bro it shows up like this and I cannot access the webui
  8. rebooting hard rebooting my switch and AP didn't work. I also tried the custom:br0 with the IP I was using prior and the container doesn't seem to work like that?
  9. Okay I will reboot them. I had the controller on a a different IP than I do now.
  10. hmm I also did the restore and it seemed to work. Maybe I need to start over again. yeah deleted everything and the appdata folder and restored from backup and still just spinning adopting does it matter it has a docker IP in the GUI?
  11. now I am wondering how long it takes to adopt my unifi devices? IT just keeps trying over and over? sorry for all the newbie questions.
  12. yes you are right it is not Plex. It is something else using port 1900 but I have no idea what or how to figure it out Found this command and figured out it was my docker container airconnect once I turned that off it worked. and again ports are not listed in that docker template
  13. I am using the official PMS Docker? Here is the Unifi Reborn error
  14. trying out this container now. I am having a conflict with port 1900. Plex is also using that port and I do not see an option in the Plex Template to change it. I changed on the unifi reborn but then it wasn't adopting my unifi devices. So I turned plex off and tried using port 1900 on Unifi Reborn and it is still saying it can't bind to 1900 as plex is using it though it is powered off.
  15. ok good to know. So this one will be updated going forward and maintained? I'll make the switch!
  16. sorry, trying to figure out how this is better than the other docker containers? Very curious to give it a try but I want to understand the difference first? thank you
  17. I think the same thing happened to me. Grocy just broke
  18. Does anyone have an updated URL for Samsung Magician trying to upgrade my 980 pro firmware as there is an issue on an older firmware. This link http://www.samsung.com/global/business/semiconductor/minisite/SSD/downloads/software/ Does not work anymore. Thank you
  19. I am having the same issue and it is a huge problem as it is my zigbee usb stick so all my zigbee devices stop working. looking for a fix: May 11 12:48:04 RAID kernel: usb 3-3: new full-speed USB device number 88 using xhci_hcd May 11 12:48:04 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:04 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:05 RAID kernel: usb 3-3: new full-speed USB device number 89 using xhci_hcd May 11 12:48:05 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:05 RAID kernel: usb 3-3: device descriptor read/64, error -71 May 11 12:48:05 RAID kernel: usb usb3-port3: attempt power cycle May 11 12:48:05 RAID kernel: usb 3-3: new full-speed USB device number 90 using xhci_hcd May 11 12:48:05 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: device not accepting address 90, error -71 May 11 12:48:06 RAID kernel: usb 3-3: new full-speed USB device number 91 using xhci_hcd May 11 12:48:06 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: Device not responding to setup address. May 11 12:48:06 RAID kernel: usb 3-3: device not accepting address 91, error -71 May 11 12:48:06 RAID kernel: usb usb3-port3: unable to enumerate USB device
  20. @JorgeB I did find this jumper on my motherboard. Not sure if that is of any help?
  21. oooh, interesting. I had no idea. I am also talking to the creator of the PCIe adaptor
  22. yes, I guess I am not sure what you are getting at?