Kimai time tracking software

transocean · August 24, 2024, 10:59am

I have now reinstalled Kimai. Without the plugin and so far without rebooting.

pike · August 24, 2024, 11:07am

Now i know that “speicher” is the german word for “RAM”.

transocean · August 24, 2024, 11:09am

After reboot, shutdown and restart, but further without the plugin, kimai is working.But the question is what happens when I install the plugin again.

mrmarkuz · August 24, 2024, 11:13am

I’m also going to install the plugin on another test server.
When you install the plugin again please share the commands you use.
In case the plugin doesn’t work again it should be also possible to just remove the plugin instead of the whole app.

dnutan · August 24, 2024, 11:20am

Sorry, I removed it and had to reinstall the plugin again.
It fails because control process exited with error code.

Or SELinux ? (EDIT: doesn’t seem to be that)
This is on Rocky.

transocean · August 24, 2024, 11:26am

I installed the plugin again.But no reboot so far. Here are the commands:

curl -L -O GitHub - Keleo/DeductionTimeBundle: Configure certain activities as deduction time, resulting in negative durations for timesheets. archive/refs/tags/2.0.1.tar.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:–:-- 0:00:05 --:–:-- 0
100 6618 0 6618 0 0 585 0 --:–:-- 0:00:11 --:–:-- 1397
[root@ ~]# tar -xvf 2.0.1.tar.gz
DeductionTimeBundle-2.0.1/
DeductionTimeBundle-2.0.1/.github/
DeductionTimeBundle-2.0.1/.github/workflows/
DeductionTimeBundle-2.0.1/.github/workflows/linting.yaml
DeductionTimeBundle-2.0.1/.gitignore
DeductionTimeBundle-2.0.1/.php-cs-fixer.dist.php
DeductionTimeBundle-2.0.1/CHANGELOG.md
DeductionTimeBundle-2.0.1/DeductionTimeBundle.php
DeductionTimeBundle-2.0.1/DependencyInjection/
DeductionTimeBundle-2.0.1/DependencyInjection/DeductionTimeExtension.php
DeductionTimeBundle-2.0.1/EventSubscriber/
DeductionTimeBundle-2.0.1/EventSubscriber/ActivityMetaDefinitionSubscriber.php
DeductionTimeBundle-2.0.1/LICENSE
DeductionTimeBundle-2.0.1/README.md
DeductionTimeBundle-2.0.1/Resources/
DeductionTimeBundle-2.0.1/Resources/config/
DeductionTimeBundle-2.0.1/Resources/config/services.yaml
DeductionTimeBundle-2.0.1/Resources/translations/
DeductionTimeBundle-2.0.1/Resources/translations/messages.de.xlf
DeductionTimeBundle-2.0.1/Resources/translations/messages.en.xlf
DeductionTimeBundle-2.0.1/Timesheet/
DeductionTimeBundle-2.0.1/Timesheet/Calculator/
DeductionTimeBundle-2.0.1/Timesheet/Calculator/DeductionTimeCalculator.php
DeductionTimeBundle-2.0.1/composer.json
DeductionTimeBundle-2.0.1/phpstan.neon
[root@ ~]# mv DeductionTimeBundle-2.0.1/ /home/kimai3/.local/share/ containers/storage/volumes/kimai-plugins/_data/DeductionTimeBundle
[root@ ~]# chown -R 558784:558784 /home/kimai3/.local/share/contain ers/storage/volumes/kimai-plugins/_data/DeductionTimeBundle/
[root@ ~]# runagent -m kimai3 podman exec kimai-app /opt/kimai/bin/ console kimai:reload --env=prod
PHP Warning: include(/opt/kimai/vendor/composer/…/…/var/plugins/DeductionTime Bundle/DeductionTimeBundle.php): Failed to open stream: Permission denied in /op t/kimai/vendor/composer/ClassLoader.php on line 576
PHP Warning: include(): Failed opening ‘/opt/kimai/vendor/composer/…/…/var/pl ugins/DeductionTimeBundle/DeductionTimeBundle.php’ for inclusion (include_path=’ .:/usr/local/lib/php’) in /opt/kimai/vendor/composer/ClassLoader.php on line 576
Validating config file syntax …

[OK] All 26 YAML files contain valid syntax.

[OK] All 555 XLIFF files contain valid syntax.

Rebuilding your cache, please be patient …

// Clearing the cache for the prod environment with debug false

11:20:52 WARNING [php] Warning: include(/opt/kimai/vendor/composer/…/…/var/p lugins/DeductionTimeBundle/DeductionTimeBundle.php): Failed to open stream: Perm ission denied [“exception” => ErrorException { …}] [“channel” => “php”]
11:20:52 WARNING [php] Warning: include(): Failed opening ‘/opt/kimai/vendor/c omposer/…/…/var/plugins/DeductionTimeBundle/DeductionTimeBundle.php’ for inclu sion (include_path=‘.:/usr/local/lib/php’) [“exception” => ErrorException { …}] [“channel” => “php”]
[2024-08-24T11:20:52.646773+00:00] deprecation.INFO: User Deprecated: Since kevi npapst/tabler-bundle 1.5.0: The child node “tabler_logout” at path “tabler.route s” is deprecated. {“exception”:“[object] (ErrorException(code: 0): User Deprecat ed: Since kevinpapst/tabler-bundle 1.5.0: The child node "tabler_logout" at pa th "tabler.routes" is deprecated. at /opt/kimai/vendor/symfony/config/Definiti on/ArrayNode.php:248)”} {“channel”:“deprecation”}
[2024-08-24T11:20:52.747507+00:00] deprecation.INFO: User Deprecated: Since kevi npapst/tabler-bundle 1.5.0: The child node “tabler_logout” at path “tabler.route s” is deprecated. {“exception”:“[object] (ErrorException(code: 0): User Deprecat ed: Since kevinpapst/tabler-bundle 1.5.0: The child node "tabler_logout" at pa th "tabler.routes" is deprecated. at /opt/kimai/vendor/symfony/config/Definiti on/ArrayNode.php:248)”} {“channel”:“deprecation”}
[2024-08-24T11:20:52.841776+00:00] deprecation.INFO: User Deprecated: Since kevi npapst/tabler-bundle 1.5.0: The child node “tabler_logout” at path “tabler.route s” is deprecated. {“exception”:“[object] (ErrorException(code: 0): User Deprecat ed: Since kevinpapst/tabler-bundle 1.5.0: The child node "tabler_logout" at pa th "tabler.routes" is deprecated. at /opt/kimai/vendor/symfony/config/Definiti on/ArrayNode.php:248)”} {“channel”:“deprecation”}
[OK] Cache for the “prod” environment (debug=false) was successfully cleared.

// Warming up the cache for the prod environment with debug false

[OK] Cache for the “prod” environment (debug=false) was successfully warmed.

[OK] Kimai config was reloaded

transocean · August 24, 2024, 11:34am

After installin of the plugin and a a reboot, kimai is down.

dnutan · August 24, 2024, 11:42am

Same problem with a different plugin after reboot.

mrmarkuz · August 24, 2024, 11:42am

Thanks for sharing all the information, I’m going to check and trying to reproduce the issue.

Do you use Rocky?

Please could you post the service status or if you did already please point me to the post:

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

Maybe it is, will try the plugins volume using :z instead of :Z

github.com

mrmarkuz/ns8-kimai/blob/main/imageroot/systemd/user/kimai-app.service#L25


      
          WorkingDirectory=%S/state
          Restart=always
          TimeoutStopSec=70
          ExecStartPre=/bin/rm -f %t/kimai-app.pid %t/kimai-app.ctr-id
          ExecStartPre=-runagent discover-smarthost
          ExecStart=/usr/bin/podman run --conmon-pidfile %t/kimai-app.pid \
              --cidfile %t/kimai-app.ctr-id --cgroups=no-conmon \
              --pod-id-file %t/kimai.pod-id --replace -d --name  kimai-app \
              --env-file=%S/state/environment \
              --volume kimai-app:/opt/kimai/var/data:Z \
              --volume kimai-plugins:/opt/kimai/var/plugins:Z \
              --env DATABASE_URL=mysql://kimai:kimai@127.0.0.1/kimai?charset=utf8mb4&serverVersion=8.3.0 \
              --env ADMINPASS=Nethesis,1234 \
              --env ADMINMAIL=admin@example.com \
              ${KIMAI2_IMAGE}
          ExecStop=/usr/bin/podman stop --ignore --cidfile %t/kimai-app.ctr-id -t 10
          ExecReload=/usr/bin/podman kill -s HUP kimai-app
          SyslogIdentifier=%u
          ExecStopPost=/usr/bin/podman rm --ignore -f --cidfile %t/kimai-app.ctr-id
          PIDFile=%t/kimai-app.pid
          Type=forking

See this issue:

github.com/containers/podman-compose

error preparing container for attach: lsetxattr elasticsearch.yml operation not supported

opened 11:23AM - 22 Jun 22 UTC

closed 04:49PM - 25 Jun 22 UTC

typekpb

bug

**Describe the bug** Running docker-elk from: https://github.com/deviantony/doc…ker-elk fails to start. **To Reproduce** Steps to reproduce the behavior: ``` git clone https://github.com/deviantony/docker-elk.git cd docker-elk podman-compose up ``` **Expected behavior** ELK stack starts. **Actual behavior** ELK stack startup fails with error **Output** ``` $ podman-compose version podman-compose version: 1.0.4 ['podman', '--version', ''] using podman version: 4.1.1 podman-composer version 1.0.4 podman --version podman version 4.1.1 exit code: 0 $ podman-compose up podman-compose version: 1.0.4 ['podman', '--version', ''] using podman version: 4.1.1 ** excluding: set() ['podman', 'inspect', '-t', 'image', '-f', '{{.Id}}', 'docker-elk_elasticsearch'] ['podman', 'inspect', '-t', 'image', '-f', '{{.Id}}', 'docker-elk_setup'] ['podman', 'inspect', '-t', 'image', '-f', '{{.Id}}', 'docker-elk_logstash'] ['podman', 'inspect', '-t', 'image', '-f', '{{.Id}}', 'docker-elk_kibana'] ['podman', 'ps', '--filter', 'label=io.podman.compose.project=docker-elk', '-a', '--format', '{{ index .Labels "io.podman.compose.config-hash"}}'] podman pod create --name=pod_docker-elk --infra=false --share= ecfbff01f7dd7486d5f50d30ff5bb05f91b7d5b6c1caaafee6b0e89ab3a9705c exit code: 0 podman volume inspect docker-elk_elasticsearch || podman volume create docker-elk_elasticsearch ['podman', 'volume', 'inspect', 'docker-elk_elasticsearch'] ['podman', 'network', 'exists', 'docker-elk_elk'] podman create --name=docker-elk_elasticsearch_1 --pod=pod_docker-elk --label io.podman.compose.config-hash=96ff242820bcac2c8eaf55dd5ea7ec8298b3f64f6d4f84b411c9ffe8f5aa0e45 --label io.podman.compose.project=docker-elk --label io.podman.compose.version=1.0.4 --label com.docker.compose.project=docker-elk --label com.docker.compose.project.working_dir=/Users/butkovic/all/projects/20220318_CV_index/unofficial/docker-elk --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=elasticsearch -e ES_JAVA_OPTS=-Xms512m -Xmx512m -e ELASTIC_PASSWORD=changeme -e discovery.type=single-node -v /Users/foo/docker-elk/elasticsearch/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml:z,ro -v docker-elk_elasticsearch:/usr/share/elasticsearch/data:z --net docker-elk_elk --network-alias elasticsearch -p 9200:9200 -p 9300:9300 docker-elk_elasticsearch 6c90495e396155f61690d6fad64786567a97176ee69596b1711c68b13f7b689f exit code: 0 podman volume inspect docker-elk_setup || podman volume create docker-elk_setup ['podman', 'volume', 'inspect', 'docker-elk_setup'] ['podman', 'network', 'exists', 'docker-elk_elk'] podman create --name=docker-elk_setup_1 --pod=pod_docker-elk --requires=docker-elk_elasticsearch_1 --label io.podman.compose.config-hash=96ff242820bcac2c8eaf55dd5ea7ec8298b3f64f6d4f84b411c9ffe8f5aa0e45 --label io.podman.compose.project=docker-elk --label io.podman.compose.version=1.0.4 --label com.docker.compose.project=docker-elk --label com.docker.compose.project.working_dir=/Users/butkovic/all/projects/20220318_CV_index/unofficial/docker-elk --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=setup -e ELASTIC_PASSWORD=changeme -e LOGSTASH_INTERNAL_PASSWORD=changeme -e KIBANA_SYSTEM_PASSWORD=changeme -v docker-elk_setup:/state:Z --net docker-elk_elk --network-alias setup --init docker-elk_setup 91b13f0e53f192d40cd06fbdf65e0accf16d8f3962a0529572331f34bf240155 exit code: 0 ['podman', 'network', 'exists', 'docker-elk_elk'] podman create --name=docker-elk_logstash_1 --pod=pod_docker-elk --requires=docker-elk_elasticsearch_1 --label io.podman.compose.config-hash=96ff242820bcac2c8eaf55dd5ea7ec8298b3f64f6d4f84b411c9ffe8f5aa0e45 --label io.podman.compose.project=docker-elk --label io.podman.compose.version=1.0.4 --label com.docker.compose.project=docker-elk --label com.docker.compose.project.working_dir=/Users/butkovic/all/projects/20220318_CV_index/unofficial/docker-elk --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=logstash -e LS_JAVA_OPTS=-Xms256m -Xmx256m -e LOGSTASH_INTERNAL_PASSWORD=changeme -v /Users/foo/docker-elk/logstash/config/logstash.yml:/usr/share/logstash/config/logstash.yml:Z,ro -v /Users/foo/docker-elk/logstash/pipeline:/usr/share/logstash/pipeline:Z,ro --net docker-elk_elk --network-alias logstash -p 5044:5044 -p 5000:5000/tcp -p 5000:5000/udp -p 9600:9600 docker-elk_logstash f15d5f8f8e8d10c4227a240b1fcf31b2d5dfc9ba4bc597200a06c6d5e4253f90 exit code: 0 ['podman', 'network', 'exists', 'docker-elk_elk'] podman create --name=docker-elk_kibana_1 --pod=pod_docker-elk --requires=docker-elk_elasticsearch_1 --label io.podman.compose.config-hash=96ff242820bcac2c8eaf55dd5ea7ec8298b3f64f6d4f84b411c9ffe8f5aa0e45 --label io.podman.compose.project=docker-elk --label io.podman.compose.version=1.0.4 --label com.docker.compose.project=docker-elk --label com.docker.compose.project.working_dir=/Users/butkovic/all/projects/20220318_CV_index/unofficial/docker-elk --label com.docker.compose.project.config_files=docker-compose.yml --label com.docker.compose.container-number=1 --label com.docker.compose.service=kibana -e KIBANA_SYSTEM_PASSWORD=changeme -v /Users/foo/docker-elk/kibana/config/kibana.yml:/usr/share/kibana/config/kibana.yml:Z,ro --net docker-elk_elk --network-alias kibana -p 5601:5601 docker-elk_kibana 0339266b82050414f837fced610c8b1469d4a77a8c20c8c1011e93f26df79710 exit code: 0 podman start -a docker-elk_elasticsearch_1 Error: unable to start container 6c90495e396155f61690d6fad64786567a97176ee69596b1711c68b13f7b689f: error preparing container 6c90495e396155f61690d6fad64786567a97176ee69596b1711c68b13f7b689f for attach: lsetxattr /Users/foo/docker-elk/elasticsearch/config/elasticsearch.yml: operation not supported exit code: 125 podman start -a docker-elk_setup_1 Error: unable to start container 91b13f0e53f192d40cd06fbdf65e0accf16d8f3962a0529572331f34bf240155: error preparing container 91b13f0e53f192d40cd06fbdf65e0accf16d8f3962a0529572331f34bf240155 for attach: error starting some containers: internal libpod error exit code: 125 podman start -a docker-elk_logstash_1 Error: unable to start container f15d5f8f8e8d10c4227a240b1fcf31b2d5dfc9ba4bc597200a06c6d5e4253f90: error preparing container f15d5f8f8e8d10c4227a240b1fcf31b2d5dfc9ba4bc597200a06c6d5e4253f90 for attach: error starting some containers: internal libpod error exit code: 125 podman start -a docker-elk_kibana_1 Error: unable to start container 0339266b82050414f837fced610c8b1469d4a77a8c20c8c1011e93f26df79710: error preparing container 0339266b82050414f837fced610c8b1469d4a77a8c20c8c1011e93f26df79710 for attach: error starting some containers: internal libpod error exit code: 125 ``` **Environment:** - OS: Mac - podman version: 4.1.1 - podman compose version: 1.0.4

transocean · August 24, 2024, 11:48am

I use rocky.

● kimai-app.service - Podman kimai-app.service
Loaded: loaded (/home/kimai3/.config/systemd/user/kimai-app.service; disab>
Active: activating (start) since Sat 2024-08-24 13:46:49 CEST; 1s ago
Process: 86511 ExecStartPre=/bin/rm -f /run/user/1009/kimai-app.pid /run/us>
Process: 86512 ExecStartPre=runagent discover-smarthost (code=exited, statu>
Cntrl PID: 86513 (podman)
Tasks: 27 (limit: 151382)
Memory: 94.5M
CPU: 1.478s
CGroup: /user.slice/user-1009.slice/user@1009.service/app.slice/kimai-app.>
├─86513 /usr/bin/podman run --conmon-pidfile /run/user/1009/kimai->
├─86522 buildah-copier
└─86523 buildah-copier

transocean · August 24, 2024, 12:13pm

And now it gets mysterious. After about 20, I see this in the settings:

I haven’t done anything to the server in the meantime.

runagent -m kimai3 systemctl --user status kimai-app -l
● kimai-app.service - Podman kimai-app.service
Loaded: loaded (/home/kimai3/.config/systemd/user/kimai-app.service; disab>
Active: active (running) since Sat 2024-08-24 13:56:15 CEST; 16min ago
Process: 131350 ExecStartPre=/bin/rm -f /run/user/1009/kimai-app.pid /run/u>
Process: 131352 ExecStartPre=runagent discover-smarthost (code=exited, stat>
Process: 131353 ExecStart=/usr/bin/podman run --conmon-pidfile /run/user/10>
Main PID: 131414 (conmon)
Tasks: 1 (limit: 151382)
Memory: 4.0M
CPU: 1.675s
CGroup: /user.slice/user-1009.slice/user@1009.service/app.slice/kimai-app.>
└─131414 /usr/bin/conmon --api-version 1 -c dee22b1c9f42bb183e50c

mrmarkuz · August 24, 2024, 12:17pm

Maybe you did upgrade via command line to the latest version of kimai?

I included the change in the volume so maybe you unintentionally already tested the fix and it works?

transocean · August 24, 2024, 12:19pm

Maybe, markus…

We will see it after the now following reboot.

mrmarkuz · August 24, 2024, 12:20pm

I thought you meant reboots but you meant minutes…

transocean · August 24, 2024, 12:21pm

Yes, minutes…

transocean · August 24, 2024, 12:24pm

Unfortunately, it was only a glimmer of hope.

mrmarkuz · August 24, 2024, 12:26pm

OK I’ll try to find the issue and report back asap. Thanks to everybody for testing and supporting!

transocean · August 24, 2024, 12:29pm

I don’t want to put you to any trouble. But the software is simply great.

transocean · August 24, 2024, 12:46pm

And again…

20 minutes after the last reboot, the kimai app is up and i can work with the software. Maybe it’s because of the heat here.

mrmarkuz · August 24, 2024, 12:53pm

I think I finally found the (owner) issue. In the documentation I wrote

chown -R 558784:558784 /home/kimai1/.local/share/containers/storage/volumes/kimai-plugins/_data/DeductionTimeBundle/

but the owner changes from one installation to another and it occurs on Rocky only.

I tested on Rocky first and it it didn’t occur on Debian so without your help and the community support I maybe never noticed the bug.

Please check owner:

ls -lisa /home/kimai1/.local/share/containers/storage/volumes/kimai-plugins/_data
total 16
2100396 4 drwxr-xr-x 3 952000 952000 4096 Aug 22 10:49 .
2100395 4 drwx------ 3 kimai1 kimai1 4096 Aug 22 10:47 ..
2103378 4 -rw-r--r-- 1 952000 952000   55 Jul 28 16:06 .gitkeep
 920361 4 drwxrwxr-x 7 558784 558784 4096 Mar  9  2023 DeductionTimeBundle

and change it accordingly, in this example I change it from the wrong value 558784 to the right value 952000:

chown -R 952000:952000 /home/kimai1/.local/share/containers/storage/volumes/kimai-plugins/_data/DeductionTimeBundle/

I needed to restart the service to make it work:

runagent -m kimai1 systemctl --user restart kimai

I also found this helpful error message when reloading the cache on a new Rocky VM test system that made me follow the permission issue direction:

 // Clearing the cache for the prod environment with debug false                

Failed to open stream: Permission denied ["exception" => ErrorException { …}] ["channel" => "php"]

Just to clarify, kimai is the enabled service, kimai-app is started as a requirement of kimai:

github.com

mrmarkuz/ns8-kimai/blob/main/imageroot/systemd/user/kimai.service#L13


      
          # SPDX-License-Identifier: GPL-3.0-or-later
          #
          
          #
          # This systemd unit starts a kimai instance using Podman.
          # Most parts of this file come from podman-generate-systemd.
          #
          
          [Unit]
          Description=Podman kimai.service
          Requires=mariadb-app.service kimai-app.service
          Before=mariadb-app.service kimai-app.service
          
          [Service]
          Environment=PODMAN_SYSTEMD_UNIT=%n
          EnvironmentFile=-%S/state/environment
          Restart=always
          TimeoutStopSec=70
          ExecStartPre=/bin/rm -f %t/kimai.pid %t/kimai.pod-id
          ExecStartPre=/usr/bin/podman pod create --infra-conmon-pidfile %t/kimai.pid \
              --pod-id-file %t/kimai.pod-id \

Glances is a nice tool too, used it on NS7.
AFAIK on NS8 we currently have Grafana, Netdata and Zabbix for monitoring and graphs etc.