Parted Magic not working in pxe boot
-
@Dino_Nerd ok fixed no more redirect message…
next??
just a minute let me look at what a default one should be.
-
@Dino_Nerd Well the default was as you had it originally with the redirect in there.
Is there any hidden .htaccess files in the root directory? hint:
ls -la /var/www/html
-
@george1421 looking at your configs I see a conflict.
There is /var/www/html/fog and /var/www/fog I’m wondering if the right path for your partition magic files shouldn’t be
/var/www/pmagic
I’m pretty sure debian variants use /var/www as the document root where rhel based ones use /var/www/html. -
not that I can see, I hope im in the right place here
-
@Dino_Nerd key in the following command.
cp /var/www/html/pmagic /var/www
Then
ls -la /var/www
and ensure there is a pmagic directory there.Your document root for debian/ubuntu should be /var/www not /var/www/html (but I’m a rhel guy, so I’m not absolutely sure)
-
@george1421 said in Parted Magic not working in pxe boot:
@Dino_Nerd key in the following command.
cp /var/www/html/pmagic /var/www
Then
ls -la /var/www
and ensure there is a pmagic directory there.Hey that works wonderfully! Thanks a bunch
Your document root for debian/ubuntu should be /var/www not /var/www/html
Maybe this should be updated in the wiki as an ubuntu method
(but I’m a rhel guy, so I’m not absolutely sure)
I’m a big fan of RHEL myself (also archlinux). maybe you can help me on a new topic trying to get CentOS to play ball with FOG? (I’ll create a new thread for this)
-
@Dino_Nerd Centos 7.x and 6.5+ work with FOG. That is what we run on our campus. This IS a current issue with centos 7 in that a defective rpcinfo rpm was released. I believe they just update that in the repo. But other than that, fog works perfectly on cento 7.
-
@george1421 said in Parted Magic not working in pxe boot:
@Dino_Nerd Centos 7.x and 6.5+ work with FOG. That is what we run on our campus. This IS a current issue with centos 7 in that a defective rpcinfo rpm was released. I believe they just update that in the repo. But other than that, fog works perfectly on cento 7.
Any idea if it works as a UEFI booted VMWare workstation Virtual machine?
Is there any advantage to using UEFI over BIOS for a FOG server? -
@Dino_Nerd I can’t say for sure. By default when you create a vm its bios/legacy mode. I can’t see why it wouldn’t. EFI mode under virtual box is a bit wonky, but VMWare esxi or workstation should be OK. You’ll know right away if it will work or not because centos won’t boot if its wrong.
No advantage for efi. GPT yes if you need really big drives.
-
@george1421 said in Parted Magic not working in pxe boot:
@Dino_Nerd I can’t say for sure. By default when you create a vm its bios/legacy mode. I can’t see why it wouldn’t. EFI mode under virtual box is a bit wonky, but VMWare esxi or workstation should be OK. You’ll know right away if it will work or not because centos won’t boot if its wrong.
I’ll start a new thread when I hit the roadblock I was getting before, thanks so much for your help
-
@Dino_Nerd @george1421 I am still wondering about this. Just found out that it is doing this (redirect loop) on a clean fresh install on debian too. Just didn’t see this on my home FOG server where I customize most configs.
Disabling the redirection rule is fine in this case but I ought to find a general solution for this. When looking at the HTTP traffic I see a HTTP 302 answer with a
Location
header but the value is empty! I am wondering if this is a ubuntu/debian specific thing or if we have this with RHEL/CentOS as well? -
@Sebastian-Roth @george1421 @Dino_Nerd
I think this is the problem he’s having: https://forums.fogproject.org/topic/10121/directories-under-var-www-html-not-showing-after-upgrade-to-1-4/6
-
@george1421 said in Parted Magic not working in pxe boot:
Your document root for debian/ubuntu should be /var/www not /var/www/html (but I’m a rhel guy, so I’m not absolutely sure)
/var/www/html is valid for Debian 8.
-
After some more debugging I found that the redirection loop is not caused by the apache rewrite rules but by /var/www/fog/api/index.php and those included by that PHP file. Maybe this is because we don’t supply correct parameters?! Would be nice if it wouldn’t redirect in an endless loop.
@Dino_Nerd I think you can re-add the
RewriteRule ^/(.*)$ /fog/api/index.php [QSA,L]
in your 001-fog.conf and still should be able to access and boot http://192.168.0.143/pmagic/bzImage64 if that folder is in/var/www
!!Note to myself: Accessing directories (like http://192.168.0.143/pmagic/) does not work albeit the second RewriteCond because DirectoryIndex setting makes it request index.html in that directory, which usually does not exist. Therefore again redirecting it to /fog/api/index.php