MMA is on a new server. Please read.

[Greg@GLD]

After repeated hardware failures in a short timespan, our provider has agreed to replace the entire box. As such, overnight MMA and all my other sites are now moved to a brand new Dell PowerEdge server. Like before, we have 4 processors and 2GB ram.

We are terribly sorry about lost posts and private messages. There is no way to recover them.

If you have tried to contact me the past two days and I didn't respond, please understand that I have been VERY preoccupied with this and lost all my recent PM's.

Things should be more reliable now and Kirk and I truly appologize for the problems.

Greg

[smokin'Red35th]

Glad you got things squared away greg. You da man!!!

[88Nightmare]

thank you for all your hard work greg... and other parties too that werent mentioned!

[Fast95Stang]

Thank you everyone!!

[smokin'Red35th]

man for a few hours there I couldnt get on mma, but my wife could. wierd

[SLOWZ]

Hey, you guys are providing us with a "home" to chill and all correspond, so as long as it's still here, I'm a happy camper!

[Greg@GLD]

We're still having "issues" folks. It may take awhile for everyone to see things "correctly"

If you come back here, and this message is gone, and you see "we are still having trouble" that is the old server...

[1slo5.0]

Put yourself in for a raise Greg!

[quietflow]

Thanks Greg! I thought it was just my computer that wouldnt let me on.

[smokin'Red35th]

Was it just now down again? havent been able to get on all night so far

[Greg@GLD]

Nope. You were probably resolving to the old box. This could continue for a few days...

[smokin'Red35th]

is there anything i can do from my end to keep that from happening. I know dawn is having that problem right now. wierd that i can get on but she cant. yesterday it was the other way around

[Greg@GLD]

When you say "can't get on" what exactly do you or her see?

[MrsSmokin'Red35th]

Haha I'm on now but now devin cant get on. LoL

It comes up with some page saying its down or something and to try back later

[Greg@GLD]

Haha I'm on now but now devin cant get on. LoL

It comes up with some page saying its down or something and to try back later


Ok, that means you have been seeing the old server Dawn.

This should clear up soon. So sorry for the problems.

I have only aged about 10 years this past week. :thud:

[Greg@GLD]

Just to add: The "users who visited today" is showing those who have been able to get to the new server today. The numbers are slowly returning back to normal. And things seem to be working faster than they have in a long time.

Dawn, If you want to upload that file for Devin, drop me a PM...

[Greg@GLD]

Symptom

You add or delete machines or servers but your changes are not recognized or do not take effect. Or in some instances the changes are recognized and at other times they are not yet in effect.

Probable cause

The most likely cause is that you forgot to increment the SOA serial number on the master server after you made your change. Since there is no new SOA number, your slave servers do not update their data to match that of the master so they are working with the old, unchanged data files.

Another possible cause is that the SOA serial number in one or more of the master data files was set to a value lower than the corresponding serial number on your slave servers. This could happen, for example, if you deleted a file on the master and then recreated it from scratch using an input file of some sort.

A third possible cause is that you forgot to send a HUP signal to the master server after making changes to the primary's data files.

Diagnosis and solution

First, check the SOA serial numbers in the data file that you changed and the corresponding file on the slave server.

If the SOA serial number in the master file is equal to, or less than, the serial number in the slave file, increase the serial number on the primary's file so that it is greater than the number in the slave file. For example, if the SOA number in both files is 37, change the number in the primary's file to 38. The next time the slave checks with the primary, it will load the new data. (There are utilities that can force a master to immediately transfer data to the secondaries, if you have one of these utilities you can update the slave without waiting for it to check the primary.)
Review the syslog output for the most recent named nnnn restarted or named nnn reloading nameserver entry. If the timestamp for that entry is before the time you finished making changes to the file, either reboot the server or force it to read the new data as explained in Forcing in.named to Reload DNS Data.

[1slo5.0]

Wtf???????????????

[orange67stang]

Wtf???????????????
X2

[Greg@GLD]

That's just some research information... Pay no mind... :D

[upngo50]

I just figured by that point you needed a mental break and paid no never mind to it, but I did read it with a WTF expression on my face..

[Tom]

There's a translation where the 'bad boys' hang out. :p Eh, I try. :rolleyes:

[smokin'Red35th]

Its working again for me, hopefully this time it will last all night

[Jesse James]

Working Great Guys! :shifter: Got the email, site loads quickly, no issues that I have noticed yet. :cool:

[Greg@GLD]

Thanks for the info James. On this end it seems things have finally settled down, DNS has refreshed on most ISP's and the number of visitors is returning back to normal levels again... :beer:

[Jesse James]

Page generated in 0.14699507 seconds (91.97% PHP - 8.03% MySQL) with 13 queries

:banana: :cool:

No problem Greg :rockon: The time shows one hour difference in your post vs Cali time when it used to be the same
"daylight savings?" It's all good. :cool:

Edit: after posting this time is the same, only my local time on my machine is different, it's all good. :thumbs_up

[BlackLX]

Looking great over here...I got an e-mail this moring from the site. Hopefully the bugs are all gone.