[Touch-packages] [Bug 1953719] Re: logrotate.service fails because it starts before winbind.service
Command: /usr/bin/smbcontrol winbindd reload-config return value 1 if there is no winbind process. I believe solution maybe to change in /etc/logrotate.d/winbind from postrotate if [ -x /usr/bin/smbcontrol ]; then /usr/bin/smbcontrol winbindd reload-config elif [ -f /run/samba/winbindd.pid ]; then kill -HUP `cat /run/samba/winbindd.pid` fi endscript to postrotate if [ -f /run/samba/winbindd.pid ]; then if [ -x /usr/bin/smbcontrol ]; then /usr/bin/smbcontrol winbindd reload-config else kill -HUP `cat /run/samba/winbindd.pid` fi fi endscript -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1953719 Title: logrotate.service fails because it starts before winbind.service Status in logrotate package in Ubuntu: Confirmed Bug description: I have started to play with Prometheus on my Ubuntu 20.04.3. You can configure Prometheus to alert you when a systemd service fails, and in this way I noticed a problem with the logrotate.service immediately after booting the system. I looked with Cockpit, and Cockpit was reporting logrotate.service as "Failed to start". This is the log for logrotate.service : 8<8<8< Dez 09 08:00:56 rdiez3 systemd[1]: Starting Rotate log files... Dez 09 08:00:58 rdiez3 logrotate[1760]: Can't find pid for destination 'winbindd' Dez 09 08:00:58 rdiez3 logrotate[1069]: error: error running non-shared postrotate script for /var/log/samba/log.winbindd of '/var/log/samba/log.winbindd ' Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Dez 09 08:00:58 rdiez3 systemd[1]: logrotate.service: Failed with result 'exit-code'. Dez 09 08:00:58 rdiez3 systemd[1]: Failed to start Rotate log files. 8<8<8< I then looked at winbind.service , which was fine: 8<8<8< Dez 09 08:01:01 rdiez3 systemd[1]: Starting Samba Winbind Daemon... Dez 09 08:01:01 rdiez3 systemd[1]: Started Samba Winbind Daemon. 8<8<8< But I noticed that winbind.service started after logrotate.service . I wonder whether this is a service dependency issue. I am using this PC only during normal working hours, and logrotate.timer is set to run at midnight, when the computer will never be turned on. The worry is that this problem could effectively cause the complete log rotation to stop working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1953719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763100] Re: FONT="x/y/z" is not applied due to setupcon script bug
I confirm the bug also on Ubuntu 20.04.1
Patch on post #3 resolve the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1763100
Title:
FONT="x/y/z" is not applied due to setupcon script bug
Status in console-setup package in Ubuntu:
Confirmed
Bug description:
apt-cache policy console-setup
console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
*** 1.178ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
On 18.04 I wanted to set the TTY font to use a Powerline font. Despite
being able to set the font manually it wasn't being set at boot-time.
/etc/default/console-setup contains:
FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz"
"setupcon -v -f" reported an error:
putfont: KDFONTOP: Invalid argument
due to passing the font filename twice:
executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline-
v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz.
The problem is in /bin/setupcon where the collecting variable
FONTFILES has the font added twice, once at the top of the for loop
FONTFILES="$FONTFILES `findfile $fontdir $f`"
and again at the bottom
FONTFILES="$FONTFILES $RES"
Removing the first assignment fixes it.
FONTFILES=''
echo "DEBUG: FONT=$FONT"
if [ "$FONT" ]; then
for f in $FONT; do
echo "DEBUG: for loop"
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi
FONTFILES=`echo $FONTFILES` # remove extra spaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1763100/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853714] [NEW] libpam-runtime misconfigurred module option in /etc/pam.d/sshd
Public bug reported: Ubuntu version: Ubuntu 18.04.3 LTS libpam-runtime: 1.1.8-3.6ubuntu2.18.04.1 In file /etc/pam.d/sshd there is part: # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. sessionoptional pam_motd.so motd=/run/motd.dynamic sessionoptional pam_motd.so noupdate but it should be: # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. sessionoptional pam_motd.so noupdate motd=/run/motd.dynamic Current version runs update of dynamic part of motd on every login by ssh, what is slowing it significantly and clearly is not what author had in mind. ** Affects: pam (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1853714 Title: libpam-runtime misconfigurred module option in /etc/pam.d/sshd Status in pam package in Ubuntu: New Bug description: Ubuntu version: Ubuntu 18.04.3 LTS libpam-runtime: 1.1.8-3.6ubuntu2.18.04.1 In file /etc/pam.d/sshd there is part: # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. sessionoptional pam_motd.so motd=/run/motd.dynamic sessionoptional pam_motd.so noupdate but it should be: # Print the message of the day upon successful login. # This includes a dynamically generated part from /run/motd.dynamic # and a static (admin-editable) part from /etc/motd. sessionoptional pam_motd.so noupdate motd=/run/motd.dynamic Current version runs update of dynamic part of motd on every login by ssh, what is slowing it significantly and clearly is not what author had in mind. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1853714/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763100] Re: FONT="x/y/z" is not applied due to setupcon script bug
This solution seems to work. Thanks! ;)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.launchpad.net/bugs/1763100
Title:
FONT="x/y/z" is not applied due to setupcon script bug
Status in console-setup package in Ubuntu:
Confirmed
Bug description:
apt-cache policy console-setup
console-setup:
Installed: 1.178ubuntu1
Candidate: 1.178ubuntu1
Version table:
*** 1.178ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages
100 /var/lib/dpkg/status
On 18.04 I wanted to set the TTY font to use a Powerline font. Despite
being able to set the font manually it wasn't being set at boot-time.
/etc/default/console-setup contains:
FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz"
"setupcon -v -f" reported an error:
putfont: KDFONTOP: Invalid argument
due to passing the font filename twice:
executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline-
v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz.
The problem is in /bin/setupcon where the collecting variable
FONTFILES has the font added twice, once at the top of the for loop
FONTFILES="$FONTFILES `findfile $fontdir $f`"
and again at the bottom
FONTFILES="$FONTFILES $RES"
Removing the first assignment fixes it.
FONTFILES=''
echo "DEBUG: FONT=$FONT"
if [ "$FONT" ]; then
for f in $FONT; do
echo "DEBUG: for loop"
FONTFILES="$FONTFILES `findfile $fontdir $f`"
RES=`findfile $fontdir $f`
if [ -z "$RES" ]; then
fdec="${f%.gz}"
RES=`findfile $fontdir $fdec`
fi
FONTFILES="$FONTFILES $RES"
done
fi
FONTFILES=`echo $FONTFILES` # remove extra spaces
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1763100/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
