This message was deleted.
# supports
Slackbot
12/07/2022, 9:40 PMThis message was deleted.
p
Pranay
12/08/2022, 7:23 AM
@Prashant Shahi Do you have more insights here?
@Kenneth Fuglsang Docker Swarm should ideally work, but k8s and docker standalone is more battleproof as lot more users try that route.
Can you give SigNoz try on K8s or docker swarm is a hard requirement for you?
k
Kenneth Fuglsang
12/08/2022, 11:15 PMDocker Swarm is hard requirement. I don't think this is the issue though.
I would expect though that the query-service would output any meaningful log content to why it crashes.
p
Prashant Shahi
12/10/2022, 9:53 AM@Kenneth Fuglsang Tested SigNoz on Swarm, it works as expected.
Prashant Shahi
12/10/2022, 9:53 AMcan you share more about the Swarm cluster?
Prashant Shahi
12/10/2022, 9:54 AMdo you have more than 1 nodes?
Prashant Shahi
12/10/2022, 9:54 AMHave you changed anything from the default config?
k
Kenneth Fuglsang
12/12/2022, 10:11 PMI have three nodes in the swarm cluster. I had to modify the default config a bit since I don't have access to anything other than the Portainer interface, and thus I spin everything up from just the docker compose file. Other configs are placed as configs in the swarm and mounts are nfs-based.
Kenneth Fuglsang
12/12/2022, 10:20 PMI've just updated query-service to 0.12.0 and now I get this error logged: FATAL query-service/main.go:68 Failed to create server{error 26 0 Error in creating tables: database is locked}
Which database is it referring to?
p
Prashant Shahi
12/13/2022, 3:02 AMMost likely SQLite db file.
Prashant Shahi
12/13/2022, 3:03 AMThat would be mounted on query services with both read/write access.
14 Views