Tag Archives: frustration

ahhhh! now we find out…

my newly redesigned site uses the enfold theme, which has faulty (under certain circumstances) caching and optimisation routines, so we use lightspeed cache, which doesn’t have those (particular) faults, and works better (under certain circumstances).

except, last year, prior to my site being redesigned (when i was still using the avada theme), i was told (by SOMEONE) to disable lightspeed cache, because it had some sort of incompatibility with… something…

so, i went through the site redesign with a disabled lightspeed plugin. no problem, until i put in the enfold theme, and whatever circumstances that cause the caching and optimisation routines to fail, were happening, which was the cause of the first go-round.

turning on the lightspeed cache fixed the first go-round, but whatever incompatibility i was trying to avoid by having the lightspeed plugin disabled, took effect, which was the cause of the second go-round.

which was further confused by the fact that part of my routine for fixing the first go-round was good enough that it fixed the second go-round well enough that i didn’t find out about it until it was too late.

what i found out, today, via my web developer, is that the people who make the lightspeed cache and webhost python (my host provider) have their own battle going on: on webhost python’s servers (which include mine), the lightspeed plugin causes expired transients to multiply and duplicate. lightspeed says it’s python’s fault. python disagrees…

on the record…

OFF the record, python agrees that there is a bug in their system that they haven’t found yet… compounded by the fact that it was THEIR ERROR which caused the third go-round… 😠 but it’s not for me to say “i told you so”, especially with my already somewhat precarious position with this particular host provider…

and so, i’m caught in the middle. 😒

apparently, for the time being anyway, the plan is to disable the caching modules on both enfold AND lightspeed, keep an eye on the database (which hasn’t blown up since implementing this plan), clear the expired transients manually, and examine other options for a cache.

😒

oy! why won’t this just go away?

at midnight (which was 3:00 in the morning, florida time), i got a message saying that the database was blowing up again. they said it was 183 GIGABYTES

because of the fact that i was asleep (thankfully), i didn’t actually read the message until 7:00 my time (10:00 florida time). i immediately logged into my web server, and discovered that the MySQL disk usage was lower than i have ever seen it before, which is to say 253 MEGABYTES

what this tells me is that there’s something else going on besides this whole “enfold-theme-not-caching-correctly” horseshit.

which is bad.

it also tells me that, whatever it is, we haven’t actually found it… we may have found another problem, but not the one for which we’re looking… yet…

which is bad, but not as bad as it could be.

it also tells me that, whatever it is that is going wrong, the cronjob that we put in place to solve the problem, works, REGARDLESS of the actual problem.

which is good.

but, when it comes right down to it, it is not good for me to be so stressed out about something over which i have very little control.

which is bad.

something has to be done. this is ridiculous.

oh, but it couldn’t have ended there, now, could it?

and the answer is, a big, fat, OF COURSE NOT! 😒

i woke up this morning, and couldn’t log in to my web site… at, like, SEVEN in the fucking morning, i was wide awake because i couldn’t log in to my web site.

at NINE, the web designer gets back to me. he can’t login either. apparently the host provider has disabled the config file that makes everything work — i login using SSH, and there’s the file… everything LOOKS okay, but… the host provider apparently did SOMETHING to my web site. as far as i can tell, everything works, sort of, until you get one or two pages deep, at which point it gives me a “unable to connect to database” error.

😠

so, i file a ticket with the host provider. a couple hours later, (all the while, i’m sweating bullets) they get back to me, apparently, the database blew up AGAIN. they disabled the config file so that nobody could use the web site, because the database was growing by gigabytes A SECOND.

😠😠

eventually (seriously, they took most of the day to UN-disable the config file), the web designer went in and turned off everything having to do with the built-in, screwy, does-not-work, enfold caching and optimisation routines, turned OFF “store transients”, and set a cronfile to delete three rows of a table in the database, every hour.

😠😠😠😠‼‼‼

this better be the last of it for a while, because i’m just about ready to throw in the towel.

databases

my first direct experience with databases was in the late 1980s or early 1990s, when i got a “job”, “working” for this… guy…

i don’t remember his name — possibly “henry” — but i remember his attitudes: he was always right, nothing he thought of had ever been thought of before, he was the richest, smartest, trendiest, most “on-top-of-it” dude that ever hit the face of the planet, and GAWD HELP YOU if you EVER got in his way.

needless to say, the “job” didn’t last long. it started with him demonstrating how generous he was, by buying me a disk caddy, so that i would have somewhere to keep all of the disks i was going to accumulate working for him. then he started asking me about computers. at the time, i was NOT a “computer geek”, nor did i want to be one (my father was one of the original “computer geeks” and i DID NOT want to be like my father), but i knew about computers because i had been working as a typesetter for a few years. he asked me what i didn’t know about computers, and one of the first things out of my mouth was “databases”, so he signed me up for a week of training with “FileMaker”…

what i learned was a bunch of recycled stuff from my already ample knowledge of microslut word and excel, with a bunch of “hypercard-like” stuff which i sort of vaguely understood (but nobody i knew used hypercard for anything, so i never really knew what i had missed until years later), and, at the same time i was doing this training, i was helping this… guy… clean out his house, because he was going through a divorce, or some awful shit like that, and he, basically, had to move EVERYTHING that was “his”, out of one house and into another, that was a few houses down the street…

which is where i learned that his “rich” persona was heavily financed by several HUNDRED overdrawn credit cards — he had been using one credit card to pay off another credit card, and when he ran out of credit cards, he would just start up a new one, and use it to pay off the previous ones… FOR YEARS… — at which point i decided that working for this guy might not be such a good idea, if i wanted to get paid.

quite apart from the fact that working for him was REALLY annoying…

so, ultimately, i spent a week learning really complex software that i never got to use for anything, and that was it, until i got my job at software.com, testing email servers, in 2001.

and, for all of my work with databases at software.com/openwave, i still don’t have a really solid grasp of what they are… where they “live”, what they do, how they work… anything… all i know is that, under the right set of circumstances, you can give “commands” to a database, and it will perform certain functions with a variety of different “objects”, the outcomes of which can be used in a multitude of different ways, depending on what is contained in your database.

i get the impression that databases are a lot like the world wide web, in that they both have a lot of objects (web sites) that are linked together in a somewhat-haphazard, but definitely organised way.

so, you can imagine that it was something of a surprise when, the other morning, i woke up, checked my email, and discovered two somewhat alarming notices. the first was warning me that i had used up 90% of my disk space on my server, and the other was warning me that a “table” on my main database was malfunctioning… or something… and collecting 251 GB worth of data… which, somehow, was NOT showing up in my cPanel, which says “Disk Usage 18.43 GB / 292.97 GB”…

and, of course, it happened on a sunday, when nobody’s in the office, and on mothers day, when even fewer people are in the office, and during a PANDEMIC… 😒

so, first thing this morning, after waking up to a broken heat pump, and a wife who wrenched her back, i wrote to my web designer, who said, oh yeah, we’ve seen this kind of thing before, it’ll cost between $200 and $500 to fix it…

and I DON’T EVEN KNOW WHAT’S WRONG… 😖

yeah, woo… 😒

so, #SCROTUS has well and truly been impeached, but pelosi now says she’s not even going to send the articles of impeachment over to the house, because the house has said that they’re not going to follow through…

so we’re sitting here with an impeached president and nothing is being done about it, even from the people who impeached him.

meanwhile, he’s requested and been granted even MORE money for the wall, and for the “space force”, and he’s paying for it with massive CUTS in food stamps, SSI, and SSDI (which includes me), and there has been precisely no response from the people who impeached him, apart from mildly harsh words…

and there has been some protest, in a limited sort of way, but no mass uprising, which means that they are probably not even going to try…

and people wonder why i want to die. 😒