ITD fails to start Daemon #50

When attempting to use any function of ITD I am greeted with the following message

FTL Error while running app error="dial unix /tmp/itd/socket: connect: connection refused"

After some research, I figured this had to be the daemon failing to load, so I checked with systemctl status and got this.

ejhal@TheBigKahuna:~/Downloads$ systemctl --user status itd
× itd.service - InfiniTime Daemon (itd)
     Loaded: loaded (/usr/lib/systemd/user/itd.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Tue 2023-01-24 16:39:15 PST; 1min 17s ago
   Duration: 29ms
    Process: 6282 ExecStart=itd (code=exited, status=2)
   Main PID: 6282 (code=exited, status=2)
        CPU: 38ms

Jan 24 16:39:14 TheBigKahuna systemd[853]: itd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jan 24 16:39:14 TheBigKahuna systemd[853]: itd.service: Failed with result 'exit-code'.
Jan 24 16:39:15 TheBigKahuna systemd[853]: itd.service: Scheduled restart job, restart counter is at 5.
Jan 24 16:39:15 TheBigKahuna systemd[853]: Stopped InfiniTime Daemon (itd).
Jan 24 16:39:15 TheBigKahuna systemd[853]: itd.service: Start request repeated too quickly.
Jan 24 16:39:15 TheBigKahuna systemd[853]: itd.service: Failed with result 'exit-code'.
Jan 24 16:39:15 TheBigKahuna systemd[853]: Failed to start InfiniTime Daemon (itd).

Running on Ubuntu 22.10

When attempting to use any function of ITD I am greeted with the following message ``` FTL Error while running app error="dial unix /tmp/itd/socket: connect: connection refused" ``` After some research, I figured this had to be the daemon failing to load, so I checked with systemctl status and got this. ``` ejhal@TheBigKahuna:~/Downloads$ systemctl --user status itd × itd.service - InfiniTime Daemon (itd) Loaded: loaded (/usr/lib/systemd/user/itd.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Tue 2023-01-24 16:39:15 PST; 1min 17s ago Duration: 29ms Process: 6282 ExecStart=itd (code=exited, status=2) Main PID: 6282 (code=exited, status=2) CPU: 38ms Jan 24 16:39:14 TheBigKahuna systemd[853]: itd.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Jan 24 16:39:14 TheBigKahuna systemd[853]: itd.service: Failed with result 'exit-code'. Jan 24 16:39:15 TheBigKahuna systemd[853]: itd.service: Scheduled restart job, restart counter is at 5. Jan 24 16:39:15 TheBigKahuna systemd[853]: Stopped InfiniTime Daemon (itd). Jan 24 16:39:15 TheBigKahuna systemd[853]: itd.service: Start request repeated too quickly. Jan 24 16:39:15 TheBigKahuna systemd[853]: itd.service: Failed with result 'exit-code'. Jan 24 16:39:15 TheBigKahuna systemd[853]: Failed to start InfiniTime Daemon (itd). ``` Running on Ubuntu 22.10

What happens if you try to run ITD_LOGGING_LEVEL=debug itd in the terminal?

What happens if you try to run `ITD_LOGGING_LEVEL=debug itd` in the terminal?

What happens if you try to run ITD_LOGGING_LEVEL=debug itd in the terminal?

I get the following output

ejhal@TheBigKahuna:~$ ITD_LOGGING_LEVEL=debug itd
panic: Adapter hci0 not found

goroutine 1 [running]:
go.arsenm.dev/infinitime.Init({0xa0927f8, 0x4})
	/go/pkg/mod/go.arsenm.dev/infinitime@v0.0.0-20221107042015-72b558707ee3/btsetup.go:33 +0x192
main.main()
	/woodpecker/src/gitea.arsenm.dev/Arsen6331/itd/main.go:63 +0x1f8

> What happens if you try to run `ITD_LOGGING_LEVEL=debug itd` in the terminal? I get the following output ``` ejhal@TheBigKahuna:~$ ITD_LOGGING_LEVEL=debug itd panic: Adapter hci0 not found goroutine 1 [running]: go.arsenm.dev/infinitime.Init({0xa0927f8, 0x4}) /go/pkg/mod/go.arsenm.dev/infinitime@v0.0.0-20221107042015-72b558707ee3/btsetup.go:33 +0x192 main.main() /woodpecker/src/gitea.arsenm.dev/Arsen6331/itd/main.go:63 +0x1f8 ```

What is the output of rfkill list?

What is the output of `rfkill list`?

What is the output of rfkill list?

ejhal@TheBigKahuna:~$ rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

> What is the output of `rfkill list`? ``` ejhal@TheBigKahuna:~$ rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ```

Interesting. You have hci0, and it should be working, but BlueZ isn't detecting it for some reason. This doesn't appear to be an ITD issue as ITD doesn't handle the Bluetooh adapters directly, but I would check if you can connect to the watch using your regular Bluetooth settings or bluetoothctl. You should try rebooting your device, and if that doesn't fix it, try updating your system.

Interesting. You have `hci0`, and it should be working, but BlueZ isn't detecting it for some reason. This doesn't appear to be an ITD issue as ITD doesn't handle the Bluetooh adapters directly, but I would check if you can connect to the watch using your regular Bluetooth settings or `bluetoothctl`. You should try rebooting your device, and if that doesn't fix it, try updating your system.

I'm going to close this due to inactivity and because there's nothing obvious that I can do about this. If you're still having this problem and think it's due to ITD, please re-open the issue or write a comment and I'll reopen it. Thanks.

Labels Milestones

ITD fails to start Daemon #50