Error on start

[JAR4x4]

Great work @bernikr !, I'm trying to run ownhaystack on a rasperry. I have a fresh install of raspberry os. I get the following error on startup:

Connected to MQTT server
Stopped Listening to MQTT messages, got 0 last timestamps
loading keys from /data/keys
querying http://anisette:6969 for an anisette server
Encountered exception: HTTPConnectionPool(host='anisette', port=6969): Max retries exceeded with url: / (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7facbfd2b0>: Failed to establish a new connection: [Errno 111] Connection refused'))
Retrying #1 after 5 seconds

[bernikr]

can you try starting the project with docker compose up and see if the same error happens?

[isibizi]

i have the same error in my new env

<urllib3.connection.HTTPConnection object at 0x754cb4185d90>: Failed to resolve 'anisette' ([Errno -2] Name or service not known)"))
haystack-1 | Retrying #6 after 10 seconds
mqtt-1 | 1736859438: New connection from 172.19.0.5:53437 on port 1883.
mqtt-1 | 1736859438: New client connected from 172.19.0.5:53437 as auto-BFA7292E-8259-847E-12C2-B69DA0350BFD (p2, c1, k60).
haystack-1 | Connected to MQTT server
haystack-1 | Stopped Listening to MQTT messages, got 0 last timestamps
haystack-1 | loading keys from /data/keys
haystack-1 | querying http://anisette:6969 for an anisette server
haystack-1 | Encountered exception: HTTPConnectionPool(host='anisette', port=6969): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x754cb4199480>: Failed to resolve 'anisette' ([Errno -2] Name or service not known)"))
haystack-1 | Retrying #7 after 10 seconds
mqtt-1 | 1736859449: New connection from 172.19.0.5:47147 on port 1883.
mqtt-1 | 1736859449: New client connected from 172.19.0.5:47147 as auto-F14430CE-E82D-08C8-844B-429554E2744C (p2, c1, k60).
haystack-1 | Connected to MQTT server
haystack-1 | Stopped Listening to MQTT messages, got 0 last timestamps
haystack-1 | loading keys from /data/keys
haystack-1 | querying http://anisette:6969 for an anisette server
haystack-1 | Encountered exception: HTTPConnectionPool(host='anisette', port=6969): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x754cb419a030>: Failed to resolve 'anisette' ([Errno -2] Name or service not known)"))
haystack-1 | Retrying #8 after 30 seconds
mqtt-1 | 1736859480: New connection from 172.19.0.5:49427 on port 1883.
mqtt-1 | 1736859480: New client connected from 172.19.0.5:49427 as auto-E12106C3-3E9C-A0E2-4415-64323C00A627 (p2, c1, k60).
haystack-1 | Connected to MQTT server
haystack-1 | Stopped Listening to MQTT messages, got 0 last timestamps
haystack-1 | loading keys from /data/keys
haystack-1 | querying http://anisette:6969 for an anisette server
haystack-1 | Encountered exception: HTTPConnectionPool(host='anisette', port=6969): Max retries exceeded with url: / (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x754cb419a470>: Failed to resolve 'anisette' ([Errno -2] Name or service not known)"))
haystack-1 | Retrying #9 after 30 seconds

[isibizi]

The Solution for this issue is to add UID and GID from the docker user, see my example. The Anisette Server won't start and this is why we see this error.

Next issue is this:

user: 'GID:UID' <<<< change it with you docker user id.

services:
haystack:
image: ghcr.io/bernikr/ownhaystack
depends_on:
- mqtt
- anisette
- owntracks
volumes:
- ./data:/data
environment:
- APPLE_USERNAME=xxxxxxx
- APPLE_PASSWORD=xxxxxxx
- MQTT_SERVER=mqtt
- ANISETTE_URL=http://anisette:6969
mqtt:
image: eclipse-mosquitto:2.0
configs:
- source: mosquitto.conf
target: /mosquitto/config/mosquitto.conf
anisette:
image: dadoum/anisette-v3-server:latest
volumes:
- ./data/anisette:/home/Alcoholic/.config/anisette-v3
user: '0:0'
ports:
- "6969:6969"
owntracks:
image: owntracks/recorder:0.9.9
depends_on:
- mqtt
volumes:
- ./data/owntracks:/store
environment:
- OTR_HOST=mqtt
ports:
- "8083:8083"

configs:
mosquitto.conf:
content: |
allow_anonymous true
listener 1883

[isibizi]

This issue is still exists, do you have a solution for that?

[bernikr]

@isibizi i just published an image with better logging so i can find this error, can you pull the latest image and try again?