WordPress database error: [Table 'com0800608122374.wp_terms' doesn't exist]
SELECT t.*, tt.*, tr.object_id FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON tt.term_id = t.term_id INNER JOIN wp_term_relationships AS tr ON tr.term_taxonomy_id = tt.term_taxonomy_id WHERE tt.taxonomy IN ('category', 'post_tag') AND tr.object_id IN (17169) ORDER BY t.name ASC
I never had the experience, when I was younger, of a girl giving me a fake phone number so I couldn’t actually call her, but now a customer service woman from GoDaddy’s done it to me!]]>
And yes, Usenet lives forever. I once had some wisenheimer resurrect a comment of mine off Usenet some 20 years later on some forum I’ve never been to, and then the forum toadies spent a good long time kicking me and burning me in effigy because they didn’t like what I had had to say 20 years before. And scarily their goto method was to try and doxx me — as if that would put me in my place for daring to have a contrary opinion 20 years earlier — and even more scary was how bad they were at it. My name full name signed the post, and the best they were able to come up with was my LinkedIn page, which I have long ago given up for satire. The best part of all this was I didn’t even find out I was being mortally insulted in this forum until 2 or 3 years after this all went down when I happened to do a vanity Google search on my name (and all the clear links to me and pictures of my life and even my address and phone number (old, but don’t tell them that) where there for the taking from a simple Google search …)
Even here with my semi-obscurity, I know anyone who really wants to can trivially find out all about me based on the address (sorry, mitch4 — domain name!) it’s hosted from. Still, I would have been happier without a permanent link in Google…]]>
If goDaddy is just testing that a DNS change has propagated, that seems already done, and accounts for why they repeatedly think their work is done. In terms of testing, of course they absolutely have to just try raising the site in a web browser, as Bill has been telling them.
But then, in terms of testing for what’s causing the errors we see and they will see, I hope they focus on the MySQL backend connection, and the things that can go wrong there. One possibility is my odd hunch about internal DNS; but there could also be problems with authentication to MySQL or actual damage to the database at some point.
Errors with the MySQL database and how the server is connecting to it are not, strictly speaking, WordPress errors, though it’s related and could go under that label if it helps. But it should not go under that label if that is GoDaddy hosting support making an excuse that it is not their problem to solve anymore.
continued wishes for good luck!]]>
Next may be a cache on your local access point (in its role as “router”, to accept a common misnomer), and then a DNS server specified by your ISP, and then the DNS servers that one looks to as authorities, and so on. At some point an answer is decided on, and gets updated at each step back down the chain. It’s a little complicated as described, but that is what makes it a distributed system, and what allows it to function without bogging down the root authorities, as would happen if all queries had to be resolved centrally.
That business about using the latest answer you already have, if it is recent enough to not count as stale, typically may be around three days. This is why you sometimes hear that DNS changes can take that long to “propagate”. It’s not that transmission could actually take that long, but that there is a timeout involved. Nowadays it is generally shorter in practice, but your provider may say three days out of habit or to be safe.
And indeed, if your hosting company moves your site, for a while end users looking for www.comicsidontunderstand.com will not know it is at 184.108.40.206 and will be sending their requests to maybe 220.127.116.11 and not get a good result. Again, things have improved over the years, and now the old server is likely to send back a notice of permanently changed address, which will trigger the DNS chain to skip the timeout and force an update.
(to be continued)]]>
There are many things the Domain Name Service (or System) is used for, but a fundamental part of it is “translating” from a domain name, or hostname in a domain, to the numerical IP address associated with that name. That’s necessary for most communications on the internet, because the names aren’t really addresses (though people do say “web address” sometimes for a domain + hostname), and most messages or requests need to go somewhere specified by a real address, which is to say, a numerical IP address.
In comment 104, Ï was using a user-oriented tool called nslookup to look up the ip addresses for a couple of names. For “www.comicsidontunderstand.com” the answer was “18.104.22.168″. (There is other stuff in the command response, mostly about identifying the server that is answering the query.) For ” www.thewinnetkaclub.com” the answer was also “22.214.171.124″. I could also have asked about a hostname “ip-45-40-157-1.ip.secureserver.net” and the answer would have been that same numerical ip address.
There’s nothing actually wrong with that. A hosting company like goDaddy can have many customers with different domain names all sitting on one physical server which might have just one IP address. (Also they will have their own name for it, not connected to any client — like the “ip-45-40-157-1.ip.secureserver.net” in this case.) These are different virtual hosts, or vhosts.
If you type either “www.comicsidontunderstand.com” or ” www.thewinnetkaclub.com” into a web browser, it will send an http request for a web page in both cases to the same place, IP “126.96.36.199″. The names were used to get the IP address, but weren’t totally discarded after serving that purpose. The name is sent as part of the request, and the web server software at “188.8.131.52″ will use the transmitted name to figure out which customer vhost files to send back.
If you plug in just the numerical 184.108.40.206, or the hosting company’s native name for ther server “ip-45-40-157-1.ip.secureserver.net”, into the location bar of the web browser, what happens? It just depends on what their setup is. In this case — give it a try. Whoa! I get The Winnetka Club. That means they are sort of the most-favored child — the default vhost.
(to be continued)]]>
I started looking at usenet groups again about a year or so ago. It was really surprising, even shocking, how much the traffic had declined.
RACS had always been fairly low-traffic, but there was a dedicated core. Now there’s almost nothing. A couple of guys like to track which which comics are in reruns/reuse.
RASFW was a high-traffic group when I left, although it always had a large portion of that was off-topic crap. Now the traffic is low and the off-topic crap is almost all of it.
Right now I follow RACS and RASFW via Google Groups and that’s it. I will be retiring from Megacorp here in a few weeks, and I haven’t decided whether to up my participation in usenet or not. At its peak, there wasn’t anything like it and there hasn’t been since. Probably reddit is as close as you get to centralized discussion on a wide range of topics.
I miss fun little groups like alt.fan.tom-servo. They were kind of the canaries in the coal mine. When those began dropping below critical mass, I knew things were turning. Today, some are doing . . . okay I guess. But it’s kind of like the mall where a few stores that face out to the parking lot are in business, but the interior is a ghost-town. The future ain’t bright.]]>