Postgres Pro
Downloads
Home   >   mailing lists

Thread: 500 Internal Server Error

500 Internal Server Error

From
Pavel Klimenko
Date:
After a long time with pgAdmin4, queries stop executing and text is displayed in the Messages window:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>500 Internal Server Error</title>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error and was unable to complete your request.  Either the server is overloaded or there is an error in the application.</p>

The problem is solved only by reconnecting to the DBMS.

Re: 500 Internal Server Error

From
Murtuza Zabuawala
Date:
Hi,

Please report your issue here

While creating the ticket, please attach the pgadmin4.log file, that will help us debug the issue,

Steps:
1) Change the logging level to debug, Refer: https://www.pgadmin.org/faq/#8
2) Change the refresh time interval values from '1' to '123456' for all the graphs to prevent unwanted logging from dashboard queries.
File -> Preferences -> Paths -> Dashboards -> Graphs
3) Close pgAdmin4
4) Delete/Rename existing pgAdmin4.log file from 
Windows:
C:\Users\<YourUsername>\AppData\Roaming\pgAdmin\pgadmin4.log
Linux:
~/.pgadmin/pgadmin4.log
5) Open pgAdmin4 again, try to re-produce the issue.
6) Upload/Attach pgAdmin4.log file on bug tracker.


--
Regards,
Murtuza Zabuawala
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


On Fri, Oct 13, 2017 at 5:05 PM, Pavel Klimenko <dzy4yzd@gmail.com> wrote:
After a long time with pgAdmin4, queries stop executing and text is displayed in the Messages window:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>500 Internal Server Error</title>
<h1>Internal Server Error</h1>
<p>The server encountered an internal error and was unable to complete your request.  Either the server is overloaded or there is an error in the application.</p>

The problem is solved only by reconnecting to the DBMS.

Re: 500 Internal Server Error

From
GregS
Date:
Hi,

very often it is a result of database messages converting problems. They
seem to be related to ASCII to Unicode conversion for languages and codesets
other than English, and this may be related to Python 2 which under pgAdmin4
(default at least on the Windows platforms).

If so, your transaction is broken, and until you invoke ROLLBACK
explicitely, you will get the error 500 because this situation generates
another message which cannot be converted similarly.

You may try to change yout lc_messages (error messages) to English either
for a current session:

set lc_messages to 'English_United States.UTF-8'

or persistently for the whole instance:

1. $datadir\postgresql.conf: lc_messages = 'English.United States.UTF-8'
2. select pg_reload_conf();

It looks that 'English_United States.UTF-8' is Windows-bound and
'en_US.utf8' is for Linux.

I hope it will help.

Kind regards,
Greg




--
Sent from: http://www.postgresql-archive.org/PostgreSQL-pgadmin-support-f2191615.html