Category Archives: stress

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.

maybe i was a bit hasty…

it’s definitely “not all bad” living here, but things are definitely NOT “normal”, by any stretch of the imagination.

we were supposed to have a fence installed… BEFORE we moved in… but COVID19 put an end to such frivolities, and we moved in anyway.

now we’ve got to leash the dogs when we let them out to go potty. not because our dogs would be irresponsible, but because the other dog owners on the street are being irresponsible… there are three dogs, from two separate houses, which “roam freely” on the street: no fence, no leash, no humans… three separate dogs. one of them (bentley) is friendly enough when he’s not startled, but the other two (hershey is one of them, i don’t know what the other one is called) are less amicable, and hershey likes to push his limits.

but if it were just the dogs, it would be tolerable… barely…

however, there’s also the issue of DJ, a seven-year-old autistic boy who lives at the end of the street, two doors down from us. this morning, i went out to the mailbox and discovered a partially clothed (he was wearing a shirt, but no pants) DJ, and the two aforementioned dogs, wandering aimlessly by the pond across from our house. i said hi, but DJ doesn’t speak. so i went back into MY house, only to have DJ try to follow me. and when he couldn’t get in the front door, he went around to the back, and climbed over three locked gates and x-pens we put on the deck to discourage the other dogs from coming up on the deck…

apparently, the previous owners thought DJ was cute, or something, and gave him cookies when he showed up on their porch.

and he is “cute” in the way that all children are “cute”… but when encountering him, sans adult, and sans pants, it is a bit unnerving… and when he tried to follow me into the house, and then climbed over the barriers in his way to get onto our back deck, it was more than a little disturbing.

particularly since moe “facebook-messaged” his parents, waited half an hour, got no response, went to his parents’ door, and woke up his father, before she could get help for him.

on one hand, it’s a really good thing we didn’t call the cops, but on the other hand… what parent, in their right mind, allows their non-verbal, autistic child to wander the neighbourhood WITHOUT PANTS, on a friday morning?? and if we hadn’t been warned, ahead of time (moe and her farcebook group saved the day), we probably would have called the cops… and it would have served them right, although it would, doubtless, have been incredibly traumatic for the kid.

it’s a REALLY GOOD THING that, when the fence is installed (we’re hoping for next week… really…), it will be a SIX FOOT fence. 😖

COVID19 update

one of the people moe “manages” (one of the doctors who is not the owner of the clinic) got on an airplane yesterday.

shortly after she got on the airplane, word came down from the state that any healthcare provider who gets on an airplane has to voluntarily quarantine for two weeks. in this case, “healthcare provider” apparently applies to veterinarians, as well.

so, along with ramping up her side hustle (she’s already more than half-filled the webinar that she’s giving next sunday), moving into a new house, and managing a veterinary hospital (which is a job, under the best of circumstances), now she has to figure out how to cover for a doctor who potentially “has COVID19”. 😒

but here’s something that i never considered: during the first couple weeks of january, i was sick for two or three days. i got my (very first) flu shot (ever) in november (or it might have been october), and, at the time, i just thought it was a mild case of the flu… but moe says that the symptoms didn’t match the flu: there was minimal nausea, just coughing and fatigue… moe says that it’s possible that i have already had COVID19, and just didn’t realise it.

it’s not totally out of the question: i have spent, at least, the past year’s worth of weekends at the pike place market, which is the first place tourists from cruise ships, and other conveyances, go when they land in seattle…

and healthy people don’t get as sick to begin with…

one of the other doctors moe manages (still not the owner) got sick a few weeks ago, and got better almost immediately, but she still has a lingering cough, and moe thinks she may have gotten COVID19, as well.