-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR "Failed to set current task contexttx is closed" #541
Comments
Hello. Thanks for your request. Would you, please, be so kind to add [Unit]
Description=pg_timetable
Wants=network.target postgresql-11.service
After=network-online.target postgresql-11.service
[Service]
Restart=on-failure
ExecStartPre=/usr/bin/rm -f /%t/%n-pid /%t/%n-cid
ExecStart=/usr/bin/podman run --conmon-pidfile /%t/%n-pid --cidfile /%t/%n-cid -d --name pg_timetable-v5 \
-e PGTT_PGHOST=192.168.50.97 \
-e PGTT_PGPORT=5432 \
-e PGTT_PGDATABASE=timetablev5 \
-e PGTT_PGUSER=timetable \
-e PGTT_PGPASSWORD=xxxxx \
-e PGTT_RESTPORT=8111 \
--net=host \
-p 8111:8111 \
-v /etc/localtime:/etc/localtime:ro \
cybertecpostgresql/pg_timetable:5.1 \
-c umbosspm --log-level=debug
ExecStop=/usr/bin/sh -c "/usr/bin/podman rm -f `cat /%t/%n-cid`"
KillMode=none
Type=forking
PIDFile=/%t/%n-pid
[Install]
WantedBy=multi-user.target Thanks in advance. |
Hi, pg_timetable_debug_chain_147.txt Tanks for fast response. |
Would you please check patched version. The docker image is Thanks in advance! |
Hi, debug logs Thanks. |
Nice! Thanks for your report! |
…set-current-task-contexttx-is-closed [-] fix executor context for pgengine.SetCurrentTaskContext(), fixes #541
Hi,
error "Failed to set current task contexttx is closed" is logged in table timetable.log when task is configured to be executed on external database.
The task is completed successfully, but an error is shown in the log.
The task from the example is executed every minute, but the behavior is the same for tasks that are started in some other periods.
If the task is defined in a way that it is executed on the same DB where is pg_timetable then there is no error in log.
ERROR message is between messages "Remote connection established..." and "Closing remote session".
Timetable database and external database is on same Postgres cluster.
Timetable version: pg_timetable:5.1
OS: CentOS Linux release 7.9.2009 (Core)
Postgres: PostgreSQL 11.11
Task definition
database_connection is in format
postgres://username:password@ipaddress:port/database_name?sslmode=disable
Chain definition
Logs from execution_log table
Logs from log table
All podman logs for one chain.
podman_logs_chain_147.txt
pg_timetable service
pg_timetable_v5_service_podman_conf.txt
The text was updated successfully, but these errors were encountered: