Jump to content

tayshserve

Members
  • Content count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tayshserve

  • Rank
    Member

Recent Profile Visitors

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

  1. tayshserve

    What is "rpc.statd"?

    Will post my system logs if they are necessary but this is more of a general question I'm looking to get answered to help me solve a problem with a Docker container. I've actually posted for help in the Container specific thread, but figured I would ask here as I'm looking for some more generalized information. Basically I'm trying to start the OpenVPN-as Docker and running into issues when it tries to start up it's web server. It's trying to start something up on port `984` – this generates an error as something is already running on that port. Here's what is running on that port: COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME rpc.statd 1656 rpc 5u IPv4 8965 0t0 UDP tower:984 What is `rpc.statd`? Some quick Googling points to something related to NFS but I'm not actually running NFS right now. If this isn't something that can be stopped, is it possible that the port it uses can be configured? I'm starting to think that this problem isn't related to the container itself since it seems like no one else is running into the issue that I have. For science, here's the error that the Container spits out when I try to start it up 2018-09-12 16:16:20-0700 [-] PortPool: port 984: [Errno 98] Address already in use: util/sock:199,python2.7/socket:228 (socket.error) Any information y'all can offer would be great! Again, I know this is kind of double posted but I'm looking for more information about what `rpc.statd` does rather than direct help trying to fix this container. Thanks!
  2. tayshserve

    [Support] Linuxserver.io - OpenVPN-AS

    I'm guessing the problem I referenced above is related to this line.. 2018-09-12 16:16:20-0700 [-] PortPool: port 984: [Errno 98] Address already in use: util/sock:199,python2.7/socket:228 (socket.error) When I check what's on that port I get the following... COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME rpc.statd 1656 rpc 5u IPv4 8965 0t0 UDP tower:984 I'm seeing this is related to NFS? EDIT: I feel like I should also note.. I have Bonding turned ON but I have no idea what it is or why I would need it. I think it was on by default. I'm using whatever onboard LAN my mother board has, nothing special.
  3. tayshserve

    [Support] Linuxserver.io - OpenVPN-AS

    Hey All, Having some trouble getting OpenVPN-as running on my machine. Seems like the only way I've been able to actually get it running and access the web ui is when I run it in `Bridge` mode, which from what I understand is not the correct way to get this set up. Any insight here would be greatly appreciated! Here is my log from Docker Initializing OpenVPN... Adding new user login... useradd -s /sbin/nologin "admin" Writing as configuration file... Perform sa init... Wiping any previous userdb... Creating default profile... Modifying default profile... Adding new user to userdb... Modifying new user as superuser in userdb... Getting hostname... Hostname: tayshserve Preparing web certificates... Getting web user account... Adding web group account... Adding web group... Adjusting license directory ownership... Initializing confdb... Generating init scripts... Generating PAM config... Generating init scripts auto command... Starting openvpnas... Error: Could not execute server start. [cont-init.d] 40-openvpn-init: exited 0. [cont-init.d] 50-interface: executing... MOD Default {u'admin_ui.https.ip_address': u'all'} {u'admin_ui.https.ip_address': 'bond0'} MOD Default {u'admin_ui.https.ip_address': u'all'} {u'admin_ui.https.ip_address': 'bond0'} MOD Default {u'cs.https.ip_address': u'all'} {u'cs.https.ip_address': 'bond0'} MOD Default {u'vpn.daemon.0.listen.ip_address': u'all'} {u'vpn.daemon.0.listen.ip_address': 'bond0'} MOD Default {u'vpn.daemon.0.server.ip_address': u'all'} {u'vpn.daemon.0.server.ip_address': 'bond0'} [cont-init.d] 50-interface: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. And here is the full log from the OpenVPN container itself: https://pastebin.com/V8ZAHfDZ @aptalca fixed! My bad.
  4. tayshserve

    unRAID Random Crashes (v 6.5.3)

    Sorry for the late reply here, we started our move last week so I didn't have much time for tinkering. Thanks for all the help and input @John_M and @PSYCHOPATHiO, I really appreciate it.. So I went a head and tried down clocking my memory speed to about 2400mhz and got the same result. At that point I was really frustrated – but I did some more research on motherboards and using the information John gave me about ASRock's compatibility issues with Ryzen I noticed that other manufacturers are seeing the same problems. Add on top of that the fact that I was using an open box motherboard from Microcenter and it started to be clear to me that I was "getting what I paid for". So, super frustrated, I went to Microcetner and bought myself a brand new Asus TUF b450m-Plus motherboard and swapped out the (extremely) budget Inland Professional SSD for a Samsung model. I realized that the b450 chipset boards just came out only a few weeks ago, so these guys come from Asus ready to roll with Ryzen 2000. So I put everything together – for the time being with one stick of ram, still downclocked to 2400mhz.. and presto, things seems to be working fine. I know this isn't much of a resolution, as all I did was replace my motherboard (rather blindly :D).. but I wanted to post my story here so others going Ryzen can follow suit. Just spend the extra money (honestly they're like $10-15 more) and get a b450 board. Much better compatibility with Ryzen, and plays nicer with memory. Also, if you're going to save some money and buy open box retail parts.. maybe spend real money on the motherboard. Since most of us are looking to run 24/7 and expect some reliability there's no reason to cheap out on the motherboard. I started to realize that retailers (or ebayers) aren't going to stress test their item for hours on end. Anyway.. TLDR: If you're going with a Ryzen processor, go with a motherboard that has supported it from it's initial release. You'll have a much better experience in my opinion.
  5. tayshserve

    unRAID Random Crashes (v 6.5.3)

    Just another quick update @PSYCHOPATHiO – I went through the memory QVL and I actually can only find my memory listed as supported for pre Raven Ridge CPUs. When I look to the 450 motherboards they all show support. Motherboard upgrade is looking promising.
  6. tayshserve

    unRAID Random Crashes (v 6.5.3)

    Thanks for that @PSYCHOPATHiO, when I get myself set back up maybe I'll try that tonight. You reminded me I should go check motherboard memory compatibility before heading to Microcenter. Were you ever able to get things stabilized?
  7. tayshserve

    unRAID Random Crashes (v 6.5.3)

    Alright so I tried adding pci=noaer To my syslinux.cfg file, as well as nomsi and pcie_aspm=off. None of which helped to solve my problems.. I also ended up seeing another error that read "SATA link down". I have also removed the SSD (which was a cheapo thing) from my setup, and now I'm going to actually return my motherboard for a new one since my current one was open box. I just want to eliminate all the possibilities here. Also when I put everything back together tonight I'll be using some fresh SATA cables. Really hoping this isn't pointing to an HDD problem. I'm hoping that switching from a b350 to a b450 board helps shore up any remaining issues I may have related to Ryzen.
  8. tayshserve

    unRAID Random Crashes (v 6.5.3)

    Thanks for the reply @John_M! Hmm alright tomorrow I’ll try a different sata cable along with the setting you passed and updating the BIOS. Could just be the crappy SSD I bought.
  9. tayshserve

    unRAID Random Crashes (v 6.5.3)

    So I wasn't too worried about the data on these drives as this is a brand new server so I formatted both the cache drive and my main drive to XFS... still seeing i/o errors.
  10. Seeing random crashes becoming more and more constant. When I first booted up I got about 2 days uptime before the first crash, the most recent one happened after only 11 minutes. Hardware listed below: Motherboard: ASRock ab350m Pro4 (BIOS v4.70 – there is one newer version) CPU: AMD Ryzen 3 2200g Memory: ADATA 8gb ddr4-3000 xpg z1 x 2 Storage: 240GB SSD, 4TB HDD Attaching the FCP log, as well as the diagnostics. Also grabbed this photo of the unRAID console when the crash happened. Sometimes the console is non-responsive. Also I have C-States disabled and the line of code (which of course now I can't find) that lime-tech recommended Ryzen users add. edit: Guess I should ask an actual question.. should I start by updating bios? Are there any other steps I can take here? I'm not finding anything specific about the errors I see in the console. New here so let me know if any info is missing tayshserve-diagnostics-20180805-1852.zip FCPsyslog_tail.txt