On windows (10,11 and windows server 2022).
With PostgreSQL 14 and 15.
Pgagent is running as a service.
It runs SQL jobs and access pgpass correctly to run jobs as Local on multiple DBs.
It also execute batch files correctly.
**BUT if the batch files called in the step does not exists, the job fail (as expected) but the step hangs in an "r" state.**
Job log:
Step log:
The expected behavior is that it return as status "f", result "1" and output "path to file does not exist"
On another vm, with pg10, It works as intended like below:
The "r" state is not an effect of PgAgent crashing.
The service keeps running.(To be noted that the service crash if I run another agent that crashes whether it is SQL or Batch)
**Anyone had that issue and managed to fix it ?**
EDIT :
The postgresql log points to the encoding. It is in french and the accents aren't handled.
*
It runs SQL jobs and access pgpass correctly to run jobs as Local on multiple DBs.
It also execute batch files correctly.
**BUT if the batch files called in the step does not exists, the job fail (as expected) but the step hangs in an "r" state.**
Job log:
Step log:
The expected behavior is that it return as status "f", result "1" and output "path to file does not exist"
On another vm, with pg10, It works as intended like below:
The "r" state is not an effect of PgAgent crashing.
The service keeps running.(To be noted that the service crash if I run another agent that crashes whether it is SQL or Batch)
**Anyone had that issue and managed to fix it ?**
EDIT :
The postgresql log points to the encoding. It is in french and the accents aren't handled.
*2023-05-31 17:08:05.928 CEST ERREUR: séquence d'octets invalide pour l'encodage « UTF8 » : 0x82*
Asked by Boodoo
(65 rep)
May 30, 2023, 06:58 PM
Last activity: Feb 27, 2025, 04:00 PM
Last activity: Feb 27, 2025, 04:00 PM