Skip to main content ↑ ↓
Recent Posts
72
Site Feedback / Re: Back On Line
Last post by Spuds -
And still here this AM  :grin:

The error I saw yesterday was OOM on attempting the database connection, so I'm currently assuming the DB process was ended for some reason.  Well at least that is where I'll starting looking in the error logs. 
73
Site Feedback / Re: Back On Line
Last post by Burke Knight -
I noticed it was giving the 500 error at about noon, central.
Was not sure what was going on, but checked at various times after until it was back and I got a notification about @Spuds liking a post.

As usual, giving it the re"boot" seems to have worked....  :tongue:
74
Site Feedback / Re: Back On Line
Last post by Steeley -
It apparently started shortly after BurkeKnight posted just before 09:00 zulu,. I was up most of the night on a 'project' and when I checked email at 0-dark-30 I saw the notification and ... discovered EA was crippled..  probably having seizures for half the day before you kicked it in the butt.
I turned in about 6:30 this morning (PST) and when I got up around 10:30 it was still writhing around on the floor until sometime this afternoon whenever you found it.

Now, I'm not saying it's BurkeKnight's fault, but I'm going to blame him anyway..
75
Site Feedback / Re: Back On Line
Last post by Spuds -
Honestly not sure what happened!

It was a birthday (not mine) today and when I finally was able to set down for the evening, the site was broken:man_shrugging:

The only error I noted was unable to allocate 123XYZ memory. There is not a lot of memory on this instance so I should have done more digging, but with all the sake in me I just made a command decision and did a reboot and all was well :D  Something to keep an eye on.
78
Bug Reports / Re: Attachment Permissions change..
Last post by Steeley -
Quote from: Spuds – Did you try 775 as well ?

But yeah all of my attachment directories are 755 and my PHP files are all 644 ..  As you noted, its likely your host did some update such that web user/group under which your PHP runs has changed.

No, I just threw 0777 at it and the problem went away so I called it good.  In the course of chasing it down I noticed the following Webserver info:

Database client version: libmysql - mysqlnd 8.1.27
PHP version: 8.1.27

That was released 21 Dec 2023, and I suspect that was patched in very recently and that was the offending action.



79
Feature Discussion / Re: Moderation information
Last post by Steeley -
Well, the message for moderation was from my host email server telling me the receiving domain (Outlook.com) was blocking messages from my host's domain (not my ip). I confirmed neither I nor my host were on any known black lists, and outlook's support confirmed neither my IP or my host's ip were blocked at the time I inquired.  I set up a user with an outlook email account, and then sent a PM to it - and it went through just fine (albeit into the spam folder). (Touche', my  spam system marks Outlook's support emails as spam too..  :tongue: )

Anyway, my host was unable to find a clue, and outlook's support, to their credit, responded in a timely manner (although their first email response had no message payload which gave me no information except that my trouble ticket number listed in the subject indicated my submission had generated "something", but otherwise gave me no positive "first impression" of how the troubleshooting effort might play out - and the time stamp of that message indicated it wasn't "auto-generated"). However, my "WTF" reply to the empty message elicited a response fairly quickly and over the course of the next few hours revealed no existing blocks by outlook.com.  

Anyway, what was not part of the moderation information I had was "when" the bounce message was received for 'moderation". I checked the member account (the only one with an outlook.com email) and verified  was not configured to receive email notifications of posts so I concluded the message sent earlier in the day was not the culprit. My error logs revealed, however the member signed up on the 28th and tried to access the account on both the 28th and then again on the 29th, and was rejected because  the account had not been authenticated. However, there are no accounts awaiting authentication, and the new member account is now valid (without my intervention), and the log showed sign up on the 28th, and last active on the 29th, so I assumed the member found the authentication message in his spam folder, and completed the sign up process.  

Now, the authentication email is not the only possible email-exchange scenario between the member and Elkarte that I can imagine, just the one that I know for sure occurred, and is the most likely trigger - if something else went on that I'm not aware of, well, by the very nature of that, I'm not aware of it.

All told, it occurred to me that this dive into all the rabbit holes I could think of chasing the error only to come up empty (because of the transient nature of this particular one) could have been avoided if the moderation notification included the date and time of the moderation flag, narrowing down the event horizon..



I would think a timestamp memorializing the event on the temporal plane we're all flying on could he helpful information regardless of what actually activates the moderation flag, not just for a received email. 

And thusly, a timestamp included with setting the moderation flag is the full width, breadth and depth of my "product improvement request".  :sparkles:
80
Bug Reports / Re: Attachment Permissions change..
Last post by Spuds -
Did you try 775 as well ?

But yeah all of my attachment directories are 755 and my PHP files are all 644 ..  As you noted, its likely your host did some update such that web user/group under which your PHP runs has changed.