Arch Linux User Repository

When trying to install (confirming "rfraile"):

:: Processing package changes...

(1/1) installing tuptime

[#########################################################] 100%

chown: invalid spec: ‘_tuptime:’ <============

tuptime has been installed and the required units ...

Hi derintendant,

Checking the behaviour after your last update, it miss the "_tuptime" user creation. Please, check this patch [1] that I've done getting [2] as reference.

Thanks,

[1] - https://pastebin.com/NbTXcNB5 [2] - https://github.com/archlinux/svntogit-community/tree/packages/haproxy/trunk

I have just pushed a new version, please test if everything works. This should finally fix the Unit file stuff without the need for the user to enable the units themselves. The Units now also run as a dedicated user so that we do not deviate more than needed from upstream.

As the dedicated user was recently renamed (from tuptime to _tuptime), the package also renames that user if the old one is found. Additionally it sets the owner of the /var/lib/tuptime directory to prevent permission errors.

@df8oe: Let me know, if this fixes your errors.

Since the update yesterday tuptime no longer works:
[root@webserver ~]# systemctl status tuptime-cron.service × tuptime-cron.service - Tuptime scheduled execution service Loaded: loaded (/usr/lib/systemd/system/tuptime-cron.service; static) Active: failed (Result: exit-code) since Mon 2022-01-03 08:30:01 CET; 4min 54s ago TriggeredBy: ● tuptime-cron.timer Docs: man:tuptime(1) file:///usr/share/doc/tuptime/tuptime-manual.txt.gz Main PID: 106124 (code=exited, status=217/USER) CPU: 1ms

Jan 03 08:30:01 webserver systemd[1]: Starting Tuptime scheduled execution service... Jan 03 08:30:01 webserver systemd[106124]: tuptime-cron.service: Failed to determine user credentials: No such process Jan 03 08:30:01 webserver systemd[106124]: tuptime-cron.service: Failed at step USER spawning /usr/bin/tuptime: No such process Jan 03 08:30:01 webserver systemd[1]: tuptime-cron.service: Main process exited, code=exited, status=217/USER Jan 03 08:30:01 webserver systemd[1]: tuptime-cron.service: Failed with result 'exit-code'. Jan 03 08:30:01 webserver systemd[1]: Failed to start Tuptime scheduled execution service.
Something is broken here...

Hi derintendant,

A new diff patch [1] is available to setup correctly the .timer unit and update the .install information. Please, it would be fine to have it applied.

Thanks,

[1] - https://pastebin.com/A2BDQhL0

I have just pushed the new release which also incorporates the fix from https://github.com/rfrail3/tuptime/issues/43.

Sorry for the delay there!

Hi @quickwater,

'BAD' shutdowns means that the systems doesn't power off gracefully executing the shutdown steps. It maybe had a power failure, a hang or similar...

Hello, I have been wondering, what does 'BAD' shutdown mean in the output.

Thanks

Hi @derintendant,

I received an issue [1] from an user and looking for the problem, I found that it's here. Please, consider this patch [2] that solves the integration with systemd.

[1] - https://github.com/rfrail3/tuptime/issues/43 [2] - https://pastebin.com/vasJZy3b

Thanks,

The post-install echoes doesn't work for me, nevertheless thanks for the fixes!

edit: of course it doesn't work for me, i'm doing an upgrade not a new install