Page 1 of 1

CentOS; No Console & "address is in use"

Posted: Fri May 01, 2009 9:36 pm
by reddozen
If you want to receive support we need this info to help you properly.
ยป 2941
L2J Revision Number: 2941
L2JDP Revision Number: 5986

We've looked for a solution and reinstalled it a couple times. Things seem to be fine on windows, but as the subject states, there's no console that comes up when you launch it in Linux, and in the error logs it's saying that "address is in use" but noting is running on the defined ports.

Anyone have any ideas or suggestions?

Re: CentOS; No Console & "address is in use"

Posted: Fri May 01, 2009 10:39 pm
by kotk
Here is your console:
cd log
tail -f stdout.log

Need more info to help you.

Re: CentOS; No Console & "address is in use"

Posted: Sat May 02, 2009 12:52 am
by reddozen

Code: Select all

May 1, 2009 4:01:35 PM net.sf.l2j.loginserver.LoginController <init>INFO: Loading LoginContoller...May 1, 2009 4:01:36 PM net.sf.l2j.loginserver.LoginController <init>INFO: Cached 10 KeyPairs for RSA communicationMay 1, 2009 4:01:36 PM net.sf.l2j.loginserver.LoginController generateBlowFishKeysINFO: Stored 20 keys for Blowfish communicationMay 1, 2009 4:01:36 PM net.sf.l2j.loginserver.GameServerTable <init>INFO: Loaded 1 server namesMay 1, 2009 4:01:36 PM net.sf.l2j.loginserver.GameServerTable <init>INFO: Loaded 1 registered Game ServersMay 1, 2009 4:01:37 PM net.sf.l2j.loginserver.GameServerTable <init>INFO: Cached 10 RSA keys for Game Server communication.May 1, 2009 4:01:37 PM net.sf.l2j.loginserver.L2LoginServer <init>INFO: Listening for GameServers on *:8888May 1, 2009 4:01:37 PM net.sf.l2j.loginserver.L2LoginServer <init>INFO: Telnet server is currently disabled.May 1, 2009 4:01:37 PM net.sf.l2j.loginserver.L2LoginServer <init>SEVERE: FATAL: Failed to open server socket. Reason: Address already in use

Re: CentOS; No Console & "address is in use"

Posted: Sun May 03, 2009 1:27 am
by kotk
As root do
netstat -anp | grep 8888 | grep -i listen

The last column should list what is already running on that port. Any reason why you changed it from the default (9014)?