Closed Sakrecoer closed 3 years ago
Hi @Sakrecoer, could you please provide instructions on how to reproduce the issue? I created a new telegrambee and could not reproduce the bug on my side. The bot is correctly sending a message to my chat_id. Please provide the error log.
Thank you.
I haven't had that much luck. I don't understand: absolutely nothing has changed in my set-up. It used to work fine. @corrantho Could you please instruct me where to find the error logs? I've been looking all over the place without result.
@Sakrecoer There's no separate logfile. Simply start beehive, and it will log on stdout
. If you're running beehive as a systemd
service, check journalctl
.
@muesli of course... silly me lol...
Well, this is very weird. The bot is authorized on telegram. Filters are executing fine. No error messages at all and nothing happens.
aug 18 10:05:29 pi7 beehive[20230]: INFO[0166] Executing filter: {{test eq .user_id "numer_redacted}}
aug 18 10:05:29 pi7 beehive[20230]: INFO[0166] Executing filter: {{test Contains .text "#hashtag"}}
wow.... i have no idea what has happened. It's like the Nth time i restart it. I did it again, but this time after restart it sent out the last event i tried to deliver before reboot. (sending a message to the telegram bot for it to deliver them in a channel)
But there's nothing about it in journalctl
Closing this, everything seems to be working again. Probably something fishy with the system my beehive is running on.
As of august 6th the telegram bee stopped working. I suspect there might have been some change in the API. I've tested with a new API token, but i'm not too sure how to debug it as i don't seem to be able to locate the logs anymore :/