@sebastian-roth Fixed.

r4196 I still have the same issue, error is still the same.

Although the recent update pretty much stopped all errors in Apache that I was seeing. Yay. lol

This is good stuff.

It never hurts to have extra backups.
But fog does backup the web directory now, along with the database too. automatically. And the installer also updates only the packages that need updated. This is probably more stable than updating everything, because you have less things in motion at one time. Inside of the /opt/fog/.fogsnapins file, there is a backup setting now, which defines the backup path. The default is the home directory.
But again I’ll say that it never hurts to have extra backups.

@Tom-Elliott Thank you!

With the help of this site http://ipxe.org/howto/winpe I will eliminate “copying the iso to ram” that we have tragically been dealing with for so long.

We will be able to boot a 200mb windows PE environment and auto-launch win7 installation from a network location on the fog server via Samba.

Give me time - but expect a WiKi article on this in the near future

Bumping this.

@sudburr said:

Why does 3.18.5 work with either both connected or just the Legacy connected? … while 4.1.4 requires that both be connected?

Who cares, it works??? lol. Stop making our brains hurt and just enjoy the victory

@Arrowhead-IT https://forums.fogproject.org/topic/6330/remove-legacy-client-and-replace-with-latest-new-client

@hlcstudy Did you disable SELinux and the firewall on Fedora 21?

Check the status of SELinux and firewall with these:

sestatus
systemctl status firewalld

If both of those are off, I’d recommend trying what @EAHarvey suggested next.

@tom-elliott That would be perfect, just to inform the user that something might be wrong.

@Tom-Elliott Last night I tried re-running the installer several times.

I also rebooted all my network equipment and tried again too.

For what it’s worth, the internet on all my devices last night was really slow, probably has something to do with it.

Bumping this thread… I’m planning on working on this tomorrow night.

@jeffzimmm said:

Hi Wayne, Thanks for all of your generous attention.

I have tried every possible boot configuration.

With kpxe: The farthest I get is with Legacy BIOS, Secureboot Off. It takes me to “Initializing Devices,” then beeps and reboots.

With kkpxe: The farthese I get is with Legacy BIOS, Secureboot Off. It gets me as far as “Configuring (MAC address) …” Then times out and reboots.

It looks just like the screencap in @hlcstudy 's post https://forums.fogproject.org/topic/5721/ipxe-intialising-devices-ok-then-reboots. The difference is that kkpxe is already in use and I get the same symptom.

I note that you recommended in that thread to turn off firewalls. I thought I did that but will recheck.

Just to make it clear, Secure Boot is currently required to be OFF to network boot with FOG. Can you provide us with a screen shot of the error ? You might need to take a video to capture the error, often times the errors are only displayed for fractions of a second. What happens if you try to boot using ipxe.efi ??

Also - see my old post below on the subject of using a USB dongle.

@Wayne-Workman said in Surface 3 and Fog 1.2:

You have to specify that the NIC is a USB adapter with a kernel parameter on the host’s general page. YOu must set the ‘has_usb_nic=1’ kernel parameter.

So, it should look like this:

But, I believe that Surface 3s are UEFI, so you will need to use an .efi boot file. All the boot files available are in the /tftpboot directory, I suggest trying ipxe.efi first.

Past these things, you will need to upgrade to trunk, I believe, for better Windows Tablet support. There’s been a lot of work done in this area in FOG Trunk. You will still need to use the .efi files and the kernel arguments with fog trunk, but you might have better odds with getting it working and getting all the partitions to recognize correctly. Here’s info on FOG Trunk: https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk

Please report your findings - this is how you give back to the fog project - by reporting back with details.

@jflippen I’ve asked for this before too. FOG currently only supports 1 domain per ‘fog system’. My best advice to you is to get rid of the excessive domains and have just one ‘academic’ domain. This would simplify much more than just fog.

@Jbob Figured it out.

The newest SELinux userspace project release 2015-02-02 includes a change of the location of the SELinux policy store, which defaults to /var/lib/selinux/.

https://fedoraproject.org/wiki/Changes/SELinuxPolicyStoreMigration

find /var/lib/selinux | grep fog

/var/lib/selinux/targeted/active/modules/400/fog
/var/lib/selinux/targeted/active/modules/400/fog/lang_ext
/var/lib/selinux/targeted/active/modules/400/fog/hll
/var/lib/selinux/targeted/active/modules/400/fog/cil

I made this script to monitor the httpd processes. Problem was, I can’t easily figure out where the issue is when I’m going through thousands of lines of text that all looks the same to me. I needed a way to make it more visual than just text. I modified my script to include color to represent severity of the problem. It highlights the text based on the number of httpd processes returned.

So… if it returned 100 processes, the text would be highlighted bright red.

Updated script:

#Get the date.
dt="$(date  +"%I:%M %p %m-%d-%Y")"

#Get number of running httpd instances.
x=$( /usr/bin/ps -ef | /usr/bin/grep httpd | /usr/bin/wc -l )
color=$x


# Seriousness multiplier
let color*=5

#Don't let it go over the maximum.
if [[ $color -gt 255 ]]; then
        color=255
fi

# Convert to hex.
hexR=$(printf '%x\n' $color)

#Print the ine to the file.
echo '<p style="color: #66ccff; background-color: #'$hexR'0000">'$x' httpd instances running. '$dt'</p>' | cat - /var/www/html/httpd.html > /var/www/html/temp && mv /var/www/html/temp /var/www/html/httpd.html
chown apache:apache /var/www/html/httpd.html

Here’s my crontab -e entry for it, this makes it run every minute.

* * * * * /root/monitor.sh

Initial html file create code for Fedora/CentOS:

rm -f /var/www/html/httpd.html;touch /var/www/html/httpd.html;chown apache:apache /var/www/html/httpd.html

Sample output is below. I artificially manipulated the last return value in the script just to demonstrate color difference

Right after you hit the blank page - can you then go to the logs area and copy any errors in there to here?
FOG Config -> Log Viewer -> Apache errors.

@jflippen if you want FOG to do the domain joining, you’re going to need a ‘fog system’ per domain currently. You can probably do something special with unattend files or even snapins so you could use fog to image and then do this special stuff to join different domains - but all that is on you, fog can help but won’t do it for you.

Correction - image data was not deleted.

Upon closer inspection, I have incorrect permissions on the image I tried to delete.

That likely goofed it up, it had drwxr-xr-x owner and group was root:root instead of fog:root

So I think this was probably my fault.

@Arrowhead-IT said:

Since the actions you make in the gui are essentially doing things in the database, I suppose that it would be possible to manually edit the database with a script to queue the actions you want on the computers you want.

I outlined how it’d be done in the thread I posted below.

@kverkiss Good !!! The next time I see a jumble of nonsense errors such as this I’ll recommend trying a different drive.