[hlds_linux] New server pid on crash

2010-12-31 Thread Michael K. Gosvig
 

We have some problems with our server. Whenever a source server crashes
throughbreakpad, the server then starts with a new pid, but it does not
close the old one, so then the server takes over the other server's ports,
as its own is occupied by the server's old pid.

Anyone know a solution to this problem

 

Regards

Michael

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


[hlds_linux] Bind -port permanent ?

2010-09-05 Thread Michael K. Gosvig
Since the Source Server was moved to the OB engine, they have been able to
take a new port, if their own was taken. On the old engine, the server
simply would not start, if it couldn't get the port written in the start
line.

 

I seek the same solution on the new OB engine, We have tried with the
"-hostport X, and the "-port X".  None of them binds the port
permanent, the server is still able to take a random port if it can't get
it's own.

 

So basically the question is, is there a command to bind the server port
permanent on the OB engine ?

 

Michael

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


[hlds_linux] Bind Client port- Linux

2010-07-12 Thread Michael K. Gosvig
Hi all.

 

Can any of you guys tell me if there is a way to bind the Client port on
Linux Source servers. We have been trying "-clintport X",

But the server still seems to take a random port each time. 

 

Michael

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


Re: [hlds_linux] Rcon Problem after update

2010-07-07 Thread Michael K. Gosvig
It's the Server port we change the range on. The client port still bindes
from 27005 and up.
Can the Client port be the reason or does RCON use the server port ?

Michael

-Oprindelig meddelelse-
Fra: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Blob
Sendt: 6. juli 2010 12:46
Til: h...@oneskylitnight.org; Half-Life dedicated Linux server mailing list
Emne: Re: [hlds_linux] Rcon Problem after update

If I have recently enabled DMZ on my router and set it to forward all
traffic to my clearOS box. This give me a lot more power for traffic
management.

http://www.clearfoundation.com/Software/overview.html

There is also an advanced Firewall plug-in for it.

-Original Message-
From: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Jake
Eisenman
Sent: 06 July 2010 02:13
To: Half-Life dedicated Linux server mailing list
Subject: Re: [hlds_linux] Rcon Problem after update

I disagree, what routers are these?

On 7/5/2010 7:37 PM, Shane Arnold wrote:
> I found that with most modems and routers, if you set Protocol in your
> port forwarding to "both" it would break things. If this is the case, I
> recommend creating two seperate port forwards, one for TCP and one for
UDP.
>
> On 6/07/2010 6:27 AM, Nicholas Hastings wrote:
>
>> Rcon is TCP on Source. (UDP on GoldSrc)
>>
>> On 7/5/2010 6:07 PM, Björn "GRYZOR" Rohlén wrote:
>>
>>  
>>> RCON is udp as well, most likely a problem with your firewall.
>>>
>>> -TheG
>>>
>>> On Mon, Jul 5, 2010 at 10:28 PM, Cc2iscooL
wrote:
>>>
>>>
>>>> Not necessarily, as rcon is TCP and game is UDP, from my memory.
>>>>
>>>> On Mon, Jul 5, 2010 at 2:16 PM, Peter Lindblom
wrote:
>>>>
>>>>
>>>>  
>>>>> it shouldnt matter, if players are able to join, then rcon should
work
>>>>> if its not a problem within the code- that I cant answer.
>>>>>
>>>>> Peter
>>>>>
>>>>> - Original Message -
>>>>> From: "Michael K. Gosvig"
>>>>> To:
>>>>> Sent: Monday, July 05, 2010 12:13 PM
>>>>> Subject: [hlds_linux] Rcon Problem after update
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>> Hi.
>>>>>>
>>>>>>
>>>>>>
>>>>>> After the new Source Update was released, we change our port range on
our
>>>>>> source servers from 270XX to 300XX.
>>>>>>
>>>>>>
>>>>>>
>>>>>> After that we can't use the RCON command ingame any more, it just
says
>>>>>> Unable to connect to remote server (XX.XX.XX.XX:300XX) Can you guys
tell
>>>>>> me
>>>>>> if this is because of the port range change or an error in our
firewall
>>>>>> system, we have changed the port range in the firewall.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>>
>>>>>> ___
>>>>>> To unsubscribe, edit your list preferences, or view the list
archives,
>>>>>> please visit:
>>>>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>>>>>
>>>>>>
>>>>>>  
>>>>> ___
>>>>> To unsubscribe, edit your list preferences, or view the list archives,
>>>>> please visit:
>>>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>>>>
>>>>>
>>>>>
>>>> ___
>>>> To unsubscribe, edit your list preferences, or view the list archives,
please visit:
>>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>>>
>>>>
>>>>  
>>> ___
>>> To unsubscribe, edit your list preferences, or view the list archives,
please visit:
>>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>>>
>>>
>> ___
>> To unsubscribe, edit your list preferences, or view the list archives,
please visit:
>>

[hlds_linux] Rcon Problem after update

2010-07-05 Thread Michael K. Gosvig
Hi.

 

After the new Source Update was released, we change our port range on our
source servers from 270XX to 300XX. 

 

After that we can't use the RCON command ingame any more, it just says
Unable to connect to remote server (XX.XX.XX.XX:300XX) Can you guys tell me
if this is because of the port range change or an error in our firewall
system, we have changed the port range in the firewall.

 

Michael

 

___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


Re: [hlds_linux] New Source server takes a random port

2010-06-27 Thread Michael K. Gosvig
Can any of you show me how your Linux CSS command line looks like ?

Michael

-Oprindelig meddelelse-
Fra: hlds_linux-boun...@list.valvesoftware.com 
[mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Allan Button
Sendt: 27. juni 2010 18:57
Til: Half-Life dedicated Linux server mailing list
Cc: Half-Life dedicated Linux server mailing list
Emne: Re: [hlds_linux] New Source server takes a random port

Client Port:

http://tinyurl.com/2awheq7

Sent from my mobile.

On Jun 27, 2010, at 12:52 PM, "Saul Rennison"  
 wrote:

> What is a client port anyway?
>
> On Sunday, June 27, 2010, Cc2iscooL  wrote:
>> Uh...
>>
>> The source engine always takes two ports. One server and one client.
>>
>> Either specify client ports as ICS mentioned or put servers farther  
>> apart.
>>
>> On Sun, Jun 27, 2010 at 9:08 AM, Michael K. Gosvig > >wrote:
>>
>>> The problem is, in the start command line the server is set to a  
>>> specific
>>> port, example 27030. But in the screen it writes. " Network: IP
>>> 92.246.12.12, mode MP, dedicated Yes, ports 27030 SV / 27031 CL"
>>>
>>> The server side is set to 27030, but then the client side takes  
>>> 27031, and
>>> there the problem starts, as there is another server on 27031. And  
>>> when it
>>> trys to start it's port I taken by the previous one on the client  
>>> side.
>>>
>>> Why is it that the client side on some severs take the next port  
>>> but on
>>> others take "-1" in screen ?
>>>
>>> Michael
>>>
>>> -Oprindelig meddelelse-
>>> Fra: hlds_linux-boun...@list.valvesoftware.com
>>> [mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af M 
>>> arc.B
>>> Sendt: 27. juni 2010 14:45
>>> Til: Half-Life dedicated Linux server mailing list
>>> Emne: Re: [hlds_linux] New Source server takes a random port
>>>
>>> Michael,
>>>
>>> As far as I know, it don't pick up a random port. It try port + 1  
>>> until it
>>> find a free port.
>>> There are other games that work the same way, so I think you  
>>> should make a
>>> fix on your side since you are not supposed to start a server on a  
>>> port
>>> that
>>> is already used.
>>>
>>> Checking if that the port is available using netstat before you  
>>> launch a
>>> server is the best way, and you can also make a sleep between the  
>>> server
>>> kill and the server start.
>>>
>>> We are hosting about 5.000 and have no issue with this new port  
>>> management.
>>> We do also reboot most servers in the morning.
>>>
>>> Cheers,
>>>
>>> Marc.
>>>
>>> On Sun, Jun 27, 2010 at 2:04 PM, Eric Riemers   
>>> wrote:
>>>
>>>> You can always do a netstat -an|grep LISTEN|grep   
>>>> then "if
>>>> found, wait 10 seconds" and try again before starting.
>>>> Might not be the nicest solution , but could work for you.
>>>>
>>>> Eric
>>>>
>>>> -Original Message-
>>>> From: hlds_linux-boun...@list.valvesoftware.com
>>>> [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of  
>>>> Michael
>>> K.
>>>> Gosvig
>>>> Sent: zondag 27 juni 2010 2:50
>>>> To: 'Half-Life dedicated Linux server mailing list'
>>>> Subject: Re: [hlds_linux] New Source server takes a random port
>>>>
>>>> No luck with "-hostport" instead of "-port"
>>>>
>>>> -Oprindelig meddelelse-
>>>> Fra: hlds_linux-boun...@list.valvesoftware.com
>>>> [mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af 
>>>>  Cc2iscooL
>>>> Sendt: 27. juni 2010 02:38
>>>> Til: Half-Life dedicated Linux server mailing list
>>>> Emne: Re: [hlds_linux] New Source server takes a random port
>>>>
>>>> Yes but the ports shouldn't be in use if they're restarting.  
>>>> Maybe try
>>>> adding some delays to your reboot scripts so the daemon has a  
>>>> chance to
>>>> shut
>>>> down and a check to see if the process is closed before starting  
>>>> up a new
>>>> server.
>>>>
>>>> On Sat, Jun 26, 2010 at 7:27 PM, Michael K. Gosvig
>>>> wrote:
>>>>

Re: [hlds_linux] New Source server takes a random port

2010-06-27 Thread Michael K. Gosvig
The problem is, in the start command line the server is set to a specific
port, example 27030. But in the screen it writes. " Network: IP
92.246.12.12, mode MP, dedicated Yes, ports 27030 SV / 27031 CL"

The server side is set to 27030, but then the client side takes 27031, and
there the problem starts, as there is another server on 27031. And when it
trys to start it's port I taken by the previous one on the client side. 

Why is it that the client side on some severs take the next port but on
others take "-1" in screen ?

Michael  

-Oprindelig meddelelse-
Fra: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Marc.B
Sendt: 27. juni 2010 14:45
Til: Half-Life dedicated Linux server mailing list
Emne: Re: [hlds_linux] New Source server takes a random port

Michael,

As far as I know, it don't pick up a random port. It try port + 1 until it
find a free port.
There are other games that work the same way, so I think you should make a
fix on your side since you are not supposed to start a server on a port that
is already used.

Checking if that the port is available using netstat before you launch a
server is the best way, and you can also make a sleep between the server
kill and the server start.

We are hosting about 5.000 and have no issue with this new port management.
We do also reboot most servers in the morning.

Cheers,

Marc.

On Sun, Jun 27, 2010 at 2:04 PM, Eric Riemers  wrote:

> You can always do a netstat -an|grep LISTEN|grep  then "if
> found, wait 10 seconds" and try again before starting.
> Might not be the nicest solution , but could work for you.
>
> Eric
>
> -Original Message-
> From: hlds_linux-boun...@list.valvesoftware.com
> [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Michael K.
> Gosvig
> Sent: zondag 27 juni 2010 2:50
> To: 'Half-Life dedicated Linux server mailing list'
> Subject: Re: [hlds_linux] New Source server takes a random port
>
> No luck with "-hostport" instead of "-port"
>
> -Oprindelig meddelelse-
> Fra: hlds_linux-boun...@list.valvesoftware.com
> [mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Cc2iscooL
> Sendt: 27. juni 2010 02:38
> Til: Half-Life dedicated Linux server mailing list
> Emne: Re: [hlds_linux] New Source server takes a random port
>
> Yes but the ports shouldn't be in use if they're restarting. Maybe try
> adding some delays to your reboot scripts so the daemon has a chance to
> shut
> down and a check to see if the process is closed before starting up a new
> server.
>
> On Sat, Jun 26, 2010 at 7:27 PM, Michael K. Gosvig
> wrote:
>
> > The problem is, that we are an official Gameserver provider, so when
> > our servers restart in the morning, som servers are faster than
> > others, it depends on how many mods the customer has installed.
> >
> > That why we loved the way the old engine worked, if it could not get
> > the port, written in the command line, it would not start. But the new
> > Source Engine, just takes a random port to start on. It's seams like
> > the server sometimes ignores the "-port x" in the command line.
> >
> > Michael
> >
> > -Oprindelig meddelelse-
> > Fra: hlds_linux-boun...@list.valvesoftware.com
> > [mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Eric
> > Riemers
> > Sendt: 27. juni 2010 01:51
> > Til: 'Half-Life dedicated Linux server mailing list'
> > Emne: Re: [hlds_linux] New Source server takes a random port
> >
> >
> > If it cant get it's own, I would look at that problem first.
> >
> > If you did a restart and it changed port after that, try waiting some
> > time before starting up again, perhaps the process is keeping the port
> > in use for a little while (rare conditions, but could occur)
> >
> > Eric
> > -Original Message-
> > From: hlds_linux-boun...@list.valvesoftware.com
> > [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of
> > m...@michaelgosvig.dk
> > Sent: zondag 27 juni 2010 1:28
> > To: hlds_linux@list.valvesoftware.com
> > Subject: [hlds_linux] New Source server takes a random port
> >
> > Hi.
> >
> > After the new update to source, we have been having som problems whit
> > our servers.
> >
> > The new engine takes a random port, if i can't get it's own. Thats a
> > major problem for us, as we host a lot af serveres, an when a server
> > take a port that it should not have, the another server, can't start on
> the right one.
> >
> > In our start command line we us

Re: [hlds_linux] New Source server takes a random port

2010-06-26 Thread Michael K. Gosvig
No luck with "-hostport" instead of "-port"

-Oprindelig meddelelse-
Fra: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Cc2iscooL
Sendt: 27. juni 2010 02:38
Til: Half-Life dedicated Linux server mailing list
Emne: Re: [hlds_linux] New Source server takes a random port

Yes but the ports shouldn't be in use if they're restarting. Maybe try
adding some delays to your reboot scripts so the daemon has a chance to shut
down and a check to see if the process is closed before starting up a new
server.

On Sat, Jun 26, 2010 at 7:27 PM, Michael K. Gosvig
wrote:

> The problem is, that we are an official Gameserver provider, so when our
> servers restart in the morning, som servers are faster than others, it
> depends on how many mods the customer has installed.
>
> That why we loved the way the old engine worked, if it could not get the
> port, written in the command line, it would not start. But the new Source
> Engine, just takes a random port to start on. It's seams like the server
> sometimes ignores the "-port x" in the command line.
>
> Michael
>
> -Oprindelig meddelelse-
> Fra: hlds_linux-boun...@list.valvesoftware.com
> [mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Eric
> Riemers
> Sendt: 27. juni 2010 01:51
> Til: 'Half-Life dedicated Linux server mailing list'
> Emne: Re: [hlds_linux] New Source server takes a random port
>
>
> If it cant get it's own, I would look at that problem first.
>
> If you did a restart and it changed port after that, try waiting some time
> before starting up again, perhaps the process is keeping the port in use
> for
> a little while (rare conditions, but could occur)
>
> Eric
> -Original Message-
> From: hlds_linux-boun...@list.valvesoftware.com
> [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of
> m...@michaelgosvig.dk
> Sent: zondag 27 juni 2010 1:28
> To: hlds_linux@list.valvesoftware.com
> Subject: [hlds_linux] New Source server takes a random port
>
> Hi.
>
> After the new update to source, we have been having som problems whit our
> servers.
>
> The new engine takes a random port, if i can't get it's own. Thats a major
> problem for us, as we host a lot af serveres, an when a server take a port
> that it should not have, the another server, can't start on the right one.
>
> In our start command line we uses the "-port x" but it's still able to
> take other ports. Is there any way to lock the new source server to only
> one
> port, as the old server engine?
>
> Best Regards
> Michael
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>
>
> ___
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds_linux
>
___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


Re: [hlds_linux] New Source server takes a random port

2010-06-26 Thread Michael K. Gosvig
The problem is, that we are an official Gameserver provider, so when our
servers restart in the morning, som servers are faster than others, it
depends on how many mods the customer has installed.

That why we loved the way the old engine worked, if it could not get the
port, written in the command line, it would not start. But the new Source
Engine, just takes a random port to start on. It's seams like the server
sometimes ignores the "-port x" in the command line. 

Michael 

-Oprindelig meddelelse-
Fra: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] På vegne af Eric Riemers
Sendt: 27. juni 2010 01:51
Til: 'Half-Life dedicated Linux server mailing list'
Emne: Re: [hlds_linux] New Source server takes a random port


If it cant get it's own, I would look at that problem first.

If you did a restart and it changed port after that, try waiting some time
before starting up again, perhaps the process is keeping the port in use for
a little while (rare conditions, but could occur)

Eric
-Original Message-
From: hlds_linux-boun...@list.valvesoftware.com
[mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of
m...@michaelgosvig.dk
Sent: zondag 27 juni 2010 1:28
To: hlds_linux@list.valvesoftware.com
Subject: [hlds_linux] New Source server takes a random port

Hi.

After the new update to source, we have been having som problems whit our
servers.

The new engine takes a random port, if i can't get it's own. Thats a major
problem for us, as we host a lot af serveres, an when a server take a port
that it should not have, the another server, can't start on the right one.

In our start command line we uses the "-port x" but it's still able to
take other ports. Is there any way to lock the new source server to only one
port, as the old server engine?

Best Regards
Michael

___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


___
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux


___
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux