reviving a somewhat older windows server, have some questions - Page 2

provocating · #1 11-17-2013, 01:02 PM

I am of limited help since my server is on Debian, but what O.S. is this and is it a fresh install? Where did you snapshot? Before or after the MySQL install?

khalathas · #2 11-17-2013, 01:05 PM

Incidentally, just to give specs, I'm currently running vmware workstation 10, windows 7 ultimate x64 with sp1, allocating 8gb of ram to the vm, with 2x dualcore cpus to the vm (I have plenty of hardware on the host machine). 60gb virtual hard drive. I am not patching in any way before the install of mysql. This is as fresh as it gets off the win7 install disc (an ISO I got through my MSDN subscription).

khalathas · #3 11-17-2013, 01:06 PM

The snapshot is immediately after win7 itself finishes its install. There isn't a single bit of post-install modification on it.

provocating · #4 11-17-2013, 01:10 PM

x32 or x64?

khalathas · #5 11-17-2013, 01:12 PM

OS is x64, I need that for the amount of RAM I'm allocating. I'm using the 32bit installer per the instructions in the server guide.

provocating · #6 11-17-2013, 01:15 PM

I see no reason to use the x32 bit of MySQL unless I am missing something. Revert your snapshot, install the x64 and try again. Also just for giggles disable the Windows Firewall.

wolfwalkereci · #7 11-20-2013, 03:15 PM

Sounds like you have really been thrown some bad luck here.
Hope you figure it out, I'll watch this thread for a few days in case you have more issues that I might be able to assist with.

khalathas · #8 11-17-2013, 01:16 PM

I'll give those a shot. I ONLY used the 32bit versions because the guide said to, and I've successfully used the guide to set up the server before (and had quite a bit of enjoyable playtime out of it). I do prefer using 64 bit when I can unless there's a specific reason not to.

khalathas · #9 11-17-2013, 01:20 PM

Hah. 64bit worked first try. I guess the 32 bit installer truly hates 64bit windows. I think I will keep the server as a vm and proceed with the rest then.

khalathas · #10 11-17-2013, 01:23 PM

speaking of ram, I wonder how much ram would be necessary cumulatively to run every single zone as a static, and only have dynamics for instanced content...

provocating · #11 11-17-2013, 01:57 PM

My personal findings, and this is just me....I had problems with static zones. Memory wise they did not tax my server at all, it was an issue with the day/night cycles and maybe a few old peq scripts that need TLC, the zone logs got huge and that told me the server was constantly having to write to these log files. Other zones would randomly shutdown and I think it was script problems, I run vanilla PEQ. I run a pseudo dynamic / static zone thing where the zones stay open for maybe an hour, then close if they are vacant.

khalathas · #12 11-17-2013, 02:01 PM

hmm..well what I was running was statics that contained any valid rare/named/group/raid targets that my friends and I were actively interested in. If it were too high or too low, I just kept 'em dynamic. Then again I'm also planning on those vsphere boxes and spreading the zoneservers out across them.

provocating · #13 11-17-2013, 02:20 PM

I may go back to statics but this time I will start with classics and run them for a while and weed out the bad zones, then go from there.

khalathas · #14 11-17-2013, 03:50 PM

Gah I could kick myself right now. In my frustrations last night to reinstall mysql I backed up the peq database, but I was still using the older system that used a separate peqlogindb database and forgot to back up my accounts. I still have all the character data, but now I gotta rebuild the accounts in the correct order so they attach to the character data properly >.<

provocating · #15 11-17-2013, 05:11 PM

Unless you have a ton, it should not be a major endeavor.