[Support]: The Go2rtc service exited with code 256 (by signal 11) #14755

VinvarLaLece · 2024-11-03T13:25:39Z

VinvarLaLece
Nov 3, 2024

Describe the problem you are having

I have docker running on a bare metal Beelink EQ12. Except from a Traefik and cAdvisor container, nothing is installed or running on the EQ12.

When trying to run the Frigate container, I get a Go2RTC error that it 'exited with code 256 (by signal 11)'. I have stripped down to the bare/recommended docker compose file and frigate configuration file*. I am able to reach the Frigate WebUI (http://..ip..:5000) but I would like to have an application running that is not continiously busy trying to start Go2RTC.

Anybody an idea what I am doing wrong?

* In the files/outputs below, I added the files/logs which returns when I run the recommended configuration. However, the Go2RTC error persists regardless if I fix all the Frigate errors which happen in the log. So, using a existing path for the camera, making sure the Coral is loaded via the configuration file, etc. does not solve the issue.

Version

0.14.1-f4f3cfa

What browser(s) are you using?

Edge 130.0.2849.68

Frigate config file

mqtt:
  enabled: false

cameras:
  garage:
    enabled: false
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:544/rtsp
          roles:
            - detect
version: 0.14

Relevant Frigate log output

2024-11-03 14:02:21.157887257  [INFO] Preparing Frigate...
2024-11-03 14:02:21.174656748  [INFO] Starting Frigate...
2024-11-03 14:02:22.617863929  [2024-11-03 14:02:22] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-11-03 14:02:22.617922560  [2024-11-03 14:02:22] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-11-03 14:02:22.622745251  [2024-11-03 14:02:22] frigate.util.config            INFO    : frigate config does not need migration...
2024-11-03 14:02:22.630281401  [2024-11-03 14:02:22] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2024-11-03 14:02:22.632052160  [tcp @ 0x3769c840] Connection to tcp://127.0.0.1:544?timeout=0 failed: Connection refused
2024-11-03 14:02:22.652818957  [2024-11-03 14:02:22] peewee_migrate.logs            INFO    : Starting migrations
2024-11-03 14:02:22.653553466  [2024-11-03 14:02:22] peewee_migrate.logs            INFO    : There is nothing to migrate
2024-11-03 14:02:22.657824946  [2024-11-03 14:02:22] frigate.app                    INFO    : Recording process started: 343
2024-11-03 14:02:22.662261661  [2024-11-03 14:02:22] frigate.app                    INFO    : Recording process started: 346
2024-11-03 14:02:22.684208179  [2024-11-03 14:02:22] frigate.app                    INFO    : Output process started: 373
2024-11-03 14:02:22.685692742  [2024-11-03 14:02:22] detector.cpu                   INFO    : Starting detection process: 371
2024-11-03 14:02:22.686065479  [2024-11-03 14:02:22] frigate.detectors              WARNING : CPU detectors are not recommended and should only be used for testing or for trial purposes.
2024-11-03 14:02:22.692636220  [2024-11-03 14:02:22] frigate.app                    INFO    : Camera processor not started for disabled camera garage
2024-11-03 14:02:22.693391758  [2024-11-03 14:02:22] frigate.app                    INFO    : Capture process not started for disabled camera garage

Relevant go2rtc log output

2024-11-03 14:02:21.164828583  [INFO] Preparing new go2rtc config...
2024-11-03 14:02:21.630514364  [INFO] Starting go2rtc...
2024-11-03 14:02:21.644562087  [INFO] The go2rtc service exited with code 256 (by signal 11)
2024-11-03 14:02:22.652977047  [INFO] Removing stale config from last run...
2024-11-03 14:02:22.654011470  [INFO] Preparing new go2rtc config...
2024-11-03 14:02:22.969048899  [INFO] Starting go2rtc...

... endless loop of starting, exited with code 256, removing, etc. ...

FFprobe output from your camera

* redacted names, ips, etc. as it seems not relevant to initial boot of Go2RTC (to me).

user@server:~$ sudo docker exec -ti frigate /bin/bash
root@57367650719d:/opt/frigate# ffprobe https://[fqdn]/stream.html?src=[stream_name]
ffprobe version n5.1-2-g915ef932a3-20220731 Copyright (c) 2007-2022 the FFmpeg developers
  built with gcc 12.1.0 (crosstool-NG 1.25.0.55_3defb7b)
  configuration: --prefix=/ffbuild/prefix --pkg-config-flags=--static --pkg-config=pkg-config --cross-prefix=x86_64-ffbuild-linux-gnu- --arch=x86_64 --target-os=linux --enable-gpl --enable-version3 --disable-debug --enable-iconv --enable-libxml2 --enable-zlib --enable-libfreetype --enable-libfribidi --enable-gmp --enable-lzma --enable-fontconfig --enable-libvorbis --enable-opencl --enable-libpulse --enable-libvmaf --enable-libxcb --enable-xlib --enable-amf --enable-libaom --enable-libaribb24 --enable-avisynth --enable-libdav1d --enable-libdavs2 --disable-libfdk-aac --enable-ffnvcodec --enable-cuda-llvm --enable-frei0r --enable-libgme --enable-libass --enable-libbluray --enable-libjxl --enable-libmp3lame --enable-libopus --enable-mbedtls --enable-librist --enable-libtheora --enable-libvpx --enable-libwebp --enable-lv2 --enable-libmfx --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenh264 --enable-libopenjpeg --enable-libopenmpt --enable-librav1e --enable-librubberband --disable-schannel --enable-sdl2 --enable-libsoxr --enable-libsrt --enable-libsvtav1 --enable-libtwolame --enable-libuavs3d --enable-libdrm --enable-vaapi --enable-libvidstab --enable-vulkan --enable-libshaderc --enable-libplacebo --enable-libx264 --enable-libx265 --enable-libxavs2 --enable-libxvid --enable-libzimg --enable-libzvbi --extra-cflags=-DLIBTWOLAME_STATIC --extra-cxxflags= --extra-ldflags=-pthread --extra-ldexeflags=-pie --extra-libs='-ldl -lgomp' --extra-version=20220731
  libavutil      57. 28.100 / 57. 28.100
  libavcodec     59. 37.100 / 59. 37.100
  libavformat    59. 27.100 / 59. 27.100
  libavdevice    59.  7.100 / 59.  7.100
  libavfilter     8. 44.100 /  8. 44.100
  libswscale      6.  7.100 /  6.  7.100
  libswresample   4.  7.100 /  4.  7.100
  libpostproc    56.  6.100 / 56.  6.100
[tcp @ 0x560e37a0ecc0] Failed to resolve hostname [fqdn]: Name or service not known
https://[fqdn]/stream.html?src=[stream_name]: Input/output error

Frigate stats

No response

Install method

Docker Compose

docker-compose file or Docker CLI command

services:
  frigate:
    container_name: frigate
    privileged: true
    restart: unless-stopped
    image: ghcr.io/blakeblackshear/frigate:stable
    shm_size: "64mb" # update for your cameras based on calculation above
    devices:
      - /dev/apex_0:/dev/apex_0
      - /dev/dri/renderD128:/dev/dri/renderD128
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - /path/to/your/config:/config
      - /path/to/your/storage:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "8971:8971"
      - "5000:5000"
      - "8554:8554"
      - "8555:8555/tcp"
      - "8555:8555/udp"
    environment:
      FRIGATE_RTSP_PASSWORD: "password"

Object Detector

Coral

Network connection

Wired

Camera make and model

N/A

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

NickM-27 · 2024-11-04T20:06:39Z

NickM-27
Nov 4, 2024
Collaborator Sponsor

Are there any port conflicts? This seems to look like something else is using the port causing go2rtc to be unable to run

0 replies

VinvarLaLece · 2024-11-05T05:56:26Z

VinvarLaLece
Nov 5, 2024
Author

Hi NickM-27, thank you for thinking with me. To my knowledge the problem does not arises because of a port conflict for two reasons.

I have not exposed the Go2RTC port 1984 in my docker compose file.
Running sudo ss -tunlp confirms there is nothing listening on port 1984.

When explicitly exposing port 1984, the same error occurs. As a result, the webUI of Go2RTC is not reachable (http://ip:1984).

In the meantime I also went ahead by trying to add a Go2RTC block in the Frigate configuration file

mqtt:
  enabled: false

go2rtc:
  streams:
    camera_1:
      - ffmpeg:https://ip/...

cameras:
  garage:
    enabled: false
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:544/rtsp
          roles:
            - detect
version: 0.14

I validated the stream's address by running a separate instance of Go2RTC (my desired setup) with this Go2RTC configuration. When doing so, this stand-alone Go2RTC works as expected. (But, it does not solve the initial problem.)

So, unfortunately no solution yet. Might I ask if anybody has an idea what the problem could be?

1 reply

NickM-27 Nov 5, 2024
Collaborator Sponsor

Go2rtc uses many other ports besides that like 8555 and 8554

VinvarLaLece · 2024-11-06T07:27:56Z

VinvarLaLece
Nov 6, 2024
Author

Thanks again NickM-27 for helping me. I did a deep-dive on the ports ranning two scenarios. Unfortunately, not one of them solved the problem.
* In both scenarios I did not have a Go2RTC block in the Frigate config. I used the recommended (minimal) configuration as stated in my initial post.

Set up
I stopped & removed the traefik, cadvisor and frigate container. So, the system is now running without any application installed by me. Which I consider running a native/bare-bone Debian 12. At that moment I ran the following confirming no ports where opened.

user@server:~$ sudo ss -tunlp
Netid             State              Recv-Q             Send-Q                         Local Address:Port                         Peer Address:Port            Process                                             
tcp               LISTEN             0                  128                                  0.0.0.0:22                                0.0.0.0:*                users:(("sshd",pid=591,fd=3))                      
tcp               LISTEN             0                  128                                     [::]:22                                   [::]:*                users:(("sshd",pid=591,fd=4))

Also, I double checked it by running the command sudo ss -a | grep [port] where the port was a number specified in the official Docker Compose of Frigate. (So, 8971, 5000, 8554, 8555). None of these commands returned anything.

Scenario 1: running Frigate with the recommended configuration.
After I verified with sudo docker ps -a that Frigate was running with status '(healthy)', I confirmed that all ports where opened as expected. In the WebUI the error was mentioned again as an infinite loop.

user@server:~$ sudo ss -tunlp
Netid             State              Recv-Q             Send-Q                         Local Address:Port                         Peer Address:Port            Process                                             
udp               UNCONN             0                  0                                    0.0.0.0:8555                              0.0.0.0:*                users:(("docker-proxy",pid=5366,fd=4))             
udp               UNCONN             0                  0                                       [::]:8555                                 [::]:*                users:(("docker-proxy",pid=5373,fd=4))             
tcp               LISTEN             0                  128                                  0.0.0.0:22                                0.0.0.0:*                users:(("sshd",pid=591,fd=3))                      
tcp               LISTEN             0                  4096                                 0.0.0.0:8555                              0.0.0.0:*                users:(("docker-proxy",pid=5352,fd=4))             
tcp               LISTEN             0                  4096                                 0.0.0.0:8554                              0.0.0.0:*                users:(("docker-proxy",pid=5337,fd=4))             
tcp               LISTEN             0                  4096                                 0.0.0.0:8971                              0.0.0.0:*                users:(("docker-proxy",pid=5379,fd=4))             
tcp               LISTEN             0                  4096                                 0.0.0.0:5000                              0.0.0.0:*                users:(("docker-proxy",pid=5322,fd=4))             
tcp               LISTEN             0                  128                                     [::]:22                                   [::]:*                users:(("sshd",pid=591,fd=4))                      
tcp               LISTEN             0                  4096                                    [::]:8555                                 [::]:*                users:(("docker-proxy",pid=5360,fd=4))             
tcp               LISTEN             0                  4096                                    [::]:8554                                 [::]:*                users:(("docker-proxy",pid=5345,fd=4))             
tcp               LISTEN             0                  4096                                    [::]:8971                                 [::]:*                users:(("docker-proxy",pid=5387,fd=4))             
tcp               LISTEN             0                  4096                                    [::]:5000                                 [::]:*                users:(("docker-proxy",pid=5329,fd=4))

Scenario 2: running Frigate with recommended configuration WITHOUT any ports exposed
Ran the same test but this time I commented out the ports section in the Docker compose. As expected, Frigate ran healthy and the host was not listening on any of the ports. As I could obviously not enter the WebUI, I ran sudo docker logs frigate and I saw the same errors. So, Go2RTC was still exiting with exit code '256 (by signal 11)'.

user@server:~$ sudo ss -tunlp
Netid             State              Recv-Q             Send-Q                         Local Address:Port                         Peer Address:Port            Process                                             
tcp               LISTEN             0                  128                                  0.0.0.0:22                                0.0.0.0:*                users:(("sshd",pid=591,fd=3))                      
tcp               LISTEN             0                  128                                     [::]:22                                   [::]:*                users:(("sshd",pid=591,fd=4))

Conclusion
To me it seems highly unlikely that a port conflict on the host is the issue here. If that were the case, scenario 2 should have resulted in a proper start up/no exit codes.
I cannot rule out a port conflict within the container. However, as this forum is not flooded with comments on that, this seems very unlikely also.

Would anybody have another idea?

1 reply

NickM-27 Nov 6, 2024
Collaborator Sponsor

https://serverfault.com/a/67506 seems interesting, not sure why this would be occurring, but agreed it does not seem to be a port issue

VinvarLaLece · 2024-11-16T16:13:07Z

VinvarLaLece
Nov 16, 2024
Author

Thanks, NickM-27. That seems to be a step in the right direction as it got me to an error message.
I am not (that) familiar with segmentation violations. So here is what I did to further investigated the issue.

While the container was running I ran docker exec -ti frigate /bin/bash.

When executing df -h I do not see anything peculiar.

Filesystem                     Size  Used Avail Use% Mounted on
overlay                         30G  5.7G   23G  21% /
tmpfs                           64M     0   64M   0% /dev
shm                             64M  760K   64M   2% /dev/shm
[volume mount]                  30G  5.7G   23G  21% /config
tmpfs                          954M     0  954M   0% /tmp/cache

When executing top %Cpu(s), MiB Mem, and MiB Swap represents roughly the same values as running it on the host with enough head room on all parameters. (So, no CPU or memory overload to my eyes).

However, when running dmesg (still from inside the container), I do see the following

[ 3135.436601] Code: Unable to access opcode bytes at 0x7fe7a7f8bfd6.                                                                                                                                              
[ 3136.714106] go2rtc[45638]: segfault at 7fdd1b754000 ip 00007fdd1b754000 sp 00007ffe95fbc580 error 15 likely on CPU 3 (core 3, socket 0)                                                                         
[ 3136.714115] Code: Unable to access opcode bytes at 0x7fdd1b753fd6.                                                                                                                                              
[ 3137.994544] go2rtc[45650]: segfault at 7fded6a62000 ip 00007fded6a62000 sp 00007ffe576297f0 error 15 likely on CPU 2 (core 2, socket 0)                                                                         
[ 3137.994554] Code: Unable to access opcode bytes at 0x7fded6a61fd6.                                                                                                                                              
[ 3139.270420] go2rtc[45665]: segfault at 7f1dc77b0000 ip 00007f1dc77b0000 sp 00007ffeb827ecf0 error 15 likely on CPU 1 (core 1, socket 0)                                                                         
[ 3139.270434] Code: Unable to access opcode bytes at 0x7f1dc77affd6.                                                                                                                                              
[ 3140.550339] go2rtc[45677]: segfault at 7ff5af4ab000 ip 00007ff5af4ab000 sp 00007ffeb2b46030 error 15 likely on CPU 1 (core 1, socket 0)                                                                         
[ 3140.550348] Code: Unable to access opcode bytes at 0x7ff5af4aafd6.                                                                                                                                              
[ 3141.829471] go2rtc[45689]: segfault at 7f7c4ea2b000 ip 00007f7c4ea2b000 sp 00007fff02846200 error 15 likely on CPU 1 (core 1, socket 0)                                                                         
[ 3141.829480] Code: Unable to access opcode bytes at 0x7f7c4ea2afd6.
[ 3143.104549] go2rtc[45701]: segfault at 7f2f6679c000 ip 00007f2f6679c000 sp 00007ffdf4cdfab0 error 15 likely on CPU 0 (core 0, socket 0)
...

Does this sparks somebody's mind so you could point me to a solution?

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Support]: The Go2rtc service exited with code 256 (by signal 11) #14755

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 2 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

[Support]: The Go2rtc service exited with code 256 (by signal 11) #14755

VinvarLaLece Nov 3, 2024

Describe the problem you are having

Version

What browser(s) are you using?

Frigate config file

Relevant Frigate log output

Relevant go2rtc log output

FFprobe output from your camera

Frigate stats

Install method

docker-compose file or Docker CLI command

Object Detector

Network connection

Camera make and model

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 4 comments · 2 replies

NickM-27 Nov 4, 2024 Collaborator Sponsor

VinvarLaLece Nov 5, 2024 Author

NickM-27 Nov 5, 2024 Collaborator Sponsor

VinvarLaLece Nov 6, 2024 Author

NickM-27 Nov 6, 2024 Collaborator Sponsor

VinvarLaLece Nov 16, 2024 Author

VinvarLaLece
Nov 3, 2024

Replies: 4 comments 2 replies

NickM-27
Nov 4, 2024
Collaborator Sponsor

VinvarLaLece
Nov 5, 2024
Author

NickM-27 Nov 5, 2024
Collaborator Sponsor

VinvarLaLece
Nov 6, 2024
Author

NickM-27 Nov 6, 2024
Collaborator Sponsor

VinvarLaLece
Nov 16, 2024
Author