Bug#914954: Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user.
Hi Axel, Great to reat that the issue has been solved. I just update it upstream with the "Architecture: all". As the documentation points [1], it takes more sense, you are right. Thanks, [1] - https://www.debian.org/doc/debian-policy/ch-controlfields.html#architecture
Bug#914954: Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user.
Hi Ricardo, Ricardo Fraile wrote: > I have the fix committed on the repo but before update it to Debian, > if possible, I would like that you test it before. Thanks! > git clone -b dev https://github.com/rfrail3/tuptime.git > > cd tuptime && dpkg-buildpackage -us -uc > > dpkg -i ../tuptime_3.4.1_*.deb 3.4.2 indeed fixes the issue for me. So it basically was a permissions issue hidden by suboptimal error messages… P.S.: Why is tuptime "Architecture: any"? I don't see any compiled binary in the binary package, just python scripts. So wouldn't "Architecture: all" make more sense? Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#914954: Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user.
Hi Axel, I have the fix committed on the repo but before update it to Debian, if possible, I would like that you test it before. I attached the .deb file to this mail. If you want to build it, these are the steps that you need to do: git clone -b dev https://github.com/rfrail3/tuptime.git cd tuptime && dpkg-buildpackage -us -uc dpkg -i ../tuptime_3.4.1_*.deb Please, let me know if you have any problem. Thanks, tuptime_3.4.1_amd64.deb.tar.gz Description: GNU Zip compressed data
Bug#914954: Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user.
Hi Ricardo, Ricardo Fraile wrote: > I tested an upgrade from 3.4.0 to 3.4.1 on a fresh install of Sid > and it doesn't report any issue. JFTR: uptimed is also installed. Not sure if that makes a difference as tuptime seems to be able to import uptimed's database. > What is the output of "ls -al /var/lib/tuptime"? total 12 drwxr-xr-x 2 root root 4096 Sep 25 02:00 . drwxr-xr-x 113 root root 4096 Nov 22 00:48 .. -rw-r--r-- 1 root root 2048 Sep 25 02:00 tuptime.db > Did you reboot the computer between the 3.4.0 installation and the > upgrade? Yes. tuptime 3.4.0 was uploaded to unstable on 2018-09-23 and I last rebooted on 2018-09-30. # zfgrep tuptime /var/log/dpkg.log.2.gz 2018-09-25 02:01:37 upgrade tuptime:amd64 3.3.3 3.4.0 2018-09-25 02:01:37 status half-configured tuptime:amd64 3.3.3 2018-09-25 02:01:37 status unpacked tuptime:amd64 3.3.3 2018-09-25 02:01:37 status half-installed tuptime:amd64 3.3.3 2018-09-25 02:01:37 status half-installed tuptime:amd64 3.3.3 2018-09-25 02:01:38 status unpacked tuptime:amd64 3.4.0 2018-09-25 02:01:38 status unpacked tuptime:amd64 3.4.0 2018-09-25 02:01:55 configure tuptime:amd64 3.4.0 2018-09-25 02:01:55 status unpacked tuptime:amd64 3.4.0 2018-09-25 02:01:55 status unpacked tuptime:amd64 3.4.0 2018-09-25 02:01:55 status unpacked tuptime:amd64 3.4.0 2018-09-25 02:01:55 status half-configured tuptime:amd64 3.4.0 2018-09-25 02:01:56 status installed tuptime:amd64 3.4.0 > Please, can you add here the output of 'su -s /bin/sh tuptime -c > "tuptime -x"'? # su -s /bin/sh tuptime -c "tuptime -x" ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user. HTH. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#914954: Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user.
Hi, I tested an upgrade from 3.4.0 to 3.4.1 on a fresh install of Sid and it doesn't report any issue. What is the output of "ls -al /var/lib/tuptime"? Did you reboot the computer between the 3.4.0 installation and the upgrade? Please, can you add here the output of 'su -s /bin/sh tuptime -c "tuptime -x"'? Thanks,
Bug#914954: Fails to upgrade from 3.4.0 to 3.4.1: ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user.
Package: tuptime Version: 3.4.1 Severity: serious Hi, tuptime failed to upgrade from 3.4.0 to 3.4.1 for me as follows: Setting up tuptime (3.4.1) ... Installing new version of config file /etc/init.d/tuptime ... ERROR:root:After system restart, the values must be saved into db. Please, execute tuptime with a privileged user. dpkg: error processing package tuptime (--configure): installed tuptime package post-installation script subprocess returned error exit status 255 As I'm reading the error message, it seems to think for some reason that root is not a privileged user… O.o -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), (500, 'buildd-unstable'), (110, 'experimental'), (1, 'experimental-debug'), (1, 'buildd-experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages tuptime depends on: ii adduser 3.118 ii init-system-helpers 1.56 ii lsb-base 10.2018112800 ii python3 3.7.1-2 tuptime recommends no packages. tuptime suggests no packages. -- no debconf information
