Posts made by dholtz-docbox

Just as an update, as I am not sure what the hitch here is.

In an attempt to quarantine the issue, these are the steps being used.

Pre-installation:

• Starting from a blank Ubuntu 14.04.5 Server LVM installation
• Skipping internal bootstrap

Post-installation:

• Login
• Create /opt/fog directory
• sudo apt-get install git
• sudo git clone https://github.com/FOGProject/fogproject.git /opt/fog/dist
• Copy .fogsettings from configuration server
• cd /opt/fog/dist/bin
• sudo ./installfog.sh -y

After installfog.sh successfully completes - as denoted by the * Setup Complete prompt during FOG installation - I then try to access the fog database, using mysql -u root -D fog. At this point, I am prompted the following, “ERROR 1049 (42000): Unknown database ‘fog’.”

I am unsure what is causing this, but it simply appears, to me, that commons/schema.php isn’t being applied. I have attempted a handful of things, as well as begun digging through the repository in an attempt to better understand this. Unfortunately, I have not figured out a manual way to install the database, nor a way to identify what may be occurring that would cause this.

Further, if there is another variable I can cut down on, please let me know. I am trying to replicate the issue with as few of our own variables mixed in as possible. At this stage, we have not bootstrapped the system, and have only installed the necessary package. I have also tried running sudo apt-get update && apt-get upgrade -y --force-yes before proceeding as well, to no success. This is also using the git HEAD, so there should be no concern about our git mirror of the FOG Project intervening either.

No matter what I do with the latest RC, I cannot get the ‘fog’ database to install - outside of manually running the create+insert script myself.

Is there a way to manually install the database (read, not relying on foginstall.sh) just to validate that everything works. I suppose that’s moot, as I shouldn’t be in control of creating the schema anyway and the installer should always handle it. Just in this current state, I am curious if everything would work if I could install the database. If the -y switch is working as designed, I guess I am curious where this region of logic is handled so that I may further diagnose what the issue might be. My hope in manually doing it was that it would validate whether there was another issue at hand. That said, if there were another issue at hand, you would think the installer would fail.

I feel a little lost with this one, given that RC15 worked without a hitch, and that everything is “installed” successfully with RC21. Yet, when I go to query the ‘fog’ database, am told it doesn’t exist. Thus, indicating to me that some action wasn’t triggered/routed correctly, or that something error’d out and was silently handled.

I will be back on this tomorrow morning - I have to go vote for now.

-Dustin

@Tom-Elliott 0.0.0.0 and 127.0.0.1 resolve the same, unless I am mistaken about something. That said, that was just for my sample wget and curl calls, which unfortunately return the same output when switched to 127.0.0.1.

@Tom-Elliott : that’s just for the localhost? I am running that from the machine where FOG is installed. This server is on an isolated network, so it’s easiest to do from the machine itself. Is this invalid? I only thought about trying this, knowing that, when I wget the management page, if the database isn’t installed, I am told that my “FOG database schema is not up to date” and everything else that comes with schemaupdaterpage.php. I suppose the other thing this page mentions is that my database connection appears invalid, and that I should check the credentials. Let me double check these, I assumed they would be fine as I haven’t changed anything other than updating our FOG git mirror.

-Dustin

PS> Output…

Installing LSB_Release as needed
 * Attempting to get release information.......................Done


   +------------------------------------------+
   |     ..#######:.    ..,#,..     .::##::.  |
   |.:######          .:;####:......;#;..     |
   |...##...        ...##;,;##::::.##...      |
   |   ,#          ...##.....##:::##     ..:: |
   |   ##    .::###,,##.   . ##.::#.:######::.|
   |...##:::###::....#. ..  .#...#. #...#:::. |
   |..:####:..    ..##......##::##  ..  #     |
   |    #  .      ...##:,;##;:::#: ... ##..   |
   |   .#  .       .:;####;::::.##:::;#:..    |
   |    #                     ..:;###..       |
   |                                          |
   +------------------------------------------+
   |      Free Computer Imaging Solution      |
   +------------------------------------------+
   |  Credits: http://fogproject.org/Credits  |
   |       http://fogproject.org/Credits      |
   |       Released under GPL Version 3       |
   +------------------------------------------+


   Version: 1.3.0-RC-21 Installer/Updater


 * Found FOG Settings from previous install at: /opt/fog/.fogsettings

 * Performing upgrade using these settings


  Starting Debian based Installation



   ######################################################################
   #     FOG now has everything it needs for this setup, but please     #
   #   understand that this script will overwrite any setting you may   #
   #   have setup for services like DHCP, apache, pxe, tftp, and NFS.   #
   ######################################################################
   # It is not recommended that you install this on a production system #
   #        as this script modifies many of your system settings.       #
   ######################################################################
   #             This script should be run by the root user.            #
   #      It will prepend the running with sudo if root is not set      #
   ######################################################################
   #           ** Notice ** FOG is difficult to setup securely          #
   #        SELinux and IPTables are usually asked to be disabled       #
   #           There have been strides in adding capabilities           #
   #          The recommendations would now be more appropriate         #
   #    to set SELinux to permissive and to disable firewall for now.   #
   #  You can find some methods to enable SELinux and maintain firewall #
   #   settings and ports. If you feel comfortable doing so please do   #
   ######################################################################
   #            Please see our wiki for more information at:            #
   ######################################################################
   #             https://wiki.fogproject.org/wiki/index.php             #
   ######################################################################

 * Here are the settings FOG will use:
 * Base Linux: Debian
 * Detected Linux Distribution: Ubuntu
 * Server IP Address: 10.1.0.11
 * Server Subnet Mask: 255.255.255.0
 * Interface: p3p1
 * Installation Type: Normal Server
 * Donate: 0
 * Internationalization: 0
 * Image Storage Location: /images
 * Using FOG DHCP: Yes
 * DHCP router Address: 



 * Installation Started

 * Installing required packages, if this fails
 | make sure you have an active internet connection.

 * Adding needed repository....................................OK
 * Preparing Package Manager...................................OK
 * Packages to be installed:

	 apache2 bc build-essential cpp curl g++ gawk gcc gzip htmldoc isc-dhcp-server lftp libapache2-mod-php5 libc6 libcurl3 m4 mysql-client mysql-server net-tools nfs-kernel-server openssh-server php5 php5-bcmath php5-cli php5-curl php5-fpm php5-gd php5-json php5-ldap php5-mcrypt php5-mysqlnd php-gettext sysv-rc-conf tar tftpd-hpa tftp-hpa vsftpd wget xinetd zlib1g 


 * Installing package: apache2.................................OK
 * Skipping package: bc........................................(Already Installed)
 * Skipping package: build-essential...........................(Already Installed)
 * Skipping package: cpp.......................................(Already Installed)
 * Skipping package: curl......................................(Already Installed)
 * Skipping package: g++.......................................(Already Installed)
 * Skipping package: gawk......................................(Already Installed)
 * Skipping package: gcc.......................................(Already Installed)
 * Skipping package: gzip......................................(Already Installed)
 * Installing package: htmldoc.................................OK
 * Skipping package: isc-dhcp-server...........................(Already Installed)
 * Installing package: lftp....................................OK
 * Installing package: libapache2-mod-php5.....................OK
 * Skipping package: libc6.....................................(Already Installed)
 * Skipping package: libcurl3..................................(Already Installed)
 * Installing package: m4......................................OK
 * Installing package: mysql-client............................OK
 * Installing package: mysql-server............................OK
 * Skipping package: net-tools.................................(Already Installed)
 * Installing package: nfs-kernel-server.......................OK
 * Skipping package: openssh-server............................(Already Installed)
 * Installing package: php5....................................OK
 * Skipping package: php5-bcmath...............................(Does not exist)
 * Skipping package: php5-cli..................................(Already Installed)
 * Installing package: php5-curl...............................OK
 * Installing package: php5-fpm................................OK
 * Installing package: php5-gd.................................OK
 * Skipping package: php5-json.................................(Already Installed)
 * Installing package: php5-ldap...............................OK
 * Installing package: php5-mcrypt.............................OK
 * Installing package: php5-mysqlnd............................OK
 * Installing package: php-gettext.............................OK
 * Installing package: sysv-rc-conf............................OK
 * Skipping package: tar.......................................(Already Installed)
 * Installing package: tftpd-hpa...............................OK
 * Installing package: tftp-hpa................................OK
 * Installing package: vsftpd..................................OK
 * Skipping package: wget......................................(Already Installed)
 * Installing package: xinetd..................................OK
 * Skipping package: zlib1g....................................(Already Installed)
 * Updating packages as needed.................................OK

 * Confirming package installation

 * Checking package: apache2...................................OK
 * Checking package: bc........................................OK
 * Checking package: build-essential...........................OK
 * Checking package: cpp.......................................OK
 * Checking package: curl......................................OK
 * Checking package: g++.......................................OK
 * Checking package: gawk......................................OK
 * Checking package: gcc.......................................OK
 * Checking package: gzip......................................OK
 * Checking package: htmldoc...................................OK
 * Checking package: isc-dhcp-server...........................OK
 * Checking package: lftp......................................OK
 * Checking package: libapache2-mod-php5.......................OK
 * Checking package: libc6.....................................OK
 * Checking package: libcurl3..................................OK
 * Checking package: m4........................................OK
 * Checking package: mysql-client..............................OK
 * Checking package: mysql-server..............................OK
 * Checking package: net-tools.................................OK
 * Checking package: nfs-kernel-server.........................OK
 * Checking package: openssh-server............................OK
 * Checking package: php5......................................OK
 * Checking package: php5-cli..................................OK
 * Checking package: php5-curl.................................OK
 * Checking package: php5-fpm..................................OK
 * Checking package: php5-gd...................................OK
 * Checking package: php5-json.................................OK
 * Checking package: php5-ldap.................................OK
 * Checking package: php5-mcrypt...............................OK
 * Checking package: php5-mysqlnd..............................OK
 * Checking package: php-gettext...............................OK
 * Checking package: sysv-rc-conf..............................OK
 * Checking package: tar.......................................OK
 * Checking package: tftpd-hpa.................................OK
 * Checking package: tftp-hpa..................................OK
 * Checking package: vsftpd....................................OK
 * Checking package: wget......................................OK
 * Checking package: xinetd....................................OK
 * Checking package: zlib1g....................................OK

 * Configuring services

 * Setting up fog user.........................................OK
 * Setting up fog password.....................................OK
 * Stopping FOGMulticastManager Service........................OK
 * Stopping FOGImageReplicator Service.........................OK
 * Stopping FOGSnapinReplicator Service........................OK
 * Stopping FOGScheduler Service...............................OK
 * Stopping FOGPingHosts Service...............................OK
 * Setting up and starting MySQL...............................OK
 * Backing up user reports.....................................Done
 * Stopping web service........................................OK
 * Setting up Apache and PHP files.............................OK
 * Testing and removing symbolic links if found................OK
 * Backing up old data.........................................OK
 * Copying new files to web folder.............................OK
 * Creating config file........................................OK
 * Getting checksum files for kernels and inits................OK
 * Downloading inits, kernels, and the fog client..............OK
 * Comparing checksums of kernels and inits....................Done
 * Enabling apache and fpm services on boot....................OK
 * Creating SSL CA.............................................OK
 * Creating SSL Private Key....................................OK
 * Creating SSL Certificate....................................OK
 * Creating auth pub key and cert..............................OK
 * Resetting SSL Permissions...................................OK
 * Setting up SSL FOG Server...................................OK
 * Restarting Apache2 for fog vhost............................OK
 * Changing permissions on apache log files....................OK
 * Backing up database.........................................OK
 * Updating Database...........................................OK
 * Setting up storage..........................................OK
 * Setting up and starting DHCP Server......................... !!! No router address found !!!
 !!! No dns address found !!!
OK
 * Setting up and starting TFTP and PXE Servers................OK
 * Setting up and starting VSFTP Server........................OK
 * Setting up FOG Snapins......................................OK
 * Setting up UDPCast..........................................OK
 * Configuring UDPCast.........................................OK
 * Building UDPCast............................................OK
 * Installing UDPCast..........................................OK
 * Installing FOG System Scripts...............................OK


 * Configuring FOG System Services


 * Setting FOGMulticastManager script executable...............OK
 * Enabling FOGMulticastManager Service........................OK
 * Setting FOGImageReplicator script executable................OK
 * Enabling FOGImageReplicator Service.........................OK
 * Setting FOGSnapinReplicator script executable...............OK
 * Enabling FOGSnapinReplicator Service........................OK
 * Setting FOGScheduler script executable......................OK
 * Enabling FOGScheduler Service...............................OK
 * Setting FOGPingHosts script executable......................OK
 * Enabling FOGPingHosts Service...............................OK
 * Setting up FOG Services.....................................OK
 * Starting FOGMulticastManager Service........................OK
 * Starting FOGImageReplicator Service.........................OK
 * Starting FOGSnapinReplicator Service........................OK
 * Starting FOGScheduler Service...............................OK
 * Starting FOGPingHosts Service...............................OK
 * Setting up exports file.....................................OK
 * Setting up and starting RPCBind.............................OK
 * Setting up and starting NFS Server..........................OK
 * Linking FOG Logs to Linux Logs..............................OK
 * Linking FOG Service config /etc.............................OK
 * Ensuring node username and passwords match..................Done

 * Setup complete

   You can now login to the FOG Management Portal using
   the information listed below.  The login information
   is only if this is the first install.

   This can be done by opening a web browser and going to:

   http://10.1.0.11/fog/management

   Default User Information
   Username: fog
   Password: password

After installation…

mysql -u root fog
ERROR 1049 (42000): Unknown database 'fog'

When I query MySQL for its databases, I only see…

information_schema
mysql
performance_schema

I am not sure what the difference in a storage server and storage node are, but when I selected the normal install type.

I had everything worked on RC15 fine, but for some reason, the sources.list file that gets distributed with it was having a lot of issues. As soon as I updated our mirror to the latest, RC21, the apt-get issues went away, but it appears that mysql doesn’t install its database now. Everything appears to have installed correctly; I just can’t get it to install the ‘fog’ database (as far as I can tell). It also appears that the system recognizes the same, as I get back the contents schemaupdaterpage.php when I run wget 0.0.0.0/fog/management.

I figured I would just curl this page and attempt to submit it, forcing the database installer/updater - just to validate that all that is missing is the database. However, I seem to be running in circles identifying both the PHP file and the parameters to submit to/with. Unless I am successfully submitting a command and nothing is occurring - which you indicate should not be the case. In which case, I circle back around to, why, given a fresh OS, does FOG successfully install w/o issues yet fail to install the ‘fog’ database.

Anything to manually kick this off though would be helpful too, just to aid in debugging scenarios such as this.

Currently, I am trying stuff like… curl -s -d "confirm=value&fogverified=value" htttp://0.0.0.0/fog/management/index.php I have also tried with other data fields and php pages, such as commons/schema.php.

-Dustin

Everything, from the log’s point of view, is a success. It backs-up and updates the database “fine”, according to the logs. It says that the setup complete and that I can log into /fog/management. The services are accounted for and Apache is hosting the website fine. However, if I try to do mysql -u root fog;, I received a database does not exist error message.

Further, if I ‘wget 0.0.0.0/fog/management’, I get content back indicating that the databases have not been installed yet. I was going to curl and submit the page to see if it would manually kick off the action, but that’s where I am currently.

edit> Further, when I get into MySQL, as root, if I query show databases; the ‘fog’ database is also not present.

Server

• FOG Version: 1.3.0-RC21
• OS: Ubuntu 14.04.5

Description

After updating from RC15 to RC21, I noticed that I can no longer automate the installation of the ‘fog’ MySQL database using the -y switch on installfog.sh. Is this now intended? If not, I was wondering if you guys had a workaround for automating the installation w/o a browser (said machine only has command-line access).

Thanks!

-Dustin

@george1421 : Hmm… There must be something on /dev/sda because quick registration handled it for /dev/sda instead of /dev/sdb. That said, when it boots, it boots with an empty cursor. It would state it in lsblk if it had a boot part, right? I feel we are close…

@george1421 : I feel I have tried this, but let me give it a go. I have tried so many permutations of these settings, it’s hard to say which combinations haven’t been checked, heh. Do you have the Host Primary Disk setup too?

@george1421 said in Host Startup; Booting into LVM Disk Fails:

@dholtz-docbox Well thats a bit unexpected.

sda is a unpartitioned ~1tb disk

sdb is a bit confusing since there are two small partitions and then a large partition (where the lvm probably is). The two small partitions is what I’m questioning. One I might understand since that is a boot partition since you are using lvm on sdb3.

sdc looks like maybe a 8GB flash drive?

Is this an accurate assessment?

Pretty spot-on

Let me take a snapshot of what the partitioner does to the disk…

Edit> Installer Album
Edit> This is how it looks after installing ubuntu, all I do is move the IBA option to the top for network boot priority

@george1421 said in Host Startup; Booting into LVM Disk Fails:

Second, when you installed ubuntu you are sure that you didn’t install the any type of boot loader onto that first drive?

When I install Ubuntu, I go through the guided installation of LVM, using the entire disk. From there I let it create and write the partitions. I only install Ubuntu on the second disk.

I haven’t done anything to the other disk yet - it’s still just a factory-default drive. I don’t have an option to format this disk when I go through the process, at least I don’t feel like I do. I am use to the desktop installer, I guess. That said, should I try to also format this drive?

@george1421 said in Host Startup; Booting into LVM Disk Fails:

Third, In the AMD bois for this, when you tell it to boot from the disk with the ubuntu on it. In bios is this listed as the second hard drive? So the bios is seeing it as disk 2 or is it seeing it as another number disk? (I’m not sure if number is base 0 or base 1 for this discussion).

I posted this earlier in the thread, let me dig it up. That said, I am pretty sure it’s…

1. NIC
2. ubuntu (not sure who this one is, but it’s the only one I can boot from)
3. ubuntu (not sure who these guys are)
4. sata drive (which should be /dev/sdb)

@george1421 said in Host Startup; Booting into LVM Disk Fails:

I still plan on testing a similar setup with a dell 780 and 2 hard drives to see if I can boot off the second drive.

Oh, that’s awesome! Thank you very much.

@george1421 : Let me get started on the first, and I will return with the rest.

Edit> Output from debug…

@Wayne-Workman : No dice - good suggest. It just takes me to the GRUB4DOS terminal.

I feel at an impasse, as I know I can leverage FOG as the solution I am looking for. However, I don’t think we have figured out how to structure our partitions so that it works well with remote imaging. If that is the case, I think it will take us a little longer to finalize everything, but I will start looking into how to install Ubuntu the way we need it - where the OS disk is /dev/sda, and the data disk is /dev/sdb. It feels kind of silly, but I feel like a lot of issues would be cleared up by figuring that out first. I just wish the Ubuntu installer let me map them to sda or sdb, it always assigns them automatically. I wish I had more control over it, I guess.

-Dustin

@george1421 said in Host Startup; Booting into LVM Disk Fails:

@george1421 OK I have a hackish way to test this idea.

But first, I went through each of the exit modes and all pick the first hard drive. Looking into the code all of the exit modes are hard coded to boot to the first hard disk.

Sooo… as a test please edit this file /var/www/html/fog/lib/fog/bootmenu.class.php search for some fragment of “sanboot --no-describe --drive 0x80” it should be listed only once in that file. Change the 0x80 to 0x81 then file and save the class file. Be sure that you have the host set to sanboot and then use the browser trick I chatted to you to confirm that the sanboot is now sending to the 0x81 disk. Once confirmed try to boot that target computer again. If it works then we have to find the next steps, but we can prove the process works.

Haha, yeah… I tried that earlier. The disk just boot looped with no prompt, indefinitely, until I force-killed-power to the machine.

Edit> That was my immediate hack idea too, just to see if it would work
PS> Everything checked out, regarding your hack for reviewing the settings passed - 0x81 was assigned when tested.

That makes sense. I guess my thought here, is, before trying to boot through network, after installing Ubuntu, I run a set of udev rules, this remapping which disk /dev/sda and /dev/sdb are associated with.

Also, I can’t switch the cables around, one drive is SATA where the other is… like an onboard PCI-e disk. I wanted to handle it when installing Linux, but it looks like they have their own set of udev rules which always maps the larger drive to /dev/sda instead /dev/sdb. Which is why I was thinking, maybe we’ll just have our own we run as necessary to correct this, prior to building our golden image.

At the end of the day, the primary disk should be /dev/sda anyway, so I want to figure out how to get the smaller drive mapped to /dev/sda instead of /dev/sdb if I can.

Anyway, my time has run up for today. I will try a few more things tomorrow morning, specifically regarding udev rules first, most likely.

Thanks again for everyone’s help.

-Dustin

I am looking to have someone open the enclosure so I can swap the cables - darn special screwdriver that I don’t have. Until then, I am looking at how to handle how /dev/sda is assigned, and it looks like it comes down to udev rules? That’s what I am looking at right now. I know a lot of this is hitting a bridge I was looking to prolong, but I have been looking to more intimately setup the partitions. I guess this is the start of understanding how some of this is handled.

@Tom-Elliott : Yeah, I wasn’t having any luck trying anything from the other thread. I have been tossing around the idea, why are these drives setup this way and what can we do to change it. In my head, is it as easy as just swapping the SATA cables? I am not sure why the drives are the way they are, but I would not mind changing it if I can. I just haven’t looked into it yet - it just sounds like a lot of issues would be resolved if the OS was on the first disk?

@Wayne-Workman : Agreed! I am actually trying things from that topic as we speak.

@Wayne-Workman : Nothing too interesting, just some shutdown/startup commands I made earlier today.

[Wed Oct 19 18:15:32.174284 2016] [core:notice] [pid 1564] AH00094: Command line: '/usr/sbin/apache2'
[Wed Oct 19 18:15:32.173684 2016] [mpm_prefork:notice] [pid 1564] AH00163: Apache/2.4.7 (Ubuntu) OpenSSL/1.0.1f configured -- resuming normal operations
[Wed Oct 19 18:15:13.109673 2016] [mpm_prefork:notice] [pid 4501] AH00169: caught SIGTERM, shutting down
[Wed Oct 19 18:12:39.854083 2016] [core:notice] [pid 4501] AH00094: Command line: '/usr/sbin/apache2'
[Wed Oct 19 18:12:39.853942 2016] [mpm_prefork:notice] [pid 4501] AH00163: Apache/2.4.7 (Ubuntu) OpenSSL/1.0.1f configured -- resuming normal operations
[Wed Oct 19 18:12:18.080349 2016] [mpm_prefork:notice] [pid 24123] AH00169: caught SIGTERM, shutting down

What George and I were discussing regarded the saboot switches, in particular –drive 0x80. His thought was, whatever needs to be done, should be handling the assignment of this to 0x81, if I am trying to boot to /dev/sdb, which is on the second drive. These drives though, they are listed according to what the BIOS has listed? Or is there anyway to change what drive is mapped to 0x80?

I also wanted to update you on this…

I believe some services needed to be restarted after upgrading to RC-14, or something needed to be restarted. But after looking at the DHCP issues and talking w/ George, I have queried it again, for EXIT mode, and now I get…

Edit> I removed the output. It was misleading, because I had the PXE menu enabled. George and I are talking, and when looking at the SANBOOT option, it tries to boot into 0x80 instead of 0x81, which would be the second drive - which is the drive I am looking to boot from.

My SANBOOT output is…

#!ipxe
set fog-ip 10.1.10.42
set fog-webroot fog
set boot-url http://${fog-ip}/${fog-webroot}
sanboot --no-describe --drive 0x80

The EXIT output is still the same, with the last line being exit.