AutoKuma icon indicating copy to clipboard operation
AutoKuma copied to clipboard

AutoKuma v2 does not start

Open alexandervnuchkov opened this issue 1 month ago • 2 comments

When try to run AutoKuma 2.0.0 binary (both self-built and downloaded from the releases page), it fails with the following error:

Unable to load config: TOML parse error at line 1, column 26
  |
r�����}AM�|����º}��u�PPP�����jNº�`��␦�ֽwכ|%u��N�N�N�xؼlؼlؼl@ppp ���DD�N�N�NpS�tdppp P�td��(��(��(�D�DQ�tdR�td�N�N�N,,/lib64/ld-linux-x86-64.so.2GNU��GNU�����v	B�v@u���:O`K�GNU*��in�Ld� ���������������1��
  |                          ^
key with no value, expected `=`
 in autokuma
Invalid config: TOML parse error at line 1, column 26
  |
r�����}AM�|����º}��u�PPP�����jNº�`��␦�ֽwכ|%u��N�N�N�xؼlؼlؼl@ppp ���DD�N�N�NpS�tdppp P�td��(��(��(�D�DQ�tdR�td�N�N�N,,/lib64/ld-linux-x86-64.so.2GNU��GNU�����v	B�v@u���:O`K�GNU*��in�Ld� ���������������1��
  |                          ^
key with no value, expected `=`
 in autokuma

The config.toml file is in the ~/.config/autokuma folder. The previous version of AutoKuma (1.0.0) runs without issues and successfully creates monitors for Kuma v2.

The contents of the config.toml are:

sync_interval = 60
tag_name = "autokuma"
on_delete = "delete"
default_settings = '''
    docker.docker_container: {{container_name}}
    docker.docker_host: 1
    *.max_retries: 10
    *.interval: 60
    *.retryInterval: 60
    *.notification_id_list: {"1":true}
'''

[kuma]
url = "http://localhost:3001/"
username = "username"
password = "password"
sync_interval = 60

[docker]
hosts = "unix:///var/run/docker.sock"

Tried to put the config file into the AutoKuma folder, delete the config file and config DB, no luck.

My system: Ubuntu 24.04.3 x86_64 Kuma version is 2.0.2

alexandervnuchkov avatar Nov 13 '25 04:11 alexandervnuchkov

Looks like it is picking up the autokuma executable itself as config file, as a workaround you can try just renaming the file to something else then autokuma (or running it from a different working dir than the dir in which the file is located)

BigBoot avatar Nov 13 '25 04:11 BigBoot

You're right, renaming the file did the trick and it started alright. Thanks for the workaround!

alexandervnuchkov avatar Nov 13 '25 05:11 alexandervnuchkov