Database Schema Updater/Installer Not Being Displayed



  • Server
    • FOG Version: 1.3.0 (Revision 15)
    • OS: Ubuntu 14.04 & 16.04
    Client
    • Service Version:
    • OS:
    Description

    Hi all,

    I’m currently trying to upgrade my FOG installation to the latest trunk version, but every time I try it, my fog/management page looks like the below, with no means of updating the schema. Has anyone run into this issue before?
    I thought it might be a problem with Ubuntu 14.04, so I upgraded to 16.04 to no avail.

    0_1483105261722_Capture2.PNG

    Any help with this would be greatly appreciated.



  • @Tom-Elliott Updated correctly now - not sure why it wasn’t working the other day. Thanks for the help once again!


  • Moderator

    @RobTitian16 if you go to your fog repository location and run the below command it should output the hash your on. You can post that or compare it yourself to what is in git.
    git rev-parse HEAD


  • Senior Developer

    @RobTitian16 I’m unable to replicate the problem on 1.3.1-RC-3, are you sure you’re on the right branch and trying to install the correct “trunk” if you will?



  • @Tom-Elliott Yep, it’s the same as the screenshot above again.


  • Senior Developer

    @RobTitian16 I don’t understand.

    You’re at the Database Schema Installer page and there’s nothing being displayed?



  • @Tom-Elliott Same problem again, I’m afraid. I just tried upgrading to trunk and it’s not displaying the schema Installer/Updater button.



  • @Tom-Elliott Resolved - thanks a lot! :D


  • Senior Developer

    @RobTitian16 Repull and install. All should work now.



  • @Tom-Elliott

    var runInterval;
    $(function() {
        runDBCheck();
        $('form').submit(function(e) {
            clearInterval(runInterval);
        });
    });
    function runDBCheck() {
        $.ajax({
            url: '../status/dbrunning.php',
            dataType: 'json',
            success: function(data) {
                if (data.running === false) {
                    $('#dbNotRunning').show();
                    $('#dbRunning').hide();
                } else {
                    $('#dbNotRunning').hide();
                    $('#dbRunning').show();
                }
            },
            complete: function() {
                setTimeout(runDBCheck, 1000 - ((new Date().getTime() - startTime) % 1000));
        });
    }
    

    It says line 23 is wrong - seems like there are one too many brackets, or not enough.



  • @george1421 Here is the log result:

    [Fri Dec 30 06:44:08.080615 2016] [mpm_prefork:notice] [pid 1451] AH00163: Apache/2.4.23 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
    [Fri Dec 30 06:44:08.080647 2016] [core:notice] [pid 1451] AH00094: Command line: '/usr/sbin/apache2'
    [Fri Dec 30 13:03:05.052894 2016] [core:warn] [pid 1451] AH00045: child process 51905 still did not exit, sending a SIGTERM
    [Fri Dec 30 13:03:07.053599 2016] [core:warn] [pid 1451] AH00045: child process 51905 still did not exit, sending a SIGTERM
    [Fri Dec 30 13:03:09.054656 2016] [core:warn] [pid 1451] AH00045: child process 51905 still did not exit, sending a SIGTERM
    [Fri Dec 30 13:03:11.055334 2016] [core:error] [pid 1451] AH00046: child process 51905 still did not exit, sending a SIGKILL
    [Fri Dec 30 13:03:12.055927 2016] [mpm_prefork:notice] [pid 1451] AH00169: caught SIGTERM, shutting down
    [Fri Dec 30 13:03:38.963672 2016] [mpm_prefork:notice] [pid 62960] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
    [Fri Dec 30 13:03:38.963740 2016] [core:notice] [pid 62960] AH00094: Command line: '/usr/sbin/apache2'
    [Fri Dec 30 13:16:02.326855 2016] [mpm_prefork:notice] [pid 62960] AH00169: caught SIGTERM, shutting down
    [Fri Dec 30 13:16:03.860704 2016] [mpm_prefork:notice] [pid 8504] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
    [Fri Dec 30 13:16:03.860767 2016] [core:notice] [pid 8504] AH00094: Command line: '/usr/sbin/apache2'
    [Fri Dec 30 13:29:21.914129 2016] [mpm_prefork:notice] [pid 1093] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
    [Fri Dec 30 13:29:21.921437 2016] [core:notice] [pid 1093] AH00094: Command line: '/usr/sbin/apache2'
    [Fri Dec 30 13:55:26.301303 2016] [mpm_prefork:notice] [pid 1093] AH00169: caught SIGTERM, shutting down
    [Fri Dec 30 13:55:48.781576 2016] [mpm_prefork:notice] [pid 12171] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
    [Fri Dec 30 13:55:48.781634 2016] [core:notice] [pid 12171] AH00094: Command line: '/usr/sbin/apache2'
    [Fri Dec 30 13:56:47.437312 2016] [mpm_prefork:notice] [pid 12171] AH00169: caught SIGTERM, shutting down
    [Fri Dec 30 13:57:35.348797 2016] [mpm_prefork:notice] [pid 24506] AH00163: Apache/2.4.25 (Ubuntu) OpenSSL/1.0.2j configured -- resuming normal operations
    [Fri Dec 30 13:57:35.348861 2016] [core:notice] [pid 24506] AH00094: Command line: '/usr/sbin/apache2'
    

    @Tom-Elliott Here’s what I see under the console tab, which looks like the cause of the issue:

    0_1483106680249_Capture2.PNG


  • Senior Developer

    Because of how the messages are displayed, you might also want to “inspect” the page. Look under the “console” tab to hopefully show more info as well.


  • Moderator

    Can you check the apache error log for anything specific? I think for ubuntu its called error.log


Log in to reply
 

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.