Salut. Problemă Sursă Cartof :D

Gaz3rNr1 · 21 Oct 2015, 19:14

Salut. Am compilat Sursa cartof, am băgat repede să citească .sql . Am băgat game și db. Am dat reboot, am pornit server, Am făcut Toată partea de server. Doar client nu am făcut. Și imi zice Eroare la Conectarea la server. Este de la faptul că nu am făcut și partea de client????

REALSaiyajin · 21 Oct 2015, 19:51

Daca vrei sa citeasca din .sql nu ai nevoie de parte de client. Pune syserr din server db/auth/ch.

Gaz3rNr1 · 21 Oct 2015, 19:57

REALSaiyajin scrie:Daca vrei sa citeasca din .sql nu ai nevoie de parte de client. Pune syserr din server db/auth/ch.

La citirea .sql, mă refeream doar ce am modificat in sursă !
Și la partea de client, ce am zis eu acolo, mă refeream că nu am făcut partea de client pentru eșarfe. Acum o fac și revin cu edit
DB:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:36 :: pid_init: 
Start of pid: 1034

SYSERR: Oct 17 00:50:36 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 00:50:37 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 17 04:41:56 :: pid_init: 
Start of pid: 1847

SYSERR: Oct 17 04:41:56 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:41:57 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:41:57 :: pid_deinit: 
End of pid

SYSERR: Oct 17 04:46:08 :: pid_init: 
Start of pid: 1875

SYSERR: Oct 17 04:46:08 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:46:09 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:46:09 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:33 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:49 :: pid_init: 
Start of pid: 943

SYSERR: Oct 20 20:03:49 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 20:03:50 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:41 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:04 :: pid_init: 
Start of pid: 942

SYSERR: Oct 20 22:22:04 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 22:22:05 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:22:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Oct 20 22:22:32 :: Process: FDWATCH: peer null in event: ident 22

Auth:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:41 :: pid_init: 
Start of pid: 1037

SYSERR: Oct 17 04:42:01 :: pid_init: 
Start of pid: 1850

SYSERR: Oct 17 04:46:13 :: pid_init: 
Start of pid: 1878

SYSERR: Oct 17 04:46:13 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:55 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:39 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:10 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:22:31 :: SetBilling: cannot find login key 0

REALSaiyajin · 21 Oct 2015, 20:08

In /map/index ai linie goala la final de fisier?
Posteaza si syserr din ch1.

Gaz3rNr1 · 21 Oct 2015, 20:14

REALSaiyajin scrie:In /map/index ai linie goala la final de fisier?
Posteaza si syserr din ch1.

Imediat iți zic, e in reboot !
Edit: Ch1

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:46 :: pid_init: 
Start of pid: 1040

SYSERR: Oct 17 00:51:29 :: LoadSkillMotion: Motion: Skill exist but no motion data for index 0 mob 3596 skill 257
SYSERR: Oct 17 00:51:29 :: LoadSkillMotion: Motion: Skill exist but no motion data for index 1 mob 3596 skill 258
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'
SYSERR: Oct 17 00:51:30 :: heart_idle: losing 42 seconds. (lag occured)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10080) name(10080 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10078) name(10078 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10080) name(10080 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10079) name(10079 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10078) name(10078 Noname)
SYSERR: Oct 17 00:51:33 :: FuncCheckWarp: Warp NPC name wrong : vnum(10079) name(10079 Noname)

Da, aveam in index, chiar 2 linii. Le-am șters pe amândouă !

REALSaiyajin · 21 Oct 2015, 20:20

Gaz3rNr1 scrie:

REALSaiyajin scrie:In /map/index ai linie goala la final de fisier?
Posteaza si syserr din ch1.

Imediat iți zic, e in reboot !
Edit: Ch1

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:46 :: pid_init: 
Start of pid: 1040

SYSERR: Oct 17 00:51:29 :: LoadSkillMotion: Motion: Skill exist but no motion data for index 0 mob 3596 skill 257
SYSERR: Oct 17 00:51:29 :: LoadSkillMotion: Motion: Skill exist but no motion data for index 1 mob 3596 skill 258
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'
SYSERR: Oct 17 00:51:30 :: heart_idle: losing 42 seconds. (lag occured)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10080) name(10080 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10078) name(10078 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10080) name(10080 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10079) name(10079 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10078) name(10078 Noname)
SYSERR: Oct 17 00:51:33 :: FuncCheckWarp: Warp NPC name wrong : vnum(10079) name(10079 Noname)

Da, aveam in index, chiar 2 linii. Le-am șters pe amândouă !

Doar una trebuie lasata.
Verifica si porturile din serverinfo.

Gaz3rNr1 · 21 Oct 2015, 20:23

REALSaiyajin scrie:

Gaz3rNr1 scrie:

REALSaiyajin scrie:In /map/index ai linie goala la final de fisier?
Posteaza si syserr din ch1.

Imediat iți zic, e in reboot !
Edit: Ch1

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:46 :: pid_init: 
Start of pid: 1040

SYSERR: Oct 17 00:51:29 :: LoadSkillMotion: Motion: Skill exist but no motion data for index 0 mob 3596 skill 257
SYSERR: Oct 17 00:51:29 :: LoadSkillMotion: Motion: Skill exist but no motion data for index 1 mob 3596 skill 258
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/dog_god/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/lion/run.msa'
SYSERR: Oct 17 00:51:30 :: LoadMotion: cannot find accumulation data in file 'data/monster/horse_event1/03.msa'
SYSERR: Oct 17 00:51:30 :: heart_idle: losing 42 seconds. (lag occured)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10080) name(10080 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10078) name(10078 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10080) name(10080 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10079) name(10079 Noname)
SYSERR: Oct 17 00:51:30 :: FuncCheckWarp: Warp NPC name wrong : vnum(10078) name(10078 Noname)
SYSERR: Oct 17 00:51:33 :: FuncCheckWarp: Warp NPC name wrong : vnum(10079) name(10079 Noname)

Da, aveam in index, chiar 2 linii. Le-am șters pe amândouă !

Doar una trebuie lasata.

Ok, las doar 1. Dar de ce imi da eroare conectare la server? Am compilat Sursa Cartof, Am facut partea de Navicat( a trebuit sa rulez niște fișiere.... ) Am făcut Partea de Client, Am luat un Launcher cu eșarfele. si-mi dă eroare la conectarea la server !
Oare de la ce o fi? NU e compatibilă Sursa cu Svf meu?
Porturi verificate. Nimic in neregula !

zmyl3 · 21 Oct 2015, 20:37

Gaz3rNr1 scrie:

REALSaiyajin scrie:Daca vrei sa citeasca din .sql nu ai nevoie de parte de client. Pune syserr din server db/auth/ch.

La citirea .sql, mă refeream doar ce am modificat in sursă !
Și la partea de client, ce am zis eu acolo, mă refeream că nu am făcut partea de client pentru eșarfe. Acum o fac și revin cu edit
DB:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:36 :: pid_init: 
Start of pid: 1034

SYSERR: Oct 17 00:50:36 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 00:50:37 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 17 04:41:56 :: pid_init: 
Start of pid: 1847

SYSERR: Oct 17 04:41:56 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:41:57 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:41:57 :: pid_deinit: 
End of pid

SYSERR: Oct 17 04:46:08 :: pid_init: 
Start of pid: 1875

SYSERR: Oct 17 04:46:08 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:46:09 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:46:09 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:33 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:49 :: pid_init: 
Start of pid: 943

SYSERR: Oct 20 20:03:49 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 20:03:50 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:41 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:04 :: pid_init: 
Start of pid: 942

SYSERR: Oct 20 22:22:04 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 22:22:05 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:22:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Oct 20 22:22:32 :: Process: FDWATCH: peer null in event: ident 22

Auth:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:41 :: pid_init: 
Start of pid: 1037

SYSERR: Oct 17 04:42:01 :: pid_init: 
Start of pid: 1850

SYSERR: Oct 17 04:46:13 :: pid_init: 
Start of pid: 1878

SYSERR: Oct 17 04:46:13 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:55 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:39 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:10 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:22:31 :: SetBilling: cannot find login key 0

Uita-te in DB ca ai "SYSERR: Oct 20 22:22:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Oct 20 22:22:32 :: Process: FDWATCH: peer null in event: ident 22" din cate stiu eu aceasta eroare iti e fatala pentru server si se refera la modificarile facute in baza, adaugari...

Gaz3rNr1 · 21 Oct 2015, 20:41

zmyl3 scrie:

Gaz3rNr1 scrie:

REALSaiyajin scrie:Daca vrei sa citeasca din .sql nu ai nevoie de parte de client. Pune syserr din server db/auth/ch.

La citirea .sql, mă refeream doar ce am modificat in sursă !
Și la partea de client, ce am zis eu acolo, mă refeream că nu am făcut partea de client pentru eșarfe. Acum o fac și revin cu edit
DB:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:36 :: pid_init: 
Start of pid: 1034

SYSERR: Oct 17 00:50:36 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 00:50:37 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 17 04:41:56 :: pid_init: 
Start of pid: 1847

SYSERR: Oct 17 04:41:56 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:41:57 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:41:57 :: pid_deinit: 
End of pid

SYSERR: Oct 17 04:46:08 :: pid_init: 
Start of pid: 1875

SYSERR: Oct 17 04:46:08 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:46:09 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:46:09 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:33 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:49 :: pid_init: 
Start of pid: 943

SYSERR: Oct 20 20:03:49 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 20:03:50 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:41 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:04 :: pid_init: 
Start of pid: 942

SYSERR: Oct 20 22:22:04 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 22:22:05 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:22:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Oct 20 22:22:32 :: Process: FDWATCH: peer null in event: ident 22

Auth:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:41 :: pid_init: 
Start of pid: 1037

SYSERR: Oct 17 04:42:01 :: pid_init: 
Start of pid: 1850

SYSERR: Oct 17 04:46:13 :: pid_init: 
Start of pid: 1878

SYSERR: Oct 17 04:46:13 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:55 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:39 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:10 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:22:31 :: SetBilling: cannot find login key 0

Uita-te in DB ca ai "SYSERR: Oct 20 22:22:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Oct 20 22:22:32 :: Process: FDWATCH: peer null in event: ident 22" din cate stiu eu aceasta eroare iti e fatala pentru server si se refera la modificarile facute in baza, adaugari...

Gata, știu. SUnt acele fișiere de la eșarfe care le-am rulat in player și in log.

Gaz3rNr1 · 21 Oct 2015, 20:53

zmyl3 scrie:

Gaz3rNr1 scrie:

REALSaiyajin scrie:Daca vrei sa citeasca din .sql nu ai nevoie de parte de client. Pune syserr din server db/auth/ch.

La citirea .sql, mă refeream doar ce am modificat in sursă !
Și la partea de client, ce am zis eu acolo, mă refeream că nu am făcut partea de client pentru eșarfe. Acum o fac și revin cu edit
DB:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:36 :: pid_init: 
Start of pid: 1034

SYSERR: Oct 17 00:50:36 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 00:50:37 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 17 04:41:56 :: pid_init: 
Start of pid: 1847

SYSERR: Oct 17 04:41:56 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:41:57 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:41:57 :: pid_deinit: 
End of pid

SYSERR: Oct 17 04:46:08 :: pid_init: 
Start of pid: 1875

SYSERR: Oct 17 04:46:08 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 17 04:46:09 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 04:46:09 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:33 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:49 :: pid_init: 
Start of pid: 943

SYSERR: Oct 20 20:03:49 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 20:03:50 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:41 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:04 :: pid_init: 
Start of pid: 942

SYSERR: Oct 20 22:22:04 :: Start: TABLE_POSTFIX not configured use default
SYSERR: Oct 20 22:22:05 :: Load:  DirectQuery failed(SELECT IP_FROM, IP_TO, COUNTRY_NAME FROM iptocountry)
SYSERR: Oct 20 22:22:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Oct 20 22:22:32 :: Process: FDWATCH: peer null in event: ident 22

Auth:

Cod: Selectaţi tot

SYSERR: Oct 17 00:50:41 :: pid_init: 
Start of pid: 1037

SYSERR: Oct 17 04:42:01 :: pid_init: 
Start of pid: 1850

SYSERR: Oct 17 04:46:13 :: pid_init: 
Start of pid: 1878

SYSERR: Oct 17 04:46:13 :: socket_bind: bind: Address already in use
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:26 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 17 05:36:27 :: pid_deinit: 
End of pid

SYSERR: Oct 20 20:03:55 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:18:38 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Oct 20 22:18:39 :: pid_deinit: 
End of pid

SYSERR: Oct 20 22:22:10 :: pid_init: 
Start of pid: 946

SYSERR: Oct 20 22:22:31 :: SetBilling: cannot find login key 0

Uita-te in DB ca ai "SYSERR: Oct 20 22:22:31 :: Process: FDWATCH: peer null in event: ident 21
SYSERR: Oct 20 22:22:32 :: Process: FDWATCH: peer null in event: ident 22" din cate stiu eu aceasta eroare iti e fatala pentru server si se refera la modificarile facute in baza, adaugari...

Mersi mult FRT pentru ajutor, dar le dai naibi de Esarfe. Platesc pentru Implementarea lor si cu asta basta ! Sau nu le mai iau deloc. Uite skype meu daca vrei sa vb... gazer.nr1

Salut. Problemă Sursă Cartof :D

Problema compilare sursa cartof v1

Problema compilare sursa cartof.

Problemă Curele (sursă cartof)

Problema compilare sursa cartof v2. (GAME)

Cine este conectat