[arch-general] pacman -Syu -- Applying kernel sysctl settings... Not setting ... Worry?
Arch devs, For the past several updates, I have noticed the kernel sysctl settings messages saying: ( 5/17) Applying kernel sysctl settings... Not setting net/ipv4/conf/all/rp_filter (explicit setting exists). Not setting net/ipv4/conf/default/rp_filter (explicit setting exists). Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists). Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists). Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). After the recent netctl message issue, I want to nail down what set these in /proc and whether it is something I need to do something about. I didn't set any of these specifically, so I presume they are either explicit settings made during the kernel build or they were set somewhere long ago by some previous Arch default. In either case, if there were no issues, I wouldn't expect pacman to go out of its way to tell me about them if nothing needs to be done. Though I can also see the messages just being some default behavior of whatever the kernel sysctl hook is warning about choices that are explicitly set. Do I need to do anything about these? -- David C. Rankin, J.D.,P.E.
Re: [arch-general] No login after update
On Fri, Aug 21, 2020 at 10:28:58PM +0200, Manuel Reimer wrote:
> On 21.08.20 22:23, Manuel Reimer wrote:
> > A diff between the actuall file and its ".pacnew":
> >
> >
> > $ diff -U 8 -p 00-dns.sh 00-dns.sh.pacnew
> > --- 00-dns.sh 2013-05-30 19:35:30.0 +0200
> > +++ 00-dns.sh.pacnew 2020-02-20 22:37:04.0 +0100
> > @@ -1,7 +1,11 @@
> > #!/bin/sh
> >
> > if [ "$USEPEERDNS" = "1" -a -f /etc/ppp/resolv.conf ]; then
> > - [ -e /etc/resolv.conf ] && mv /etc/resolv.conf
> > /etc/resolv.conf.backup.${IFNAME}
> > - mv /etc/ppp/resolv.conf /etc/resolv.conf
> > - chmod 644 /etc/resolv.conf
> > + if [ -x /usr/bin/resolvconf ]; then
> > + /usr/bin/resolvconf -a ${IFNAME} > + else
> > + [ -e /etc/resolv.conf ] && mv /etc/resolv.conf
> > /etc/resolv.conf.backup.${IFNAME}
> > + mv /etc/ppp/resolv.conf /etc/resolv.conf
> > + chmod 644 /etc/resolv.conf
> > + fi
> > fi
>
> And here the dates of the files:
>
>
> $ ls -lh
> total 8,0K
> -rwxr-xr-x 1 root root 229 30. Mai 2013 00-dns.sh
> -rwxr-xr-x 1 root root 344 20. Feb 2020 00-dns.sh.pacnew
>
>
> So when copying over from HDD to SSD I seem to have taken care of keeping
> the filestamps as I did not have my SSD in year 2013.
>
> If pacman had a bug in the past which did not properly move .pacnew into
> place (or maybe the "move into place feature" came some time later). Could a
> existing ".pacnew", created from older pacman versions, cause issues here?
>
> This is a pretty old Arch install. Never reinstalled. Always just updated.
> The oldest date I could find is August 2012.
>
> Manuel
This isn't a bug, it's however concerning that you haven't read the output of
pacman for 7 years and left .pacnew files unresolved.
https://github.com/archlinux/svntogit-packages/commit/c57cbb700c8b9e8ccfdc8c522e55ec1f80508462
As you can see, the files has been missing from the backup array thus pacman was
not aware of it. It does what it's suppose to do and preserves it's old file and
stores the new files as `.pacnew`.
This is documented in the manpage:
https://www.archlinux.org/pacman/pacman.8.html#_handling_config_files_a_id_hcf_a
--
Morten Linderud
PGP: 9C02FF419FECBE16
signature.asc
Description: PGP signature
Re: [arch-general] No login after update
On 21.08.20 22:23, Manuel Reimer wrote:
A diff between the actuall file and its ".pacnew":
$ diff -U 8 -p 00-dns.sh 00-dns.sh.pacnew
--- 00-dns.sh 2013-05-30 19:35:30.0 +0200
+++ 00-dns.sh.pacnew 2020-02-20 22:37:04.0 +0100
@@ -1,7 +1,11 @@
#!/bin/sh
if [ "$USEPEERDNS" = "1" -a -f /etc/ppp/resolv.conf ]; then
- [ -e /etc/resolv.conf ] && mv /etc/resolv.conf
/etc/resolv.conf.backup.${IFNAME}
- mv /etc/ppp/resolv.conf /etc/resolv.conf
- chmod 644 /etc/resolv.conf
+ if [ -x /usr/bin/resolvconf ]; then
+ /usr/bin/resolvconf -a ${IFNAME} + [ -e /etc/resolv.conf ] && mv /etc/resolv.conf
/etc/resolv.conf.backup.${IFNAME}
+ mv /etc/ppp/resolv.conf /etc/resolv.conf
+ chmod 644 /etc/resolv.conf
+ fi
fi
And here the dates of the files:
$ ls -lh
total 8,0K
-rwxr-xr-x 1 root root 229 30. Mai 2013 00-dns.sh
-rwxr-xr-x 1 root root 344 20. Feb 2020 00-dns.sh.pacnew
So when copying over from HDD to SSD I seem to have taken care of
keeping the filestamps as I did not have my SSD in year 2013.
If pacman had a bug in the past which did not properly move .pacnew into
place (or maybe the "move into place feature" came some time later).
Could a existing ".pacnew", created from older pacman versions, cause
issues here?
This is a pretty old Arch install. Never reinstalled. Always just
updated. The oldest date I could find is August 2012.
Manuel
Re: [arch-general] No login after update
On 21.08.20 22:09, Morten Linderud via arch-general wrote:
There are more ".pacnew" in my /etc. All for files that I never touched
myself.
That is concerning, but it is simply something touching those files you are
unaware of. It's however you system and it's expected that you are aware of what
does this.
I don't know what this could be. What exactly is compared? File
timestamps? Checksums? How to debug this?
For example I have a /etc/ppp/ip-up.d/00-dns.sh.pacnew
I for sure never edited this. I don't care about ppp at all. This
package came as dependency of something else (maybe NetworkManger).
A diff between the actuall file and its ".pacnew":
$ diff -U 8 -p 00-dns.sh 00-dns.sh.pacnew
--- 00-dns.sh 2013-05-30 19:35:30.0 +0200
+++ 00-dns.sh.pacnew2020-02-20 22:37:04.0 +0100
@@ -1,7 +1,11 @@
#!/bin/sh
if [ "$USEPEERDNS" = "1" -a -f /etc/ppp/resolv.conf ]; then
- [ -e /etc/resolv.conf ] && mv /etc/resolv.conf
/etc/resolv.conf.backup.${IFNAME}
- mv /etc/ppp/resolv.conf /etc/resolv.conf
- chmod 644 /etc/resolv.conf
+ if [ -x /usr/bin/resolvconf ]; then
+/usr/bin/resolvconf -a ${IFNAME} +[ -e /etc/resolv.conf ] && mv /etc/resolv.conf
/etc/resolv.conf.backup.${IFNAME}
+mv /etc/ppp/resolv.conf /etc/resolv.conf
+chmod 644 /etc/resolv.conf
+ fi
fi
I guess there is something wrong with the way how pacman decides when to move
".pacnew" into place directly.
There isn't. Peopel with `.pacnew` has modified their files, wittingly or not.
For sure not. I guess it somehow also depends on how they are compared.
At some point in the past I replaced my HDD with an SSD and as far as I
remember I copied over the system. Could this have caused the way how
pacman decides when to move ".pacnew" into place somehow?
I may also have deleted the whole /var/cache/pacman/pkg at some point in
the past to save space. Is this where pacman checks for "old files"?
Manuel
Re: [arch-general] No login after update
On Fri, Aug 21, 2020 at 10:01:50PM +0200, Manuel Reimer wrote: > There have to be edge cases where the replacement does not happen even if I > never touched a file myself. But I don't know how to debug this. No, you are mistaken. There are two issues, which is quite apparent if you do read the bugreports. 1) People modifying /etc/pam.d files and promptly forgetting it. Breaking their system as the new file is inserted as `/etc/pam.d/system-login.pacnew`. 2) Some change introduced into the new /etc/pam.d/system-login where auxillary files such as ~/.pam_environment can sometimes break your system. I have no clue how the latter works. > There are more ".pacnew" in my /etc. All for files that I never touched > myself. That is concerning, but it is simply something touching those files you are unaware of. It's however you system and it's expected that you are aware of what does this. > I guess there is something wrong with the way how pacman decides when to move > ".pacnew" into place directly. There isn't. Peopel with `.pacnew` has modified their files, wittingly or not. -- Morten Linderud PGP: 9C02FF419FECBE16 signature.asc Description: PGP signature
Re: [arch-general] No login after update
There have to be edge cases where the replacement does not happen even if I never touched a file myself. But I don't know how to debug this. There are more ".pacnew" in my /etc. All for files that I never touched myself. And about the "system-login"-thing: I'm not the only one who had this problem: https://www.reddit.com/r/archlinux/comments/id6tem/cant_login_as_user_or_root_after_upgrade/ https://www.reddit.com/r/archlinux/comments/ie3i8d/super_weird_login_problem/ https://www.reddit.com/r/archlinux/comments/idjpw3/issues_with_pam_tally2_after_full_system_upgrade/ https://www.reddit.com/r/archlinux/comments/iczyr0/psa_be_careful_with_pacnew_when_updating/ https://www.reddit.com/r/archlinux/comments/id3dsu/unable_to_login_after_upgrade/ https://www.reddit.com/r/archlinux/comments/id6ce4/not_able_to_login_after_updating_pam_to_1403/ https://www.reddit.com/r/archlinux/comments/icnzrx/after_latest_update_my_computer_cant_login/ https://www.reddit.com/r/archlinux/comments/icr4sv/incorrect_login_with_correct_password_even_reset/ And maybe more. I guess there is something wrong with the way how pacman decides when to move ".pacnew" into place directly. And I'm wondering how many users actually got lost with this issue of not being able to log in after updating and just wiped Arch off their hard drive... :( IMHO something should be done to at least find out why pacman does not replace *non user modified* files in some cases... Manuel On 19.08.20 21:07, Josef Miegl wrote: This can only happen if you or another program modified the original file. Josef Miegl On August 19, 2020 9:02:12 PM GMT+02:00, Manuel Reimer wrote: Hello, I know that Arch is not for the "average user" and some background knowledge is expected, but this was the first time I needed a boot stick since I think at least one year. Some minutes ago I did a regular system update and after that decided to reboot. After reboot I was unable to log into my system. After fiddling a bit I rebooted to an Arch boot stick to find the following message in pacman.log: [2020-08-19T20:42:55+0200] [ALPM] warning: /etc/pam.d/system-login installed as /etc/pam.d/system-login.pacnew As this seemed to be a candidate that may cause login problems, I deleted "system-login" and moved the ".pacnew" into place. After reboot I'm now able to log in again... IMHO something like this should not happen... Maybe it's worth a note on the Arch homepage that it is important to move this pacnew into place before reboot? Manuel
Re: [arch-general] HP Laserjet plus 1020 Problem
On 8/21/20 9:33 AM, das via arch-general wrote: On Wed, Aug 19, 2020 at 9:25 PM Giancarlo Razzolini wrote: I believe your printer works without hplip and using the driverless option. That's something you can also try. 'lsusb' is showing this device: <> 'hp-firmware -n' is giving: <> 'hp-config_usb_printer -l warn 001:005' is giving: <> But, 'hp-check' is finding it. The relevant portion is: << HP-LaserJet-1020 Type: Unknown Device URI: usb://Unknown/Printer PPD: /etc/cups/ppd/HP-LaserJet-1020.ppd warning: Failed to read /etc/cups/ppd/HP-LaserJet-1020.ppd ppd file PPD Description: Printer Unable to send data to printer.0 disabled since Fri 21 Aug 2020 12:27:00 PM IST - warning: Printer is not HPLIP installed. Printers must use the hp: or hpfax: CUPS backend for HP-Devices. 'system-config-printer' is finding it out. But it is not printing the test-page. Can anyone please suggest anything? I never use 'system-config-printer' because it lacks of settings. I prefer cups interface in a browser: http://localhost:631/help/admin.html -- Maderios
Re: [arch-general] HP Laserjet plus 1020 Problem
On Wed, Aug 19, 2020 at 9:25 PM Giancarlo Razzolini wrote: > > I believe your printer works without hplip and using the driverless > option. That's something you can also try. > 'lsusb' is showing this device: <> 'hp-firmware -n' is giving: <> 'hp-config_usb_printer -l warn 001:005' is giving: <> But, 'hp-check' is finding it. The relevant portion is: << HP-LaserJet-1020 Type: Unknown Device URI: usb://Unknown/Printer PPD: /etc/cups/ppd/HP-LaserJet-1020.ppd warning: Failed to read /etc/cups/ppd/HP-LaserJet-1020.ppd ppd file PPD Description: Printer Unable to send data to printer.0 disabled since Fri 21 Aug 2020 12:27:00 PM IST - warning: Printer is not HPLIP installed. Printers must use the hp: or hpfax: CUPS backend for HP-Devices. >> 'system-config-printer' is finding it out. But it is not printing the test-page. Can anyone please suggest anything?
