My problem. please help me.
My problem. please help me.
This has already been answered, search please.Originally Posted by T3RMiN4T0R
My problem. please help me.
Btw, CHANGE ur TITLE
wait 4 minutes from starting the server to login
(this error hits me too sometimes, I do not know the exact cause)
Last edited by Psytrac; 23-08-12 at 01:14 AM.
your gs is offline or no started
check that
it's gshop, but that error happens even with correct gshop, trust me, I tested that
It's on 144 is corrupted gshopsev and gshop data. you can fix it with the gshop editor easy
^this (doesn't anyone read..)
The client needs to submit a hash for access to the server, if the hashes mismatch, that error is generated.
ensure the data (in your case im guessing ghop & gshop1) contain the same timestamp data for hash comparison...
This may be the case if you're using low 'scrape by' amounts of ram <.<
I've never had to "wait" when using 32GB+ of physical RAM
and you're assuming s/he is? It's a solution I've had to do and get used to, it's QUITE possible it could be the same for them.I've never had to "wait" when using 32GB+ of physical RAM
Yes, it could be, but again, if people used adequate amounts of ram this would not be necessary...
This is all you need to know...
The gs must be fully initialised for the hash to be generated and sent for the client to receive. Generally GS has finished initialisation once the world map (albeit first map) has been fully expressed.
So the 4 minute statement previously hinted is in fact not accurate as time is dependent on the system to initialise the GS daemon.
If your map services are running and you cannot enter the game due to that error, then please see below.
The client needs to compare a hash for access to the server, if the hashes mismatch, that error is generated.
ensure the data (in your case im guessing ghop & gshop1) contain the same timestamp data for hash comparison...
2.2 mono @ 4mins, I highly doubt anyone's slower
why so many people hard to read the log? lemme show you where are the log files in, mmm... i guess they are inside element/logs... :D well if you get something weird on client, First Aid is in your "damn" logs directory need to be post here...
Client logs will only detail faults within the client or client-server connection, they are not useful with diagnosing server related issues.
This issue is hash mismatch, so fault lies within the data of both server and client for comparison.
if this case is hash mismatch then you have to start from client, isn't it? :D
no, as the hash is generated server-side, and it is that which you must match. think of the client as a "dumb" client.
Reply With Quote