Skip to content

Error on fixcore container #2325

Open
Open

Description

@senthilnathan-am

Description

After deploying all containers, I am unable to access fix shell as below,

root@skywalk-rnd:~# docker exec -it fixshell fixsh
25-04-19 11:02:14|fixshell| INFO|38|MainThread  Waiting up to 300.00s for fixcore to come online at http://localhost:8900
25-04-19 11:07:15|fixshell|CRITICAL|38|MainThread  fixcore is not online at http://localhost:8900

Found fixcore container is throwing below error.... Need someone help to fix it issue.

root@skywalk-rnd:~/fixinventory# docker logs -f fixcore
INFO - Setting uid:gid of fixinventory to 0:0
INFO - Setting timezone Etc/UTC
{"timestamp": "2025-04-19T10:34:40", "level": "INFO", "message": "Starting up version=4.2.0 on system with cpus=8, available_mem=14.37 GiB, total_mem=15.61 GiB", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:40", "level": "INFO", "message": "Create ArangoHTTPClient with timeout=900 and verify=False", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:40", "level": "WARNING", "message": "Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d95726c0>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:42", "level": "WARNING", "message": "Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9571af0>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:46", "level": "WARNING", "message": "Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9572f00>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:46", "level": "WARNING", "message": "Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9573470>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:48", "level": "WARNING", "message": "Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9572630>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:52", "level": "WARNING", "message": "Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9572f00>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:52", "level": "WARNING", "message": "Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9572c90>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:54", "level": "WARNING", "message": "Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9573ad0>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:58", "level": "WARNING", "message": "Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fd3d9573e30>: Failed to establish a new connection: [Errno 111] Connection refused')': /_db/fix/_admin/echo", "pid": 28, "thread": "MainThread", "process": "fixcore"}
{"timestamp": "2025-04-19T10:34:58", "level": "WARNING", "message": "Can not access database. Trying again in 5 seconds: Can't connect to host(s) within limit (3)", "pid": 28, "thread": "MainThread", "process": "fixcore"}

Version

4.2.0

Environment

Ubuntu 22.04 LTS

Steps to Reproduce

After installing fixinventory 4.2.0, run below command
docker exec -it fixshell fixsh

Logs

Additional Context

No response

Activity

  1. lloesche commented on May 18, 2025

    @lloesche
    Member

    The error says "Can not access database". Have you checked that the database is accessible from the fixcore container?

  2. Requium commented on May 29, 2025

    @Requium

    Probably is the same error i had, the graphdb was on stale with logs error Illegal instruction (core dumped), that refers to arangodb needs AVX Support, and led me to the hypervisor, which was not sending the AVX support to the VM,changing that on the VM Hardware options helped....with that it was solved, maybe it can help you with your problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions