June 12, 201610 yr Hello, as the topic says my unraid system and plex server won't respond after about 10 minutes online, I have resetted router Changed TP cable unraid webgui and plex media server goes unresponsive, and abit later the shares go down to syslog included syslog.txt
June 12, 201610 yr What are your complete hardware specs on the server including PS make and model The syslog is way too short to be of any use. What you need to do is reboot the server, install fix common problems, and then put it into troubleshooting mode. After the system crashes, then post from your flash drive folder logs the latest diagnostics files, and the syslog.txt file
June 12, 201610 yr Author AMD A10-7890K Black Edition, Socket-FM2+ Corsair Vengeance DDR3 1600MHz 4GB CL9 Corsair RM750, 750W PSU ASUS A88X-Plus, Socket-FM2+ Corsair Flash Voyager GT 32GB USB 3.0 PS? It seems to be working for now, dunno why, my syslog got 129mb so can't upload it. skynas-diagnostics-20160612-2054.zip syslog_2.txt
June 12, 201610 yr AMD A10-7890K Black Edition, Socket-FM2+ Corsair Vengeance DDR3 1600MHz 4GB CL9 Corsair RM750, 750W PSU ASUS A88X-Plus, Socket-FM2+ Corsair Flash Voyager GT 32GB USB 3.0 PS? It seems to be working for now, dunno why, my syslog got 129mb so can't upload it. Point being that after it crashes is when you'd upload the syslog.txt (as it will be up to and including the crash). Guess I should've mentioned that you'd probably have to zip the syslog.txt when that happens
June 12, 201610 yr Author Any tips for what to do as I don't know when the server crashes and the log files reaches max after 40-50mins? Edit: It's only increasing with a few kbytes every 10minutes, so when the file is 129megs - have my server crashed and captured the reason for crashing?
June 12, 201610 yr Not sure why, but your log is filling up so quickly with just repeats of this section: Jun 12 20:58:36 SkyNAS kernel: Call Trace: Jun 12 20:58:36 SkyNAS kernel: [<ffffffff815f2403>] dump_stack+0x65/0x85 Jun 12 20:58:36 SkyNAS kernel: [<ffffffff815ee38a>] __schedule_bug+0x46/0x54 Jun 12 20:58:36 SkyNAS kernel: [<ffffffff815f462c>] __schedule+0x66/0x6d6 Jun 12 20:58:36 SkyNAS kernel: [<ffffffff815f4d0c>] schedule+0x70/0x7f Jun 12 20:58:36 SkyNAS kernel: [<ffffffff815f4f5b>] schedule_preempt_disabled+0x10/0x19 Jun 12 20:58:36 SkyNAS kernel: [<ffffffff810729a4>] cpu_startup_entry+0x2aa/0x2b2 Jun 12 20:58:36 SkyNAS kernel: [<ffffffff810324e4>] start_secondary+0x10e/0x12c Jun 12 20:58:36 SkyNAS kernel: BUG: scheduling while atomic: swapper/1/0/0x00000002 Jun 12 20:58:36 SkyNAS kernel: Modules linked in: kvm_amd kvm xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables iptable_filter ip_tables tun md_mod fam15h_power r8169 mii i2c_piix4 k10temp ahci libahci acpi_cpufreq [last unloaded: kvm] Jun 12 20:58:36 SkyNAS kernel: CPU: 1 PID: 0 Comm: swapper/1 Tainted: G W 4.1.18-unRAID #1 Jun 12 20:58:36 SkyNAS kernel: Hardware name: System manufacturer System Product Name/A88X-PLUS, BIOS 1102 12/30/2013 Jun 12 20:58:36 SkyNAS kernel: 0000000000000001 ffff88011a323e48 ffffffff815f2403 ffffffff8182e140 Jun 12 20:58:36 SkyNAS kernel: Hardware name: System manufacturer System Product Name/A88X-PLUS, BIOS 1102 12/30/2013 Jun 12 20:58:36 SkyNAS kernel: 0000000000000001 ffff88011a323e48 ffffffff815f2403 ffffffff8182e140 Jun 12 20:58:36 SkyNAS kernel: 0000000000000296 0000000000000001 ffff88011ec95ec0 ffff88011a323e58 Jun 12 20:58:36 SkyNAS kernel: ffffffff815ee38a ffff88011a323ea8 ffffffff815f462c ffff88011a323e98 The amount of entries for this all with the same timestamp in the section you last posted easily explain why your log file is so big and I suspect it has something to do with why your server is crashing.
June 12, 201610 yr Author Been running syslog for 1hour 20mins now And the file is just 30kb's. Do you find any similarities in this one? Do I need to do something in BIOS when changing CPU? syslog.txt
June 12, 201610 yr Been running syslog for 1hour 20mins now And the file is just 30kb's. Do you find any similarities in this one? Do I need to do something in BIOS when changing CPU? First I'd recommend installing the powerdown plugin as it's an absolute must in my book for any Unraid box. Also to eliminate confusion, if it were me I'd remove any other plugins for the time being and see if you can get a stable Unraid server, before adding in Plex etc. Phaze's Plex plugin I don't personally use, although many do successfully, however any plugin just confounds the issue at the moment. I'd stick with just powerdown at the moment. EDIT: Also powerdown can save logs on shutdown so when your server goes down if you can telnet/SSH to it, you may get some valuable info from that.
June 13, 201610 yr Been running syslog for 1hour 20mins now And the file is just 30kb's. Do you find any similarities in this one? Do I need to do something in BIOS when changing CPU? First I'd recommend installing the powerdown plugin as it's an absolute must in my book for any Unraid box. Also to eliminate confusion, if it were me I'd remove any other plugins for the time being and see if you can get a stable Unraid server, before adding in Plex etc. Phaze's Plex plugin I don't personally use, although many do successfully, however any plugin just confounds the issue at the moment. I'd stick with just powerdown at the moment. EDIT: Also powerdown can save logs on shutdown so when your server goes down if you can telnet/SSH to it, you may get some valuable info from that. But not in the event of a crash where you can't ssh into it. Hence why FCP should be running in troubleshooting mode if that's what happens, as it also logs a lot more info about memory usage, running processes, etc every 10 minutes
June 13, 201610 yr But not in the event of a crash where you can't ssh into it. Hence why FCP should be running in troubleshooting mode if that's what happens, as it also logs a lot more info about memory usage, running processes, etc every 10 minutes Considering you're what I consider a good friend, I really should pay more attention to what your plugin is capable of....
June 13, 201610 yr Considering you're what I consider a good friend, I really should pay more attention to what your plugin is capable of.... Toss it in troubleshooting mode for a half hour and look at the logs. I *think* (could be mistaken) that what it logs really helps with diagnosing lock ups, unresponsive, etc as some of the info isn't really available in normal diagnostics, and since it does certain limited tests every 10 minutes it helps to establish a trend of what's going on leading up to a crash.
June 13, 201610 yr Author The problem is that the server was working fine (Plex included) before I changed my CPU. Do you still think I should uninstall plex? Here's syslog and diagnostic that ended 02:18 my time skynas-diagnostics-20160613-0218.zip syslog.txt
June 13, 201610 yr Been running syslog for 1hour 20mins now And the file is just 30kb's. Do you find any similarities in this one? Do I need to do something in BIOS when changing CPU? First I'd recommend installing the powerdown plugin as it's an absolute must in my book for any Unraid box. Also to eliminate confusion, if it were me I'd remove any other plugins for the time being and see if you can get a stable Unraid server, before adding in Plex etc. Phaze's Plex plugin I don't personally use, although many do successfully, however any plugin just confounds the issue at the moment. I'd stick with just powerdown at the moment. EDIT: Also powerdown can save logs on shutdown so when your server goes down if you can telnet/SSH to it, you may get some valuable info from that. But not in the event of a crash where you can't ssh into it. Hence why FCP should be running in troubleshooting mode if that's what happens, as it also logs a lot more info about memory usage, running processes, etc every 10 minutes You know that's the first time you've mentioned changing your CPU right.... Have you had a look in your BIOS and checked your temps? The problem is that the server was working fine (Plex included) before I changed my CPU. Do you still think I should uninstall plex? Here's syslog and diagnostic that ended 02:18 my time
June 13, 201610 yr Been running syslog for 1hour 20mins now And the file is just 30kb's. Do you find any similarities in this one? Do I need to do something in BIOS when changing CPU? First I'd recommend installing the powerdown plugin as it's an absolute must in my book for any Unraid box. Also to eliminate confusion, if it were me I'd remove any other plugins for the time being and see if you can get a stable Unraid server, before adding in Plex etc. Phaze's Plex plugin I don't personally use, although many do successfully, however any plugin just confounds the issue at the moment. I'd stick with just powerdown at the moment. EDIT: Also powerdown can save logs on shutdown so when your server goes down if you can telnet/SSH to it, you may get some valuable info from that. But not in the event of a crash where you can't ssh into it. Hence why FCP should be running in troubleshooting mode if that's what happens, as it also logs a lot more info about memory usage, running processes, etc every 10 minutes You know that's the first time you've mentioned changing your CPU right.... Have you had a look in your BIOS and checked your temps? The problem is that the server was working fine (Plex included) before I changed my CPU. Do you still think I should uninstall plex? Here's syslog and diagnostic that ended 02:18 my time And that makes sense. With a quick scan of the syslog with my first coffee, it looks like everything was fine up until the point that Plex started doing its thing (Final entry shows that it was running @101% of the CPU (previous entry showed ~60%, and the prior ones were all 1%)
June 13, 201610 yr Author @CHBMB - I realize I didn't mention it at first, sorry about that.Ofc its relevant, but thats me thinking you know The temprature seemed to be ok, but it was dropping before I reached BIOS. @Squid - I checked and it was on ASUS Optimal, is that the reason it goes above 100%? My previous CPU (AMD A4-6320) almost used 100% when someone was watching Plex, now my (AMD A10-7890K Black Edition, Socket-FM2+) don't use as much when someone is watching plex on my server. So I don't know why it went 101% as I've disabled remote access for the time being. Can you think of any reason? Is it bcus it was ASUS Optimal? I've restarted with Normal Settings, and hope it doesn't overload.
June 13, 201610 yr @CHBMB - I realize I didn't mention it at first, sorry about that.Ofc its relevant, but thats me thinking you know @Squid - I checked and it was on ASUS Optimal, is that the reason it goes above 100%? My previous CPU (AMD A4-6320) almost used 100% when someone was watching Plex, now my (AMD A10-7890K Black Edition, Socket-FM2+) don't use as much when someone is watching plex on my server. So I don't know why it went 101% as I've disabled remote access for the time being. Can you think of any reason? Is it bcus it was ASUS Optimal? I've restarted with Normal Settings, and hope it doesn't overload. Don't know about the 101% (doesn't make alot of sense to me, but I'd have to investigate) But the kernel panic happening while Plex is running full bore implies CPU overheating. (I know that my A8-6600K's stock cooler was pathetic when used in a "normal" case and just not up to doing the job of cooling the system down)
June 13, 201610 yr Author The temprature seemed to be ok, but it was dropping before I reached BIOS. FM2 coolers support FM2+? Would it be enough to get a new cooler? Or is something else entirely wrong as it reaches 101%? I used the stock cooler for my amd 10-6980k cpu Also trying to see if it is enough to turn to normal mode, will post update
June 13, 201610 yr The temprature seemed to be ok, but it was dropping before I reached BIOS. FM2 coolers support FM2+? Would it be enough to get a new cooler? Or is something else entirely wrong as it reaches 101%? Maybe install Dynamix System temp, then start a Plex transcode or two and watch the temperatures on the bottom of the webUI
June 13, 201610 yr Author Installed system temp, but guess I'm missing perl, did a search for it on the forum - but only found plenty of posts with "properly" Nothing happens when i press "Detect" Only asking here because ur online
June 13, 201610 yr Installed system temp, but guess I'm missing perl, did a search for it on the forum - but only found plenty of posts with "properly" Nothing happens when i press "Detect" Only asking here because ur online Only online for another minute. Install Nerd Pack plugin, go to its settings and install Perl
June 13, 201610 yr Author Installed perl5 and "Detect" drivers for System temp refreshes but doesn't find anything. On my screen grep: /etc/sensors.d/sensors.conf: No such file or directory
June 13, 201610 yr Installed perl5 and "Detect" drivers for System temp refreshes but doesn't find anything. On my screen grep: /etc/sensors.d/sensors.conf: No such file or directory You might need to grab the sensors-detect script Look in the dynamix plugins thread, or try here: http://lime-technology.com/forum/index.php?topic=36543.msg430371#msg430371 (Although the link that the post links to is out of date, as the way-back machine no longer has that one, but IIRC there are others if you look through way-back machine.)
June 13, 201610 yr Author Installed perl5 and "Detect" drivers for System temp refreshes but doesn't find anything. On my screen grep: /etc/sensors.d/sensors.conf: No such file or directory You might need to grab the sensors-detect script Look in the dynamix plugins thread, or try here: http://lime-technology.com/forum/index.php?topic=36543.msg430371#msg430371 (Although the link that the post links to is out of date, as the way-back machine no longer has that one, but IIRC there are others if you look through way-back machine.) I've been running the server for 3-4hrs now, without the problems, so it was probably the heat\because of ASUS Optimal, I really should have figured that out by myself - so thanks for bearing with me. How do I install https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect I tried adding .plg to the end, but plugin: installing: https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect.plg plugin: downloading https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect.plg plugin: downloading: https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect.plg ... failed (Invalid URL / Server error response) plugin: wget: https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect.plg download failure (Invalid URL / Server error response) and without .plg plugin: installing: https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect plugin: downloading https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect plugin: downloading: https://web.archive.org/web/20150513093034/http://dl.lm-sensors.org/lm-sensors/files/sensors-detect ... done Warning: simplexml_load_file(): /tmp/plugins/sensors-detect:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 213 Warning: simplexml_load_file(): #!/usr/bin/perl -w in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 213 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 213 plugin: xml parse error
Archived
This topic is now archived and is closed to further replies.