January 29, 20188 yr Hi all, I'm hoping some of you smart people can help me out here, as my unRAID server seems to just lock up at random times. I'll provide all the information I can think of, but please let me know if you need anything else from me. unRAID version: 6.4 stable CPU: Dual Intel Xeon E5 2630L V3 Motherboard: Asus Intel C612 PCH Socket LGA2011-v3 (Z10PE-D8 WS) RAM: 4 X Kingston 16GB 2133MHz DDR4 ECC Reg CL15 NIC: Intel I350-T4 PCI-Express HBA: 2 X IBM ServeRaid M1015 46M0861 (flashed to IT mode) HDDs: 4 X Seagate IronWolf Pro 10TB NAS Hard Drive (ST10000NE0004) + 8 X Seagate Enterprise Capacity 3.5 10TB Desktop Hard Drive (ST10000NM0016) Cache: 2 X Crucial MX300 1TB 2.5" Solid State Drive (RAID 0) This is a fairly new server, and I'm a new convert to unRAID. I've been loving the amazing ease of use, it's just made my life so much simpler. The first 2 or 3 times that it locked up, it was early morning (around 4am), but I had not properly read the forums yet, and had just restarted the server (hard reset). Since I enabled the logging, etc. it had seemed pretty stable, until about an hour or so ago, and then it just locked up again. When it locks up I can't access the web interface, SSH, or any SAMBA shares. I have attached the files that I think I'm supposed to, but please let me know if I need to provide more information. I will make a copy of the files on the flash drive, just in case. Thank you in advance for any assistance. Kind regards, Vinaduro FCPsyslog_tail.txt photon-diagnostics-20180129-1701.zip
January 29, 20188 yr Community Expert I looked over your syslogs and saw that you had a lot of login failures. It appears that you are being attacked (every 12 seconds). Is your server directly connected to the Internet or in a DMZ? What plugins, Dockers and VM's are you running?
January 30, 20188 yr Author Hi Frank, I think the login failures were due to me still having a Terminal window open (from the web GUI), but the session had expired. I definitely don't have the server in the DMZ, I do however have the following ports forwarded to the server: 80 443 1194 943 32400 I have 1 VM running Ubuntu-server, with 2 physical cores, and 2GB of RAM allocated to it. I have the following plugins installed: CA Auto Turbo Write Mode, CA Auto Update Applications, CA Backup / Restore Appdata, CA Docker Autostart Manager, Community Applications, Dynamix Cache Directories, Dynamix SSD TRIM, Dynamix System Buttons, Dynamix System Information, Dynamix System Statistics, Dynamix System Temperature, Fix Common Problems, Nerd Tools (mcelog-153-x86_64-1.txz, perl-5.24.0-x86_64-1.txz, screen-4.6.1s-x86_64-1.txz, utempter-1.1.6-x86_64-2.txz ), Tips and Tweaks, Unassigned Devices, User Scripts. I have the following dockers: Dolphin (aptalca), Hydra, Letsencrypt, Muximux, Netdata(titpetric), Nzbget, Ombi, OpenVPN-as, Plex, Plexpy, Radarr, Sonarr, Unifi All dockers are Linuxserver, except for Dolphin and Netdata. Kind regards, Vinaduro Edit: Clarified web GUI terminal window Edited January 30, 20188 yr by vinaduro
January 30, 20188 yr Community Expert 7 hours ago, vinaduro said: definitely don't have the server in the DMZ, I do however have the following ports forwarded to the server: 80 443 1194 943 32400 Why are you opening ports? Normally, routers are designed to 'open' a port from the LAN and remembers that particular IP address that was requested on the WAN/Internet and allows traffic into the LAN from only those addresses. An open port normally means that anyone has access to your server from any place in the world.
January 30, 20188 yr Author Ports 80 and 443 are required for Letsencrypt, and Nginex. Ports 1194 and 943 are for OpenVPN. Port 32400 is for Plex. It's fairly common to have services facing the internet, as long as you secure them properly. Port 22 is definitely not open to the rest of the world, so those "attacks" you were seeing, was just my browser trying to reconnect the terminal session. Kind regards, Vinaduro
January 30, 20188 yr Try booting in safe mode to start with and close all the ports to troubleshoot. Then start from there. You're dead in the water at the moment.
January 31, 20188 yr Author Thanks CHBMB, I have removed the port forwards from my router. I am busy running a parity check at the moment, so I'll wait for that to complete before restarting in safe mode.
January 31, 20188 yr Thanks CHBMB, I have removed the port forwards from my router. I am busy running a parity check at the moment, so I'll wait for that to complete before restarting in safe mode. You say you have port 80 open for letsencrypt, what port are you forwarding to? Sent from my LG-H815 using Tapatalk
January 31, 20188 yr Author 1 minute ago, CHBMB said: You say you have port 80 open for letsencrypt, what port are you forwarding to? Sent from my LG-H815 using Tapatalk Sorry, I had port 80 forwarded to port 81 for Letsencrypt. And the container forwards port 81 back to 80. Not sure if that makes sense?
January 31, 20188 yr Sorry, I had port 80 forwarded to port 81 for Letsencrypt. And the container forwards port 81 back to 80. Not sure if that makes sense? Makes perfect sense, just checking.....Sent from my LG-H815 using Tapatalk
Archived
This topic is now archived and is closed to further replies.