CWE with MOSS

[dragosserban]

I am trying to connect to my MOSS server but I can't get it to work correctly.

If it let it patch, it goes into an infinite loop where it downloads a temporary file and launches that which in turn downloads a temporary file and ...

If I disable the self-patcher, it goes to Updating URU and then complains it couldn't download some file from the server. The MOSS logs are not very helpful there either.

If I disable the whole patcher, the client gives me an access violation right after login:

UruLive.Live.1.897 - External.Release
Exception type: Access violation
Call stack (14 levels):
0x00000000
0x00000000
0x00000000
0x00000000
0x77C7B3FC
0x77C7B429
0x77721194
0x0087F478
0x00464379
0x00462F18
0x00461E09
0x00461C2A
0x0076D6FB
0x0512970D

I did all the steps in the wiki. Any ideas?

[Mystler]

Installing the newest Nvidia PhysX driver should solve the problem, afaik.

[dragosserban]

PhysX is not a problem. I was able to connect to the official server, so I assume it's something that I either screwed up in the code (unlikely), or with the MOSS data files.

[Mac_Fife]

No, the issue here is that the latest available PhysX SDK (that you can download from the nVIDIA website) is 2.6.4, while the original MOULa version was 2.6.0. The 2.6.0 driver is what gets installed if you used the MOUL, MOULa or MagiQuest Online installers to install PhysX.

A CWE client, built using the 2.6.4 SDK will detect that the driver on your PC is "out-of-date" and try to run the installer. But the installer that you have will likely be the 2.6.0 one, so once it completes, it'll still be out-of-date. Hence the infinite loop. Mystler is right, installing the latest PhysX driver (or "PhysX System Software" an nVIDIA prefer to call it) should resolve your problem, and it won't adversely affect your MOULa installation. There's more about this in the Technical Note: http://wiki.openuru.org/index.php?title ... CWE_Client

[dragosserban]

That's what I meant. I was able to connect to the official server using a build of CWE which I compiled against the PhysX SDK. However it doesn't seem to like my own server for some reason. I have the latest driver installed. The loop was for the patcher, if it were PhysX, shouldn't that happen after login?

[a'moaca']

A loop in the patcher sounds like the file server manifest is wrong. If it downloads the compressed file, and the checksum matches, it decompresses it. But if the decompressed checksum doesn't match, after restarting it will download the file again, decompress, restart, etc.

Not sure what else it might be without more data. You can change MOSS's log level to something more verbose. If you set "file_log_level = MSGS" it will log every file requested in moss_file.log.

If you need to see what the server actually sends, I suggest the Wireshark plugin. The file server traffic is unencrypted so it's easy to check on.

- a'moaca'

[dragosserban]

Thanks! I will try rebuilding the manifest. Is it enough to do External.txt / ExternalPatcher.txt / ThinExternal.txt or do I need to do the whole structure again for all the files to be okay?

EDIT: Looking through the log files, it seems that I set auth dir to auth/default instead of auth so it tried to get the encryption key from a path that didn't exist. Let's see if this fixes the crash.

EDIT 2: Nope. But at least rebuilding the manifest fixed the loop. The access violation happens right after

1302980892.627770 INFO auth.c0a83865:55409: AcctLoginRequest for dragos (os: win)

so I assume it has something to do with the database not being set up properly maybe?

Wohoo! It works! I rebuilt the manifest and copied everything over again. Guess that was it

[MercAngel]

ok what about UruLauncher stuck at checking for patcher update and just sits there for hours

[a'moaca']

Probably a bad key.

Make sure the public key you've compiled into CWE goes with the private key you've configured in moss.cfg. If the keys aren't a matched set, the server gets garbage when decrypting the client's message and throws out the connection (there is nothing else it can do). I think UruLauncher ought to respond better to the connection closing, but anyway...

You can tell from the MOSS logs. If moss_gatekeeper.log reports an unknown message type ("Unrecognized gatekeeper message"), this is the problem. Unfortunately, it looks like this is logged at the "NET" level and the default is "WARN" (which means it won't log the complaint). Set "gatekeeper_log_level = NET" in the moss.cfg file and reload the configuration, before trying again.

A different way you could have a key mismatch is to do all the compiling and setup right and then have UruLauncher talking to the MOULa server. So check on that. If there is nothing at all about your connection in moss_gatekeeper.log this is probably what's going on.

Finally, if you had a bad key problem and had to kill UruLauncher with the Task Manager, you might end up in a situation where UruLauncher just does not even try to talk to the server, and the only solution I know of is to reboot Windows. Grar. This doesn't happen to everyone but it does happen to me.

- a'moaca'

[MercAngel]

i tried to change log type i get Invalid gatekeeper_log_level: NET
i get this on all the log stuff