reviving a somewhat older windows server, have some questions

[khalathas]

Hey all, I was running a private server for just a few select friends a year or so ago..interest waned and I shelved it for a while. Didn't delete anything, or move anything..but the server was running on my main machine, which I kept using and updating.

I decided I wanted to revive my server and play a bit again, but for whatever reason, the loginserver kept crashing within seconds of launching. I looked at version numbers and decided there were enough changes that rather than try to fix the problem, a full rebuild would be easier, so I went through the guide (again), compiled everything successfully, and got to the part where I set up the database. I know I could drop system and import the new one..but before I do that (yes I backed up as well), I wanted to just generally ask about how drastic the changes have been since roughly rev1900 to rev2500ish. Is it going to be relatively viable to move forward or should I just back up my account/character data and re-source the entire thing from scratch, then restore what I want? Also, should I be worried about client compatibility? I was using SoD prior.

[provocating]

At this point if it were me, I would backup everything. Install everything from scratch and make sure everything works with a new character, maybe even play a bit to make positive there are no issues. Then I would just create some SQL statements to move the accounts, characters and such over.

[khalathas]

Thanks, I think that's probably what I'm going to do. I've already backed up the database, and then I've gone further and selectively dumped individual tables (or in some cases, just specific data sets from those tables) to sql to restore. Was hoping not to have to do that, but it looks like the changes might be too much to easily just keep jumping upwards by upgrades/revision imports.

I am going to try to just drop the system and keep accounts intact first..unless there have been major changes to those tables as well?

[provocating]

Well the best thing to do is try it. It will tell you pretty quick if there are problems, monitor those error log files.

[khalathas]

Well, as it turns out, apparently the login server is still crashing when the world server finishes loading zones and connects to it.

Problem signature:
Problem Event Name: APPCRASH
Application Name: EQEmuLoginServer.exe
Application Version: 0.0.0.0
Application Timestamp: 4d03c97f
Fault Module Name: LIBMYSQL.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4f8bcacf
Exception Code: c0000005
Exception Offset: 00009b3a
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

[khalathas]

I didn't rip out all the installs and reinstall them from scratch, so I am backing up the current db, ripping everything out from the roots, and going 100% from scratch this time around, then I'll just source my backup db which contains the updates.

[khalathas]

Welp, got stopped in my tracks. uninstalled (and even manual purged) mysql, in prep to reinstall the correct version..
Installed correct version, got to configure it, and it can't start the service. Can't start it manually either. I've even gone through it a couple times uninstalling, purging the data folders manually, purging the service registry keys manually, etc...still can't get it. I think this machine is hosed as far as mysql goes, unless I wipe and reinstall windows. I'm going to move the whole thing to a virtual server for now until I build my dedicated box for it I think. Unless anyone knows how to get around that service issue...

[provocating]

I do both of my servers as VM's, there are so many advantages to it.

[khalathas]

Honestly I'm hopefully on the verge of a new job where what i want will be possible...so if that happens I intend to actually build 3-4 physical machines that actually support vSphere, and then run VM servers for various purposes, and actually have the zoneservers spread across the physical machines as well. I guess this might end up being my solution for now and then it'll just be portable to the vSphere machines when they're built.

[khalathas]

Apparently I'm stopped in my tracks yet again. Brand new server 2008r2 standard VM, and mysql again refuses to start as a service. I'm at my wits end on this one, and I've done this successfully all before. Anyone know how to deal with this mysql error log?

131116 17:23:15 [Note] Plugin 'FEDERATED' is disabled.
131116 17:23:15 InnoDB: Initializing buffer pool, size = 2.0G
131116 17:23:15 InnoDB: Error: cannot allocate 2147500032 bytes of
InnoDB: memory with malloc! Total allocated memory
InnoDB: by InnoDB 30993228 bytes. Operating system errno: 8
InnoDB: Check if you should increase the swap file or
InnoDB: ulimits of your operating system.
InnoDB: On FreeBSD check you have compiled the OS with
InnoDB: a big enough maximum process size.
InnoDB: Note that in most 32-bit computers the process
InnoDB: memory space is limited to 2 GB or 4 GB.
InnoDB: We keep retrying the allocation for 60 seconds...
131116 17:24:15InnoDB: Fatal error: cannot allocate the memory for the buffer pool
131116 17:24:15 [ERROR] Plugin 'InnoDB' init function returned error.
131116 17:24:15 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
131116 17:24:15 [ERROR] Unknown/unsupported table type: INNODB
131116 17:24:15 [ERROR] Aborting

131116 17:24:15 [Note] C:\Program Files (x86)\MySQL\MySQL Server 5.1\bin\mysqld: Shutdown complete

[khalathas]

Ok, after making my 2nd vm and testing it yet again on a fresh install of win7...I'm forced to conclude that the problem is with mysql-5.1.72
I've found a copy of the 5.1.68 installer (since it isn't available on oracle's official site), and am trying that next.

[provocating]

They have most all of there old GA releases available on the MySQL site so you should have no issues finding old versions.

[khalathas]

weird, because I went to the old GA archives and it only offered me .72
either way I've got a fresh VM now, with a snapshot AT its immediate post-install state so I don't have to uninstall, I'll just revert to snapshot on failure...but I'm going to figure out why mysql hates me.

[provocating]

Snapshots rock.

[khalathas]

wow...I clearly have something wrong. Fresh vm, fresh 5.1.68, still have the "cannot start service" error on install. No clue at this point, and on the verge of giving up.