Register for your free account! | Forgot your password?

Go Back   elitepvpers › Popular Games › Metin2 › Metin2 Private Server
fehler - hmm ? fehler - hmm ?
You last visited: Today at 10:25

  • Please register to post and access all features, it's quick, easy and FREE!

Advertisement


Advertise with us!

fehler - hmm ?

Discussion on fehler - hmm ? within the Metin2 Private Server forum part of the Metin2 category.

Reply
Page 1 of 2 1 2
 
Old   #1
 
*~.ιηνιη¢ιвℓє.~*'s Avatar
 
elite*gold: 5
The Black Market: 3/0/0
Join Date: Dec 2011
Posts: 1,823
Received Thanks: 951
fehler - hmm ?

Code:
SYSERR: Apr 20 22:32:17 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:19 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:41 :: socket_bind: bind: Address already in use
SYSERR: Apr 20 22:33:07 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 22:33:07 :: socket_block: fcntl: nonblock: Bad file descriptor
was bedeutet das ._.
*~.ιηνιη¢ιвℓє.~* is offline  
Old   #2
 
elite*gold: 10
The Black Market: 7/0/0
Join Date: Jan 2013
Posts: 471
Received Thanks: 228
game crashed, irgendweche falschen dif's gepatcht ?
Hatte das auch vor 'nem Tag habe die 2089 Gabe genommen & Ordentliche Dif's draufgehauen.
Danach gings..
[LxR].Vulka' is offline  
Old   #3
 
*~.ιηνιη¢ιвℓє.~*'s Avatar
 
elite*gold: 5
The Black Market: 3/0/0
Join Date: Dec 2011
Posts: 1,823
Received Thanks: 951
nicht das ich wüsste ._.

ist die game aus meinen hamachi files und auf hamachi geht alles einwandfrei.
Jetzt habe ich das aufn root gezogen und neben bei die drops eingefügt und jz funktionierts iwie nich ._. ich versuch mal nomma die game rüber zuziehen :3
*~.ιηνιη¢ιвℓє.~* is offline  
Old   #4
 
elite*gold: 10
The Black Market: 7/0/0
Join Date: Jan 2013
Posts: 471
Received Thanks: 228
mh... Hast du mal mit IDA den fehler Analysiert?
[LxR].Vulka' is offline  
Old   #5
 
nostradame37's Avatar
 
elite*gold: 0
The Black Market: 4/0/0
Join Date: Jan 2011
Posts: 2,504
Received Thanks: 870
PHP Code:
SYSERR: Apr 20 22:32:17 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:19 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down. 
bedeutet das der server/channel wegen irgent einem grund runtergefaren ist

PHP Code:
SYSERR: Apr 20 22:32:41 :: socket_bind: bind: Address already in use 
bedeutet das der auth server nicht coneckten kann oder schon coneckted ist warscheinlich beim hochfaren des channels/server
irgend was hatt deinen core/channel runtergefahren soltest mehr von der syserror posten
mfg
nostradame37 is offline  
Old   #6
 
elite*gold: 10
The Black Market: 7/0/0
Join Date: Jan 2013
Posts: 471
Received Thanks: 228
Die gamecores müssen auch mitgeändert werden...
[LxR].Vulka' is offline  
Old   #7
 
*~.ιηνιη¢ιвℓє.~*'s Avatar
 
elite*gold: 5
The Black Market: 3/0/0
Join Date: Dec 2011
Posts: 1,823
Received Thanks: 951
hab die gamefile neu hochgeladen
Code:
SYSERR: Apr 20 22:32:17 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:19 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:41 :: socket_bind: bind: Address already in use
SYSERR: Apr 20 22:33:07 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 22:33:07 :: socket_block: fcntl: nonblock: Bad file descriptor
SYSERR: Apr 20 23:14:05 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:14:05 :: heart_idle: losing 75 seconds. (lag occured)
Ganze Syserr jetzt

krieges nich gefixxt
*~.ιηνιη¢ιвℓє.~* is offline  
Old   #8
 
nostradame37's Avatar
 
elite*gold: 0
The Black Market: 4/0/0
Join Date: Jan 2011
Posts: 2,504
Received Thanks: 870
was fuer ein problem haste den ?
nostradame37 is offline  
Old   #9
 
*~.ιηνιη¢ιвℓє.~*'s Avatar
 
elite*gold: 5
The Black Market: 3/0/0
Join Date: Dec 2011
Posts: 1,823
Received Thanks: 951
Code:
YSERR: Apr 20 22:32:17 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:19 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:41 :: socket_bind: bind: Address already in use
SYSERR: Apr 20 22:33:07 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 22:33:07 :: socket_block: fcntl: nonblock: Bad file descriptor
SYSERR: Apr 20 23:14:05 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:14:05 :: heart_idle: losing 75 seconds. (lag occured)
Diesen ich kann mich halt nicht einloggen und in putty steht Operation timed out
*~.ιηνιη¢ιвℓє.~* is offline  
Old   #10
 
nostradame37's Avatar
 
elite*gold: 0
The Black Market: 4/0/0
Join Date: Jan 2011
Posts: 2,504
Received Thanks: 870
Operation timed out bedeutet das der jeweilige core gestartet worden ist Operation timed out ist keine fehler meldung
kanst du dich mit dem clienten nicht einloggen? und um was fuer einen server sprechen wir den hier ? hamachi? dns? root?
nostradame37 is offline  
Old   #11
 
Spartan#117's Avatar
 
elite*gold: 0
The Black Market: 0/0/0
Join Date: Apr 2013
Posts: 151
Received Thanks: 149
Hi!

Code:
socket_bind: bind: Address already in use
Dieser Fehler(und alle folgenden socket_* Fehler) bedeutet, dass besagter Socket bereits benutzt wird, demnach läuft auf dem Server noch ein Core bzw hat den Socket reserviert.

Versuch diese Befehle in der Shell einzugeben:
Code:
killall -9 game
und
Code:
killall -9 db
Danach sollte der Socket wieder freigegeben und jegliche offenen Metin2-Server-Prozesse terminiert sein.

Ich hoffe ich konnte dir helfen.
Spartan#117 is offline  
Old   #12
 
*~.ιηνιη¢ιвℓє.~*'s Avatar
 
elite*gold: 5
The Black Market: 3/0/0
Join Date: Dec 2011
Posts: 1,823
Received Thanks: 951
Quote:
Originally Posted by Spartan#117 View Post
Hi!

Code:
socket_bind: bind: Address already in use
Dieser Fehler(und alle folgenden socket_* Fehler) bedeutet, dass besagter Socket bereits benutzt wird, demnach läuft auf dem Server noch ein Core bzw hat den Socket reserviert.

Versuch diese Befehle in der Shell einzugeben:
Code:
killall -9 game
und
Code:
killall -9 db
Danach sollte der Socket wieder freigegeben und jegliche offenen Metin2-Server-Prozesse terminiert sein.

Ich hoffe ich konnte dir helfen.
*Es ist ein Root-Server*
____________________________
Was ist eine Shell ._.
und wie soll ich das denn genau machen ._. ?
*~.ιηνιη¢ιвℓє.~* is offline  
Old   #13
 
Spartan#117's Avatar
 
elite*gold: 0
The Black Market: 0/0/0
Join Date: Apr 2013
Posts: 151
Received Thanks: 149
Da es ja ein * Root-Server * ist, verbindest du bestimmt über PuTTY(Oder einen anderen SSH-Client), um auf dem Server Befehle auszuführen.

Befehle sind beispielsweise auch das Starten/Beenden des Servers, meistens etwas wie
Code:
./start.sh
oder ähnlich.

Nun, anstelle den Server zu starten oder zu stoppen, gibst du die oben genannten Befehle ein.

Um dir deine andere Frage zu beantworten: Eine Shell stellt dir diese Eingabemöglichkeiten für Befehle zur Verfügung. Die Standard-Shell ist meistens /bin/sh.
Spartan#117 is offline  
Old   #14
 
*~.ιηνιη¢ιвℓє.~*'s Avatar
 
elite*gold: 5
The Black Market: 3/0/0
Join Date: Dec 2011
Posts: 1,823
Received Thanks: 951
wenn ich deine beiden befehle eingebe also
so siehts dann aus

#killall -9 game
No matching processes were found
#killall -9 db
No matching processes were found
#
Code:
SYSERR: Apr 20 22:32:17 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:19 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 20 22:32:41 :: socket_bind: bind: Address already in use
SYSERR: Apr 20 22:33:07 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 22:33:07 :: socket_block: fcntl: nonblock: Bad file descriptor
SYSERR: Apr 20 23:14:05 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:14:05 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:15:20 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:15:20 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:16:35 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:16:35 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:17:50 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:17:50 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:19:05 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:19:05 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:20:20 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:20:21 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:21:36 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:21:36 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:22:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:22:51 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:24:06 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:24:06 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:25:21 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:25:21 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:26:36 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:26:36 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:27:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:27:51 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:29:06 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:29:06 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:30:21 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:30:21 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:31:36 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:31:36 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:32:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:32:51 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:34:06 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:34:06 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:35:21 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:35:21 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:36:36 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:36:36 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:37:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:37:51 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:39:06 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:39:06 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:40:21 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:40:21 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:41:36 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:41:36 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:42:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:42:51 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:44:06 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:44:06 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:45:21 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:45:21 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:46:36 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:46:36 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:47:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:47:51 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:49:06 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:49:06 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:50:21 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:50:21 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:51:36 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:51:37 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:52:51 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:52:52 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:54:07 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:54:07 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:55:22 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:55:22 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:56:37 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:56:37 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:57:52 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:57:52 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 20 23:59:07 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 20 23:59:07 :: heart_idle: losing 75 seconds. (lag occured)
SYSERR: Apr 21 00:00:16 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 21 00:00:17 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Apr 21 00:00:22 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Apr 21 00:00:22 :: socket_block: fcntl: nonblock: Bad file descriptor
*~.ιηνιη¢ιвℓє.~* is offline  
Old   #15
 
Spartan#117's Avatar
 
elite*gold: 0
The Black Market: 0/0/0
Join Date: Apr 2013
Posts: 151
Received Thanks: 149
Führe diesen Befehl aus und poste das Ergebnis:
Code:
sockstat -4 -l | grep 15000
Spartan#117 is offline  
Reply
Page 1 of 2 1 2

« Metin2 Pserver DMG Hack | [Problem]d.join »

Similar Threads Similar Threads
So ein Fehler gibt es nicht, DB alels funzt ingame Fehler -.-
01/19/2012 - Metin2 Private Server - 6 Replies
Hey Com, ich habe alles gestartet (Hamachi Daroo Files). Navicat geht, alles funzt nur folgendes: Wenn ich mich mit falschen Logins einlogge: Dieser Account existiert nicht. Wenn ich richtige Daten eingebe: Fehler beim Verbinden mit dem Server
[Root]Setting.lua fehler aber Fehler nicht zu beheben??
08/09/2011 - Metin2 Private Server - 5 Replies
Richte für jemanden den root ein, aber bei dem fehler bin ich jetzt selber an meine grenzen gekommen. Folgender Fehler kommt beim starten: http://www.fotos-hochladen.net/uploads/unbenan11n tij3uvlnr5d.png Die syserr daneben gehört dazu, die Setting.lua habe ich schon durch getauscht, kommt aber immer noch der Fehler :confused: Datenbank auch schon getauscht, aber was ist dieses:
Infinite Aion: Fehler (1024) Fehler beim initialisieren des Spiels
06/09/2011 - Aion Private Server - 5 Replies
Hi Leute, ich hab ein Probem mit AION: jedesmal wenn ich starte, egal ob mit dem NCSoft Launcher oder mit dem Infinite Aion Launcher kommt die Meldung Fehler beim initialisieren des Spiels... Hab schon alle möglichen Sprachkombinationen durchprobiert, da es überall heißt man soll Region und Sprache beim NCSoft Launcher ändern und dann gehts... Alles probiert, und siehe da: geändert hat sich nichts... Immer noch der Fehler 1024... wäre nett, wenn mir da jemand helfen könnte und auch...
Server fehler!! (core fehler) bitte hilfee!!
02/16/2011 - Metin2 Private Server - 6 Replies
Hallo liebes ePvP. Ich habe gerade versucht die neuen reittiere einzufügen und da reboote ich den server und bekomme einen core fehler :( hier der genaue fehler: mv: rename cores/core .2 to cores/core .1: No such file or directory mv: rename cores/core .3 to cores/core .2: No such file or directory mv: rename cores/core .4 to cores/core .3: No such file or directory mv: rename cores/core .5 to cores/core .3: No such file or directory mv: rename cores/core .6 to cores/core .5: No such file...
Fehler : java.net.socet.exception:connection reset fehler bitte um hilfe
12/21/2010 - Minecraft - 9 Replies
Hab denn java.net.socet.exception:connection reset fehler immer und immer wieder :( könnt ihr mir dabei vill helfen? :) LG DieVerrückteMango =)



All times are GMT +2. The time now is 10:25.

elitepvpers - play less, get more - Top

Powered by vBulletin®
Copyright ©2000 - 2026, Jelsoft Enterprises Ltd.
SEO by vBSEO ©2011, Crawlability, Inc.

Support | Contact Us | FAQ | Advertising | Privacy Policy | Terms of Service | Abuse
Copyright ©2026 elitepvpers All Rights Reserved.