Jump to content

jbear

Members
  • Content Count

    133
  • Joined

  • Last visited

Community Reputation

1 Neutral

About jbear

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. Did an iGPU version of the new BIOS get released privately or other? Just wanted to follow-up. Thanks.
  2. If they produce an iGPU version of the new BIOS, please let us know. Would like a copy, if possible.
  3. My Unraid server locked up last night, it was extracting a large multi file RAR, as far as I can tell anyway, this is not an unusual task, and have done this many times with the new setup, with no issues. Not sure what to think of it, I suppose I will just monitor my server. I'm running 6.9 BETA 1. Outside of the BIOS settings relating to Onboard VGA for Plex transcoding, did you guys massage any of the other settings? I looked through them based on my experience, and nothing jumped out at me, virtualization stuff was enabled by default etc. I do have room for the larger cooler, before I spring for that, I want to make sure it's necessary. No distributed computing dockers enabled. No real CPU intensive tasks. I may transcode 2-3 Plex streams on occasion, all being doing via HW in RAM, which I have confirmed is working correctly. JB
  4. I'm also running the NH-U9S, which seems to be adequate for my intended usage. I'm not currently taking part in BOINC or FOLDINGATHOME, which I assume would potentially expose the shortcoming of this cooler. With that said, I found it interesting the Noctua didn't exactly recommend a cooler. So what cooler is recommended for the E-2288G at full load?
  5. Thank you sir, swapped out my old motherboard combo for the new combo. Everything seems good so far.
  6. I ended up going with this setup also, can someone email me or provide link to download BETA BIOS? Still waiting to hear from ASROCK. Would like to move forward with install. Thanks. JB jsbear@gmail.com
  7. Wanted to follow-up on my own post, from what I can tell, this manifests itself if I fail to logout of the browser based admin interface. So essentially after about 24 of being logged in, the system log will start to fill with the entries seen above. After 48- 72 hours or so my system log will be at 100%. If I logout, they stop. Obviously logging out here is the answer but you wouldn't think this would be the end result. Is there a way to automatically logout of a session after X minutes of inactivity? I've really never had this issue until the 6.8 releases, currently on 6.9 beta 1. I will continue to monitor, but this is where I'm currently at. Any feedback is appreciated. Thanks. tower-diagnostics-20200401-1525.zip
  8. I'm getting the following errors in my system log, I've been seeing this issue in the last several versions. I thought I would try the BETA in the hope it would address this issue., which it hasn't. I can't download diagnostics, the web interface becomes unstable / partially functional, eventually my log will hit 100% after 2-3 days, forcing me to reboot. Log is filed with this. Mar 25 14:56:35 Tower nginx: 2020/03/25 14:56:35 [alert] 7994#7994: worker process 20475 exited on signal 6 Mar 25 14:56:37 Tower nginx: 2020/03/25 14:56:37 [alert] 7994#7994: worker process 20476 exited on signal 6 Mar 25 14:56:39 Tower nginx: 2020/03/25 14:56:39 [alert] 7994#7994: worker process 20493 exited on signal 6 Mar 25 14:56:41 Tower nginx: 2020/03/25 14:56:41 [alert] 7994#7994: worker process 20497 exited on signal 6 Mar 25 14:56:42 Tower nginx: 2020/03/25 14:56:42 [alert] 7994#7994: worker process 20500 exited on signal 6 Mar 25 14:56:44 Tower nginx: 2020/03/25 14:56:44 [alert] 7994#7994: worker process 20502 exited on signal 6 Mar 25 14:56:46 Tower nginx: 2020/03/25 14:56:46 [alert] 7994#7994: worker process 20505 exited on signal 6 Mar 25 14:56:46 Tower nginx: 2020/03/25 14:56:46 [alert] 7994#7994: worker process 20510 exited on signal 6 Mar 25 14:56:48 Tower emhttpd: error: publish, 244: Connection reset by peer (104): read Mar 25 14:56:48 Tower nginx: 2020/03/25 14:56:48 [alert] 7994#7994: worker process 20511 exited on signal 6 Mar 25 14:56:50 Tower nginx: 2020/03/25 14:56:50 [alert] 7994#7994: worker process 20515 exited on signal 6 Mar 25 14:56:50 Tower nginx: 2020/03/25 14:56:50 [alert] 7994#7994: worker process 20516 exited on signal 6 Mar 25 14:56:52 Tower nginx: 2020/03/25 14:56:52 [alert] 7994#7994: worker process 20517 exited on signal 6 Mar 25 14:56:52 Tower nginx: 2020/03/25 14:56:52 [alert] 7994#7994: worker process 20526 exited on signal 6 Mar 25 14:56:54 Tower nginx: 2020/03/25 14:56:54 [alert] 7994#7994: worker process 20527 exited on signal 6 Mar 25 14:56:54 Tower nginx: 2020/03/25 14:56:54 [alert] 7994#7994: worker process 20529 exited on signal 6 Mar 25 14:56:56 Tower nginx: 2020/03/25 14:56:56 [alert] 7994#7994: worker process 20530 exited on signal 6 Mar 25 14:56:56 Tower nginx: 2020/03/25 14:56:56 [alert] 7994#7994: worker process 20533 exited on signal 6 Any input or ideas are appreciated. If I could download diagnostics, I would.
  9. Mar 2 19:57:39 Tower nginx: 2020/03/02 19:57:39 [alert] 6557#6557: worker process 15193 exited on signal 6 Mar 2 19:57:42 Tower nginx: 2020/03/02 19:57:42 [alert] 6557#6557: worker process 15264 exited on signal 6 Mar 2 19:57:44 Tower nginx: 2020/03/02 19:57:44 [alert] 6557#6557: worker process 15270 exited on signal 6 Mar 2 19:57:46 Tower nginx: 2020/03/02 19:57:46 [alert] 6557#6557: worker process 15295 exited on signal 6 My system log is filling up with these line items. Any thoughts? tower-syslog-20200303-1852.zip
  10. 108c, that is off the charts, never heard of such a thing, that is 226 degrees Fahrenheit, I believe max operating temp on Seagate Ironwolf drives is 70c, similar on WD Red NAS drives. Something seem off, you need to improve you airflow ASAP, make sure fans are working, install more fans. Where is your NAS located? Closet? Dungeon?
  11. The OAuth2Proxy container is always stuck in "Update Ready" status, not experiencing issues with any of my other containers. I've tried updating, re-installing, with no luck. It does work however, which is the most important thing It's been like this for some time now, dating back to 6.6. Thought I would post to see if anyone had an idea what may be going on. Currently on 6.7.0-RC7. Thanks.
  12. Note sure if anyone replied on this, but files can't be added to Nextcloud by copying them directly into the user profile in the file folder. You must leverage webdav, web interface etc. Alternatively, iI you do choose to add them in this manner, you would need to invoke the occ tool from the command line, there is a parameter to add them to the database with files:scan. Not sure if this would make sense or not. Hope this helps.
  13. I followed the manual instructions via the link on the first post. It does state you can use the web interface also, but I couldn't find any proof that was the preferred method after reading this entire thread. I did have to re-install all of my apps for some reason, not sure why, but I did follow the directions exactly as provided. Re-adding the apps was very simple, configuration settings relating to those apps appear to have been retained. So I'm now on 15.0.2.
  14. https://blog.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/