Can't Edit Exisiting Snapins or Create New ones


  • Testers

    On the latest revision 6096, as well as the one this morning (6094 I believe, I noticed the problem and updated before posting)
    When I try to edit a snapin or create a new one it goes to a blank white page in firefox.
    In chrome it gives a 500 error saying the system might be down for maintenance.


  • Testers

    @Arrowhead-IT Scratch that, it totally worked after a restart. So if you go breaking your permissions just run the script posted and restart and violia!


  • Testers

    @Arrowhead-IT Well it was worth a shot but it didn’t do the trick, maybe restarting would work, I’m backing up before I try that though.


  • Testers

    I found a script to restore permissions here
    http://serverfault.com/questions/221447/how-to-repair-restore-ubuntu-10-04-after-sudo-chmod-777

    #!/bin/bash
    # Restores file permissions for all files on a debian system for which .deb
    # packages exist. 
    #
    # Author: Larry Kagan <me at larrykagan dot com>
    # Since 2007-02-20
    
    ARCHIVE_DIR=/var/cache/apt/archives/
    PACKAGES=`ls $ARCHIVE_DIR`
    cd /
    
    function changePerms() {
        CHOWN="/bin/chown"
        CHMOD="/bin/chmod"
        PERMS=`echo $1 | sed -e 's/--x/1/g' -e 's/-w-/2/g' -e 's/-wx/3/g' -e 's/r--/4/g'  -e 's/r-x/5/g' -e 's/rw-/6/g' -e 's/rwx/7/g' -e 's/---/0/g'`
        PERMS=`echo ${PERMS:1}`
        OWN=`echo $2 | /usr/bin/tr '/' '.'`
        PATHNAME=$3
        PATHNAME=`echo ${PATHNAME:1}`
    
    #    echo -e "CHMOD: $CHMOD $PERMS $PATHNAME"    
    
    #    result=`$CHOWN $OWN $PATHNAME`
    #    if [ $? -ne 0 ]; then
    #   echo -e $result
    #        exit 123;
    #    fi
    
        echo -e "CHOWN: $CHMOD $PERMS $PATHNAME"
        result=`$CHMOD $PERMS $PATHNAME`
        if [ $? -ne 0 ]; then
        echo -e $result
        fi
    }
    
    for PACKAGE in $PACKAGES;
    do
        if [ -d $PACKAGE ]; then
        continue;
        fi
        echo -e "Getting information for $PACKAGE\n"
        FILES=`/usr/bin/dpkg -c "${ARCHIVE_DIR}${PACKAGE}"`
    
        for FILE in "$FILES";
        do
            #FILE_DETAILS=`echo "$FILE" | awk '{print $1"\t"$2"\t"$6}'`
        echo "$FILE" | awk '{print $1"\t"$2"\t"$6}' | while read line;
            do
                changePerms $line
            done
            #changePerms $FILE_DETAILS
        done
    done```
    
    It's running right now, hopefully that does the trick.

  • Moderator

    @Arrowhead-IT said:

    So this is a me accidentally running chmod -R 775 / instead of chmod -R 775 ./ and not cancelling it fast enough problem, not a fog problem at all.

    That would do it.


  • Testers

    @Wayne-Workman
    [Mon Jan 25 12:30:49.536526 2016] [:error] [pid 24884] [client 192.168.100.108:61538] PHP Fatal error: Uncaught exception ‘Exception’ with message 'FOGFTP: Failed to connect. Host: 192.168.100.100, Error: Undefined variable: whereA$

    I couldn’t copy the whole error message from the terminal with ease, it appears to be ftp related. So I tried to ftp in only for it to not work on port 22 and on port 21 I get this message
    OOPS: vsftpd: refusing to run with writable root inside chroot()

    So this is a me accidentally running chmod -R 775 / instead of chmod -R 775 ./ and not cancelling it fast enough problem, not a fog problem at all.


  • Moderator

    Apache error logs right after the white page is displayed.


Log in to reply
 

355
Online

39.3k
Users

11.0k
Topics

104.4k
Posts

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