Jump to content

databases crashes, server dont start


Recommended Posts

  • Premium
SYSERR: Apr 12 02:06:16 :: pid_init: 
Start of pid: 981

SYSERR: Apr 12 02:06:16 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Apr 12 02:06:18 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Apr 12 02:06:18 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:18 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:19 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:23 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:24 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:24 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:29 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:29 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Apr 12 02:06:29 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:34 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:34 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:34 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:39 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:39 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:39 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:44 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:44 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:44 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:54 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:54 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:54 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:59 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:59 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:06:59 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:04 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:04 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:04 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:09 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:10 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:10 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:15 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:15 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:15 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:20 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:20 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:20 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:25 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:25 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:25 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:30 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:30 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:30 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:35 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:36 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Apr 12 02:07:36 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Apr 12 02:07:41 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:41 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:41 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:46 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:46 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:46 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Apr 12 02:07:52 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:52 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:52 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:57 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:57 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:07:58 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Apr 12 02:08:03 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:03 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Apr 12 02:08:03 :: Process: FDWATCH: peer null in event: ident 22
SYSERR: Apr 12 02:08:08 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:08 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Apr 12 02:08:08 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:13 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:13 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:13 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:18 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:18 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:19 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:24 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:24 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:24 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:29 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:29 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:29 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:34 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:34 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:34 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:39 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:39 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:39 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:44 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:44 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:44 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:49 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:54 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:54 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Apr 12 02:08:54 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:59 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:59 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:08:59 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:04 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:04 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:05 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:09 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:10 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:10 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:15 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:15 :: socket_accept: accept: Software caused connection abort (fd 19)
SYSERR: Apr 12 02:09:15 :: socket_accept: accept: Software caused connection abort (fd 19)

please help anyone

Link to comment
Share on other sites

1 oră în urmă, Dr3Ame3r a spus:

Hello, can you please provide us a GDB report regarding your server crash?

If you don't have a ".core" file, how did you find out that your server crashed?

 

Please provide the output of the following commands too:

dmesg

tail -f /var/log/messages

 

:facepalm:

 

		if (!peer)
		{
			if (fdwatch_check_event(m_fdWatcher, m_fdAccept, idx) == FDW_READ)
			{
				AddPeer(m_fdAccept);
				fdwatch_clear_event(m_fdWatcher, m_fdAccept, idx);
			}
			else
			{
				sys_err("FDWATCH: peer null in event: ident %d", fdwatch_get_ident(m_fdWatcher, idx));
			}

			continue;
		}

 

 

int fdwatch_get_ident(LPFDWATCH fdw, unsigned int event_idx)
{
	assert(event_idx < fdw->nfiles * 2);
	return fdw->kqrevents[event_idx].ident;
}
	LPKEVENT kqrevents;
typedef struct kevent* LPKEVENT;

sys/event.h

struct kevent {
	uintptr_t	ident;		/* identifier for this event */
	short		filter;		/* filter for event */
	u_short		flags;
	u_int		fflags;
	intptr_t	data;
	void		*udata;		/* opaque user data identifier */
};

from kqueue documentation

     The fields	of struct kevent are:

     ident	Value used to identify this event.  The	exact interpretation
		is determined by the attached filter, but often	is a file
		descriptor.

Now use your brain and identify event with

 

Acum 12 ore, .Avenue™ a spus:

Process: FDWATCH: peer null in event: ident 21

number 21.
 

Link to comment
Share on other sites

  • Premium
43 minutes ago, Салом said:

:facepalm:

 


		if (!peer)
		{
			if (fdwatch_check_event(m_fdWatcher, m_fdAccept, idx) == FDW_READ)
			{
				AddPeer(m_fdAccept);
				fdwatch_clear_event(m_fdWatcher, m_fdAccept, idx);
			}
			else
			{
				sys_err("FDWATCH: peer null in event: ident %d", fdwatch_get_ident(m_fdWatcher, idx));
			}

			continue;
		}

 

 


int fdwatch_get_ident(LPFDWATCH fdw, unsigned int event_idx)
{
	assert(event_idx < fdw->nfiles * 2);
	return fdw->kqrevents[event_idx].ident;
}

	LPKEVENT kqrevents;

typedef struct kevent* LPKEVENT;

sys/event.h


struct kevent {
	uintptr_t	ident;		/* identifier for this event */
	short		filter;		/* filter for event */
	u_short		flags;
	u_int		fflags;
	intptr_t	data;
	void		*udata;		/* opaque user data identifier */
};

from kqueue documentation


     The fields	of struct kevent are:

     ident	Value used to identify this event.  The	exact interpretation
		is determined by the attached filter, but often	is a file
		descriptor.

Now use your brain and identify event with

 

number 21.
 

Yes everything cool but, he has a failing query as main problem

DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
  • Love 1
Link to comment
Share on other sites

  • Premium
On 12/4/2018 at 2:26 PM, Салом said:

That query don't affect the startup of db core

Not too sure about that, at least it is not for the kqueue event aswell, in the else statement of the syslog for the null event you can clearly see that is treated with a mere continue;


This means that the purpose of that is just to log any empty one so it shouldn't be crashing because of this, that being said it is more likely crashing for a query, misconfiguration issues, some retarded code that breaks your db or stuff like that.
 

 

 

 

Link to comment
Share on other sites

  • Honorable Member
1 hour ago, Fleon said:

Not too sure about that, at least it is not for the kqueue event aswell, in the else statement of the syslog for the null event you can clearly see that is treated with a mere continue;

Ignore him. He's just iratm shitposting again. :lol:

1) A peer can be null, and it's used when we send something without caring for an answer from db.

2) BlockCountry return type isn't handled,  so even if it fails, it doesn't exit. ak8FHsA.png

Avenuetm didn't reply to Dr3am3r when he asked whether or not a db.core has been generated (in the thread title, it says "db crash", so we expect he got one), but he ended up giving some random likes and nothing more Lmpy3k7.png:mellow:

If he doesn't reply, mods should close this thread then. :ph34r:

 

EDIT: how to read a core dump:

This is the hidden content, please

Enjoy.

Edited by Metin2 Dev
Core X - External 2 Internal
  • Metin2 Dev 46
  • Eyes 2
  • Dislove 2
  • Angry 1
  • Not Good 1
  • Sad 1
  • Think 3
  • Confused 1
  • Good 15
  • Love 3
  • Love 20
Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now

Announcements



×
×
  • Create New...

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.