PostgreSQL jQuery error in the PostgreSQL logs

Questions about WAPT Server / Requests and help related to the WAPT server
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Answer
Mikael S
Messages: 26
Registration: January 20, 2025 - 3:54 PM

October 3, 2025 - 8:11 AM

Good morning,

In the database logs, I came across this

Code: Select all

2025-10-02 23:59:27.817 CEST [1202] LOG:  starting PostgreSQL 15.14 (Debian 15.14-0+deb12u1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14+deb12u1) 12.2.0, 64-bit
2025-10-02 23:59:27.822 CEST [1202] LOG:  listening on IPv6 address "::1", port 5432
2025-10-02 23:59:27.822 CEST [1202] LOG:  listening on IPv4 address "127.0.0.1", port 5432
2025-10-02 23:59:27.824 CEST [1202] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-10-02 23:59:27.856 CEST [1224] LOG:  database system was shut down at 2025-10-02 23:59:02 CEST
2025-10-02 23:59:27.888 CEST [1202] LOG:  database system is ready to accept connections
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt ERROR:  extension "jsquery" is not available
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt DETAIL:  Could not open extension control file "/usr/share/postgresql/15/extension/jsquery.control": No such file or directory.
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt HINT:  The extension must first be installed on the system where PostgreSQL is running.
2025-10-02 23:59:30.866 CEST [1794] wapt@wapt STATEMENT:  CREATE EXTENSION if not exists jsquery;
2025-10-02 23:59:30.867 CEST [1794] wapt@wapt WARNING:  there is no transaction in progress
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt LOG:  could not send data to client: Broken pipe
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt STATEMENT:  COPY public.hostauditdata (id, host_id, value_id, value_date, value_section, value_key, value, expiration_date, created_on, created_by) TO stdout;
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt ERROR:  canceling statement due to user request
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt STATEMENT:  COPY public.hostauditdata (id, host_id, value_id, value_date, value_section, value_key, value, expiration_date, created_on, created_by) TO stdout;
2025-10-03 00:02:58.370 CEST [2675] postgres@wapt FATAL:  connection to client lost
You don't mention the need to install the postgresql-15-jsquery package under bookworm in the wiki. Or perhaps it's on a different page than https://www.wapt.fr/en/doc/wapt-server- ... er-install



Sincerely,
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

October 3, 2025 - 11:04

Hi Mickael,

the jQuery extension is no longer necessary for WAPT itself. And on a fresh install, the postconf script only installs it if it's available on the system. But it's true that it can cause problems on a backup restore or server reinstall. This extension can be used in SQL/JSON queries.

I'll check with the team to see if we can add it back to the documentation during installation or if we can find a better way to clean this up during an upgrade.

Regards,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Answer