Kimai time tracking software

LayLow · August 21, 2024, 10:49pm

Doing that atm. It would be helpful if there are instructions on how to install, update and remover plugins.

TIA!

mrmarkuz · August 22, 2024, 10:55am

Thanks for testing!

I released an app update to be able to manage plugins.

Instructions can be found on the projects GitHub page.

We could also include some good plugins in the app so they don’t need to be installed manually.

LayLow · August 22, 2024, 11:43am

Thanks, works like a charm! Both the update and the plugin installation.

transocean · August 23, 2024, 8:18am

@mrmarkuz

After installation, Kimai worked as expected.
But after integrating Deduction-Time Bundle – Kimai, as you described, I only see Bad Gateway instead of the login page.

Regards…

Uwe

mrmarkuz · August 23, 2024, 8:38am

Thanks for testing!

It takes some time until kimai is restarted.
If it doesn’t start please check the logs on the logs page.

To check the service:

runagent -m kimai1 systemctl --user status kimai -l

To restart kimai manually:

runagent -m kimai1 systemctl --user restart kimai

transocean · August 23, 2024, 9:08am

After I removed the plugin and reinstalled it, everything works again.

LayLow · August 23, 2024, 10:26am

May I suggest these free useful plugins:

Thanks for your considerations.

transocean · August 24, 2024, 8:22am

After the server was started every morning, Kimai stopped working again. The kimai-app service does not start.

After reinstalling Kimai and the plugin yesterday, everything worked fine.

Then this morning…

The manual restart of Kimai is not successful.

LayLow · August 24, 2024, 9:49am

I performed a forced reboot. Kimai is back up, but it takes a while…

pike · August 24, 2024, 9:57am

Forced reboot of the “host” or the container?

Are you able to monitor hardware resource use while starting up kimai?

transocean · August 24, 2024, 10:01am

No better result after three reboots.

transocean · August 24, 2024, 10:02am

No, i cant.

LayLow · August 24, 2024, 10:08am

Host

No idea how to do that, mine is a remote VPS

pike · August 24, 2024, 10:09am

Personal suggestion: consider to find a way to monitor resource use on your “host”. IDK unfortunately what suggest you for “realtime”/console monitoring and statistical data collection (with graphs).

Maybe glances might be “proper enough” resource status tool for a container host.

Seems available in Debian
https://tracker.debian.org/pkg/glances
and rocky linux

should be part of epel repository.
(article dated 2023)

dnutan · August 24, 2024, 10:21am

Any other hint from:

runagent -m kimai1 systemctl --user status kimai-app -l

While installing the deduction plugin there are some php warnings (when running the console command).

Edit:
kimai-app service seems to be active but disabled by default (no autostart, so something else must start it, in this case podman run):

After reboot, kimai-app service remains inactive. Podman run call exits with status 126.

2024-08-24T12:47:21+02:00 [1:kimai1:systemd] Starting Podman kimai-app.service...
2024-08-24T12:47:23+02:00 [1:kimai1:kimai1] Error: lsetxattr /home/kimai1/.local/share/containers/storage/volumes/kimai-plugins/_data/DeductionTimeBundle: operation not permitted
2024-08-24T12:47:23+02:00 [1:kimai1:systemd] kimai-app.service: Control process exited, code=exited, status=126/n/a
2024-08-24T12:47:23+02:00 [1:kimai1:kimai1] 73211bafe42129e5f2079c824ef18d7c1990e3996f005667d2a2897191ccd9d2
2024-08-24T12:47:23+02:00 [1:kimai1:systemd] kimai-app.service: Failed with result 'exit-code'.
2024-08-24T12:47:23+02:00 [1:kimai1:systemd] Failed to start Podman kimai-app.service.

2024-08-24T12:47:24+02:00 [1:kimai1:conmon] conmon f84bd62518f106e11cfe <nwarn>: Failed to open cgroups file: /sys/fs/cgroup/user.slice/user-1018.slice/user@1018.service/user.slice/user-libpod_pod_edd36c914e8ea71e58fb3e2e452ddb634d64d1479a69270b790a63cce5128918.slice/libpod-f84bd62518f106e11cfe51f121c7a3b8386e406d3fe99073cb11302c3d98fbf7.scope/container/memory.events

There’s an env var called KIMAI2_IMAGE. I haven’t checked the code so it is possibly right but the numbering grabbed my attention.

transocean · August 24, 2024, 10:44am

It looks like the container for the kimai app will not be set up at all. At least it doesn’t find a container when I run this:

runagent -m kimai1 podman exec kimai-app /opt/kimai/bin/console kimai:reload --env=prod

But anyway, I have uninstalled the software again and will continue to use my original program for time recording

mrmarkuz · August 24, 2024, 10:47am

I can’t reproduce, it’s still running on two servers including the plugin…

Did you have the same issue that the service wasn’t started?

For a quick view it should be enough to check the Nodes pages and maybe the details. Just to exclude that there’s not enough memory or high CPU…

Please check the service status and share it as @dnutan explained.
Please also check logs in the logs page for errors or just share/send the logs.

The following creates a file dump including the logs:

journalctl > dump

Get the file dump via SCP and share it or send it.

In any case: Big thanks for testing @transocean !

mrmarkuz · August 24, 2024, 10:50am

Does it work when you restart the service?

The env var should be OK as they named the image like that because of V2. I remember issues some time age using images starting with a number.

Could it be a permission/owner issue?

To compare:

root@strato:~# ls -lis /home/kimai1/.local/share/containers/storage/volumes/kimai-plugins/_data/
total 4
920361 4 drwxrwxr-x 7 558784 558784 4096 Mar  9  2023 DeductionTimeBundle

LayLow · August 24, 2024, 10:54am

Dito, saw that too in the logs

2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app]  [OK] Congratulations! Successfully updated Kimai to version 2.19.1
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app]
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app] + '[' '!' -z Nethesis,1234 ']'
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app] + '[' '!' -a admin@example.com ']'
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app] + /opt/kimai/bin/console kimai:user:create superadmin admin@example.com ROLE_SUPER_ADMIN Nethesis,1234
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app]
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app]  [ERROR] email: This e-mail address is already in use.
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app]
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app]  [ERROR] username: The username is already used.
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app]
2024-08-24T11:07:08+02:00 [1:kimai1:kimai-app] Kimai2 ready

And somehow, it looks like/seems/feels an installation process is started whilst Kimai is laready installed. Hence some other errors:

2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app] Kimai installation running ...
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app] ==============================
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app] Database `kimai` for connection named default already exists. Skipped.
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]  [OK] Already at the latest version ("DoctrineMigrations\Version20240326125247")
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]  Rebuilding your cache, please be patient ...
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]  // Clearing the cache for the prod environment with debug false
2024-08-24T11:06:39+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:52+02:00 [1:kimai1:agent@kimai1] task/module/kimai1/1cc22ccc-760f-44a0-a2af-fe3437f2258c: get-configuration/20read is starting
2024-08-24T11:06:52+02:00 [1:kimai1:agent@kimai1] task/module/kimai1/1cc22ccc-760f-44a0-a2af-fe3437f2258c: action "get-configuration" status is "completed" (0) at step validate-output.json
2024-08-24T11:06:53+02:00 [1:kimai1:kimai-app]  [OK] Cache for the "prod" environment (debug=false) was successfully cleared.
2024-08-24T11:06:53+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:53+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:53+02:00 [1:kimai1:kimai-app]  // Warming up the cache for the prod environment with debug false
2024-08-24T11:06:53+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:56+02:00 [1:kimai1:agent@kimai1] task/module/kimai1/21368562-b227-49b8-8a0d-4e093ae80317: get-configuration/20read is starting
2024-08-24T11:06:56+02:00 [1:kimai1:agent@kimai1] task/module/kimai1/95c0d696-2548-4e5e-a8e6-30c620ebaf18: get-status/20read is starting
2024-08-24T11:06:56+02:00 [1:kimai1:agent@kimai1] task/module/kimai1/21368562-b227-49b8-8a0d-4e093ae80317: action "get-configuration" status is "completed" (0) at step validate-output.json
2024-08-24T11:06:57+02:00 [1:kimai1:agent@kimai1] task/module/kimai1/95c0d696-2548-4e5e-a8e6-30c620ebaf18: action "get-status" status is "completed" (0) at step validate-output.json
2024-08-24T11:06:58+02:00 [1:kimai1:kimai-app]  [OK] Cache for the "prod" environment (debug=false) was successfully warmed.
2024-08-24T11:06:58+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:58+02:00 [1:kimai1:kimai-app]
2024-08-24T11:06:58+02:00 [1:kimai1:kimai-app]  [OK] Congratulations! Successfully installed Kimai version 2.19.1

LayLow · August 24, 2024, 10:55am

Nope, was just running fine, just tested a reboot due to curiosity