sup3rb0wlz
-
Posts
28 -
Joined
-
Last visited
sup3rb0wlz's Achievements
Noob (1/14)
1
Reputation
-
Changed Status to Solved
-
Perfect! Solved by removing devpack plugin!
-
After manually copying over the bz I still get the 502 If I copy /boot/previous back to /boot and reboot everything works great. Here's the log after restoring to previous too
-
sounds good. I'll report back. Thanks!
-
I upgraded from the web gui, update OS in tools i believe and selected "Next"
-
root@tower:~# diagnostics /usr/bin/php: error while loading shared libraries: libicui18n.so.56: cannot open shared object file: No such file or directory See the dilema? haha.
-
That failed with this error /etc/rc.d/rc.php-fpm start Starting php-fpm /usr/sbin/php-fpm: error while loading shared libraries: libicui18n.so.56: cannot open shared object file: No such file or directory failed (Side note: is there a guide anywhere on forum formatting?)
-
I've been going through trying to diagnose some crashes with my unraid server. See the below link. But after updating to 6.5.1 I get a 502 bad gateway response from nginx after successfully loging in with BASIC auth. Below is a line from the nginx log and an last of /var/run. It looks to me like php5.sock is missing. Any idea why? Apr 3 00:16:01 tower nginx: 2018/04/03 00:16:01 [crit] 15952#15952: *793 connect() to unix:/var/run/php5-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.200, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.250", referrer: "http://192.168.1.250/Main" root@tower:/var/log# ls /var/run acpid.pid docker.sock= nginx.origin ntpd.pid rsyslogd.pid syslogd.pid acpid.socket= dockerd.pid nginx.pid rpc.statd.pid samba/ ttyd.sock= atd.pid emhttpd.socket= nginx.socket= rpcbind/ sm-notify.pid utmp dbus/ inetd.pid nmbd.pid rpcbind.lock smbd.pid winbindd.pid docker/ libvirt/ nscd/ rpcbind.sock= sshd.pid
-
yea 1 module. DDR4 is expensive. And I want to have room to upgrade This is the closest model. C16D instead of C16C and 16GVKB instead of 16CVK G.SKILL 8GB 2Rx8 F4-3200C16D-16GVKB DS 16-18-18-38 1.35v v v v 2133 G I swear I checked the support list or the ram before I bought it.
-
My ram is posted in the first post. Currently running at 2993 instead of the advertised 3200. I tried updating to the latest in the next branch heres one of the many errors from nginx along with a ls of var/run. Everything else seems to be working correctly. Apr 3 00:16:01 tower nginx: 2018/04/03 00:16:01 [crit] 15952#15952: *793 connect() to unix:/var/run/php5-fpm.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.1.200, server: , request: "POST /plugins/unassigned.devices/UnassignedDevices.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "192.168.1.250", referrer: "http://192.168.1.250/Main" root@tower:/var/log# ls /var/run acpid.pid docker.sock= nginx.origin ntpd.pid rsyslogd.pid syslogd.pid acpid.socket= dockerd.pid nginx.pid rpc.statd.pid samba/ ttyd.sock= atd.pid emhttpd.socket= nginx.socket= rpcbind/ sm-notify.pid utmp dbus/ inetd.pid nmbd.pid rpcbind.lock smbd.pid winbindd.pid docker/ libvirt/ nscd/ rpcbind.sock= sshd.pid
-
I'll add the rcu_nocbs. I am not overclocking my CPU anymore. My memory XMP profile is set, I'll try disabling that, even though it ran memtest for like 2 days strong.
-
Running in safe mode worked great for about 2 weeks. During that time i one-by-one added plugins, until I was back to about what I run with normally. Then after a few days it crashed again. Then I ran in safe mode again with no plugins but fix common problems for it's troubleshooting mode and got another crash. Here are the logs for it. Any Ideas? I don't see anything in the logs to indicate any issues. I don't think any applications are writing to ram, and the server wasn't under much load. I'm stumped, and I'm thinking it might just be a random crash due to hardware. Even though it doesn't completely shut off. starkillerbase-diagnostics-20180401-2139.zip
-
Yea I know that the difference between container and host path threw me off at first with docker. I re-created my docker image file (with 30GB to debug) and re-created all of my containers. All of the paths look right, but I still need to check the application paths. I think Resilio may be logging to inside the docker image. Hopefully I don't see another crash in the next couple days. If I do I think something else is the culprit
-
So what I'm getting is that this is all caused by mis-configured docker volumes or applications writing to a bad path in the container. I'll need to investigate some more though. I just didn't think that that would lock up the web gui. But if it's writing to ram it could be starving the system causing the web gui process to crash It also seems weird that that would be so random.
-
I'm doing a lot more than "basic NAS" stuff tho. I see a huge benefit in game in my VMs from the extra clock speed. I can play with stock settings. But I haven't seen a difference in my limited testing.