Postgresql internal server error

Steps to reproduce

1. I am using postgres as the backing DB, and I have an external storage share set up using SMB
2. I try to upload a file to the external share

Expected behaviour

The upload should succeed.

Actual behaviour

I get an «Internal Server Error» message, but upon refresh the file upload has succeeded anyway.

Server configuration

Operating system: Linux cf62e725620d 4.9.0-0.bpo.3-amd64 #1 SMP Debian 4.9.25-1~bpo8+1 (2017-05-19) x86_64

Web server: Apache/2.4.10 (Debian) (apache2handler)

Database: pgsql PostgreSQL 9.6.3 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit

PHP version: 7.1.5
Modules loaded: Core, date, libxml, openssl, pcre, sqlite3, zlib, ctype, curl, dom, fileinfo, filter, ftp, hash, iconv, json, mbstring, SPL, PDO, session, posix, Reflection, standard, SimpleXML, pdo_sqlite, Phar, tokenizer, xml, xmlreader, xmlwriter, mysqlnd, apache2handler, apcu, exif, gd, intl, ldap, mcrypt, memcached, mysqli, pdo_mysql, pdo_pgsql, pgsql, redis, zip, Zend OPcache

Nextcloud version: 11.0.3 (stable) — 11.0.3.2

Updated from an older Nextcloud/ownCloud or fresh install: Fresh install

Where did you install Nextcloud from: Using the official Docker image

Signing status:

Signing status

No errors have been found.

List of activated apps:

App list

Enabled:
 - activity: 2.4.1
 - comments: 1.1.0
 - dav: 1.1.1
 - external: 1
 - federatedfilesharing: 1.1.1
 - federation: 1.1.1
 - files: 1.6.1
 - files_downloadactivity: 1.0.1
 - files_external: 1.1.2
 - files_pdfviewer: 1.0.1
 - files_sharing: 1.1.1
 - files_texteditor: 2.2
 - files_trashbin: 1.1.0
 - files_versions: 1.4.0
 - files_videoplayer: 1.0.0
 - firstrunwizard: 2.0
 - gallery: 16.0.0
 - issuetemplate: 0.2.1
 - logreader: 2.0.0
 - lookup_server_connector: 1.0.0
 - nextcloud_announcements: 1.0
 - notifications: 1.0.1
 - password_policy: 1.1.0
 - provisioning_api: 1.1.0
 - serverinfo: 1.1.1
 - sharebymail: 1.0.1
 - survey_client: 0.1.5
 - systemtags: 1.1.3
 - theming: 1.1.1
 - twofactor_backupcodes: 1.0.0
 - updatenotification: 1.1.1
 - user_external: 0.4
 - workflowengine: 1.1.1

Disabled:
 - admin_audit
 - encryption
 - files_accesscontrol
 - files_automatedtagging
 - files_retention
 - templateeditor
 - user_ldap
 - user_saml

The content of config/config.php:

Config report

{
    "apps_paths": [
        {
            "path": "/var/www/html/apps",
            "url": "/apps",
            "writable": false
        },
        {
            "path": "/var/www/html/custom_apps",
            "url": "/custom_apps",
            "writable": true
        }
    ],
    "instanceid": "oc40kfksk5eo",
    "passwordsalt": "***REMOVED SENSITIVE VALUE***",
    "secret": "***REMOVED SENSITIVE VALUE***",
    "trusted_domains": [
        "192.168.1.132",
        "nextcloud.int.fayf.net",
        "nextcloud.fayf.net"
    ],
    "datadirectory": "/var/www/html/data",
    "overwrite.cli.url": "http://192.168.1.132",
    "dbtype": "pgsql",
    "version": "11.0.3.2",
    "dbname": "nextcloud",
    "dbhost": "192.168.1.131",
    "dbport": "",
    "dbtableprefix": "oc_",
    "dbuser": "***REMOVED SENSITIVE VALUE***",
    "dbpassword": "***REMOVED SENSITIVE VALUE***",
    "logtimezone": "UTC",
    "installed": true,
    "mail_smtpmode": "smtp",
    "mail_smtpsecure": "ssl",
    "user_backends": [
        {
            "class": "OC_User_SMB",
            "arguments": [
                "192.168.1.50"
            ]
        }
    ]
}

Are you using external storage, if yes which one:
Array
(
[0] => OCFilesStorageLocal
[1] => OCAFiles_ExternalLibStorageFTP
[2] => OCFilesStorageDAV
[3] => OCAFiles_ExternalLibStorageOwnCloud
[4] => OCAFiles_ExternalLibStorageSFTP
[5] => OCAFiles_ExternalLibStorageAmazonS3
[6] => OCAFiles_ExternalLibStorageDropbox
[7] => OCAFiles_ExternalLibStorageGoogle
[8] => OCAFiles_ExternalLibStorageSwift
[9] => OCAFiles_ExternalLibStorageSFTP
[10] => OCAFiles_ExternalLibStorageSMB
[11] => OCAFiles_ExternalLibStorageSMB
)

Are you using encryption: no

Are you using an external user-backend, if yes which one: SMB

Client configuration

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Operating system:

Logs

Web server error log

Web server error log

192.168.1.128 - - [08/Jun/2017:06:39:11 +0000] "PUT /remote.php/webdav/Home/OW%20S5.txt HTTP/1.0" 500 1065 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36"

Nextcloud log (data/nextcloud.log)

Nextcloud log

DoctrineDBALExceptionDriverException: An exception occurred while executing 'UPDATE "oc_filecache" SET "mtime"=? WHERE ("mtime" <> ? OR "mtime" IS NULL) AND "fileid" = ? ' with params ["1496685869.428", "1496685869.428", 79055]: SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for integer: "1496685869.428"
/var/www/html/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DBALException.php - line 128: DoctrineDBALDriverAbstractPostgreSQLDriver->convertException('An exception oc...', Object(DoctrineDBALDriverPDOException))
/var/www/html/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php - line 836: DoctrineDBALDBALException driverExceptionDuringQuery(Object(DoctrineDBALDriverPDOPgSqlDriver), Object(DoctrineDBALDriverPDOException), 'UPDATE "oc_file...', Array)
/var/www/html/lib/private/DB/Connection.php - line 194: DoctrineDBALConnection->executeQuery('UPDATE "oc_file...', Array, Array, NULL)
/var/www/html/lib/private/Files/Cache/Cache.php - line 312: OCDBConnection->executeQuery('UPDATE "oc_file...', Array)
/var/www/html/lib/private/Files/Cache/Wrapper/CacheWrapper.php - line 138: OCFilesCacheCache->update(79055, Array)
/var/www/html/lib/private/Files/Cache/Wrapper/CacheWrapper.php - line 111: OCFilesCacheWrapperCacheWrapper->update(79055, Array)
/var/www/html/lib/private/Files/View.php - line 1533: OCFilesCacheWrapperCacheWrapper->put('OW S5.txt', Array)
/var/www/html/lib/private/Files/View.php - line 567: OCFilesView->putFileInfo('/andrew/files/H...', Array)
/var/www/html/apps/dav/lib/Connector/Sabre/File.php - line 209: OCFilesView->touch('/Home/OW S5.txt', '1496685869.428')
/var/www/html/apps/dav/lib/Connector/Sabre/Directory.php - line 137: OCADAVConnectorSabreFile->put(Resource id #80)
/var/www/html/3rdparty/sabre/dav/lib/DAV/Server.php - line 1072: OCADAVConnectorSabreDirectory->createFile('OW S5.txt', Resource id #80)
/var/www/html/3rdparty/sabre/dav/lib/DAV/CorePlugin.php - line 525: SabreDAVServer->createFile('Home/OW S5.txt', Resource id #80, NULL)
[internal function] SabreDAVCorePlugin->httpPut(Object(SabreHTTPRequest), Object(SabreHTTPResponse))
/var/www/html/3rdparty/sabre/event/lib/EventEmitterTrait.php - line 105: call_user_func_array(Array, Array)
/var/www/html/3rdparty/sabre/dav/lib/DAV/Server.php - line 479: SabreEventEventEmitter->emit('method PUT', Array)
/var/www/html/3rdparty/sabre/dav/lib/DAV/Server.php - line 254: SabreDAVServer->invokeMethod(Object(SabreHTTPRequest), Object(SabreHTTPResponse))
/var/www/html/apps/dav/appinfo/v1/webdav.php - line 60: SabreDAVServer->exec()
/var/www/html/remote.php - line 165: require_once('/var/www/html/a...')
{main}

Browser log

Browser log

I don't think this is necessary since it's a server side issue.

Re: 500 Internal Server Error

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 AppDataRoamingpgAdminpgadmin4.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 wrote:

> After a long time with pgAdmin4, queries stop executing and text is
> displayed in the Messages window:
>
>
> 500 Internal Server Error
>

Internal Server Error

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.

>
> The problem is solved only by reconnecting to the DBMS.
>

Источник

pgAdmin4.15: 500 Internal Server Error

Subject: pgAdmin4.15: 500 Internal Server Error Date: 2019-11-30 11:36:38 Message-ID: CAKqYf_LHA=mFkfQMMzPaHdx=kNAfx0b3rSz4ErCH9gd0vBSLNw@mail.gmail.com Views: Raw Message | Whole Thread | Download mbox | Resend email Thread: Lists: pgadmin-support

Pgadmin4 isn’t working after upgrading to 4.15
(Was working before the update in server mode on wcgi)

I set the following in config.py:
DEBUG = True
CONSOLE_LOG_LEVEL = logging.DEBUG
FILE_LOG_LEVEL = logging.DEBUG
I restarted apache2
Visiting 127.0.0.1/pgadmin4 gave the attached pgadmin4.log

My system:
Ubuntu 19.04 with the postgresql apps from apt.postgresql.org

Installed packages:
pgadmin4-(apache2,common,dbgsym,doc) 4.15-1.pgdg19.04+1

Any help appreciated,

Responses

• Fwd: pgAdmin4.15: 500 Internal Server Error at 2019-11-30 12:02:10 from bw
• Re: pgAdmin4.15: 500 Internal Server Error at 2019-12-02 04:34:20 from Khushboo Vashi

Browse pgadmin-support by date

Copyright © 1996-2023 The PostgreSQL Global Development Group

Источник

RE: 500 Internal Server Error

Subject: RE: 500 Internal Server Error Date: 2017-11-22 20:29:53 Message-ID: BN6PR1301MB2212270949EA16214768119AD4200@BN6PR1301MB2212.namprd13.prod.outlook.com Views: Raw Message | Whole Thread | Download mbox | Resend email Thread: Lists: pgadmin-support

Never mind. Found the bug #: Bug #2806
Found here: https://redmine.postgresql.org/issues/2806
Ben Nachtrieb |(303) 350-4287
Only accredited investors and qualified clients will be admitted as limited partners to a Crescat fund. For natural persons, investors must meet SEC requirements including minimum annual income or net worth thresholds. Crescat funds are being offered in reliance on an exemption from the registration requirements of the Securities Act of 1933 and are not required to comply with specific disclosure requirements that apply to registration under the Securities Act. The SEC has not passed upon the merits of or given its approval to the Crescat funds, the terms of the offering, or the accuracy or completeness of any offering materials. A registration statement has not been filed for any Crescat fund with the SEC. Limited partner interests in the Crescat funds are subject to legal restrictions on transfer and resale. Investors should not assume they will be able to resell their securities. Investing in securities involves risk. Investors should be able to bear the loss of their investment. Investments in the Crescat funds are not subject to the protections of the Investment Company Act of 1940. Performance data represents past performance, and past performance does not guarantee future results. Performance data is subject to revision following each monthly reconciliation and annual audit. Current performance may be lower or higher than the performance data presented. Crescat is not required by law to follow any standard methodology when calculating and representing performance data. The performance of Crescat funds may not be directly comparable to the performance of other private or registered funds. Investors may obtain the most current performance data and private offering memorandum for a Crescat fund by contacting Linda Smith at (303) 271-9997 or by sending a request via email to lsmith(at)crescat(dot)net . See the private offering memorandum for each Crescat fund for complete information and risk factors.

From: Ben Nachtrieb
Sent: Wednesday, November 22, 2017 12:32 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org
Cc: Ben Nachtrieb
Subject: 500 Internal Server Error

When I send a query, unexpectedly and seemingly randomly I get the following text in the Message tab for the query tool output:

» 500 Internal Server Error

Internal Server Error

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.

Notes:
-The html is part of the message.
-It doesn’t seem to matter what query is sent.
-The actual query seems to stay active (as if it is still working), but eventually comes back with a wait event: ClientWrite.
-We can remedy the situation by closing the query tool window (hence closing the session) and opening a new query too window (whilst never closing pgAdmin 4 or the connection to the server) then sending the query again.
-We are connected to a Linux VM via my Windows 7 PC.
-This happens probably 10 times a day while queries are being developed and tested.

Version
2.0
Copyright
Copyright 2013 — 2017, The pgAdmin Development Team
Python Version
2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]
Flask Version
0.12.2
Application Mode
Desktop
Current User
pgadmin4(at)pgadmin(dot)org

What is causing this? What is the fix? Is this a bug? I see similar bugs listed, but they all seem to depend on a certain type of query (I think).

Источник

Re: 500 Internal Server Error

Sorry, I don’t have a solution. I experience it every day multiple times a day. Very frustrating and disruptive to workflows. The link does not have a fix. The bug/issue is outstanding (known and not fixed) as far as I know.

Are you using pgAdmin 4 and postgres 10.1? I am starting to think it is a pgAdmin 4 issue, but I haven’t drilled into it much due to time constraints.

From: Durumdara [mailto: ]
Sent: Thursday, November 30, 2017 12:27 AM
To: Ben Nachtrieb
Cc: ql.org
Subject: Re: 500 Internal Server Error

What is the solution of this problem?

I don’t have account there. 🙁

2017-11-22 21:29 GMT+01:00 Ben Nachtrieb :

Never mind. Found the bug #: Bug #2806

Only accredited investors and qualified clients will be admitted as limited partners to a Crescat fund. For natural persons, investors must meet SEC requirements including minimum annual income or net worth thresholds. Crescat funds are being offered in reliance on an exemption from the registration requirements of the Securities Act of 1933 and are not required to comply with specific disclosure requirements that apply to registration under the Securities Act. The SEC has not passed upon the merits of or given its approval to the Crescat funds, the terms of the offering, or the accuracy or completeness of any offering materials. A registration statement has not been filed for any Crescat fund with the SEC. Limited partner interests in the Crescat funds are subject to legal restrictions on transfer and resale. Investors should not assume they will be able to resell their securities. Investing in securities involves risk. Investors should be able to bear the loss of their investment. Investments in the Crescat funds are not subject to the protections of the Investment Company Act of 1940. Performance data represents past performance, and past performance does not guarantee future results. Performance data is subject to revision following each monthly reconciliation and annual audit. Current performance may be lower or higher than the performance data presented. Crescat is not required by law to follow any standard methodology when calculating and representing performance data. The performance of Crescat funds may not be directly comparable to the performance of other private or registered funds. Investors may obtain the most current performance data and private offering memorandum for a Crescat fund by contacting Linda Smith at (303) 271-9997 or by sending a request via email to . See the private offering memorandum for each Crescat fund for complete information and risk factors.

From: Ben Nachtrieb
Sent: Wednesday, November 22, 2017 12:32 PM
To: ql.org
Cc: Ben Nachtrieb
Subject: 500 Internal Server Error

When I send a query, unexpectedly and seemingly randomly I get the following text in the Message tab for the query tool output:

“ 500 Internal Server Error

Internal Server Error

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.

-The html is part of the message.

-It doesn’t seem to matter what query is sent.

-The actual query seems to stay active (as if it is still working), but eventually comes back with a wait event: ClientWrite.

-We can remedy the situation by closing the query tool window (hence closing the session) and opening a new query too window (whilst never closing pgAdmin 4 or the connection to the server) then sending the query again.

-We are connected to a Linux VM via my Windows 7 PC.

-This happens probably 10 times a day while queries are being developed and tested.

Copyright 2013 — 2017, The pgAdmin Development Team

2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

What is causing this? What is the fix? Is this a bug? I see similar bugs listed, but they all seem to depend on a certain type of query (I think).

Источник

Re: 500 Internal Server Error

Subject: Re: 500 Internal Server Error Date: 2017-12-04 04:19:28 Message-ID: CAFOhELdK9P+75PJ5wcgJq87jjVeLj4JBdjvi=LGu5Fd2MbjAKQ@mail.gmail.com Views: Raw Message | Whole Thread | Download mbox | Resend email Thread: Lists: pgadmin-support

On Thu, Nov 30, 2017 at 9:13 PM, Durumdara wrote:

> Hi!
>
> For multidatabase functions I use PGAdmin III and IV.
>
> But because this (and other) bug, I must decrease the PGAdmin IV usage.
>
> As I said, this fix will be available in the next release.

> For one database I use EMS PGSQL manager, because I can see the result
> better, and it saves my special queries automatically.
> The PGAdmin III asked for opened queries (to save) but in PGAdmin IV I
> remember more sql text loosing on close.
>
>
pgAdmin 4 also asks for the unsaved queries to save. You can customise the
setting whether you want the prompt to save the unsaved queries or not.

To change this setting,
1. Go to File > Preferences dialogue.
2. Select SQL Editor > Options from the left hand side panel. In this
dialogue, change the option «Prompt to save unsaved query changes?» to
«True» to always get a prompt for the same.

Please find the attached screen-shot for the same.

I hope in next release, because I believe that the PGAdmin IV would reach
> the level of PGAdmin III in the future (step by step).
>
> This problem happens with PG 9.4-9.6 too.
>
> Best regards
> dd
>
>
> 2017-11-30 14:51 GMT+01:00 Ben Nachtrieb :
>
>> Sorry, I don’t have a solution. I experience it every day multiple times
>> a day. Very frustrating and disruptive to workflows. The link does not have
>> a fix. The bug/issue is outstanding (known and not fixed) as far as I know.
>>
>>
>>
>> Are you using pgAdmin 4 and postgres 10.1? I am starting to think it is a
>> pgAdmin 4 issue, but I haven’t drilled into it much due to time constraints.
>>
>> Ben
>>
>> *From:* Durumdara [mailto:durumdara(at)gmail(dot)com]
>> *Sent:* Thursday, November 30, 2017 12:27 AM
>> *To:* Ben Nachtrieb
>> *Cc:* pgadmin-support(at)lists(dot)postgresql(dot)org
>> *Subject:* Re: 500 Internal Server Error
>>
>>
>>
>> Dear Ben!
>>
>>
>>
>> What is the solution of this problem?
>>
>> I don’t have account there. 🙁
>>
>>
>>
>> Thank you!
>>
>>
>>
>> BW
>>
>>
>>
>> dd
>>
>>
>>
>> 2017-11-22 21:29 GMT+01:00 Ben Nachtrieb :
>>
>> Never mind. Found the bug #: Bug #2806
>>
>> Found here: https://redmine.postgresql.org/issues/2806
>>
>> Ben Nachtrieb |(303) 350-4287
>>
>> Only accredited investors and qualified clients will be admitted as
>> limited partners to a Crescat fund. For natural persons, investors must
>> meet SEC requirements including minimum annual income or net worth
>> thresholds. Crescat funds are being offered in reliance on an exemption
>> from the registration requirements of the Securities Act of 1933 and are
>> not required to comply with specific disclosure requirements that apply to
>> registration under the Securities Act. The SEC has not passed upon the
>> merits of or given its approval to the Crescat funds, the terms of the
>> offering, or the accuracy or completeness of any offering materials. A
>> registration statement has not been filed for any Crescat fund with the
>> SEC. Limited partner interests in the Crescat funds are subject to legal
>> restrictions on transfer and resale. Investors should not assume they will
>> be able to resell their securities. Investing in securities involves risk.
>> Investors should be able to bear the loss of their investment. Investments
>> in the Crescat funds are not subject to the protections of the Investment
>> Company Act of 1940. Performance data represents past performance, and past
>> performance does not guarantee future results. Performance data is subject
>> to revision following each monthly reconciliation and annual audit. Current
>> performance may be lower or higher than the performance data presented.
>> Crescat is not required by law to follow any standard methodology when
>> calculating and representing performance data. The performance of Crescat
>> funds may not be directly comparable to the performance of other private or
>> registered funds. Investors may obtain the most current performance data
>> and private offering memorandum for a Crescat fund by contacting Linda
>> Smith at (303) 271-9997 or by sending a request via email to
>> lsmith(at)crescat(dot)net(dot) See the private offering memorandum for each Crescat
>> fund for complete information and risk factors.
>>
>>
>>
>> *From:* Ben Nachtrieb
>> *Sent:* Wednesday, November 22, 2017 12:32 PM
>> *To:* pgadmin-support(at)lists(dot)postgresql(dot)org
>> *Cc:* Ben Nachtrieb
>> *Subject:* 500 Internal Server Error
>>
>>
>>
>> Hello,
>>
>>
>>
>> When I send a query, unexpectedly and seemingly randomly I get the
>> following text in the Message tab for the query tool output:
>>
>>
>>
>> “ 500
>> Internal Server Error

Internal Server Error

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.

”
>>
>>
>>
>> Notes:
>>
>> -The html is part of the message.
>>
>> -It doesn’t seem to matter what query is sent.
>>
>> -The actual query seems to stay active (as if it is still working), but
>> eventually comes back with a wait event: ClientWrite.
>>
>> -We can remedy the situation by closing the query tool window (hence
>> closing the session) and opening a new query too window (whilst never
>> closing pgAdmin 4 or the connection to the server) then sending the query
>> again.
>>
>> -We are connected to a Linux VM via my Windows 7 PC.
>>
>> -This happens probably 10 times a day while queries are being developed
>> and tested.
>>
>>
>>
>> I have:
>>
>>
>>
>> *Version*
>>
>> 2.0
>>
>> *Copyright*
>>
>> Copyright 2013 — 2017, The pgAdmin Development Team
>>
>> *Python Version*
>>
>> 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit
>> (Intel)]
>>
>> *Flask Version*
>>
>> 0.12.2
>>
>> *Application Mode*
>>
>> Desktop
>>
>> *Current User*
>>
>> pgadmin4(at)pgadmin(dot)org
>>
>>
>>
>> What is causing this? What is the fix? Is this a bug? I see similar bugs
>> listed, but they all seem to depend on a certain type of query (I think).
>>
>>
>>
>> Thanks!
>>
>>
>>
>> *Ben *
>>
>>
>>
>>
>>
>
>
Thanks,
Khushboo

Источник

Разработка отзывов при выполнении SQL, она сталкивается с ошибкой, оператор SQL очень прост, синтаксис правильный, и какой SQL выполняется в этом сеансе, сталкивается с следующей ошибкой.

<!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>

В соответствии с либо сервером перегружен, либо есть информация об ошибке, проверьте состояние нагрузки DB, обнаруживаем, что ЦП не высокий, примерно на 30%, что аналогично нам. Выполнение этого обнаружения SQL в логине DB не связано с ошибкой.

Онлайн поиск Эта ошибка найдена относительно большая, а обратная связь разработки используется PGADMIN 4. Попытки закрыть PGADMIN 4, а затем подключите базу данных. Если передние SQL может быть выполнен, предполагается проблема PGADMIN 4.

Продолжайте искать PGADMIN 4 с этой ошибкой, обнаружил, что кто-то обратная связь имеет аналогичную проблемуhttps://www.postgresql.org/message-id/[email protected]3.prod.outlook.com

Проблема проблемы согласуется с развитием версии PGAdmin

Notes:
-The html is part of the message.
-It doesn’t seem to matter what query is sent.
-The actual query seems to stay active (as if it is still working), but eventually comes back with a wait event: ClientWrite.
-We can remedy the situation by closing the query tool window (hence closing the session) and opening a new query too window (whilst never closing pgAdmin 4 or the connection to the server) then sending the query again.
-We are connected to a Linux VM via my Windows 7 PC.
-This happens probably 10 times a day while queries are being developed and tested.

I have:

Version
2.0
Copyright
Copyright 2013 — 2017, The pgAdmin Development Team
Python Version
2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]
Flask Version
0.12.2
Application Mode
Desktop
Current User
pgadmin4(at)pgadmin(dot)org<mailto:pgadmin4(at)pgadmin(dot)org>

Связанные ошибки в соответствии со ссылкой в ​​документеhttps://redmine.postgresql.org/issues/2806(Мне нужно подать заявку на открытие аккаунта)

Однако этот документ не дает методу ремонта, общается с разработкой коллег, модернизировал версию клиента PGADMIN 4, используйте последнюю версию прежней версии, продолжайте наблюдать

https://www.pgadmin.org/download/pgadmin-4-windows/

Я установил пакет pgadmin4 (v4.4) из официального репозитория пакетов Arch Linux. Работало до последнего обновления. Теперь я не могу добавить новый сервер. В браузере я получил ошибку:

http://127.0.0.1:36699/browser/server_group/children/1 500 (INTERNAL SERVER ERROR)

И из журнала сервера я получил ошибку:

2019-04-09 21:41:49,900: ERROR  flask.app:  'psycopg2.extensions.Column' object has no attribute '_asdict'
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/flask/app.py", line 1813, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/lib/python3.7/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.view_functions[rule.endpoint](**req.view_args)
  File "/usr/lib/python3.7/site-packages/flask/views.py", line 88, in view
    return self.dispatch_request(*args, **kwargs)
  File "/usr/lib/pgadmin4/web/pgadmin/browser/utils.py", line 259, in dispatch_request
    return method(*args, **kwargs)
  File "/usr/lib/pgadmin4/web/pgadmin/browser/utils.py", line 309, in children
    children.extend(module.get_nodes(*args, **kwargs))
  File "/usr/lib/pgadmin4/web/pgadmin/browser/server_groups/servers/__init__.py", line 127, in get_nodes
    in_recovery, wal_paused = recovery_state(conn, manager.version)
  File "/usr/lib/pgadmin4/web/pgadmin/browser/server_groups/servers/__init__.py", line 52, in recovery_state
    status, result = connection.execute_dict(recovery_check_sql)
  File "/usr/lib/pgadmin4/web/pgadmin/utils/driver/psycopg2/connection.py", line 1202, in execute_dict
    desc.to_dict() for desc in cur.ordered_description()
  File "/usr/lib/pgadmin4/web/pgadmin/utils/driver/psycopg2/connection.py", line 1202, in <listcomp>
    desc.to_dict() for desc in cur.ordered_description()
  File "/usr/lib/pgadmin4/web/pgadmin/utils/driver/psycopg2/cursor.py", line 94, in to_dict
    ores = OrderedDict(self.orig_col._asdict())
AttributeError: 'psycopg2.extensions.Column' object has no attribute '_asdict'

Интересно, это только я, потому что я ничего не получил от поиска Google.