So to make a very long story very short...
I did a clean install of OP4, installed amx, and it worked. At this
point I had one server with metamod/amx that works, one that doesn't.
Now it's just a simple job to compare A to B to find out what is different.
Eventually I found the steamclient.so on my production server was
different from the one on my test server. No idea why. So I copied the
one from my working test server to my production server. Start
production server. And my production server magically started working.
So now all four of my production servers at back and running, amx works,
my other plugins work, and life is good again.
Where did that bad steamclient.so come from? Did Valve roll out a
botched update, and have since fixed it? That gets my vote. If not then
the client update somehow did not update steamclient.so. Or maybe I just
screwed something - like that's never happened before.
On 11/16/20 7:20 PM, Kyle Sanderson wrote:
Yeah let us know please - I'm sure my goldsrc peers are subscribed to
the list but this sounds like something we should try to address. I do
want to confirm you're not running retail MM though and you're running
MM from AM. Not saying it's the magic bullet but Alfred changed the
toolchain (GCC 2.4~ to 4.4~ or something) long ago on HL and that's
why we took the fork up beyond AMX.
Let us know my friend,
Kyle.
On Mon, Nov 16, 2020 at 6:13 PM Ook <ooksser...@zootal.com> wrote:
I'll set it up and post the error - it causes the linux server to crash
on startup. I vaguely recall the windows server does not crash, but
neither does metamod work. I have liblist.gam set correctly, but no
metamod functions work. I'll get back to you with more details...
When I initially tested this, it was with a working config that I had
not touched for years. All I did was update the hlds server binaries and
libs. After the update, none of my servers would start, they all crashed
in the exact same manner. Playing with liblist.gam did not help except
when I removed metamod - that was the only way to get the server to start.
On 11/16/20 7:09 PM, Kyle Sanderson wrote:
Metamod appears to not work with the latest update, not sure if there will be
any metamod updates for the new server binary or not.
Can you describe this in more detail? are you running metamod-am? If
you can give me STR I can try to help further.
Kyle.
On Mon, Nov 16, 2020 at 6:04 PM Ook <ooksser...@zootal.com> wrote:
It works well enough running the windows version with wine on a linux
box, I've not been highly motivated to look into it further. Metamod
appears to not work with the latest update, not sure if there will be
any metamod updates for the new server binary or not. And there is no
steam installed on the server.
I wonder if they updated the steam client in the windows version, but
not the Linux version? I'll revisit this when I have a chance, see what
I can find. Maybe find out what IP(s) it is trying to hit. I remember
many years ago I had to do something with the steam IPs in the config to
get it on the steam list, but dang that was a long time ago and I have
no idea what I did...
On 11/16/20 5:03 PM, Kyle Sanderson wrote:
Sorry I haven't looked at this list in a while (hopefully you already
found the answer!)... Windows uses the steamclient that's installed,
whereas on Linux it uses the steamclient that's shipped with the game
(Windows does too - if Steam is not installed). So if the game has an
old version of steamclient, you'll get stuck with situations like
this. The Ship for instance had the Steam Masters (Mains? in 2020)
hard coded into the binary and were eventually orphaned like this. I
know years ago Qwest was trying to take back their address space from
Valve and Aldred flipped addresses on us which broke a shit ton of
games - if there's a hard coded address against this it's possible you
were impacted when they made a trivial (to them) move.
Were you able to resolve it natively? I might not be able to help, but
CC me so it lands in my inbox and I can try to.
Best,
Kyle.
On Thu, Oct 8, 2020 at 4:43 PM Ook <ooksser...@zootal.com> wrote:
Well, as stupid as it sounds, I am able to get this to work by running
the Windows version of hlds with wine on Linux. I am stumped as to why,
with identical configs. the linux version gives the message "Could not
establish connection to Steam servers.", while the Winbloze version
running with wine works perfectly?
On 10/4/20 10:41 PM, Ook wrote:
I've been running my OP4 servers for years. Bloody years. And for the
last few days, my players are messaging me, saying the my servers are
no longer on the server list. I look at console, and when I start
server I get:
Could not establish connection to Steam servers.
I've changed nothing. This has been working for many years. My ports
are unchanged. My ISP is not blocking anything (that I know of).
I used steamcmd to get a fresh copy of hlds and op4, and it looks like
some of the core server files had updated, so I applied the update,
but it changes nothing.
Did Valve update hlds recently, or update something on their end? This
is hlds on linux if that makes any difference.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
https://list.valvesoftware.com/
