[Bug]: Telemetry Reporter was terminated by signal 11: Segmentation fault: 11

[promisetochi]

What type of bug is this?

Crash

What subsystems and features are affected?

Background worker, Telemetry

What happened?

Adding the Timescaledb extension to a database results in a crash that terminates all postgres processes. This wouldn't necessarily be a serious issue but it makes it impossible to create db migrations using prisma because it always terminates the migration process.

Also, I'm unsure if this has anything to do with mac os sonoma.

TimescaleDB version affected

2.11.1

PostgreSQL version used

14.8

What operating system did you use?

Mac OS Sonoma 14.0 Beta

What installation method did you use?

Other

What platform did you run on?

Other

Relevant log output and stack trace

2023-07-26 15:58:31.645 WAT [17387] WARNING:  
    WELCOME TO
     _____ _                               _     ____________  
    |_   _(_)                             | |    |  _  \ ___ \ 
      | |  _ _ __ ___   ___  ___  ___ __ _| | ___| | | | |_/ / 
      | | | |  _ ` _ \ / _ \/ __|/ __/ _` | |/ _ \ | | | ___ \ 
      | | | | | | | | |  __/\__ \ (_| (_| | |  __/ |/ /| |_/ /
      |_| |_|_| |_| |_|\___||___/\___\__,_|_|\___|___/ \____/
                   Running version 2.11.1
    For more information on TimescaleDB, please visit the following links:

     1. Getting started: https://docs.timescale.com/timescaledb/latest/getting-started
     2. API reference documentation: https://docs.timescale.com/api/latest
     3. How TimescaleDB is designed: https://docs.timescale.com/timescaledb/latest/overview/core-concepts

    Note: TimescaleDB collects anonymous reports to better understand and assist our users.
    For more information and how to disable, please see our docs https://docs.timescale.com/timescaledb/latest/how-to-guides/configuration/telemetry.

2023-07-26 15:58:31.645 WAT [17387] CONTEXT:  PL/pgSQL function inline_code_block line 16 at RAISE
2023-07-26 15:58:31.685 WAT [16874] LOG:  background worker "Telemetry Reporter [1]" (PID 17408) was terminated by signal 11: Segmentation fault: 11
2023-07-26 15:58:31.685 WAT [16874] LOG:  terminating any other active server processes
2023-07-26 15:58:31.689 WAT [16874] LOG:  all server processes terminated; reinitializing
2023-07-26 15:58:31.747 WAT [17410] LOG:  database system was interrupted; last known up at 2023-07-26 15:58:13 WAT
2023-07-26 15:58:31.955 WAT [17410] LOG:  database system was not properly shut down; automatic recovery in progress
2023-07-26 15:58:31.959 WAT [17410] LOG:  redo starts at 0/7898DD98
2023-07-26 15:58:31.966 WAT [17410] LOG:  invalid record length at 0/78B822D8: wanted 24, got 0
2023-07-26 15:58:31.966 WAT [17410] LOG:  redo done at 0/78B822B0 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2023-07-26 15:58:31.992 WAT [16874] LOG:  database system is ready to accept connections
2023-07-26 15:58:31.993 WAT [17416] LOG:  TimescaleDB background worker launcher connected to shared catalogs

How can we reproduce the bug?

1. Set up a Mac OS environment with PostgreSQL 14.8 (Homebrew) and Timescaledb 2.11.1
2. Add Timescaledb to a database with `CREATE EXTENSION IF NOT EXISTS timescaledb;`
3. View postgres logs
4. Logs should contain a `background worker "Telemetry Reporter [1]" (PID 17408) was terminated by signal 11: Segmentation fault: 11` line

[akuzm]

As a workaround, please try adding timescaledb.telemetry_level=off to your postgresql.conf, it should disable the telemetry altogether.

[promisetochi]

That worked @akuzm. Thank you!

[nikkhils]

I tried to reproduce this on my Mac, without any luck so far.

[jnidzwetzki]

Hello @promisetochi,

I tried to reproduce the issue on my Mac, but I was not able to reproduce the behavior so far. Is the issue still reproducible on your system or was this crash maybe caused by an invalid response or an unreachable Telemetry server? Could you check if the error still occurs in your environment?

[github-actions[bot]]

Dear Author,

This issue has been automatically marked as stale due to lack of activity. With only the issue description that is currently provided, we do not have enough information to take action. If you have or find the answers we would need, please reach out. Otherwise, this issue will be closed in 30 days.

Thank you!

[snps-hengxiao]

Hi all,

We have seen a similar issue on SUSE Linux with the same symptom. The workaround works, but we need the metrics service for our production environment.

Thanks.

[antekresic]

Hi there, would you mind sharing a bit about your setup? How did you install TimescaleDB?

Need a bit more details in order to reproduce the issue.

Thanks!