Minilogin - cannot see local server
 

Hello,

I installed a mini-login setup this evening using, primarily, the wiki guide aimed at mySQL5 usage.

I obtained the most recent copy of mySQL5 plus tools, ActiveState's Perl 5.8.8 plus added modules, minilogin 0.6.2, the full 300M mappack, peq rel 12/25/06 plus quest pack. The MSVC*71.DLL libs were already present in my system32 directory, so I skipped those.

Got everybody installed, the database setup, although I had to work around some of the items like account insertions. I ended up leaving only one account in place and gave it a name of cutterjohn, a password, and the local private ip of the machine to be played on(also running the servers) as it's minilogin_ip addr.

When I attempt to login with a brand spanking new titanium install, I can get to the login screen, enter the account name and pw, but then have no servers listed in the list. I have checked the other threads related to this and have tried using various combinations of 127.0.0.1 (for localhost) or the actual private IP that I use for the machine, but none of that seems to make any difference. (That was what appeared to make a difference to other people in the older threads...)

(As a side ntoe the same machine is running Mysql, perl, the eqemu stuff plus the client. 2G DDR-400, socket 939 Athlon x2 4800+, win2k.)

My world log looks like:
Continued in part 2, as I hit the character limit for a post otherwise!

rest of above
 

my other server log window


my eqemu_conf.xml is as such:
and my LoginServer.ini as:
my eqhosts.ini has been changed to contain 127.0.0.1:5999

This may not be of any help, but on:

Loginserver.ini

loginserver=192.168.0.11
loginport=5999
worldname=My Minilogin
worldaddress=192.168.0.11
locked=false
account=
password=

You said you have tried various combos, but to verify:
Have you tried changing these to 127.0.0.1?

I'm not very good with the setup, so this probably isnt the issue. I consider my ability to setup a server 50% luck and 50% uhm..well, luck.

Yep, unfortunately I believe that I tried just about every single combinations of addresses possible to no avail. (Spent about 2.5h tinkering around with various settings after the .5h initial install and still no go...)

But, I will try again shortly, but I'm not thinking it'll work as I'm sure that I already tried that combo too... Sort of why I posted just about everything I could lay my little posting fingers on, hoping that somewhere in that mess was a sparkling little clue that I entirely overlooked...

I'll edit the post again after I try a few other things too... taking a short break ATM...

Oh well, couldn't edit the previous message any longer, but I went back and checked, and I had already had it set to try using 127.0.0.1 in the loginserver.ini.

Decided to load up everything again and give it a try, but still nothing shows up in my server list once I login...

Giving up for the night though...

Personally, I wouldn't use the 127.0.0.1 for anything. While it is the hard address for localhost, I find using my actual IP works much better. I haven't run everything on one box since my first week (you know, had to spread the work over my server farm here;) ), but if you haven't tried yet, use your own machine IP for all values. "localhost" seems to work for mysql/database settings, if the world/zones are running on the SQL server.

There's a nice Wiki by Crabclaw that might help. Started me off right way back when.

http://www.eqemulator.net/wiki/wikka...iniLoginConfig


Edit: Hey, guess what just happened to me? Empty server screen. I was changing over to PEQ database to test the Fabled Crush loot thingy, when I saw no servers. :O Looking into it, I saw the variables table, LoginType was set to Public (from when I ran a server), so Minilogin didn't show up. I changed it to "minilogin" and now all is well.

And I had to add a column to table: account for minilogin_ip, and set it to my machines IP address - but I imagine you already did that one.

Not sure if it matters but your worldname in eqemu_conf.xml and loginserver.ini are not the same name.

Ah! Hah! You WERE right in a way. I followed the mySQL 5.0.23(?) setup guide under the server section as I wanted to use a recent mySQL version.

I copied and pasted the list of INSERT queries to the variables table, and NEVER checked them!

So, after reading about your comment wrt LoginType in the variables I went and checked it to find the %#^&^*&@%*&@$%7!!!! EMPTY!

So I tried the guide suggested copy and paste all INSERT query into the query browser, bang complains about duplicate ailevel. Ok, so I remove it try again, still complains about it. Look at the variables table, and only ailevel is present. WTF?!

Short story ended up adding all of those(for now) individually via query browser. (Should've dumped 'em into a text file and fed the via the CLI interface, but oh well...)

Bang! My server is now listed!

Haven't logged in and tried making a character, but will do that shortly...

Must also remember to go back and check everything else that I did through that POS query browser. (mySQL's own GUI tools suck badly...)

As to running everything on one machine, I figure it's more than capable of handling it. Even the initial peq database setup was only pushing it to about 25% utilization on ea. core, and with the 5 zones, I still see less than .5G of total memory usage... I'd run it on another machine if I had one with enough memory to bother with. I have an old 1G T-bird, but it has no drives and only 256M... also sitting as a bare mb + cpu + memory stick...

1H later,
well, you were also right sort of, in that I had to go change all of the listed IP addresses to be 127.0.0.1 . I suppose that localhost should work as well as it SHOULD be directly mapped to 127.0.0.1 anyways.

(I found the above, as while I could see the server and login it would kick me out with a log message telling me to verify my account in the account table. I did so, and created a second test account with the same results, then tried changing all of the IPs. I'm, obviously, not 100% sure that they ALL needed to be changed but it worked for me and allowed me to create a character.)

Now, I just have to figure out why my movement keys aren't moving me...

Make sure in variables table, the Rules value is empty. If there is data in this (even a space), your server will not allow any clicking or moving until you type #acceptrules. It's a way to prevent people from coming to >your world< and whining about how you choose to run a server. :)

Either that, or in your account record, rulesflag field, set it to 1.

Good to see you got it sorted out.
J

Yeah, I just happened across that little item on cavedude/sesmar's forum. I didn't have a rules row in my variables table, but I started the game up again and tried #acceptrules which allowed me to turn left and right now, but not forwards or backwards.

Prior to that I could click and interact with things AND sit down... need to go check the db again, and more digging, I imagine...

Also, keep on mind, some of us have problems with version EQEmu-0.7.0-941. one of the symptoms is, when you log into the zone, you can't move. The way to know for sure is, back down to an older version, like 940

Yep, almost beat you to it again, as I saw that mentioned either here or on Cavedude/Sesmar's forums and just checked which one I grabbed... 941...

Should I try an even older one that 940, or should 940 just do the trick?

Actually I prefer 933, because most the quest globals features were working then - So I'd say 933.

Well, I just jumped the gun and grabbed 940, renamed my old directory copied the maps, quests, startup batch file and the 2 config files over to 940. Installed the 2 IIRC minilogin files, ran it, logged in, and BANG! I can move my char forwards and backwards!

Does 941 work for anyone? If not, I really think that they ought to retract it's release status...

933: IIRC that was the one that cavedude recomended and said that he used on sesmar.net, but if 940 works ok for me I'll just go with it as I've nothing to lose at this point, other than more time... :D

Thanks for all the help.

EDIT:
oops missed the part about the quests, maybe I'll go grab 933 now then... :D

940 is fine, just has some issues with quest globals is all, but if you ever use my database, you might miss out on some cool stuff.
In fact, here's my version of 940, I've been using it all week and it works fine;
http://www.nahunta.org/~angelox/file...940-source.rar
It's source, so you'd have to get someone to compile the executables for windows.
what i did was, revert the quest globals part of the source to what it was at 933 - the rest is 940.