New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[2019.09] PHP Fatal Errors #7297
Comments
This is a recent fatal error, details here: https://friendica.hubup.pro/display/174591b4-155d-18c2-9291-98a040514688
Fixed by #7332 |
Expected behaviorShow photo. Actual behaviorWhen I try to open certain photos from /photos/$user/album I get a http 500 error, which lead me to dig what is going on and then I saw I get a PHP error, there was nothing happening in the http error log, so just php it seems. One block like this shows up in the log each time I press F5 or try to open another photo from the album.
Steps to reproduce the problemGo to some old photos, in my case it was an album from 2016. Friendica version you encountered the problemLatest released version, 2019.06. Friendica source (git, zip)git PHP version7.3.6 SQL version10.3.16-MariaDB A copy of #7340 Fixed by #7342 |
Are you getting a string of Notice messages about undefined indices in |
Not that I know of. These would be in the php error log as well?
|
If the |
Need to check this tomorrow, I never changed the settings what to log in php.ini, but no idea what is set. I will check it tomorrow.
|
No notices, just this as above (??): I changed the logging level to "E_ALL" only, which should include E_NOTICES and did "killall php" and a restart of httpd. |
Ok, thanks, the fatal error has been suppressed in #7342 |
But this does not fix the problem, right? |
Indeed, we still try to fetch missing item data for old pictures, but at least it doesn't make the page crash. |
Sorry, but I have to ask again, what do you mean by this?
I still get a http 500 error, so this is not what you mean by crash correct? |
500 error still isn't good, Has it been happening since you recently pulled? Can you provide the (hopefully new) error message triggering the 500 page? |
Nothing new in the php log, still like this: Nothing in the httpd log. Edit: Meh... sorry, I guess I need to checkout to dev? |
There are two minor DB updates in develop at the moment. No major changes. Only some bug fixes iirc. The checkout from current master to develop was a no-brainer. |
I think that will take a long time, the progress in mysql at least is not increasing sind 200 seconds. :-D Edit: Less than an hour, but more than 30 minutes... too big database and too slow server. :-/ |
Update: This shows up in php logs:
I still get the HTTP 500 fault. Fixed by #7349 |
Thanks, yes there still is a crash, but it isn't on the same place. Progress! |
I get a new error
|
It shouldn't occur anymore with the latest develop. |
Fixed by #7360 |
On it. |
If it doesn't happen that often, it may just be a dropped database connection. Nothing we can do, the fatal error actually is warranted. |
develop:
|
Seems specifically relevant to the post in question, would you be able to pull its source from the little the exception shows if it's a public post? |
Where do I have to look for it? In 'item-content' -> 'body' or somewhere else? |
Yes, then you can retrieve the GIUD and paste it in |
Hmm. Empty result set. Does the body field content start with '[h3]Le canal'? |
What about searching for |
Nothing found for the issue above. But I have a new one. :-)
Fixed by #7535 |
On it. |
Fixed by #7577 |
I got a problem that the maximum number of processes that can be run was reached, not sure if this fault might be the cause, but maybe someone understands the error.
Edit 1: There is many forks of MariaDB, not sure why it is forking so much. :-/ Edit 2: With the last MariaDB update the config was moved from /etc/mysql/my.cnf to /etc/my.cnf.d/*, just it wasn't moved/converted or anything, but actually a new blank config was created in /etc/my.cnf.d/ Fixed by #7577 |
RC:
Fixed by #7593 |
RC:
|
No one should be accessing this file, let alone directly from a browser like this, you can ignore it. |
|
Please run |
I did, some dependencies where updated |
You shouldn't be getting the same error again. |
Closed in favor of #7675 |
Please report here any PHP Fatal error message obtained running the
2019.06
stable or2019.09-dev
versions.The text was updated successfully, but these errors were encountered: