Posted on 11/15/2020 6:13:42 PM PST by John Robinson
It seems the performance issue has been resolved. Mumble mumble Apache2 was configured with MPM event causing mod_perl to segfault, changed to prefork mumble mumble and now it works.
Now that the show-stopping issue is solved, next is mail (for flesh blood/registration) and the whack line noise especially in replies. Later is mumble mumble UTF8 encoding issue, double encoding probably mumble mumble.
Don’t use quotes before and after the http/s. Works great without them.
I hear you. Just when you think you figured out their better mousetrap, they have to add new gizmos. Once you get competent with IPv4 and routing tables, here comes IPv6. Get good at pulling and terminating Cat 5 cable, they throw Cat 6 in the mix and now you have an advanced architecture to take into account. Due to mobility problems, I spent two years doing remote support on Win and Mac machines while my first leg infection was slowly healing, and dealt almost exclusively with Win XP and 7 appliances, then along comes the first public release of Win 10. We all know how that went. The one saving grace was, I worked here on 3rd shift from my den. I eventually found myself heading out to the fridge and bringing a beer back an hour before my shift was over. *chuckle*
Good job updating the servers!
Great news. But I just did get “Bad pathway” 503 gateway message a minute ago. Let’s see if this get posted.
I was starting to get the shakes.
Excellent!
It was my “smart quotes” that were fouling the html. Better than reverse engineering cut/paste...just do away with the quotes altogether.
New line of attack...
“Your connection is not private
Attackers might be trying to steal your information from 45.79.56.181 (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_COMMON_NAME_INVALID
This server could not prove that it is 45.79.56.181; its security certificate is from freerepublic.com. This may be caused by a misconfiguration or an attacker intercepting your connection.
Proceed to 45.79.56.181 (unsafe)
“
Still getting an occasional timeout, 504 message (gateway time-out, nginx).
Wondered if you tested the other two MPMs:
- mpm_prefork (current)
- mpm_worker
- mpm_event
Re: https://www.digitalocean.com/community/tutorials/apache-vs-nginx-practical-considerations
Exactly. The only time I use quotes is for a direct link to an article or a video. I haven’t posted one since the ‘migration” so not sure if they’ll work. LOL!
I just got a headache reading that. LOL!
Good job.
I always get nervous moving a website from one server to the next. I can’t imagine what moving a major international forum must be like.
That zagulator, down there in the lower right corner, can sometimes become discomfibulated, so a squirt or two of WD-40 back there ought to straighten the whole ding-dang-doggone thing out. Let 'er rip! |
absolutely stellar migration job in record time. Gold stars for everyone and a big Thank You, too !
I find that I have to log in on every post.
I log in and can post yet when I open a new post I have to log in again.
Today I installed Firefox after installing Windows 7 on a new ssd hard drive.
Other sites I have added my account back do remember my account after closing and opening Firefox
This is an issue with Chrome as well.
You do have those, right? Ahem...don�t worry, I never did, either, but you have to repeat it enough to make that work.
No, don�t repeat what just happened, but do note these exceptions.
I will say the response time was terrible, but I thought it was from rebuilding indexes or the restore going on in the background.
It’s a wonder it didn’t drive you mad! LOL!
...or did it..... :)
Maybe flush DNS cache.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.