Bournemouth, Dorset, UK

Yes, all sorted

OK, I have sorted the 403 error now.
I edited /ect/apache2/apache2.conf, adding a new line at the bottom with
[CODE]ServerName localhost[/CODE]
And restarted the services with no errors

I’m now going to look at my domain joining and naming issue.

[B]EDIT[/B]

Just imaged two PCs, in the fog log on C both get this error

[CODE]HostnameChanger Domain Error! (‘Unknown Error’ Code: 2)[/CODE]

[SIZE=3][FONT=arial]There was a typo in [COLOR=#555555]FOG_AD_DEFAULT_OU - this must be the issue[/COLOR][/FONT][/SIZE]
[COLOR=#555555][FONT=Ubuntu][SIZE=3][FONT=arial]I’m a frickin idiot[/FONT][/SIZE] [/FONT][/COLOR]

[COLOR=#000000][FONT=arial][SIZE=3]Hey, cheers for the reply.[/SIZE][/FONT][/COLOR]
[LIST]
[][COLOR=#000000][FONT=arial][SIZE=3]On version 1.0.1 (i think,) we had the issue with APIPA whenever i put option 67 in DHCP for it to find a real file, such as unidionly.kpxe. I used to change it to something like ‘unidionly.kpxeeee’ and it wouldn’t mess with IPs. Not an issue now anyway though. :)[/SIZE][/FONT][/COLOR]
[][COLOR=#000000][FONT=arial][SIZE=3]I’m almost 100% certain that it was giving names out in the format above, i’ll be able to double check when i get it back up.[/SIZE][/FONT][/COLOR]
[*][COLOR=#000000][FONT=arial][SIZE=3]So am i right in putting :[/SIZE][/FONT][/COLOR]
[CODE]FOG_AD_DEFAULT_DOMAINNAME : “Domain”
FOG_AD_DEFAULT_OU : OU=Workstations,DC=“DOMAIN”,DC=net
FOG_AD_DEFAULT_USER : “user”
FOG_AD_DEFAULT_PASSWORD : fogcrypt’d passsword[/CODE]
[COLOR=#000000][FONT=arial][SIZE=3]

Because with versions below 1.0.0 in the user field I had domain\user[/SIZE][/FONT][/COLOR]
[][COLOR=#000000][FONT=arial][SIZE=3] I will try and create one new image and see if that changes anything[/SIZE][/FONT][/COLOR]
[][COLOR=#000000][COLOR=#000000][FONT=arial][SIZE=3]If i go to the address in a browser i get [/SIZE][/FONT][/COLOR][/COLOR]
[CODE]ForbiddenYou don’t have permission to access /fog/service/ipxe/boot.php on this server.
Apache/2.2.22 (Ubuntu) Server at IP Port 80[/CODE]
[/LIST]
[COLOR=#000000][FONT=arial][SIZE=3]Have permissions been messed up on the var/www/fog/service/ipxe folders?[/SIZE][/FONT][/COLOR]

[B]EDIT[/B]
I have tried to reset permissions using
[CODE]sudo chown -R www-data:www-data /var/www/fog
sudo chown -R fog:www-data /var/www/fog/service/ipxe/[/CODE]

and then [CODE]sudo service apache2 restart[/CODE]

with still no luck, when i restart apache services i am prompted with this…
[CODE]Restarting web server apache2
apache2: Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName
… waiting apache2:
Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName[/CODE]

In regards to domain joining, i did check the individual host AD setting and it all looked fine. It pulled across successfully from fog config

Hey guys,

First off i have to apologise for the range of issues and huge wall of text approaching.
Really sorry :oops:

I was on ver 1.0.1 and when PCs booted up, they could not log in because they had been put onto the 169 range, however imaging worked and named themselves correctly.
I have upgraded to 1.2.0 and the APIPA issue was resolved, however now when i image a PC they no longer join the domain and rename themselves to something random such as - “TBO193753-1123” or similar (TBO being the first few letters of our domain.)

I have looked into the ad settings within fog config and made sure that username only has the username within and is not in the format of domain\user. The AD account has not changed, same password, permissions and it’s not expired.

I think that when i built these images last year they [U]may[/U] have been joined to the domain when i uploaded the image, is this where i am going wrong. Has the procedure changed? The images have worked fine when on versions below 1.2.0
Do i have to rebuild all my images?

My second issue is that when i was looking at this last night, my server suddenly died with a memory error.
I have since fixed the issue, however after i got the server back online the clients get the following error during iPXE boot.

[url]http://ip.address/fog/service/ipxe/boot.php[/url]… operation not permitted ([url]http://ipxe.org/410c613c[/url])
Could not boot: Operation not permitted ([url]http://ipxe.org/410c613c[/url])
PXE-M0F : Exiting PXE ROM

I have followed this thread here with no luck - [url]http://fogproject.org/forum/threads/stuck-at-boot-php-operation-not-permitted.10706/[/url]

Thank you guys in advance, love ya

Seb

[quote=“Tom Elliott, post: 28604, member: 7271”]Thanks for the support. With which undionly are you getting the issues with the 380’s? And which error?[/quote]

Both undionly.kpxe and undionly.kkpxe on [url]https://mastacontrola.com/ipxe/f473-GOOD/[/url] provide very similar results (100% working on dell 3010)
It is the same 040ee119 error on the 380s, it then reboots and trys again.
I have also since found that dell 755 and 760 have the same issue.

So it seems like just our older models.

Both undionly.kkpxe and undionly.kpxe work 100% of the time for my Dell 3010s with realtek controllers.
However now our 380s with broadcom controllers fail almost evertime with the previous and get stuck in a boot loop.

Awesome work, i really appreciate everything you guys are doing.

[quote=“Junkhacker, post: 28386, member: 21583”]try the latest undionly.kpxe, a longer max wait time for DHCP responses has been added and it seems to help a lot[/quote]

Where can i find the latest undionly.kpxe? I’m sort of losing track of all the ones that i have tried.

Is anyone else getting this issue still? Or have others been sorted out? Maybe there is something wrong with our spec?
We are currently running ubuntu 12.04, should i try going to 13.04/13.10?