GoW client with MOSS

Discussions About MOSS (Myst Online Server Software)

Moderator: a'moaca'

Post Reply
rplawrence
Member
Posts: 7
Joined: Fri Apr 15, 2011 12:36 am
Location: Utah

GoW client with MOSS

Post by rplawrence » Sun Sep 18, 2011 12:09 am

I have been trying to make the GoW client work with MOSS and it does work if the client is ran with the '-LocalData' switch.

When the client is run without the switch I get a "Secure file preloader failed" popup after a successful login, on the update screen.
The ~/file directory is empty and the ~/auth directory has been rebuilt per the instructions given on the wiki.
Here is what the auth.log says:

Code: Select all

1316302668.770153 DEBUG auth.ae17c91c:28608: Connection: (client) xxx.xxx.xxx.xxx:28608 <-> yyy.yyy.yyy.yyy:14617 (server)
1316302668.770272  INFO auth.ae17c91c:28608: auth startup
1316302668.770691  INFO auth.ae17c91c:28608: Client version: 902 Release: 1 UUID: ea489821-6c35-4bd0-9dae-bb17c585e680
1316302668.770979  MSGS auth.ae17c91c:28608: Backend connection protocol version 0
1316302669.170653  MSGS auth.ae17c91c:28608: Setting up session key (fd 6)
1316302669.171574  MSGS auth.ae17c91c:28608: Sending nonce response
1316302669.171602 DEBUG auth.ae17c91c:28608: Session key for fd 6: 48B5D70366CE8A
1316302669.256196  MSGS auth.ae17c91c:28608: Received ClientRegisterRequest
1316302669.426724  INFO auth.ae17c91c:28608: AcctLoginRequest for login@my.domain (os: win)
1316302669.430693  MSGS auth.ae17c91c:28608: (backend) Login succeeded
1316302672.602451  MSGS auth.ae17c91c:28608: FileListRequest request for Python
1316302672.602540  MSGS auth.ae17c91c:28608: File server transaction 4 -> file Python.mbam
1316302672.687723  MSGS auth.ae17c91c:28608: FileListRequest request for SDL
1316302672.687812  MSGS auth.ae17c91c:28608: File server transaction 5 -> file SDL.mbam
1316302672.689460 DEBUG auth.ae17c91c:28608: Peer on 6 reset connection
1316302672.689523  INFO auth.ae17c91c:28608: Shutdown started
1316302672.689537  INFO auth.ae17c91c:28608: Server shutdown for reason: Client connection closed
1316302672.689889 DEBUG auth.ae17c91c:28608: deleting
I suspect that the problem lies in the auth files but I have no idea where. Any thoughts?

Rael
Member
Posts: 13
Joined: Thu Apr 07, 2011 3:31 pm

Re: GoW client with MOSS

Post by Rael » Tue Oct 11, 2011 3:52 pm

I'm currently having the same issue: I'm trying to find some solutions, but this doesn't look easy like the other ones...

Here's my moss_auth.log

Code: Select all

1318348424.405785  INFO auth.5d9068d2:53340: auth startup
1318348424.406017  INFO auth.5d9068d2:53340: Client version: 902 Release: 1 UUID: ea489821-6c35-4bd0-9dae-bb17c585e680
1318348425.695939  INFO auth.5d9068d2:53340: AcctLoginRequest for dra00@drateam.org (os: win)
1318348429.518839  WARN auth.5d9068d2:53340: Server tried to mumble to itself about SDL.mbam, but no one is listening.
1318348429.591999  INFO auth.5d9068d2:53340: Shutdown started
1318348429.592030  INFO auth.5d9068d2:53340: Server shutdown for reason: Client connection closed

Christian Walther
Member
Posts: 294
Joined: Sat Dec 13, 2008 10:54 am

Re: GoW client with MOSS

Post by Christian Walther » Tue Oct 11, 2011 8:30 pm

rplawrence’s problem was traced back to an empty line in the text file that Python.mbam was generated from, and fixed by https://bitbucket.org/OpenUru_org/moss/ ... ake-mbampl.

Your case however looks different. From a quick look at the code, the “mumble to itself” message indicates that the file SDL.mbam was not found (weird error message – funny but unhelpful :?), did you place it in the correct auth subdirectory (default or whatever you configured for the logging-in user)?

cjkelly1
Member
Posts: 34
Joined: Mon Dec 29, 2008 6:08 am

Re: GoW client with MOSS

Post by cjkelly1 » Tue Oct 11, 2011 10:18 pm

Christian Walther wrote:From a quick look at the code, the “mumble to itself” message indicates that the file SDL.mbam was not found (weird error message – funny but unhelpful :?), did you place it in the correct auth subdirectory (default or whatever you configured for the logging-in user)?
Funny and very helpful in the traditional Uru way.

"Something terribly has gone wrong. Head for the cover.", anyone? :)


CW is completely correct, of course. It is looking for the SDL.mabm file, and cannot find it.

Rael
Member
Posts: 13
Joined: Thu Apr 07, 2011 3:31 pm

Re: GoW client with MOSS

Post by Rael » Wed Oct 12, 2011 8:40 pm

I fixed it. I don't remember how, but I did it :P

Anyway, thanks for the replies :D This MOSSing is really getting frustrating. I need to create a more user-friendly setup guide...

User avatar
JWPlatt
Member
Posts: 1100
Joined: Sun Dec 07, 2008 7:32 pm
Location: Everywhere, all at once

Re: GoW client with MOSS

Post by JWPlatt » Mon Dec 12, 2011 4:17 am

Rael wrote:I need to create a more user-friendly setup guide...
How's that going? ;)

A product "wrapper" with complete guide and install automation (e.g., "[checkbox] Import Sharper's Journal") would be a valuable addition.
Perfect speed is being there.

Rael
Member
Posts: 13
Joined: Thu Apr 07, 2011 3:31 pm

Re: GoW client with MOSS

Post by Rael » Tue Jan 10, 2012 8:42 pm

That's not easy, as I expected. Now my client is stuck at "downloading" phase, so I'm going through the logs once again to see what's the issue... I have been on a break for quite a lot of time, so I need to get used to the whole system once again...

If I have any news, I'll post it.

Post Reply

Return to “MOSS”

Who is online

Users browsing this forum: No registered users and 1 guest