Counter Strike Source server won't start

[lucky7]

I recently acquired a centOS server with cPanel / WHM for a few webpages I run, and I thought I'd take advantage of some of my spare server power by running a gameserver.

I setup cPGS, and I was able to install the counter strike server (the older 1.6 version) without any problems.

I then installed the newer Counter Strike Source, the installation seemed to go normally but I can't start the server. When I click "start" on the cPanel interface I get,

"ERROR: Server already started within last 10 seconds, please wait
at least 2 seconds before starting again.

Some servers can take several minutes to fully start."

I've been waiting and restarting it for hours but it never turns on.

If anyone has any advice on this I'd appreciate it.

Thanks!

[darren]

What does it say in the log (there's a link below the start button in cPGS to see it) say about it, anything ? If you ssh into the machine as the user can you start the server then ? If none of that sheds any light on the issue, put in a ticket so I can take a look.

[lucky7]

Hi Darren,

Thanks, the log file reported an error and I worked with my host to fix it. Its working fine now, thanks again.

I have another question, how would I go about getting my server listed on the steam server browser?

I can add my server IP on my favorites (69.175.59.12 if you want to look) and the server itself seems to be up and running well, 12 hours of uptime at the moment, like ~60 latency.

But I guess there must be some trick or requirement to have my server show up in the internet-search for css servers on steam?

[darren]

By default the server should be showing up in the in-game list.
I see it listed in game-monitor's search:
Servers playing All Games | Server / Player Search | Game-Monitor.com :: Server Search, Monitoring, Stats and more but didn't see it in the regular game browser. Check the logs again for any errors related to connections to steam/valve/vac, if the server it is on has a firewall that only allows the 27015 or whatever game port, it might still be blocking the master-server notification attempts. Again, let me know if you would like me to take a look if you don't see anything obvious.