Jump to content
  • 0
deadman

Error Panama Crypt

Question

Hello Guys i installed the serverside of panama and i have this.

 

 

The folder panama in:

6PqNi.jpg

 

The files .iv and the file .lst in /usr/game/auth/panama/

6PqNs.jpg

 

And the file panama.lst:

 

6PqNQ.jpg

 

I use client with 34669 binary and when i enter to the game i dont see any weapon crypted in my item.eix/item.epk

 

The xml of my item.xml

<!-- This file was generated by the Metin2 File Archiver (r3869) -->
<!-- Copyright (C) 2009-2012 Tim N -->
<ScriptFile Version="3">
	<CreateEterPack ArchivePath="item" IvPath="item.iv">
		<File ArchivedPath="d:/ymir work/item/00001.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00001.msm]]></File>
		<File ArchivedPath="d:/ymir work/item/00010.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00010.msm]]></File>
		<File ArchivedPath="d:/ymir work/item/00020.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00020.msm]]></File>
		<File ArchivedPath="d:/ymir work/item/00030.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00030.msm]]></File>

So what is the problem?¿

 

Edit: i put 777 on the iv and not run

Share this post


Link to post

19 answers to this question

Recommended Posts

  • 0

Hello Guys i installed the serverside of panama and i have this.

 

 

The folder panama in:

6PqNi.jpg

 

The files .iv and the file .lst in /usr/game/auth/panama/

6PqNs.jpg

 

And the file panama.lst:

 

6PqNQ.jpg

 

I use client with 34669 binary and when i enter to the game i dont see any weapon crypted in my item.eix/item.epk

 

The xml of my item.xml

<!-- This file was generated by the Metin2 File Archiver (r3869) -->
<!-- Copyright (C) 2009-2012 Tim N -->
<ScriptFile Version="3">
	<CreateEterPack ArchivePath="item" IvPath="item.iv">
		<File ArchivedPath="d:/ymir work/item/00001.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00001.msm]]></File>
		<File ArchivedPath="d:/ymir work/item/00010.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00010.msm]]></File>
		<File ArchivedPath="d:/ymir work/item/00020.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00020.msm]]></File>
		<File ArchivedPath="d:/ymir work/item/00030.msm" Type="PANAMA"><![CDATA[item//d_/ymir work/item/00030.msm]]></File>

So what is the problem?¿

 

Edit: i put 777 on the iv and not run

 

try chmod 644 panama.lst, and make sure the file is Unix format and not Windows

Share this post


Link to post
  • 0

Unix and Windows use different characters for line breaks. Open the file with ee in FreeBSD, if it's Windows formatted you will see something like ^M at the end of each line, remove that.

Share this post


Link to post
  • 0

The file not formated in windows i put 644 but dont run what do you think shogun?¿

Share this post


Link to post
  • 0

The xml is missing the ending tags </CreateEterPack></ScriptFile>

Share this post


Link to post
  • 0

no, this only a part of the xml he dont missing the tags 

Share this post


Link to post
  • 0

try making the msm type 2 and the rest (not text files) type 3

Share this post


Link to post
  • 0

edit i put all in type 2 and the .gr2 of sword in type 3 with the ivpath and dont works.

 

Any idea?¿

Share this post


Link to post
  • 0

you have panama in your world of metin shogun?¿

 

PD: i think is this binary dont suport type 3, i know you say me the binarys up to 2010 suport this but i think this not suport type 3 btw i think i do good the serverside config.

Share this post


Link to post
  • 0

Maybe Tim can give you an answer. I don't use Panama in WoM but I did use it in SG.

Share this post


Link to post
  • 0

What's in your auth server's syslog/syserr? Does extracting the archive again work? Kind Regards, Tim

  • Love 1

Share this post


Link to post
  • 0

my sysser of auth

SYSERR: Feb  7 17:58:08 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 17:59:23 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:26 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:29 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:32 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:35 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:38 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:42 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 17:59:53 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 18:00:24 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 18:03:14 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  7 18:03:14 :: pid_deinit: 
End of pid

SYSERR: Feb  7 18:06:33 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 18:07:18 :: SetBilling: cannot find login key 0
SYSERR: Feb  7 18:12:58 :: socket_bind: bind: Address already in use
SYSERR: Feb  9 08:19:58 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  9 08:19:59 :: pid_deinit: 
End of pid

SYSERR: Feb  9 08:22:09 :: SetBilling: cannot find login key 0
SYSERR: Feb  9 08:46:24 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  9 08:46:24 :: pid_deinit: 
End of pid

SYSERR: Feb  9 08:51:14 :: SetBilling: cannot find login key 0
SYSERR: Feb  9 11:15:44 :: socket_bind: bind: Address already in use

If i extract the archive with the IV and i put type 2 or 1  or 0 this works.

Share this post


Link to post
  • 0

and the syslog?

my sysser of auth

SYSERR: Feb  7 17:58:08 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 17:59:23 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:26 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:29 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:32 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:35 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:38 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 17:59:42 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 17:59:53 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 18:00:24 :: socket_bind: bind: Address already in use
SYSERR: Feb  7 18:03:14 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  7 18:03:14 :: pid_deinit: 
End of pid

SYSERR: Feb  7 18:06:33 :: socket_connect: HOST localhost:15000, could not connect.
SYSERR: Feb  7 18:07:18 :: SetBilling: cannot find login key 0
SYSERR: Feb  7 18:12:58 :: socket_bind: bind: Address already in use
SYSERR: Feb  9 08:19:58 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  9 08:19:59 :: pid_deinit: 
End of pid

SYSERR: Feb  9 08:22:09 :: SetBilling: cannot find login key 0
SYSERR: Feb  9 08:46:24 :: hupsig: SIGHUP, SIGINT, SIGTERM signal has been received. shutting down.
SYSERR: Feb  9 08:46:24 :: pid_deinit: 
End of pid

SYSERR: Feb  9 08:51:14 :: SetBilling: cannot find login key 0
SYSERR: Feb  9 11:15:44 :: socket_bind: bind: Address already in use

If i extract the archive with the IV and i put type 2 or 1  or 0 this works.

But type 3 doesn't work? (The other types are irrelevant, they have nothing to do with the IV file)

socket_bind: bind: Address already in use

Your auth server seems to be already/still running

 

Share this post


Link to post
  • 0

i think the type 3 dont work on my binary and the syslog is of 0kb in my auth

 

So what do you think Tim?¿

Share this post


Link to post

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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • 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.