[<application>] <PHP Fatal Error> #1679
Comments
Morfonio
added
the
tech-issues
|
Hi @Morfonio, According to the bndiagnotic output there are some syntax errors in your installation. Did you manually edit those files? Please revert the changes to the files, restart the services and try again. Did you also modify the phpMyAdmin config file for Apache located at I don't see any other errors in Apache logs apart from the ones above. |
|
After I fixed the 2 errors related to undefined variables and re-run the Bitnami Diagnostic Tool:
Although I don't remember modifying the phpMyAdmin config file for Apache located at
I ran the diagnostic again and it now showed these.
Also when I try to enter phpmyadmin from the browser it still won't let me in.
I also followed this document to see Apache Error Log: https://docs.bitnami.com/aws/infrastructure/lamp/troubleshooting/debug-errors-apache/
As I mentioned in the first thread where I commented (#1146), I have been using this same AWS server for 5 years and I know that sometimes if you modify something in the server code it can be affected. But in this case it doesn't make much sense to me because this time I didn't modify any code and suddenly almost two weeks ago I got this impediment that doesn't let me access the database with phpmyadmin. The entire list of errors are related to the Php Fatal Errors on AWS and none of them were modified by me. |
|
Hi @Morfonio, I'm afraid I don't know what's the issue with that AWS application placed at |
|
I also asked a question on Stackoverflow (https://stackoverflow.com/questions/79095103/i-am-getting-a-lot-of-errors-related-to-class-not-found-on-apache-error-log ) and following the advice of some people they recommended that I open an instance with the current version of LAMP Bitnami. Test 23th October: I have a new update for you. Following your recommendations I opened a new instance (Bitnami package for LAMP 8.2.24-3) and decided not to upload the files (from the database of my original version) to see if I was allowed access to phpmyadmin through the web browser to see if the completely clean installation would let me use it.
|
|
Hi @Morfonio, I have not been able to reproduce your issue. I have launched a fresh new LAMP server for the same PHP version you mentioned, and I have been able to connect with phpMyAdmin without issues right after the server has started. Are you performing any change on your server? Is the SSH tunnel running? Do you see any related error in the Apache logs?
Apart from the above, you may facing these issues due to the memory issue mentioned in your screenshots. Can you try using a bigger instance? |
|
Hello @gongomgra, I first tried to move the instance from t2.micro to t2.small but when I tried to access phpmyadmin through the browser there were no changes. In my case I don't remember making any changes to my server before the initial problem appeared so it's very strange. I have used the SSH Tunnel for 5 years without any problems: Yesterday I was also able to access the error_log and the acces_log of Apache and these are the screenshots for (Bitnami package for LAMP 8.2.24-3). Do you see anything that could help?
|
Platform
AWS
bndiagnostic ID know more about bndiagnostic ID
24fdd80e-656c-e652-0846-07955fc2364d
bndiagnostic output
bndiagnostic was not useful. Could you please tell us why?
/
Describe your issue as much as you can
I originally had a problem with not being able to log into phpmyadmin via my web browser.
I found this case on Github that I understood to be similar to my case and started following what they said there.
#1146
I also ran the Bitnami Diagnostic Tool and this was the result:
How can I fix the PHP Fatal Error?
The text was updated successfully, but these errors were encountered: