• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

1.3.5 RC8 Boot Key Sequence

Scheduled Pinned Locked Moved Solved
Bug Reports
3
9
2.4k
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    sudburr
    last edited by Feb 17, 2017, 7:59 PM

    Server
    • FOG Version: 1.3.5 RC8
    • OS: CentOS 7.x
    Client
    • Service Version: n/a
    • OS: n/a
    Description

    In-place upgrading versions of 1.3.0 and later with 1.3.5 RC8, the iPXE Boot Menu option of ‘Boot Key Sequence’ is being reset from its intended setting to ’ - Please select an option - '.

    [ Standing in between extinction in the cold and explosive radiating growth ]

    W 1 Reply Last reply Feb 18, 2017, 5:01 AM Reply Quote 0
    • T
      Tom Elliott
      last edited by Feb 17, 2017, 9:32 PM

      I’m not seeing any issues with this.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

      Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

      Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

      1 Reply Last reply Reply Quote 0
      • W
        Wayne Workman
        last edited by Feb 18, 2017, 4:59 AM

        Cross-linking another thread about the same thing:
        https://forums.fogproject.org/topic/9550/1-3-5-rc-7-boot-key-sequence-reset

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
        Daily Clean Installation Results:
        https://fogtesting.fogproject.us/
        FOG Reporting:
        https://fog-external-reporting-results.fogproject.us/

        1 Reply Last reply Reply Quote 0
        • W
          Wayne Workman @sudburr
          last edited by Wayne Workman Feb 17, 2017, 11:01 PM Feb 18, 2017, 5:01 AM

          @sudburr Can you dig into the apache logs and try to find something related to this issue? I cannot replicate the problem.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
          Daily Clean Installation Results:
          https://fogtesting.fogproject.us/
          FOG Reporting:
          https://fog-external-reporting-results.fogproject.us/

          1 Reply Last reply Reply Quote 0
          • S
            sudburr
            last edited by Feb 21, 2017, 3:57 PM

            I had this happen on 19 servers (no storage nodes) of varying versions 1.3.0 + up to and including RC5.

            No relevant indicators or errors in /var/log/httpd/error_log or /opt/trunkgit/fogproject/bin/error_logs .

            [ Standing in between extinction in the cold and explosive radiating growth ]

            1 Reply Last reply Reply Quote 0
            • S
              sudburr
              last edited by sudburr Feb 21, 2017, 10:29 AM Feb 21, 2017, 4:29 PM

              Upgrading from RC8 to RC10 it happened again.

              Nothing to report from the apache log, but here are some snippets from fogproject/bin/error_logs/fog_error_1.3.5-RC-10.log .

              xinetd-2.3.15-13.el7.x86_64
              New password: Retype new password: Changing password for user fog.
              passwd: all authentication tokens updated successfully.
              Failed to execute operation: Invalid argument
              ● mariadb.service - MariaDB database server
                 Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled)
              
              Feb 21 11:05:46 xyzfog systemd[1]: Started MariaDB database server.
              ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
              ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)
              Signature ok
              subject=/CN=10.12.40.14
              Getting CA Private Key
              ln: failed to create symbolic link ‘/var/www/html/fog/fog’: File exists
              ● httpd.service - The Apache HTTP Server
                 Loaded: loaded (/usr/lib/systemd/system/httpd.service; enabled; vendor preset: disabled)
              
              Feb 21 11:07:36 xyzfog systemd[1]: Starting The Apache HTTP Server...
              Feb 21 11:07:36 xyzfog systemd[1]: Started The Apache HTTP Server.
              Saving to: ‘/home//fogDBbackups/fog_sql_1.3.5-RC-10_20170221_110738.sql’
                   0K                                                        0.00 =0s
              2017-02-21 11:07:39 (0.00 B/s) - ‘/home//fogDBbackups/fog_sql_1.3.5-RC-10_20170221_110738.sql’ saved [0/0]
              ‘./10secdelay/i386-efi/intel.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/intel.efi’
              cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/intel.efi’: No such file or directory
              ‘./10secdelay/i386-efi/ipxe.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/ipxe.efi’
              cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/ipxe.efi’: No such file or directory
              ‘./10secdelay/i386-efi/realtek.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/realtek.efi’
              cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/realtek.efi’: No such file or directory
              ‘./10secdelay/i386-efi/snp.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/snp.efi’
              cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/snp.efi’: No such file or directory
              ‘./10secdelay/i386-efi/snponly.efi’ -> ‘/tftpboot/./10secdelay/i386-efi/snponly.efi’
              cp: cannot create regular file ‘/tftpboot/./10secdelay/i386-efi/snponly.efi’: No such file or directory
              ‘./10secdelay/ldlinux.c32’ -> ‘/tftpboot/./10secdelay/ldlinux.c32’
              ‘./10secdelay/libcom32.c32’ -> ‘/tftpboot/./10secdelay/libcom32.c32’
              ‘./10secdelay/libutil.c32’ -> ‘/tftpboot/./10secdelay/libutil.c32’
              ‘./10secdelay/memdisk’ -> ‘/tftpboot/./10secdelay/memdisk’
              ‘./10secdelay/menu.c32’ -> ‘/tftpboot/./10secdelay/menu.c32’
              ‘./10secdelay/pxelinux.0’ -> ‘/tftpboot/./10secdelay/pxelinux.0’
              ‘./10secdelay/pxelinux.0.old’ -> ‘/tftpboot/./10secdelay/pxelinux.0.old’
              ‘./10secdelay/pxelinux.cfg/default’ -> ‘/tftpboot/./10secdelay/pxelinux.cfg/default’
              cp: cannot create regular file ‘/tftpboot/./10secdelay/pxelinux.cfg/default’: No such file or directory
              ‘./10secdelay/vesamenu.c32’ -> ‘/tftpboot/./10secdelay/vesamenu.c32’
              

              [ Standing in between extinction in the cold and explosive radiating growth ]

              1 Reply Last reply Reply Quote 0
              • S
                sudburr
                last edited by Feb 21, 2017, 6:52 PM

                Hmm, 2nd and 3rd time around upgrading RC8 to RC10 I cannot reproduce it.

                [ Standing in between extinction in the cold and explosive radiating growth ]

                1 Reply Last reply Reply Quote 0
                • W
                  Wayne Workman
                  last edited by Feb 22, 2017, 4:58 AM

                  That makes no sense at all. I don’t disbelieve you, I just don’t know what’s going on.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
                  Daily Clean Installation Results:
                  https://fogtesting.fogproject.us/
                  FOG Reporting:
                  https://fog-external-reporting-results.fogproject.us/

                  1 Reply Last reply Reply Quote 0
                  • T
                    Tom Elliott
                    last edited by Feb 24, 2017, 7:30 PM

                    This wasn’t a problem with key sequence or even double entries as originally thought (though that could still cause similar issues).

                    However it was found and is now fixed.

                    Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    1 / 1
                    • First post
                      7/9
                      Last post

                    157

                    Online

                    12.0k

                    Users

                    17.3k

                    Topics

                    155.2k

                    Posts
                    Copyright © 2012-2024 FOG Project