Issue with Database Crashing and errors trying to upgrade to 1.3.5



  • Hi All

    Having issues saying the database is invalid on the web GUI. So i thought why not try and upgrade to 1.3.5 but i get errors please find the log file below.

    
    
    
       +------------------------------------------+
       |     ..#######:.    ..,#,..     .::##::.  |
       |.:######          .:;####:......;#;..     |
       |...##...        ...##;,;##::::.##...      |
       |   ,#          ...##.....##:::##     ..:: |
       |   ##    .::###,,##.   . ##.::#.:######::.|
       |...##:::###::....#. ..  .#...#. #...#:::. |
       |..:####:..    ..##......##::##  ..  #     |
       |    #  .      ...##:,;##;:::#: ... ##..   |
       |   .#  .       .:;####;::::.##:::;#:..    |
       |    #                     ..:;###..       |
       |                                          |
       +------------------------------------------+
       |      Free Computer Imaging Solution      |
       +------------------------------------------+
       |  Credits: http://fogproject.org/Credits  |
       |       http://fogproject.org/Credits      |
       |       Released under GPL Version 3       |
       +------------------------------------------+
    
    
       Version: 1.3.5 Installer/Updater
    
    
     * Found FOG Settings from previous install at: /opt/fog/.fogsettings
    
     * Performing upgrade using these settings
    
    
      Starting Debian based Installation
    
    
    ./installfog.sh: line 389: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    
       ######################################################################
       #     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: 192.168.1.49
     * Server Subnet Mask: 255.255.255.0
     * Interface: ens160
     * Installation Type: Normal Server
     * Donate: 0
     * Internationalization: 
     * Image Storage Location: /images
     * Using FOG DHCP: No
     * DHCP will NOT be setup but you must setup your
     | current DHCP server to use FOG for PXE services.
    
     * On a Linux DHCP server you must set: next-server and filename
    
     * On a Windows DHCP server you must set options 066 and 067
    
     * Option 066/next-server is the IP of the FOG Server: (e.g. 192.168.1.49)
     * Option 067/filename is the bootfile: (e.g. undionly.kpxe)
    
    
     * Are you sure you wish to continue (Y/N) 
     * Installation Started
    
     * Installing required packages, if this fails
     | make sure you have an active internet connection.
    
     * Adding needed repository....................................../lib/common/functions.sh: line 534: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 535: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 536: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 537: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 603: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 604: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 605: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 606: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 607: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 610: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 611: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 612: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 613: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    ../lib/common/functions.sh: line 614: $workingdir/error_logs/fog_error_${version}.log: ambiguous redirect
    Failed!
    

    Hope someone can help with our issue with database schema crashing and help with errors upgrading to 1.3.5

    Kind Regards

    Lawrence



  • @Tom-Elliott

    Hi Tom

    Running the installation again with sudo-i worked

    Thanks for your help

    Kind Regards

    Lawrence


  • Moderator

    @Tom-Elliott said in Issue with Database Crashing and errors trying to upgrade to 1.3.5:

    Mind trying to run the installer after running sudo -i

    Good catch Starting Debian based Installation from the OP post.

    Or sudo ./installfog.sh



  • @Tom-Elliott

    isops@MAFOG002:~$ df -h
    Filesystem                     Size  Used Avail Use% Mounted on
    udev                           979M     0  979M   0% /dev
    tmpfs                          200M   24M  177M  12% /run
    /dev/mapper/MAFOG002--vg-root  491G  335G  131G  72% /
    tmpfs                         1000M  276K 1000M   1% /dev/shm
    tmpfs                          5.0M     0  5.0M   0% /run/lock
    tmpfs                         1000M     0 1000M   0% /sys/fs/cgroup
    /dev/sda1                      472M  268M  180M  60% /boot
    tmpfs                          200M   72K  200M   1% /run/user/1000
    isops@MAFOG002:~$ 
    
    

  • Senior Developer

    Mind trying to run the installer after running sudo -i



  • This post is deleted!

  • Senior Developer

    @lawrence1997 said in Issue with Database Crashing and errors trying to upgrade to 1.3.5:
    Well, database crashing would most certainly happen if the volume is full.

    Please output df -h /home is typically laid out on a separate volume from /, mysql usually resides on /.



  • Hi Tom @Tom-Elliott

    Thank you for your quick reply the home drive has 140.5GB of free space so i don’t think this would be the issue for the Database crashing

    Kind Regards

    Lawrence


  • Senior Developer

    I’d recommend looking at your disk space. It can’t write to the error log file.

    df -h

    You probably will want to clean up the /home directory. We store backups of every update/upgrade/install if/when possible. Likely this is using most of the disk space? We also maintain backups of the database before it runs any upgrade on it so you will want to look at /home/fogDBbackups just to be sure.


Log in to reply
 

457
Online

38998
Users

10717
Topics

101747
Posts

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