parcela2 Posted December 31, 2017 Author Posted December 31, 2017 Yes but not only pg_close fails, for example if a pg_connect fails, the PHP also stops. When a PostgreSQL fuction fails, the php fails and no show errors. It is neccessary the use of pg_close() for security and origanization reasons. I think that if i restart all my domain and web the problem could be solved.
Krydos Posted December 31, 2017 Posted December 31, 2017 Oh, I don't even know what you mean by restart your domains. I thought you had a plan.
miwilc Posted December 31, 2017 Posted December 31, 2017 @Krydos what usually causes core dumps? It used to occur on one of my development environments, it got patched, I believe.
parcela2 Posted December 31, 2017 Author Posted December 31, 2017 I was thinking of restarting my web space with a new account or so
Krydos Posted December 31, 2017 Posted December 31, 2017 @milwilc, in this case it's a segmentation fault. The php process itself is actually crashing, not just an error in the code. @parcela2, You could try deleting your account and recreating it. Once you have everything backed up, and deleted let me know and I can send you an invitation code so you don't have to wait until midnight UTC to get a new account. No one else has reported this, and I can't reproduce the segmentation fault core dumps on any other account on the server.
parcela2 Posted January 5, 2018 Author Posted January 5, 2018 Perfect @Krydos, i deleted my account now. I restored databses and files. I have prepared to create a new account.
parcela2 Posted January 5, 2018 Author Posted January 5, 2018 Your account has been queued for deletion. Depending on the server load, and how many tasks are ahead of your deletion it could take up to 48 hours to be fully deleted. The domain will show the suspended page while it is queued to be deleted.
parcela2 Posted January 8, 2018 Author Posted January 8, 2018 Thanks very much for the support, the postgreSQL still fails but i finnally solved including at the end of the php the database connections to stop it this point. It seems that is a problem of the pool. Thanks again
parcela2 Posted February 10, 2018 Author Posted February 10, 2018 (edited) I tested to remove the comments to pg_close and works again. The problem now is really solved. Por curiosidad, ¿cuál ha sido la solución? translate.google.com: Out of curiosity, what has been the solution? Edited February 10, 2018 by Krydos translated
Krydos Posted February 10, 2018 Posted February 10, 2018 As far as I know there has been no change on the server.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now