Skip to content

Aborted/restarted Container due to some memory-errors #177

Closed
@Jman1993

Description

@Jman1993

Hi,
I am getting error messages and my container are restarting occasionally with an error.
These are some of the errors i am getting.

malloc(): unsorted double linked list corrupted
SIGABRT: abort
PC=0x7fb51ab1a5ef m=0 sigcode=18446744073709551610
signal arrived during cgo execution

double free or corruption (!prev)
SIGABRT: abort
PC=0x7f50d6ace5ef m=3 sigcode=18446744073709551610
signal arrived during cgo execution

corrupted size vs. prev_size
SIGABRT: abort
PC=0x7f69802815ef m=14 sigcode=18446744073709551610
signal arrived during cgo execution

These Exporters are running on a Docker-Host on Ubuntu 22.04.05 LTS

Client: Docker Engine - Community
 Version:    27.5.1
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.20.0
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.32.4
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

I have 16GB of RAM available and 10GB of these are free.(Because these errors are looking like memory-problems)

I don't know if this is relevant, but i am Querying a Exadata-Machine in a RAC-Configuration. Because of this i am using a custom default metrics file using the gv$-Views.
I added docker logs-excerpt for one of my exporters and one example docker compose file.

docker_logs.txt

docker-compose-example.txt

Thank you very much!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions