Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Calling run_job() for Telemetry job does not work #5605

Closed
mkindahl opened this issue Apr 24, 2023 · 0 comments · Fixed by #5614
Closed

[Bug]: Calling run_job() for Telemetry job does not work #5605

mkindahl opened this issue Apr 24, 2023 · 0 comments · Fixed by #5614
Assignees
@mkindahl
Labels
bgw The background worker subsystem, including the scheduler bug

Comments

@mkindahl
Copy link
Contributor

What type of bug is this?

Unexpected error

What subsystems and features are affected?

Background worker

What happened?

It is possible to use run_job() for all jobs except the telemetry job, which gives a strange error.

TimescaleDB version affected

2.10.0

PostgreSQL version used

14.3

What operating system did you use?

Ubuntu 22.04 x86_64

What installation method did you use?

Source

What platform did you run on?

On prem/Self-hosted

Relevant log output and stack trace

No response

How can we reproduce the bug?

mats=# SELECT id, application_name, proc_name FROM _timescaledb_config.bgw_job WHERE proc_name LIKE 'policy_%';
 id |        application_name        |         proc_name          
----+--------------------------------+----------------------------
  2 | Error Log Retention Policy [2] | policy_job_error_retention
  1 | Telemetry Reporter [1]         | policy_telemetry
(2 rows)

mats=# CALL run_job(1);
ERROR:  function _timescaledb_internal.policy_telemetry(integer, jsonb) does not exist
mats=# CALL run_job(2);
CALL
@mkindahl mkindahl added the bug label Apr 24, 2023
@mkindahl mkindahl self-assigned this Apr 24, 2023
@mkindahl mkindahl added the bgw The background worker subsystem, including the scheduler label Apr 24, 2023
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 25, 2023
@mkindahl
Enable run_job() for telemetry job
42d6f93 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
@mkindahl mkindahl mentioned this issue Apr 25, 2023
Merged
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 25, 2023
@mkindahl
Enable run_job() for telemetry job
19386db 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 25, 2023
@mkindahl
Enable run_job() for telemetry job
537538d 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 25, 2023
@mkindahl
Enable run_job() for telemetry job
4c1c65d 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 26, 2023
@mkindahl
Enable run_job() for telemetry job
149ce69 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 26, 2023
@mkindahl
Enable run_job() for telemetry job
a2376ad 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 26, 2023
@mkindahl
Enable run_job() for telemetry job
c32dba3 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
mkindahl added a commit to mkindahl/timescaledb that referenced this issue Apr 27, 2023
@mkindahl
Enable run_job() for telemetry job
ef8df2d 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes timescale#5605
mkindahl added a commit that referenced this issue Apr 27, 2023
@mkindahl
Enable run_job() for telemetry job
be28794 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes #5605
Closed
github-actions bot pushed a commit that referenced this issue Apr 27, 2023
@mkindahl @timescale-automation
Enable run_job() for telemetry job
d485e06 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes #5605

(cherry picked from commit be28794)
mkindahl added a commit that referenced this issue May 2, 2023
@mkindahl
Enable run_job() for telemetry job
040a502 
Since telemetry job has a special code path to be able to be used both
from Apache code and from TSL code, trying to execute the telemetry job
with run_job() will fail.

This code will allow run_job() to be used with the telemetry job to
trigger a send of telemetry data. You have to belong to the group that
owns the telemetry job (or be the owner of the telemetry job) to be
able to use it.

Closes #5605

(cherry picked from commit be28794)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mkindahl mkindahl

Labels
bgw The background worker subsystem, including the scheduler bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enable run_job() for telemetry job mkindahl/timescaledb
1 participant
@mkindahl