Jump to content

ErikM1970

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ErikM1970

  • Rank
    Newbie
  • Birthday 09/04/1970

Converted

  • Gender
    Male
  • Location
    Miramar, FL
  1. Good evening, I am running v4.10.0 of the ControlR application and noticed that the CPU temperature reading is showing up in Celsius but with the Fahrenheit symbol as well. Has this yet been reported? I checked back a few pages and didn’t see it. My unRAID box is configured for Fahrenheit. Thank you, Erik Sent from my iPhone using Tapatalk Pro
  2. PS: Trying to create a new post but I think I am replying to an existing post... Good evening, Finally upgraded my UnRaid to 6.7.0 and the only casualty was my DelugeVPN container. I attempted to start and continually receive an Execution Error (Server Error). I've been looking around here for something similar but haven't yet found anything. Since it first set it up, it has just worked... until now. If anyone has read about this before, I would appreciate any guidance. I checked my supervisord.log and the following was recorded for today: 2019-05-20 17:44:25,874 WARN received SIGTERM indicating exit request 2019-05-20 17:44:25,880 DEBG killing watchdog-script (pid 150) with signal SIGTERM 2019-05-20 17:44:25,880 INFO waiting for start-script, watchdog-script to die 2019-05-20 17:44:26,880 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 22387675056840 for <Subprocess at 22387675685608 with name watchdog-script in state STOPPING> (stdout)> 2019-05-20 17:44:26,881 DEBG fd 20 closed, stopped monitoring <POutputDispatcher at 22387675057008 for <Subprocess at 22387675685608 with name watchdog-script in state STOPPING> (stderr)> 2019-05-20 17:44:26,881 INFO stopped: watchdog-script (terminated by SIGTERM) 2019-05-20 17:44:26,881 DEBG received SIGCHLD indicating a child quit 2019-05-20 17:44:26,881 DEBG killing start-script (pid 149) with signal SIGTERM 2019-05-20 17:44:27,882 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 22387675056448 for <Subprocess at 22387675590496 with name start-script in state STOPPING> (stdout)> 2019-05-20 17:44:27,883 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 22387675056616 for <Subprocess at 22387675590496 with name start-script in state STOPPING> (stderr)> 2019-05-20 17:44:27,883 INFO stopped: start-script (terminated by SIGTERM) 2019-05-20 17:44:27,883 DEBG received SIGCHLD indicating a child quit I did go back a week and found the following (perhaps my container has had issues prior to today? Not sure...) 2019-05-13 17:43:11,037 DEBG 'watchdog-script' stderr output: Unhandled error in Deferred: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/twisted/protocols/policies.py", line 120, in dataReceived self.wrappedProtocol.dataReceived(data) File "/usr/lib/python2.7/site-packages/deluge/ui/client.py", line 179, in dataReceived d.callback(request[2]) File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 460, in callback self._startRunCallbacks(result) File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 568, in _startRunCallbacks self._runCallbacks() --- <exception caught here> --- File "/usr/lib/python2.7/site-packages/twisted/internet/defer.py", line 654, in _runCallbacks current.result = callback(current.result, *args, **kw) File "/usr/lib/python2.7/site-packages/deluge/ui/sessionproxy.py", line 147, in on_status self.torrents[torrent_id][0] = t exceptions.KeyError: u'0581137073caf6d96d9047368dd95b400a9953aa' Thank you, Erik
  3. Good evening, I am relatively new to unRAID and I can say so far it has been a very good experience. There is just one issue I cannot seem to figure out. My system will be humming along nicely and out of the blue a warning appears indicating "BTRFS cache pool missing devices". I have a two drive cache configured and periodically one of the cache devices (not always the same one) just disappears. I've read through the forums and found other instances; however, some of these messages are dated and the version running was much older than my 6.6.7. The only way I can get the cache drive to return is by completely powering down the system and then turning it back on again--apparently a reboot isn't sufficient. I have attached my Diagnostics file and am hoping someone here can point me in the right direction. Today, April 28, 2019 at 5:29 PM EDT was the latest occurrence. Thank you, Erik nexus-diagnostics-20190428-1928.zip