Vaultster

[monezz]

The vaultster post in the general section is getting a bit divers, so I'll post my troubles here.

With the configuration syntax of Jeroen, I no longer get an error on the configuration file.
The module and plugin seems to load fine on both servers.
(Both linux)

When I try to hop from server1 to server2 I will get an error.
The log on server2 says an invalid client tries to connect.
The log on server 1:
Invalid password, or server rejected us.

When I try to hop from server2 to server1 another error occurs.
In the log I find an error like:
Could not find latest file for pattern xandraloxdeteste

We made sure the keys and password where the same.
We tried with a server password and provided it in the ActivatePortal call
we tried without server password and removed it from the ActivatePortal call.
We set the port to 5121 since port 5100 doesn't seem to work.

[JeroenB]

The first problem looks like the IP or the DNS name of the other server is not known.

[monezz]

How does the incoming request has to match the entry for the server?
Seems that the incoming request is identified by an ip address and the server is defined by an dns entry.
Would it be possible to do the match on dns entry?
one of the 2 servers has a semi dynamic ip address that changes from time to time.


second problem occurs on the requesting server. (so sending side)
The request doesn't appear in the log on the recieving side.
I've tried it with all the characters in my servervault.
Same problem for all.
IS there a way to set the debug level?
So the path and file the vaultster is looking for appears in the log?

[JeroenB]

[monezz]

Great thanks, I'll try it asap.

[fsondahl]

I'm running fedora core 1, and have nwnx working fine, but I'm having problems with vaulster.

After I put the nwnx_vaulster.so into the nwn folder, and I start up the server, I get this error:

ERROR: dlopen: ./nwnx_vaultster.so: libstdc++.so.6: cannot open shared object file: No such file or directory

All the other plugins say "XXX plugin Registered." successfully.

I looked around, and I have libstdc++.so.5 in my /usr/lib/ I tried updating the libstdc++ library with apt-get, and it said it was up to date. I tried updating gcc too. Sort of seems like I need a file called "libstdc++.so.6", but I'm not quite sure what's going on.

Does anyone know what version of linux nwnx_vaulster.so was built on? Do I need to recompile vaulster from source to make this work?

Any help would be appreciated, thanks.

[JeroenB]

I think you have to recompile the sources yes, as it was compiled on a mandrake 10.1 system with libc++ 6.

[fsondahl]

thanks... good to know.

[monezz]

I downloaded and installed the new version but the log didn;t seem to change.

nwnx_vaultster.log after attempt to portal:
NWNX2 Vaultster version 0.2.4 Linux.
Copyright 2004 (C) Jeroen Broekhuizen
o Loading in 1 known servers.
o server1: someserver.com
o Server started
o New request: SEND
o New request: 2
o Handling client with id: 0
Could not find latest file for pattern xandraloxdeteste
o New request: STATUS
Looking up status for client: 0

[JeroenB]

Indeed, more information is not available. The plugin can't find a file starting with '
'xandraloxdeteste' in it. You should verify if the file is really in the right place.

I will see if I can look into this soon.

[monezz]

This is the bic file of the character I was using.

-rw-r----- 1 nwn users 114560 Mar 4 03:19 xandraloxdetest8.bic

Somehow sometimes copys of the bic files appear in my servervault with a number in place of the last letter. I suspect thats the cause.
I don't know why the server makes te copies, but would it be more safe to change the search pattern to the newest file matching all but the last characters in the bic file name?

[monezz]

I created a new character on the server and the vaultster now seems to find the file. (renaming the other files according to the searchpattern doesn't work btw.)

result in the log:

o Handling client with id: 0
o New request: STATUS
Looking up status for client: 0
o New request: STATUS
Looking up status for client: 0
.... much more of the same
o New request: SEND
o New request: 2
o Handling client with id: 1
o New request: STATUS
Looking up status for client: 0
o New request: STATUS
Looking up status for client: 1
o New request: STATUS
Looking up status for client: 0
o New request: STATUS
Looking up status for client: 1
o New request: STATUS
..... much more of the same
Looking up status for client: 1
Could not connect to server on port 5121.

[JeroenB]

It's already kind of strange that Vaultster didn't shorten the search pattern to a maximum of 14 characters as it should do. I will have to look in to the code to find the problem and to solve it.


About the port number 5121. Do you have Vaultster configured to use port 5121? If so, do you also have a server running on that port? When that is the case I recommend you to use the default 5100 port for vaultster.

[monezz]

Tested it again with port 5100 and a new characterfile.

Portal now failes with: invalid password or server rejected us.

Should the user the nwn server is running under exists on the target server?
Could filesystem permissions trigger such an error?

We made sure 5100/tcp was open and all password where correct.

[JeroenB]

It also states these password error when your server is not known at the other server. This will happen if you test this on a local network and only supply the external IP. You might want to test this with the local network IP of both servers in the configuration files.