Plesk 12.x / Linux :: Error 505 Bad Gateway - When Importing SQL Dump Via PHPMyAdmin
May 26, 2015
under Plesk 12.0.18 PHPMyAdmin is failing to import a 3 MB SQL dump of a simple Joomla website. "Error 505 Bad Gateway", it says.It happens with other dumps too, some as small as ~500 KB. The format (SQL or ZIP) of the file uploaded doesn't seem to matter, because the upload itself seems to work; it seems it's the post-processing what is raising the error.
The funny thing is that the import itself seems to work (the contents of the SQL dump are imported), but the error message appears and causes confusion and support requests from our clients./var/log/sw-cp-server/error_log says:
2015/05/15 03:19:31 [error] 10215#0: *5 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: XX.XX. XXX. XXX, server: , request: "POST /domains/databases/phpMyAdmin/import.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "xxxx. xxxxxxx.com:8443", referrer: URL.....To me it sounds like a timeout.
This seems to be a "popular" error among Plesk users, and I have tried this, this and this with no luck.
I'm on a VPS with Ubuntu 14.04 and Plesk 12 Web Admin Edition. I can't import a large (20 MB zipped) database dump to phpmyadmin because there is a 2MB file size limit. I suppose I have to change the server-wide PHP configuration (if I change the PHP settings for the domain nothing happens). Is there a way to change the global PHP settings via the Plesk panel?
I have upgraded from 11.5 to 12, and now if I try to open Plesk on the port 8443 I have this error:
502 Bad Gateway
nginx
This is the log: 2014/06/27 18:25:13 [crit] 1629#0: *2 connect() to unix:/var/run/sw-engine.sock failed (2: No such file or directory) while connecting to upstream, client: 79.49.206.176, server: , request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "87.106.85.233:8443"
I am not able to take backups of the content of the server. This is the error I get:
Error: Runtime error: The check dump failed with code '1'. The dump can contain invalid data! at /usr/local/psa/admin/bin/plesk_agent_manager line 1022.
Error: The dump have been invalidated by check-dump operation
We are running Plesk 12 (latest version) on openSuse 13.1. The web server is nginx as a proxy in front of Apache. We are running into a 502 Bad Gateway nginx error when trying to send data from a simple form to a php script.
The log shows: upstream prematurely closed connection while reading response header from upstream
It seems that Plesk does not configure nginx properly as some pages, especially pages that are accessed via https have broken headers. The headers of a page that is displaying
HTTP/1.1 400 Bad Request => Server => nginx Date => Sat, 26 Jul 2014 09:53:13 GMT Content-Type => text/html Content-Length => 166 Connection => close
As I read, when Plesk and WHMCS are in the same server, you may have 502 bad gateway errors when creating an account through WHMCS..Page not Found/Timeout/502 Bad Gateway error creating accounts with Plesk 10+..By default Plesk 10 and above performs a forced restart of apache when an account is created or suspended which causes WHMCS to lose connection to the server, and if your WHMCS is on the same server, you will also lose connection to WHMCS at the same time.
In order to resolve this please refer to the following knowledgebase article for instructions on configuring Plesk to perform a graceful restart instead: URL..
But when I activate nginx in Plesk the 502 bad Gateway problem comes back.Is there an option to activate Nginx graceful restart in Plesk?
We found 502 Bad Gateway error Nginx on multiple domain "currently troissoeursetunfrere.com is a wordpress site e-commerce" and also malittleboutique.com ecommerce wordpress, possibly to fix this problem we have followed this tutorial " [URL] ....
I am runing ubuntu server 64bit with plesk v.11.5.30, phpmyadmin v.4:3.4.10.1-1.
When i try to acces phpmyadmin from : myserverIP/phpmyadmin - it gives me 500 error.
When I try to acces phpmyadmin from: mydomainserver/phpmyadmin - it saves file at login into the disk instead login. I was going through different threads on the web to solve that problem but no success at all.
I have real basic knowledge about webservers, phpmyadmin and mysql server. I am runing my first cloud server just few days.
There is no possibility to access preconfigured phpmyadmin from plesk according that thread: link So what for do I need plesk?
I have been trying quite unsuccessfully to import a large sql db file via phpMyAdmin for one of my clients. Since the db file is about 250mb I get a server timeout error.how I can do this via SSH...I have a CentOS server 6.5, 64 bit that runs Plesk v 12.0.18
I have this error when i put import to mysql database
Code: #1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '<script></script><p>ERROR: Maximum execution time of 300 seconds exceeded (Util.' at line 244
I have in domain > doemainname > max_execution_time Standaard Geef een aangepaste waarde op 0
and insert in usr/local/psa/admin/htdocs/domains/databases/phpmyadmin in the file config.sample.inc.php following command $cfg['ExecTimeLimit'] = 70000;
After successful creation of a full backup, pmm-ras hangs forever (100% CPU) while trying to export the dump to FTP. I have two identical Plesk 12.0.18 installations and this happens only on one of them.
I see the following in /opt/psa/PMM/sessions/*/.stderr:
Use of uninitialized value in numeric eq (==) at /opt/psa/admin/bin/plesk_agent_manager line 827.
All domains were offline this morning. Plesk showed the following error message. It seems we are beta testing the software. I am on Suse 13.1, clean install.
Unable to rotate dump: The dump rotation is failed with code '1' at /usr/local/psa/admin/bin/plesk_agent_manager line 1041.
Warning: domain "abc.com"
The domain 'abc.com' may be inaccessible after backup. Please, resume it manually!
Code: # plesk bin pleskbackup server UNIVERSAL->import is deprecated and will be removed in a future perl at (eval 13) line 3. UNIVERSAL->import is deprecated and will be removed in a future perl at /usr/local/psa/PMM/agents/shared/IPC/Run.pm line 1060. UNIVERSAL->import is deprecated and will be removed in a future perl at /usr/local/psa/PMM/agents/shared/IPC/Run/IO.pm line 78. UNIVERSAL->import is deprecated and will be removed in a future perl at /usr/local/psa/PMM/agents/shared/IPC/Run/Timer.pm line 161. Runtime error: Could not run make dump with pmmcli[Illegal seek]
Code: # /usr/local/psa/admin/sbin/pmmcli Traceback (most recent call last): File "/usr/local/psa/admin/sbin/pmmcli", line 5, in <module> import pmmcli File "/usr/local/psa/admin/share/pmmcli/pmmcli.py", line 21, in <module> import pmmcli_session File "/usr/local/psa/admin/share/pmmcli/pmmcli_session.py", line 15, in <module> import pmm_migration_handler File "/usr/local/psa/admin/share/pmmcli/pmm_migration_handler.py", line 16, in <module> import migration_handler ImportError: Bad magic number in /usr/local/psa/admin/share/migration-handler/migration_handler.pyc
Today at 12.50 pm my (ubuntu 14.04.1 LTS) server running plesk 12.0.18 suddenly stopped serving websites. Any attempts to access a webpage on any vhost returned the 502 bad gateway using Nginx error messsage.When I looked at the nginx logs, I found messages like:
Connection refused) while connecting to upstream, client: m.m.m.m, server: , request: "GET /server-status HTTP/1.0", upstream: URL....
Restarting apache & nginx (/etc/init.d/apache2 restart & /etc/init.d/nginx restart) made no difference and I had to reboot to restore http access.
Strangely if I browsed with port 7080 specified (i.e. http://n.n.n.n:7080), this worked fine for all vhosts, so apache (which I believe is listening on this port while nginx listens on port 80) is working fine - nginx is just not able to pass stuff to it?
this is a fresh Plesk 12 installation on a Dedicated Server, on Debian 6. I haven't installed a License key yet.When i tried to run MIgration Manager, the loading was taking forever. Also, when i try to enter Webserver Configurations Troubleshooter, i get 502 Bad Gateway nginx error.In the /var/log/sw-cp-server/error_log i get this error:
Code: 2015/06/17 11:42:47 [error] 3918#0: *52 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: A.B.C.D, server: , request: "GET /modules/configurations-troubleshooter/index.php/index/list HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "X.X.X.X:8443", referrer: "https://X.X.X.X:8443/admin/module/list?context=modules" When i try to insert a Plesk License, i also get this error:
After upgrading (i know, i should not do this) from Squeeze to Wheezy i have got a problem with subscriptions.Plesk seems to work, but whein i want do manage a domain/hosting. i just see 502 Bad Gateway nginxClick to expand...
Plesk 11.5.30 all latest updated installed is used with Power-User view on an Ubuntu 12.04 LTS 64 Bit system.
The Plesk Interface is working well in general. But if the customer clicks on "Webspaces" -> Add Webspace they run in a:
[URL] ....
Browser: 502 Bad Gateway nginx
To try to fix it with:
/usr/local/psa/admin/bin/nginxmng --disable /usr/local/psa/admin/sbin/httpdmng --reconfigure-all /etc/init.d/apache2 restart /etc/init.d/ngnix restart ( does not work anyway since the customer is not using it ) -> ngnix_enable=no
Which did not work ( ngnix is and was not active )
In the log /var/log/sw-cp-server/error.log
we can see:
[error] 1936#0: *180 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 84.177.142.220, server: , request: "GET /smb/account/create-subscription HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock:", host: "server:8443", referrer: "https://server:8443/smb/account"
Since we switched to Plesk 12 and activated nginx the problem reoccurs reliably on every domain change. As soon as a customer creates a new domain or alias and Apache restarts nginx delivers 502 errors for maybe 10 seconds. After that everything is fine again.
The system is Debian 6.0.10 with Plesk 12.0.18 Update #38
That might not be a problem in small environments, but with >100 domains the timeout is annoying enough for customers to pick up the phone.
Adding this to /etc/sw-cp-server/config did not do the trick.
