Package Details: tuptime 5.2.3-2

Git Clone URL: https://aur.archlinux.org/tuptime.git (read-only, click to copy)
Package Base: tuptime
Description: Historical and statistical system uptime reporting
Upstream URL: https://github.com/rfmoz/tuptime
Keywords: tuptime uptime
Licenses: GPL-2.0-only
Submitter: derintendant
Maintainer: allddd
Last Packager: allddd
Votes: 16
Popularity: 0.006765
First Submitted: 2015-09-06 15:54 (UTC)
Last Updated: 2024-06-15 21:41 (UTC)

Latest Comments

1 2 Next › Last »

bezerkk commented on 2022-04-20 08:26 (UTC) (edited on 2022-04-20 08:29 (UTC) by bezerkk)

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 ...

rfmoz commented on 2022-02-26 08:56 (UTC)

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

derintendant commented on 2022-02-10 19:33 (UTC)

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.

df8oe commented on 2022-01-03 07:43 (UTC)

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...

rfmoz commented on 2020-01-12 10:40 (UTC)

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

derintendant commented on 2020-01-11 20:18 (UTC)

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!

rfmoz commented on 2020-01-02 22:04 (UTC)

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...

quickwater commented on 2019-04-17 15:56 (UTC)

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

Thanks

rfmoz commented on 2019-03-25 22:04 (UTC)

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,

akrai commented on 2019-01-10 20:29 (UTC) (edited on 2019-01-10 20:30 (UTC) by akrai)

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