You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I got the add-on up and running with 3 consumers in docker containers in my Synology NAS based on the default env file but I don't see them doing anything. When looking at the logs, I see Trackers being updated and that they have successfully connected to mongodb, but then I get the error: "Failed to connect and setup channel".
I see usage from the mongodb container but not much from the consumers. Perhaps I just dont understand how they work or when they are supposed to work.
To Reproduce
Steps to reproduce the behavior: N/A
Expected behavior
A clear and concise description of what you expected to happen.
Logs
Provide logs for all containers when this issue occurs.
If the logs are short, make sure to triple backtick them, or use https://pastebin.com/
'''
{"level":30,"time":1709932559776,"pid":1,"hostname":"0c0030000002","msg":"Trackers updated at 1709932559775: 98 trackers"}
{"level":30,"time":1709932560017,"pid":1,"hostname":"0c0030000002","msg":"Successfully connected to mongo db"}
{"level":50,"time":1709932560021,"pid":1,"hostname":"0c0030000002","msg":"Failed to connect and setup channel"}
'''
'''
{"level":30,"time":1709932552937,"pid":1,"hostname":"003f40000006","msg":"Trackers updated at 1709932552937: 98 trackers"}
{"level":50,"time":1709932553145,"pid":1,"hostname":"003f40000006","msg":"Failed syncing database"}
{"level":30,"time":1709932562184,"pid":1,"hostname":"003f40000006","msg":"Trackers updated at 1709932562184: 98 trackers"}
{"level":30,"time":1709932562289,"pid":1,"hostname":"003f40000006","msg":"Successfully connected to mongo db"}
{"level":50,"time":1709932562294,"pid":1,"hostname":"003f40000006","msg":"Failed to connect and setup channel"}
''' Hardware:
OS and distro: Synology NAS DSM 7.2.1
Server: Baremetal
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
I got the add-on up and running with 3 consumers in docker containers in my Synology NAS based on the default env file but I don't see them doing anything. When looking at the logs, I see Trackers being updated and that they have successfully connected to mongodb, but then I get the error: "Failed to connect and setup channel".
I see usage from the mongodb container but not much from the consumers. Perhaps I just dont understand how they work or when they are supposed to work.
To Reproduce
Steps to reproduce the behavior: N/A
Expected behavior
A clear and concise description of what you expected to happen.
Logs
Provide logs for all containers when this issue occurs.
If the logs are short, make sure to triple backtick them, or use https://pastebin.com/
'''
{"level":30,"time":1709932559776,"pid":1,"hostname":"0c0030000002","msg":"Trackers updated at 1709932559775: 98 trackers"}
{"level":30,"time":1709932560017,"pid":1,"hostname":"0c0030000002","msg":"Successfully connected to mongo db"}
{"level":50,"time":1709932560021,"pid":1,"hostname":"0c0030000002","msg":"Failed to connect and setup channel"}
'''
'''
{"level":30,"time":1709932552937,"pid":1,"hostname":"003f40000006","msg":"Trackers updated at 1709932552937: 98 trackers"}
{"level":50,"time":1709932553145,"pid":1,"hostname":"003f40000006","msg":"Failed syncing database"}
{"level":30,"time":1709932562184,"pid":1,"hostname":"003f40000006","msg":"Trackers updated at 1709932562184: 98 trackers"}
{"level":30,"time":1709932562289,"pid":1,"hostname":"003f40000006","msg":"Successfully connected to mongo db"}
{"level":50,"time":1709932562294,"pid":1,"hostname":"003f40000006","msg":"Failed to connect and setup channel"}
'''
Hardware:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: