limetech

Administrators
  • Content count

    6862
  • Joined

  • Last visited

  • Days Won

    18

limetech last won the day on January 13

limetech had the most liked content!

Community Reputation

269 Very Good

About limetech

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. I'm just going to be honest: I don't know what's happening with your particular server. There isn't a general issue where everyone is seeing high cpu usage in this manner. It's gong to take time I don't have right now to investigate this case further.
  2. In the logs you posted, there's a python process in a docker container consuming 67% CPU.
  3. You're fast... was going to add: the 99.1% you're seeing is the sum of 10 processes - do you have something hammering storage that much?
  4. Please post diagnostics.zip
  5. I think we can fix this behavior.
  6. We probably should have added some code in unRAIDServer.plg that detects if user is using -p option on their emhttp line in go file, and if so, set the USE_SSL, PORT, and SSL_PORT appropriately. We can add for 6.4.1 release.
  7. Sure. Please provide sample text and the link and I'll update OP.
  8. unRAID OS version 6.4.0 Stable Release Available

    Settle down. They were moved because you didn't read: Just click on your own icon and see where your posts (and replies) are now.
  9. Please only post suggestions here for additional information to be added to OP.
  10. Safe Mode plugin cron entries

    This will get into next point release.
  11. Logout - Login

    Yeah we'll see if we can suppress that message.
  12. 6.4, now I have Call Traces

    Well it's not a segfault (kernel crash), it's a warning that something happened that "shouldn't" happen, along with a stack dump to aide developer.
  13. 6.4, now I have Call Traces

    Someone posted same error over on redhat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1529971 Does everything seem to still work?
  14. Recent dnsmasq vulnerability & unraid

    unRAID 6.4 uses updated dnsmaq (v. 2.78) which fixes all these issues. https://access.redhat.com/security/vulnerabilities/3199382 http://www.slackware.com/security/viewer.php?l=slackware-security&y=2017&m=slackware-security.601472
  15. Security flaw discovered in Intel chips.

    Good place to monitor progress in addressing this: https://github.com/hannob/meltdownspectre-patches

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.