pengrus

Members
  • Posts

    149
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed
  • Personal Text
    i3-560
    SuperMicro X8SIL-F
    SuperMicro AOC-SASLP-MV8
    Corsair RM750
    v6.3.5
    60TB

Recent Profile Visitors

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

pengrus's Achievements

Apprentice

Apprentice (3/14)

1

Reputation

  1. Sorry, just scrolling through and found this, is it still available? If not, could you tell me what RAM you're using in there? I'm having trouble finding DIMMs that are compatible with that board. Thanks! -P
  2. An update! This is actually pretty interesting (and also frustrating), and I'm surprised no one else has had this issue, but I think I've found the cause. I run a pihole Docker on .40, and used to run (now decommissioned to reduce complexity) a SteamCacheBundle Docker on .44. Based on the rather unscientific procedure of having a terminal window tailing syslog while Wireshark runs, it seems pretty solid that ARP requests from the server to its Dockers is the cause of the entries, because the Dockers don't respond. "Who has x.x.x.40? Tell x.x.x.unraidIP." This repeats every second or so for about 7 minutes, takes a 5 minute break, then starts again. Glad I increased the log partition size... But why is it asking? I think it's because, since the server has a static IP, the network settings list the pihole and steamcache as its primary and secondary DNS entries. This would also explain why it continues happening even when Docker and VMs are shut down, or the array is stopped. On to a solution! I can probably scrounge up an actual Raspberry Pi, throw pihole on it, shut down the Dockers and call it worked around. But I feel like there's a bug here somewhere, either in unRAID's network settings, the Dockers, or something I introduced. There are other Dockers using br0, namely a Nextcloud instance and its MariaDB, as well as the unifi-controller, but those aren't seeing traffic from the server itself, at least in my testing. Any suggestions would be appreciated! -P
  3. Ok, so near as I can figure from a Wireshark run, this appears to be ARP requests from the server's IP to Docker containers and VMs it's already hosting. Can anyone give me an idea how to fix this? Also, I can no longer access the plugins page at all, it just does that wave thing until it gets tired and stops.
  4. So my logs started filling up with these messages a few weeks ago. At first, it didn't seem to be causing any problems, but then my DHCP server (hosted off unRAID) started borking all the wifi clients, and BIND9 (also hosted off unRAID) started having issues. This was followed by the wired clients getting borked as well, so now almost everything is statically assigned and at least relatively stable. Think I've got that if not fixed, then worked around, but these messages remain, and are reminiscent of an ARP storm, aren't they? The messages persist even when the array is stopped, with no Dockers or VMs running. I did update to 6.9.2 yesterday, no change. System is dual E-5 2690s on an X9DR3-F. Board has two NICs, but I'm only using one on a static IP, so I don't think it's an STP issue. I am experiencing a great deal of lag and slowness both from wired and wifi media clients, as well as a remarkable delay in accessing pages like the plugins for the webUI. The Dashboard is fine though. Diagnostics attached, thanks in advance! -P tower-diagnostics-20210418-1441.zip
  5. Thank you all for your responses, I really appreciate it. Not trying to resurrect a dead thread here, but what would cause 7 parity errors to be found on every subsequent parity check? Ever since this happened, every monthly check has returned 7 errors. I am set to correct parity errors during a check, btw, and have been up for 65 days, the reboot was intentional and orderly. Diagnostics attached, thanks! -P tower-diagnostics-20201102-1843.zip
  6. Thanks @itimpi. Perhaps I was mistaken, I thought there was some way with P+Q parity to be able to find out where the corruption (or not) was. Is this not the case? -P
  7. So I searched the wiki and the forum but can't seem to find a straight answer to this. How do I locate an error in parity found during a parity check? I have dual parity, and my last check unexpectedly showed 7 errors. I have what seem to be sectors identified in the log, but isn't that on the parity drives? Thanks! -P tower-diagnostics-20200804-1548.zip
  8. Got it. Yes, there absolutely could be an issue with the container's network access, but I've pinholed the TCP and UDP for 7777, 7778, and 27015 both ways, it should be fine, and other bridged dockers are fine. Yes, Ark requires a username, had to set up a separate account for that with SteamGuard disabled. Ok, so I removed both dockers, as well as their folders from my appdata and redownloaded Ark-SE. Here is the error I'm getting now, did my best to snippet: ---Prepare Server--- ---Server ready--- ---Start Server--- /opt/scripts/start-server.sh: line 61: cd: /serverdata/serverfiles/ShooterGame/Binaries/Linux: No such file or directory /opt/scripts/start-server.sh: line 62: ./ShooterGameServer: No such file or directory ---Setting umask to 000--- ---Update SteamCMD--- WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work. Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Logging in user 'thepengrusservers' to Steam Public ... WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work. Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Logging in user '****' to Steam Public ... Logged in OK Waiting for user info...OK ---Update Server--- WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work. Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Logging in user '****' to Steam Public ... Logged in OK Waiting for user info...OK ERROR! Failed to install app '376030' (No subscription) ---Prepare Server--- ---Server ready--- ---Start Server--- /opt/scripts/start-server.sh: line 61: cd: /serverdata/serverfiles/ShooterGame/Binaries/Linux: No such file or directory /opt/scripts/start-server.sh: line 62: ./ShooterGameServer: No such file or directory It definitely looks like the container can't get out to the network, and/or Ark isn't getting installed for some reason? Thanks! --P
  9. Hi! I'm having the "unable to query server for invite" problem again. I think it may have started when I tried to install your CS:GO docker and didn't realize the ports were the same, but I can't be sure. I also tried editing the steamcmd folder for Ark to a new one, but that hasn't worked. The server shows up in steam if I favorite it, but no other way, and it says the version is 298.41, while my clients are all on 301. There appear to be update-related errors in the logs: ---Setting umask to 000--- SteamCMD not found! steamcmd.sh linux32/steamcmd linux32/steamerrorreporter linux32/libstdc++.so.6 linux32/crashhandler.so ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' ILocalize::AddFile() failed to load file "public/steambootstrapper_english.txt". [ 0%] Checking for available update... [----] Downloading update (0 of 50328 KB)... [ 0%] Downloading update (810 of 50328 KB)... ~~~~ [ 99%] Downloading update (50328 of 50328 KB)... [100%] Download Complete. [----] Applying update... [----] Extracting package... [----] Extracting package... [----] Extracting package... [----] Extracting package... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Cleaning up... [----] Update complete, launching... WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work. Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... [ 0%] Downloading update... [ 0%] Checking for available updates... [----] Download complete. [----] Extracting package... [----] Extracting package... [----] Extracting package... [----] Extracting package... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Installing update... [----] Cleaning up... [----] Update complete, launching Steamcmd... WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work. Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Logging in user '****' to Steam Public ... Logged in OK Waiting for user info...OK ---Update Server--- ---Validating installation--- WARNING: setlocale('en_US.UTF-8') failed, using locale: 'C'. International characters may not work. Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation -- type 'quit' to exit -- Loading Steam API...OK. Logging in user '****' to Steam Public ... Logged in OK Waiting for user info...OK Update state (0x0) : Timed out waiting for update to start, bailing. Error! App '376030' state is 0x204 after update job. ---Prepare Server--- ---Server ready--- ---Start Server--- [S_API FAIL] SteamAPI_Init() failed; SteamAPI_IsSteamRunning() failed. Setting breakpad minidump AppID = 346110 Any ideas? Thanks for all the help, and the great dockers! --P
  10. Hi, I have 6.7.2 running multiple dockers and VMs which have various browser-based services running behind a reverse proxy hosted in one of those VMs. This proxy is actually kind of two-way, it handles external requests, but also internal requests on my local domain. Problem is, I cannot access several service features, including the sockets unraid uses for logs, docker updates, the terminal, etc, unless I access those domains locally. Example: sonarr.example.com proxied to 192.168.1.xxx, works fine. tower.example.com proxied to 192.168.1.yyy works, but not any of the sockets/windows 192.168.1.yyy works fine. tinymediamanager.example.com proxied to 192.168.1.zzz doesn't work at all (in case you're unfamiliar, it's written entirely in Java, displayed through what I think is similar to noVNC/etc on ip:5800) Behavior is the same whether they are publicly accessible or not. It seems as if whatever those pages are trying to pass just isn't making it through the journey from public IP to https server to proxied asset (and back). Any ideas? Thanks! -P
  11. Nailed it, my friend. I'd actually made my own container a few months ago and could never get it to work for the same reason. Forwarded the ports this afternoon, and we're good to go. Thanks very much for the assistance! I would like to mention though, to no one in particular, that this practice of requiring WAN access is just not very nice. I paid the $60 or whatever, I should be able to play this on my own LAN without giving whoever any information about how/when/etc I play. Not to mention the security implications... </rant>
  12. Ha! Hilariously, I just pulled out A0 and everything seems to be fine, no more memory errors and a parity check is moving at the appropriate pace. I do have a question though, as I said, I pulled A0, but the server now registers that I am down 8GB, instead of 4GB. In other words, I have 60GB of RAM installed, but unRAID only sees 56GB, is this by design? Something about dual channel maybe?
  13. Well, I'm trying to play on my LAN. Internal to my network. The Ark server sits on my unRAID, and I have a Windows and a Linux client to play on that instance. So I'm not sure unofficial servers is right for me, I'm just trying to play internal to my 192.168.1.x. I keep looking for it in the "LAN" section of the Ark browser and it can't find it. When I set the IP address as a favorite, it gives me the unable to query server for invite thing. Again, I didn't open any ports because I am not trying to play from the WAN, just internal to my house. Will this function in a LAN scenario or do I need to make it public-facing?
  14. Mostly no. I can specify the server IP in steam's server dialog and it appears. When I try to play, it says it's "unable to query the server for invite". I cannot find the server through Steam's browser or the browser within Ark. I'm using your template basically unchanged, 7777 and 7778, as well as 27015 are specified. Any other things I should check?
  15. It does, but there isn't. Apparently whatever is happening isn't triggering that logging mechanism. Guess I'm down to trial and error?