austinite

Members
  • Posts

    11
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Austin

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

austinite's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Same issue. Details: Plugins | Network Stats Network Stats Settings Interfaces to capture : (ALL) eth0 eth1 (ALL) VNSTAT Daemon: Stopped start (clicking start does nothing) Stats | Network Stats: vnstat service must berunning started to view network stats.
  2. Thanks @Squid and @trurl. Manually deleting the advanced buttons.plg from the cache drive and rebooted. It worked. Appreciate it. Edit: Noticed these messages every second in the log, though: May 6 23:02:51 unRAIDTower nginx: 2018/05/06 23:02:51 [error] 9375#9375: *28082 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: 192.168.1.92, server: , request: "POST /plugins/advanced.buttons/AdvancedButtons.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.99", referrer: "http://192.168.1.82/Dashboard"
  3. Hi. Running unRAID 6.5.1 and Community Applications fails to upgrade. It shows I'm on version 2018.04.22 and that 2018.05.05 is available. Tried it 4x. System logs only shows the attempt to upgrade (in the GUI, it says it fails and then that is was successful but doesn't actually update) : May 5 12:00:36 Tower ool www[23399]: /usr/local/emhttp/plugins/advanced.buttons/script/plugin 'update' 'communityapplications:.plg' &>/dev/null & Anyone else having this issue or have any recommendations? Thanks.
  4. Just started getting an authentication prompt after upgrading to Version 0.2.0.995 a few minutes ago. Found a discussion on Reddit and someone there mentioned "Web host issues, according to Discord channel" so hopefully it's just temporary. Hitting cancel seems to work fine for now.
  5. I know this is an ancient thread, but thought I'd share that while I've used the cp --reflink command before successfully, it's now failing. Apparently this is a known bug in the newer OS: https://bugs.centos.org/view.php?id=14228 Curious if anyone has any new methods for backing up VMs or any other kind of snapshot method within unRaid.
  6. Thanks @johnnie.black and @Frank1940! I've adjusted the vm.dirty_background_ratio and vm.dirty_ratios settings to 1 and 2. My server has 64GB of RAM. I'm rebooting and will monitor over the next days.
  7. I appreciate the quick reply, @Frank1940. I had the impression that the vm settings here were for virtual machines and thus not applicable as I've turned off VMs (also the help tips seem to indicate that). Just in case, I modified the vm.dirty_background_ratio and vm.dirty_ratios from their defaults of 10% and 20% to the levels suggested in the post (2% and 4%). Sep 14 22:01:09 Tower tips.and.tweaks: Tweaks Applied The system is running very sluggishly so it's hard to tell whether this has made any effect. I'm concerned that rebooting will simply delay further troubleshooting.
  8. My unRAID server has been unreliable for some time, causing docker containers to stall or become unresponsive. The unRAID GUI and even CLI/ssh response gets very sluggish when this occurs. Attempting to stop and restart containers rarely works. Usually I end up rebooting the server and things go back to normal for a few days or so. Running the Fix Common Problems plugin indicates the following: Out Of Memory errors detected on your server Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the unRaid forums Call Traces found on your server Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums I've attached the diagnostic file and would really appreciate any recommendations. Thanks! tower-diagnostics-20170914-1950.zip
  9. I'm getting the exact same thing on multiple attempts at initial/clean builds (black screen when attempting to connect via VNC). Seems the current docker has a defect of some kind for new installs.