[opensuse-factory] unexpected error message running perl-Bootloader (from new kernel installation?)
All on host gx62b, unexpected message referring to /etc/grub.conf occurred today in vtty and /var/log/zypp/history both on 42.1, and on a 42.2a installation that is an upgrade from 42.1, but did not occur on a TW upgrade from 2016051? to 20160728 (string /etc/grub.conf does not appear anywhere in TW's history dating back to 2012-10): # 42.1 # Perl-Bootloader: 2016-08-02 15:54:51 <3> pbl-7283.2 FileIO::ReadFileRaw.168: Error: Failed to open /etc/grub.conf: No such file or directory # 42.2 # Perl-Bootloader: 2016-08-02 21:10:09 <3> pbl-1994.2 FileIO::ReadFileRaw.168: Error: Failed to open /etc/grub.conf: No such file or directory /boot/grub/menu.lst was successfully updated. This is from 42.1: # rpm -qa | egrep 'grub|os-prober|ootloader' perl-Bootloader-0.844-1.1.x86_64 perl-Bootloader-YAML-0.844-1.1.x86_64 grub-0.97-207.2.x86_64 perl-Bootloader-0.844-1.1.x86_64 perl-Bootloader-YAML-0.844-1.1.x86_64 yast2-bootloader-3.1.162-7.1.x86_64 Same message occurs in 42.1 history as far back as 2015-11-12. Original 42.1 installation was 2015-10-26. Other than versions, equivalent bootloader packages are installed on gx62b's TW and 42.2 (no v2.x Grub rpms installed anywhere on gx62b's HD). String /etc/grub.conf does not appear in gx62b's 13.1 or 13.2 zypp/history either. Clearly /etc/grub.conf was missing from these two installations. The question is not why /etc/grub.conf was missing, or whether perl-Bootloader should complain on not finding it, but why perl-Bootloader should even care about /etc/grub.conf while its job seems to be updating /boot/grub/menu.lst for a new kernel installation. Am I being mislead by a post-installation script as to why /etc/grub.conf is sought by perl-Bootloader? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/
03.08.2016 07:15, Felix Miata пишет:
but why perl-Bootloader should even care about /etc/grub.conf while its job seems to be updating /boot/grub/menu.lst for a new kernel installation.
Because /etc/grub.conf was used by YaST to record bootloader installation script which was used by perl-Bootloader when reinstallation was requested. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov composed on 2016-08-03 07:24 (UTC+0300):
Felix Miata composed:
but why perl-Bootloader should even care about /etc/grub.conf while its job ^^^^^^^^^^^^^ seems to be updating /boot/grub/menu.lst for a new kernel installation. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Because /etc/grub.conf was used by YaST to record bootloader installation script which was used by perl-Bootloader when reinstallation was requested.
How is needing it during menu updating for a new kernel related to reinstalling (aka grub setup)? The only information obvious in /etc/grub.conf is the (disk,partition) location needed for the setup command. /etc/grub.conf is actually just a script. What am I missing? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Wed, Aug 3, 2016 at 8:02 AM, Felix Miata
Andrei Borzenkov composed on 2016-08-03 07:24 (UTC+0300):
Felix Miata composed:
but why perl-Bootloader should even care about /etc/grub.conf while its job
^^^^^^^^^^^^^
seems to be updating /boot/grub/menu.lst for a new kernel installation.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Because /etc/grub.conf was used by YaST to record bootloader installation script which was used by perl-Bootloader when reinstallation was requested.
How is needing it during menu updating for a new kernel related to reinstalling (aka grub setup)? The only information obvious in /etc/grub.conf is the (disk,partition) location needed for the setup command. /etc/grub.conf is actually just a script. What am I missing?
What problem exactly you have? Something does not work? Menu is not updated? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Andrei Borzenkov composed on 2016-08-03 02:24 (UTC-0400):
What problem exactly you have?
The problem is understanding why, unless due to a post script, with kernel.printk set to 3 4 1 3, an error message seems to have been triggered without a corresponding process message that might logically have triggered it. /etc/grub.conf is about setting up Grub on disk. What else could logically connect an inability to find /etc/grub.conf on disk with installation of a new kernel? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 2016-08-03 at 09:24 +0300, Andrei Borzenkov wrote:
What problem exactly you have? Something does not work? Menu is not updated? I guess that poster means this unexpected error message, although it seems to be harmless.
Apart from question above, I am also wondering why is this obscure, and likely harmless issue discussed on this mailing list instead of bugzilla? Cheers Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXoZNGAAoJEFskXWf93mhXbysP/j85P0ij1bDurX4ooRM00nKX nSd+skqAKMBT30Js52krkRzIBAedg6Lpnc7Vr5WdSh40Wdv1Z4apUpc6z1P7KE/N cNJzLuANFAzElfBTEHuvEAZ2pZY7CKEpIWSHypGtRJ3OGec6Aw4a4ZX1DI3wdeqw X4c7cMjwq9QuZicSP8ywlITqii4wygxE6i/N51kLY627Vz2W0GFGSBle2GyjFZQa OI/LxLnZB+XaluJOK5Oipd22cHLO6JoPMCis8DGHtRuVDsJhTBReoqu6L3NfVwNf NmSrtvH/OOlZsYQvU0JJs9IQlNZyIxtC0Tq5Acp3sYaL+/B5WMXNTpaDWdsnPCec Bj2DDUXEerfBb4Mv0nYJzhQwugY5PQz7LOfNx0VKgMABKlj7hal5XB7XoQu1jywK ytRiT0UTY9AftRkUY+bv6C5BYcK/4vHmAPzuqlTui3dQUx8FkFJwCEMWJ0gVqr9u lLDXNStqb7G/4lOy8ZOaJoFsnZYT25shMcEZbQe0E/pxtX3k2p1qFqHoV4g7MWhQ uM5cGDoM4lc9dJTGa5tN10UB1X6OBgLISOHTKyV5nhJ7doi3uZaOOd8eItwZGdNV TgZIg3SFIbIVumX2OsfLkKsnU+BY2/qJt1wRfc+kBtWrd8fD+gEbzp6BSLJDUyGb rtblbPqjWQiQ693HKKfe =js/q -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Martin Pluskal composed on 2016-08-03 08:46 (UTC+0200):
On Wed, 2016-08-03 at 09:24 +0300, Andrei Borzenkov wrote:
What problem exactly you have? Something does not work? Menu is not updated?
I guess that poster means this unexpected error message, although it seems to be harmless.
Apart from question above, I am also wondering why is this obscure, and likely harmless issue discussed on this mailing list instead of bugzilla?
I had a bug report ready to send, then thought about the possibility that the only bug might be in my ability to understand screen messages generated by zypper -v up, and messages appearing in /var/log/zypp/history. If the message was not in fact triggered by kernel installation, but instead by a post script, would there be any bug to report? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 2016-08-03 at 02:58 -0400, Felix Miata wrote:
Martin Pluskal composed on 2016-08-03 08:46 (UTC+0200):
On Wed, 2016-08-03 at 09:24 +0300, Andrei Borzenkov wrote:
What problem exactly you have? Something does not work? Menu is not updated?
I guess that poster means this unexpected error message, although it seems to be harmless.
Apart from question above, I am also wondering why is this obscure, and likely harmless issue discussed on this mailing list instead of bugzilla?
I had a bug report ready to send, then thought about the possibility that the only bug might be in my ability to understand screen messages generated by zypper -v up, and messages appearing in /var/log/zypp/history. If the message was not in fact triggered by kernel installation, but instead by a post script, would there be any bug to report? Well "error" is usually not a correct think to do so I assume that bugzilla would be correct place to discuss it.
Apart from that, I fail to see any usefulness in "pre bugreport checking on mailing list" - in bugzilla, issue will get only to those involved with affected components of system while here everybody has to at least title of your mail, thus you have succesfuly burned more time of people than bugzilla report would do, of people who are not interested in queer issues that you inflict upon yourself. Furthermore, as mention several times already, this mailing list is for discussion about development of Factory and Leap, not for asking "is this a bug or not?". If you want to help, report bugs in bugzilla and don't create unnecessary/useless noise here. If you want to ask for help there are forums for that. Cheers Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXoZnbAAoJEFskXWf93mhXpWIP/24ewr74bswNF/owidCSZgVa J1LRTHwkzQOlrMpPWsSFiGArje1RRNNdhbATN7kIGNc8QgqDTdpnl3QGJByWYvZG f6FI5vvi124KTbD3+ASxNgeoNjZ5DYByTa31XOv9by49e+viHPdvoeMJaFNGoo9a 1WZxK9lHNsIs09wTkqByKnHbFEqcX8TTSpydOkAuAU5XmCIBz9MVVn4viVzR/o9j U7g8y2Wwi/mzx2QOq7PYNLfnBMNe9zpYn58it4rdtoKgF8iuBapp6xDf7kx9x368 NbLSboZMN72W4xF2JEbjNt7Cl0JCQ9DKP8EQu8oWNEFJ3sv25w0OKVy0Uu0nUSe7 ROEi948cniC93dHor3o3bQZAC7yBjAQR/MHHI1HTrYMPTQpR8XMoOPLGf6eXVLwN 845/tOqLKRTXLlXUr8kCK+Kvc1OL8krrWoLC9hRt4XQZCttCtfugXkU+Ny3KVUUE azZBIyu79PLSTfqXOv1dA1sKMGd81lsxmgy211UYsD9v03Z8fUB4XHTks4YFxPKY Q0HMsr7lerE9huZcySBPemTaB6IQiB0mUEdVLBv8HkqbfaC76Ievz5lFfwEmgVUo AwSNRuwSWocCoGJWIKRFjWsL2Wr54QT/Tchb4IwXK87v6hYdNQ0yQZTa/3KXLAyU pJqcrusKODsfEg4QYyLt =R1zl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Tue, Aug 2, 2016 at 10:15 PM, Felix Miata
All on host gx62b, unexpected message referring to /etc/grub.conf occurred today in vtty and /var/log/zypp/history both on 42.1, and on a 42.2a installation that is an upgrade from 42.1, but did not occur on a TW upgrade from 2016051? to 20160728 (string /etc/grub.conf does not appear anywhere in TW's history dating back to 2012-10):
# 42.1 # Perl-Bootloader: 2016-08-02 15:54:51 <3> pbl-7283.2 FileIO::ReadFileRaw.168: Error: Failed to open /etc/grub.conf: No such file or directory
# 42.2 # Perl-Bootloader: 2016-08-02 21:10:09 <3> pbl-1994.2 FileIO::ReadFileRaw.168: Error: Failed to open /etc/grub.conf: No such file or directory
/boot/grub/menu.lst was successfully updated. This is from 42.1:
Something sounds antiquated, both grub.conf and menu.lst are GRUB legacy terms. GRUB 2 uses grub.cfg. Is the older GRUB being used? Intentionally? -- Chris Murphy -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Andrei Borzenkov -
Chris Murphy -
Felix Miata -
Martin Pluskal