Server Help

[Hunner]

Several questions: (fyi I am running ASSS 1.3.6 and 1.4.0 on a light Slackware install, Subgame and ASSS 1.4.0 on WinXP, and SSB2 on Win2003)

1. I get errors when running 1.4.0 that keep it from running. (These are both the pre-compiled and default-conf binaries.)
On windows after running from the .bat I get the error titled "asss.exe - Unable To Locate Component" and it says "This application has failed to start because ../build/asss.exe was not found. Re-installed the application may fil this poblem."
On my slack install it gives:
---Code---
asss@as3:~/asss-1.4.0$ bin/asss
asss 1.4.0 built at May 15 2005 00:03:10
Loading modules...
I <cmod> loading C module 'unixsignal' from 'internal'
I <cmod> loading C module 'deadlock' from 'internal'
I <cmod> loading C module 'prng' from 'internal'
I <cmod> loading C module 'logman' from 'internal'
Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
'import site' failed; use -v for traceback
Traceback (most recent call last):
File "<string>", line 1, in ?
ImportError: No module named os
ImportError: No module named cPickle
ImportError: No module named exec
Unrecoverable error (5): Error in loading module '<py> exec'
asss@as3:~/asss-1.4.0$
---
Because of this I have been usuing 1.3.6 on slackware and have my 2nd question.


2. Does ASSS 1.3.6 (linux) and SSB2 (windows) work together? I have tried both the biller and biller_ssc modules.

With biller module ASSS gives
---Code---
D <billing> trying to connect to user db server at 10.0.0.10:1849
W <billing> can't connect to billing server: Connection refused
---
(SSB2)
---Code---
Connection request from 10.0.0.110:1191
Invalid login from 10.0.0.110
---
biller_ssc gives (ASSS)
---Code---
I <billing_ssc> connecting to user database server at 10.0.0.10:1849
I <billing_ssc> connected to user database server, logging in
I <billing_ssc> lost connection to user database server (auto-retry in 180 seconds)
I <net> (client connection) dropping client connection
W <net> got data on client port not from any known connection: 10.0.0.10:1849
---
(SSB2)
---Code---
Connection request from 10.0.0.12:1031
Invalid login from 10.0.0.12
Connection termination from 10.0.0.12:1031
---
I have run subgame to make sure my biller settings are right and it works with the usual settings. The difference that I am working about is the ServerID and ScoreID settings with subgame that are not in AS3.

There are errors in my code tags that shouldn't be...

[Solo Ace]

Sorry, no idea, but after seeing this thread I must say someone really has to fix the use of multiple code boxes in one post (not sure if my post fixes this weird page lay-out heh)

[Purge]

In the global.conf you must add the ServerID and ScoreID keys there under [Billing]. Make the ScoreID the same as its listening Port and the ServerID to what you want. Also, in SSB2's subbill.ini make EncryptTraffic=0.

[Smong]

The loading error is to do with <py> exec, just comment it out of modules.conf (this is getting to be a common error).

The billing module is for a TCP biller, which there aren't many around at the moment. I think tehsu got billing_ssc patched to work with a variation of catids biller. I don't know the specifics or if the patch made it in to 1.4.0.

Edit: purge, I just tried what you said and catids biller still says bad password and drops the server.

[Cyan~Fire]

I dunno about 1.4.0, but Smong, when I was running a biller for you guys on SSDT, it was SSB2 (clean source) and connected fine. You sure you had EncryptTraffic=0?
_________________
This help is informational only. No representation is made or warranty given as to its content. User assumes all risk of use. Cyan~Fire assumes no responsibility for any loss or delay resulting from such use.
Wise men STILL seek Him.

[Purge]

I'm pretty sure it works on 1.4.0 - I just tried it.

[Smong]

After some experimentation I found the passwords were different (oops). Also Comms:EncryptMode=1 is ok and the ServerID/ScoreID can be anything, they just have to be present in global.conf.

[Hunner]

Fixed the code tags... kinda

Okay. I didn't see any mention of adding the Serverid Scoreid to global.conf in the docs though it passed through my mind to check. Also I had encryption set to 0 because I think I remember reading something about that interferring.

I commented out the two python modules (they both gave me errors) and I will check my python install to see what's up. I added the IDs and left encryption on 0 and it all worked. I tested changing enc to 1 and it didn't work.

Now I just gonna get python working and I will be happy.

Forgot to say that I am using 1.11j of SSB2

[Grelminar]

Thanks for the details of that error ("unable to locate component..."). I realize why it's happening now, and I'll try to fix it soon.

Next, the python stuff: to use "<py>exec", you have to have python installed somewhere on your system, in addition to using the pymod module. It should be be the same version that I built pymod.so with (2.4.1), and it should be in /usr. If you have 2.4.1 installed in another location, you'll probably have to set PYTHONHOME, as the error message indicates. Of course, if you want to use a different version, you're always able to compile pymod.so against that version yourself.

I'm changing the default config file to have the python stuff commented out, so at least it won't cause problems initially. You should comment it out also.

I see that other people helped with the billing questions. That's good, because I don't know what could be going on there (I've never used SSB2).

[Grelminar]

I made a fixed windows version. Get it at http://sscx.net/asss/asss-1.4.0p1.zip

[50% Packetloss]

wow. What/where was the problem? Looks like you completely fixed it. <3
_________________
Current Terror Alert Level

[Grelminar]

A linking bug. I link the dll in such a way that they're missing some library functions, and load them from asss.exe at runtime. Basically, I make the dlls dependent on another dll, except that the other dll happens to be named "asss.exe". This all works fine, except that when I changed the makefiles to build all object files and binaries in a separate directory, I accidentally ended up linking the dlls in such a way that they were trying to look for a dll named "../build/asss.exe" to load their functions from. I didn't notice because I tested it right after I built it, and that file did exist in that location for me. The fix was to change it to look for just "asss.exe".

[CypherJF]

Someone should update wiki if not already done.
_________________
Performance is often the art of cheating carefully. - James Gosling

[i88gerbils]

Done.
_________________
Oldbie Server Help