Closed Tyrewt closed 5 years ago
Could you please show the output of apt-dater-host status
on the affected jessie host run as the same user you are using in apt-dater? The last line should be KERNELINFO:
showing the current kernel version.
KERNELINFO: 0 3.16.0-4-amd64
Note: Most likely doesn't make a difference, but that command required sudo. My UID in apt-dater used to access all systems has the password disabled (passwd --lock). So I control + C out of the sudo prompt and information you requested displayed.
Has this been identified as an issue?
Status update?
You must not get a sudo query If you run apt-dater-host status
as the same user as from apt-dater. Since I'm not able to reproduce this issue it might be just a missing sudoers configuration (take a look at /etc/sudoers.d/apt-dater-host
).
Keep in mind this works with Debian 7/Cent OS 6. My apt-dater user has the following in sudoers configuration on the remote server:
ursername ALL=NOPASSWD: /usr/bin/apt-get, /usr/bin/aptitude
Also, /etc/sudoers.d/apt-dater-host has never been modified.
Content of this file cannot be quote on GitHub without formatting issues so I removed it.
Same issue with Debian 9. Can you please clarify how to troubleshoot or if more information is required from me.
I've ran "apt-dater-host status" from the host as the user and can see the output (including kernel info). One thing to note is that command prompts for a password, the user is locked with "passwd --lock
Please advise. Thank you.
Could you please check if your sudoers does contain a requiretty
? This would prevent apt-dater-host status
to succeed if run non-interactive.
I checked the /etc/sudoers config on a Debian 7, 8 and 9 host. None of them mention "requiretty", but as indicated in the initial bug report Debian 7 hosts display the Kernel version within Apt-Dater and Debian 8/9 do not.
Note in this screenshot, Debian 7 sows Kernel version, Debian 9 (outlined in red) does not.
After reading the issue from the beginning I realized that I was maybe misdirected by the sudo stuff. Is it correct that you still running apt-dater on Wheezy? Any machines running Jessie+ won't show kernel informations since there was a major change in apt-dater(-host) 1.0.0. Although apt-dater should support older apt-dater-host versions, the other way around is not supported.
Apt-dater (0.9.0) is running on Debian 7. It's unfortunate this feature has been removed, was rather useful.
The feature is still available but the implementation has changed. More recent versions of apt-dater(-host) use needrestart the get the current and available kernel versions.
If I execute apt-dater-host status the Kernel version is displayed. However, I noticed only some hosts (Debian 9.11) in Apt-Dater are displaying the Kernel version. You mentioned needrestart , but what should I be checking for?
It also appears that hosts built from Debian 9 work but upgraded hosts do not. Would the issue have something to do with hosts that have been upgraded from Debian 8 to Debian 9?
Does this feature work with Debian 10 Buster?
- If I execute apt-dater-host status the Kernel version is displayed. However, I noticed only some hosts (Debian 9.11) in Apt-Dater are displaying the Kernel version. You mentioned needrestart , but what should I be checking for?
You need to install the package. Since it is listed as Recommends in apt-dater-host it might get installed automaticaly.
- It also appears that hosts built from Debian 9 work but upgraded hosts do not. Would the issue have something to do with hosts that have been upgraded from Debian 8 to Debian 9?
Could you check if needrestart might make the difference? As it is only recommended by apt-dater-host it might not get be installed while dist-upgrading.
- Does this feature work with Debian 10 Buster?
It should work as in stretch.
Please use independend issue(s) for new problems or bugs.
Running Apt-Dater 0.9.0-3+wheezy1 on Debian 7. Within the host listing, Debian 8 servers do not show current Kernel version and display as "Debian 8.5 jessie; Linux", where as Debian 7 shows current Kernel version "Debian 7.11 wheezy; 3.2.0-4-amd64".
Potential bug?