ssjucrono

Members
  • Posts

    97
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

998 profile views

ssjucrono's Achievements

Apprentice

Apprentice (3/14)

6

Reputation

1

Community Answers

  1. I have had to hard reboot my server 3 times in the last 2-3 days. IT just stops working not even pingable, it is still powered on though. I have the syslog mirrored to flash but I couldn't find the log. It is a dual xeon server with an asus motherboard I can provide more information if needed. I have attached the diagnostics. If anyone can give me insight that would be great! raid-diagnostics-20240417-2107.zip
  2. To fix my issue I used a custom:br0 so it has different IP so no more port conflict
  3. Thank you! Duh yes I was messing around with some large dockers and ran out of space a few times. Thank you!
  4. 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]
  5. upgrade went well! container is working great once I got my issues sorted out!
  6. ok Great! Glad I got this all working! now excited about version 8.0.x Thank you for all this work!
  7. Ok that worked! when i click webui it shows blocked? but when I type it in manually it works! thank you very odd
  8. 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
  9. 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
  10. 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?
  11. Okay I will reboot them. I had the controller on a a different IP than I do now.
  12. 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?
  13. 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.
  14. 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