@Tom-Elliott said in Upgrade from Trunk to 1.4.2 Failed:

@Avaryan ANd what’s the output of mysql -v?

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 575
Server version: 5.5.55-0ubuntu0.14.04.1 (Ubuntu)

Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Reading history-file /home/user/.mysql_history
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

If I sudo that or log in with root I get access denied message.

@Tom-Elliott said in Upgrade from Trunk to 1.4.2 Failed:

@Avaryan What’s output of php -v?

PHP 7.1.5-1+deb.sury.org~trusty+2 (cli) (built: May 22 2017 13:39:01) ( NTS )
Copyright (c) 1997-2017 The PHP Group
Zend Engine v3.1.0, Copyright (c) 1998-2017 Zend Technologies
    with Zend OPcache v7.1.5-1+deb.sury.org~trusty+2, Copyright (c) 1999-2017, by Zend Technologies

@Tom-Elliott said in Upgrade from Trunk to 1.4.2 Failed:

Can you provide output of lsb_release -a?

No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 14.04.5 LTS
Release:        14.04
Codename:       trusty

Note: The ‘Backing up datebase’ part while installing 1.3.0 seemed to have worked, while in 1.4.2 it did not.

So, on a whim, I decided to checkout revision 07fc221, the first FOG 1.3.0 that I saw. It installed. Thought behind this was that maybe there have been too many changes from the pre 1.3 trunk build to the current 1.4.2 build and that I could update incrementally.

However, on loading the webpage I get this:

Your database connection appears to be invalid. FOG is unable to communicate with the database. There are many reasons why this could be the case. Please check your credentials in /var/www/html/fog/lib/fog/config.class.php. Also confirm that the database is indeed running. If credentials are correct, and if the Database service is running, check to ensure your filesystem has enough space.

@Tom-Elliott said in Upgrade from Trunk to 1.4.2 Failed:

@Avaryan What’s the last few lines of the bin/error_logs/fog_1.4.2_error.log?

Enabling module ssl.
See /usr/share/doc/apache2/README.Debian.gz on how to configure SSL and create self-signed certificates.
To activate the new configuration, you need to run:
  service apache2 restart
Enabling site 001-fog.
To activate the new configuration, you need to run:
  service apache2 reload
 * Stopping Apache httpd web server apache2
 * 
 * Starting Apache httpd web server apache2
AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/001-fog.conf:1
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
 * 
stop: Unknown instance: 
php7.1-fpm start/running, process 22328
 * apache2 is running
php7.1-fpm start/running, process 22328
--2017-06-05 10:53:01--  http://10.10.1.41//fog//maintenance/backup_db.php
Connecting to 10.10.1.41:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: ?node=schema [following]
--2017-06-05 10:53:01--  http://10.10.1.41//fog//maintenance/backup_db.php?node=schema
Connecting to 10.10.1.41:80... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2017-06-05 10:53:01 ERROR 500: Internal Server Error.

I commented out the lines mentioned in previous post. I’ll get the error log if it fails.

Also:

Starting Debian based Installation


 *** Detected a potential need to reinstall apache and php files.
 *** This will remove the /etc/php* and /etc/apache2* directories
 ***  and remove/purge the apache and php files from this system.
 *** If you're okay with this please type Y, anything else will
 ***  continue the installation, but may mean you will need to
 ***  remove the files later and make proper changes as
 ***  necessary. (Y/N):
y
 * Removing apache and php files...............................Done
 * Stopping web services.......................................Failed
 * Removing the apache and php packages........................Done
 * Resetting our variables to specify php version 7.1..........Done

edit: Still failed.

@Tom-Elliott When running the installer, one of the first things it mentioned was removing apacahe. I said yes.

Server

• FOG Version: Trunk (Pre 1.3)
• OS: Ubuntu 14.04

Client

• Service Version:
• OS:

Description

Here’s what happens when I try to update our live server to 1.4.2 from last years Trunk build.

 * Creating SSL Certificate....................................OK
 * Creating auth pub key and cert..............................OK
 * Resetting SSL Permissions...................................OK
 * Setting up SSL FOG Server...................................OK
 * Starting and checking status of web services................OK
 * Changing permissions on apache log files....................OK
 * Backing up database.........................................Failed!

How do I got about getting this to work?

@peer2peer Both a capture and a hardware inventory will trigger reboots. You need to PXE boot so that the tasks can continue. Usually F12 will trigger PXE boot or boot options.

Also, why FOG 1.3.5 if it’s a brand new installation?

Which linux distro is most preferred by the developers?

@Tom-Elliott Ok, thanks. I think everything is working now.

@Tom-Elliott Yes.

Under iPXE Boot Menu I have the checkbox next to ‘Advanced Menu Login’ marked.
I have ‘Boot Key Sequence’ set to CTRL + A.

My ‘Advanced Configuration Options’ are:

menu
item --gap -- ---------------- iPXE Advanced Boot Menu ----------------
item dart7 Microsoft Diagnostics and Recovery Toolset (DaRT7)
item return Return to Previous Menu
choose --default return --timeout 15000 target && goto ${target}
:dart7
kernel http://10.10.1.41/DaRT7/wimboot
initrd http://10.10.1.41/DaRT7/boot/bcd BCD
initrd http://10.10.1.41/DaRT7/boot/boot.sdi boot.sdi
initrd http://10.10.1.41/DaRT7/sources/boot.wim boot.wim
boot
:return
chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
prompt
goto MENU
autoboot

Under ‘iPXE Menu Configuration’ menu.
I see fog.advanced and fog.advancedlogin.

Which should be used and what menu should they be shown on?

Alright, so I’ve got the menu working as I want it, but I can’t get the login part to work right. Not really sure why.

@rbasart Wimboot is for booting from a .wim (Windows Imaging Format). I doubt that Mobscene uses that.

Anyway, I just copied from the wimboot files into the root of the directory I placed my DaRT files into.

http://ipxe.org/wimboot

@Tom-Elliott Oooo… so that’s what that is for. I saw that, but had no idea what it was.

I think I’ll be able to figure out the rest based on the examples in the documentation.

How do I go about setting up the Advanced Menu? Test server is on 1.4.1, basically stock settings.

The documentation on this, that I’ve seen, appears to be outdated.

@Tom-Elliott Where is the advanced script located?

Now… how to make it prompt for a password before loading? I know there is something with the Advanced Menu, but that’s not something I’ve messed with (yet).

I got it to work.

Just needed to download and add the wimboot files.

I’d like to add a Microsoft Diagnostics and Recovery Toolset (DaRT) image to the FOG menu; probably under Advanced Menu so I can force a username and password input.

Is this possible? Never tried loading another .iso from FOG before.