Activity Watch Server quit unexpectedly

Support
#1

Hello, everyone!

I’ve been using ActivityWatch for a few months now. Starting some days ago the app doesn’t start anymore and I get the error:
“Module aw_server quit unexpectedly”
2021-03-13 14:00:41 [INFO ]: Using storage method: peewee (aw_server.main:26)
2021-03-13 14:00:41 [INFO ]: Starting up… (aw_server.main:31)
2021-03-13 14:00:41 [INFO ]: Using database file: C:\Users\Blaschko\AppData\Local\activitywatch\activitywatch\aw-server\peewee-sqlite.v2.db (aw_datastore.storages.peewee:90)
2021-03-13 14:00:41 [INFO ]: * Running on http://localhost:5600/ (Press CTRL+C to quit) (werkzeug:122)

I tried to reinstall it but it didn’t change.
I even watched in the resource monitor if something else uses the port 5600 but that was negative.

I hope somebody can help me because I really like ActivityWatch!
Thank you for this awesome program :smiley:

My System specs are:
Intel(R) Core™ i7-4790K CPU @ 4.00GHz
Windows 10 Home
16 GB RAM
64 Bit

#2

Hello @AlexandersProjects

In the logs there does not seem to be anything at all mentioning a crash. In the latest version of ActivityWatch we fixed an issue when crash messages got lost from the logs, are you running the latest version and if not could you update to it and try to start it again and see if there are any more log messages?

#3

Hello @johan-bjareholt

Thank you for the fast response!

I uninstalled and reinstalled the latest version and that was the log I got out of the “aw-server” folder.

I don’t understand why the server is not running anymore. When I look at modules it shows aw-server and aw-server-rust not running.

I hope that we can find a way to make it run again.

#4

aw-server-rust should not run, only aw-server should run. aw-server-rust is just for testing and can not be run at the same time as aw-server.

Does the date and time in the log also match the last time you got the message that “aw-server quit unexpectedly”?

#5

@johan-bjareholt
Interestingly, I get the message each time I start my computer. Just the newest date in the log is still the 13th.

#6

Does anybody else have a suggestion what I can do?
I really like activity watch and I hope that I can continue using it.

#7

I’d love to help, but unfortunately there’s no mention in the logs of it actually crashing. The logs you provided just contain expected messages. Since the logs are only from the 13th and there’s nothing saved when it actually crashes I don’t have any clues what might be wrong.

#8

Oh okay. Now I understand.

What are things that I could try? I will re-install it again, maybe it will help.

#9

Maybe try to start aw-server without aw-qt in the command line? That should guarantee that the error messages from aw-server will be intact.

So pretty much, start cmd.exe, go into the activitywatch folder with cd and then start aw-server.
Something similar to this, each line is a separate command:

cd “C:\Program Files\activitywatch”
aw-server.exe

#10

Hello @johan-bjareholt,

Thank you for the next trial. I started aw-server.exe and nothing else happened. Before I uninstalled and re-installed activity watch but nothing changed.
I don’t know if you can get something out of the log files, but those are the last ones I found in the folders:
aw-server folder:
2021-03-13 14:00:41 [INFO ]: Using storage method: peewee (aw_server.main:26)
2021-03-13 14:00:41 [INFO ]: Starting up… (aw_server.main:31)
2021-03-13 14:00:41 [INFO ]: Using database file: C:\Users\Blaschko\AppData\Local\activitywatch\activitywatch\aw-server\peewee-sqlite.v2.db (aw_datastore.storages.peewee:90)
2021-03-13 14:00:41 [INFO ]: * Running on http://localhost:5600/ (Press CTRL+C to quit) (werkzeug:122)

aw-qt folder:
2021-04-05 09:24:06 [INFO ]: Searching for bundled modules in: [‘C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw_qt’, ‘C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch’] (aw_qt.manager:67)
2021-04-05 09:24:06 [WARNING]: Found matching file but was not executable: C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-qt.desktop (aw_qt.manager:55)
2021-04-05 09:24:06 [WARNING]: Found matching file but was not executable: C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-qt.exe.manifest (aw_qt.manager:55)
2021-04-05 09:24:06 [WARNING]: Found matching file but was not executable: C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-server\aw-server.exe.manifest (aw_qt.manager:55)
2021-04-05 09:24:06 [WARNING]: Found matching file but was not executable: C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-server-rust\aw-server.service (aw_qt.manager:55)
2021-04-05 09:24:06 [WARNING]: Found matching file but was not executable: C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-watcher-afk\aw-watcher-afk.exe.manifest (aw_qt.manager:55)
2021-04-05 09:24:06 [WARNING]: Found matching file but was not executable: C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-watcher-window\aw-watcher-window.exe.manifest (aw_qt.manager:55)
2021-04-05 09:24:06 [INFO ]: Found bundled modules: (aw_qt.manager:72)
2021-04-05 09:24:06 [INFO ]: - aw-qt at C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-qt.exe (aw_qt.manager:24)
2021-04-05 09:24:06 [INFO ]: - aw-server at C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-server\aw-server.exe (aw_qt.manager:24)
2021-04-05 09:24:06 [INFO ]: - aw-server-rust at C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-server-rust\aw-server-rust.exe (aw_qt.manager:24)
2021-04-05 09:24:06 [INFO ]: - aw-watcher-afk at C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-watcher-afk\aw-watcher-afk.exe (aw_qt.manager:24)
2021-04-05 09:24:06 [INFO ]: - aw-watcher-window at C:\Users\Blaschko\AppData\Local\Programs\ActivityWatch\aw-watcher-window\aw-watcher-window.exe (aw_qt.manager:24)
2021-04-05 09:24:06 [INFO ]: Found system modules: (aw_qt.manager:99)
2021-04-05 09:24:06 [INFO ]: Starting module aw-server (aw_qt.manager:128)
2021-04-05 09:24:06 [INFO ]: Starting module aw-watcher-afk (aw_qt.manager:128)
2021-04-05 09:24:06 [INFO ]: Starting module aw-watcher-window (aw_qt.manager:128)
2021-04-05 09:24:06 [INFO ]: Creating trayicon… (aw_qt.trayicon:200)
2021-04-05 09:24:07 [INFO ]: Initialized aw-qt and trayicon succesfully (aw_qt.trayicon:235)

aw-watcher-window folder:
2021-04-05 09:24:08 [INFO ]: aw-watcher-window started (aw_watcher_window.main:44)
2021-04-05 09:24:11 [WARNING]: Not connected to server, 44345 requests in queue (aw_client.client:380)
2021-04-05 09:24:23 [WARNING]: Not connected to server, 44347 requests in queue (aw_client.client:380)
This message repeats many times until the following message comes two times
2021-04-05 10:24:05 [ERROR]: Exception thrown while trying to get active window: (-2147217385, ‘OLE error 0x80041017’, None, None) (aw_watcher_window.main:71)

I don’t know what else to do, but otherwise I will sadly need to choose another tracker :frowning: