debian server - out of ideas

[trevius]

Also, for Public at least, you need to forward port 9000. The simple way to tell if your problem is port forwarding related or not is to set your server as a DMZ in your router. Most routers have a setting to allow this. If you set it to a DMZ and they connect fine, then you just need to disable the DMZ setting and keep playing with your Port Range Forwarding. Also, make sure you are using the Port Range Forwarding and not just Port Forwarding. Normally, you would want to forward ports 5998, 7000-7100 and port 9000 at least. Also, 9080 is a good port to forward if you want remote access to your server admin webpage, but it is not required.

Make sure that if you do try the DMZ setting that you disable it after you are done, because it increases security risks by leaving it open like that permanently. Also, if DMZ still doesn't let players connect, then maybe you have another issue like a firewall or something that is blocking them on your server. The default install of Debian shouldn't enable any firewalls, at least not the etch install. But, if you enabled any on your own, it could definitely cause problems.

[Jurevicius]

You guys are awesome, simple enough oversight by me. Opening via udp was the issue. Sorry should have been more clear it's not a home server but hosted. Oddly enough it didn't work initially, but going back to the iptables showed after adding the udp for the 7000 range ports that the description read something of a fileserver something or other. Changing the range in the config and opening those ports did the trick.

Now I just need to get the ax classic database working with it and I'll be in business Seems to be loading the zones but say unavailable when logging in. But, that's for another post when I get home and have a chance to post that error log.

Thanks again!

[Jurevicius]

As I mentioned before, I am trying to work through getting the ax_classic working on my server. Basically getting a bunch of cannot load item errors. Realizing I am using two different versions of each, essentially a newer emu than the database.

I went through the changelog and sourced in all of the required updates since about before the latest classic db. Coming up with some duplicate returns but plenty of accepted changes.

So now the logs show it loading items properly and everything, but still not able to log in due to "that zone is unavailable" error. Looks like i've got rid of all the errors accept one. Happens every-time I hit enter world.

Zone error log:
4601 [07.16. - 22:44:56] Loading spawn groups failed.

This is probably more general of an error I imagine and could be a number of missing things due to the updates.

But, is there any place I might be able to look at to fix this one? Any tips would be a huge help!

[Shendare]

The only think I can think of at the moment regarding that error message is that Spawn groups were updated to accomodate the new instancing features in the Emu code.

Specifically, the 'spawn2' table had a 'version' field added.

Let's see... looks like it was part of 612_instance_changes.sql.

Does your spawn2 table have the 'version' field after the 'zone' field?

[Jurevicius]

Dead on that was it, I didn't have that one sourced in. I was taking the short road and importing them by phpmyadmin which on that one threw back a duplicate error and didn't finish the rest of the source. Sourcing it through command line got the rest in there.

I got logged into the game just fine, but unfortunately I looked around and none of the NPCs are popped. No errors in any of the logs so it's a Little puzzling.

I will go back again tonight and make sure all the updates got sourced in properly if that's the best way to approach it.

Thanks again