Jump to content
×
×
  • Create New...
  • 0

Problem auth crash


Jagger

Question

Hello ,

 

I have some problem with the auth ,

sometime crash , i dont know why

 

I hope you can help me =)

the syserr :

 

SYSERR: Aug  1 15:50:02.415194 :: socket_bind: bind: Address already in use

SYSERR: Aug  1 16:11:46.124625 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

SYSERR: Aug  1 19:34:23.268036 :: checkpointing: CHECKPOINT shutdown: tics did not updated.

SYSERR: Aug  2 05:17:53.385235 :: pid_init:

Start of pid: 61823

SYSERR: Aug  2 13:53:20.518243 :: socket_bind: bind: Address already in use

SYSERR: Aug  2 13:56:54.56027 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

SYSERR: Aug  2 14:08:33.448030 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

SYSERR: Aug  2 14:10:51.788049 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

SYSERR: Aug  2 14:20:04.44031 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

SYSERR: Aug  2 16:28:05.24031 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

SYSERR: Aug  2 22:42:49.690046 :: HandshakeProcess: handshake retry limit reached! (limit 32 character !NO CHARACTER!)

SYSERR: Aug  2 22:56:29.846102 :: socket_accept: accept: Software caused connection abort (fd 11)

SYSERR: Aug  3 01:55:23.66044 :: socket_accept: accept: Software caused connection abort (fd 11)

SYSERR: Aug  3 07:29:50.434586 :: pid_init:

 

 

Link to comment
Share on other sites

  • Answers 12
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

12 answers to this question

Recommended Posts

  • 0
socket_bind: bind: Address already in use

 

Stop ALL auth processes and start only one.

$ uptime
1:26AM  up 732 days,  8:29, 1 user, load averages: 0.38, 0.31, 0.22

$ uname -srp
FreeBSD 9.1-RELEASE amd64

Link to comment
Share on other sites

  • 0

I think is this the problem:

SYSERR: Aug  1 19:34:23.268036 :: checkpointing: CHECKPOINT shutdown: tics did not updated. is ....... Abort() ......XD

edit your libthecore/signal.c

{    if (!tics)
    {
sys_err("CHECKPOINT shutdown: tics did not updated.");
abort();
    }
    else
tics = 0;
}
 
Replace with
 
{
    if (!tics)
    /*{
sys_err("CHECKPOINT shutdown: tics did not updated.");
abort();
    }
    else*/
tics = 0;
}
 

 

Link to comment
Share on other sites

  • 0

The CHECKPOINT error means that the server hangs up somwhere and not responding. If you comment out the abort() you just did nothing, the core will be still unaviable.

$ uptime
1:26AM  up 732 days,  8:29, 1 user, load averages: 0.38, 0.31, 0.22

$ uname -srp
FreeBSD 9.1-RELEASE amd64

Link to comment
Share on other sites

  • 0

The CHECKPOINT error means that the server hangs up somwhere and not responding. If you comment out the abort() you just did nothing, the core will be still unaviable.

I try this solution and run ..and nothing crash....i don't know else

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


  • Activity

    1. 2

      Problem freebsd

    2. 0

      Making chain quest

    3. 4

      Ludus2: a metin2-like browser game

    4. 6
    5. 9

      Help in implementing a switch bot

    6. 0

      Special Inventory System Can't Sell To Npc's

    7. 0

      ROV2.GLOBAL | International | Server start 14.05.2022

    8. 75

      Services - System Ard [C ++ / Python / Lua]

  • Recently Browsing

    • No registered users viewing this page.

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.