mirror
/
changedetection.io
kopia lustrzana https://github.com/dgtlmoon/changedetection.io
1
0
Forkuj 0
Kod Zgłoszenia Packages Projekty Wydania Wiki Aktywność

Improve formatting

master
Dmitriy Yukhanov 2021-11-08 23:24:06 +03:00
rodzic 3be8f46fd8
commit 67a2b4eea1
1 zmienionych plików z 16 dodań i 9 usunięć
Pokaż statystyki Ściągnij plik aktualizacji Ściągnij plik porównania Expand all files Collapse all files

25
Troubleshooting.md

@ -3,18 +3,23 @@
### Docker log ### Docker log
If you're running changedetection.io from the docker, it's as simple as calling this command: If you're running changedetection.io from the docker, it's as simple as calling this command:
`docker logs changedetection.io &> logs.txt` docker logs changedetection.io &> logs.txt
## Workaround for 'pyinit_main: can't initialize time' error on Raspberry Pi ## Workaround for 'pyinit_main: can't initialize time' error on Raspberry Pi
When using or installing changedetection.io at the Raspberry Pi device, you can experience these errors: When using or installing changedetection.io at the Raspberry Pi device, you can experience these errors:
- `docker-compose top` or `docker top changedetection.io` do return: - `docker-compose top` or `docker top changedetection.io` do return:
`Error response from daemon: Container {CONTAINER_ID} is restarting, wait until the container is running` ```
Error response from daemon: Container {CONTAINER_ID} is restarting, wait until the container is running
```
- `docker logs changedetection.io &> logs.txt` produces logs with the following error: - `docker logs changedetection.io &> logs.txt` produces logs with the following error:
`pyinit_main: can't initialize time` ```
pyinit_main: can't initialize time
```
As per https://github.com/linuxserver/docker-papermerge/issues/4, run these commands to workaround this problem: As per https://github.com/linuxserver/docker-papermerge/issues/4, run these commands to workaround this problem:
`wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_armhf.deb` `wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_armhf.deb`
`sudo dpkg -i libseccomp2_2.5.1-1_armhf.deb` `sudo dpkg -i libseccomp2_2.5.1-1_armhf.deb`
## No Notifications ## No Notifications
@ -22,8 +27,10 @@ As per https://github.com/linuxserver/docker-papermerge/issues/4, run these comm
Make sure you're not sending too long messages, as some notification targets do have message length limitations. Make sure you're not sending too long messages, as some notification targets do have message length limitations.
For example, too long notification message submitted to the Telegram will produce the following error in the log file: For example, too long notification message submitted to the Telegram will produce the following error in the log file:
`WARNING:apprise:Failed to send Telegram notification to {ID}: Bad Request: message is too long, error=400.` ```
`DEBUG:apprise:Response Details:` WARNING:apprise:Failed to send Telegram notification to {ID}: Bad Request: message is too long, error=400.
`b'{"ok":false,"error_code":400,"description":"Bad Request: message is too long"}'` DEBUG:apprise:Response Details:
b'{"ok":false,"error_code":400,"description":"Bad Request: message is too long"}'
```
You can easily get out of length limitations is you're including `{current_snapshot}` into the Notification Body. You can easily get out of length limitations is you're including `{current_snapshot}` into the Notification Body.