You can actually solve this issue - the problem was the wrong ip address - thanks guys for the support
Posts made by christianu
-
RE: Stop at boot.php when creating capture task
-
RE: Stop at boot.php when creating capture task
Yeah the settings are completely gone … even with the colors
-
RE: Stop at boot.php when creating capture task
Actually this is strange
parameter 1 to be resource, null given, Host: fogserver, Username: fog
“fogserver” is in this case the old fogserver ip instead of the new one - where can i change this?
Update: Found it - the nfsGroubmembers where still using the old ip.
On a side note - your boot menu config is gone (no bg nothing just blue and red) where can i restore this with bg and all?
-
RE: Stop at boot.php when creating capture task
And this when calling the url
PHP Fatal error: Uncaught exception ‘Exception’ with message ‘Type: 2, File: /var/www/html/fog/lib/fog/fogurlrequests.class.php, Line: 108, Message: curl_multi_add_handle() expects parameter 1 to be resource, null given, Host: fogserver, Username: fog’ in /var/www/html/fog/lib/fog/fogftp.class.php:51\nStack trace:\n#0 /var/www/html/fog/lib/fog/storagenode.class.php(102): FOGFTP->connect()\n#1 /var/www/html/fog/lib/fog/fogcontroller.class.php(245): StorageNode->loadImages()\n#2 /var/www/html/fog/lib/fog/fogcontroller.class.php(48): FOGController->loadItem(‘images’)\n#3 /var/www/html/fog/lib/fog/storagenode.class.php(41): FOGController->get(‘images’)\n#4 /var/www/html/fog/lib/fog/storagegroup.class.php(44): StorageNode->get(‘images’)\n#5 [internal function]: StorageGroup->{closure}(Object(StorageNode))\n#6 /var/www/html/fog/lib/fog/storagegroup.class.php(52): array_map(Object(Closure), Array)\n#7 /var/www/html/fog/lib/fog/bootmenu.class.php(641): StorageGroup->getOptimalStorageNode(‘1’)\n#8 /var/www/html/fog/lib/fog/bootmenu.class.php(1 in /var/www/html/fog/lib/fog/fogftp.class.php on line 51
I call it a night and will continue tomorrow
-
RE: Stop at boot.php when creating capture task
This comes when creating the task
PHP Warning: curl_setopt_array() expects exactly 2 parameters, 1 given in /var/www/html/fog/lib/fog/fogurlrequests.class.php on line 107, referer: http://fog.mgmt.offber/fog/management/index.php?node=host&sub=deploy&id=2&type=2
-
RE: Stop at boot.php when creating capture task
Yeah just the first 4 lines
#!ipxe set fog-ip 192.168.22.76 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot}
-
RE: Stop at boot.php when creating capture task
This is what i get when i call it without capture task
#!ipxe set fog-ip 192.168.22.76 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot} cpuid --ext 29 && set arch x86_64 || set arch i386 goto get_console :console_set goto MENU :alt_console goto MENU :get_console console --picture http://192.168.22.76/fog/service/ipxe/ --left 100 --right 80 && goto console_set || goto alt_console :MENU menu item --gap Host is registered as BPY-LAP-028! item --gap -- ------------------------------------- item fog.local Boot from hard disk item fog.memtest Run Memtest86+ item fog.keyreg Update Product Key item fog.quickimage Quick Image item fog.multijoin Join Multicast Session item fog.quickdel Quick Host Deletion item fog.sysinfo Client System Information (Compatibility) choose --default fog.local --timeout 0 target && goto ${target} :fog.local sanboot --no-describe --drive 0x80 || goto MENU :fog.memtest kernel memdisk iso raw initrd memtest.bin boot || goto MENU :fog.keyreg login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param keyreg 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.quickimage login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.multijoin login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param sessionJoin 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.quickdel login params param mac0 ${net0/mac} param arch ${arch} param username ${username} param password ${password} param delhost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :fog.sysinfo kernel bzImage32 loglevel=4 initrd=init_32.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=192.168.22.76/fog/ consoleblank=0 rootfstype=ext4 loglevel=4 mode=sysinfo imgfetch init_32.xz boot || goto MENU :bootme chain -ar http://192.168.22.76/fog/service/ipxe/boot.php##params || goto MENU autoboot
-
RE: Stop at boot.php when creating capture task
Yeah but the management console is running
-
RE: Stop at boot.php when creating capture task
When i create a new capture task its the same error again. But i have to change the title apparently
-
RE: Stop at boot.php when creating capture task
Yes to all of it - the “//” was not the problem. Yes the servers owns a static ip and is behind a dhcp - all options are set (i already saw your bootmenu)
But i found something else for now
I called the url with the MAC address the not working host and i got just these lines
#!ipxe set fog-ip 192.168.22.76 set fog-webroot fog set boot-url http://${fog-ip}/${fog-webroot}
Than i remembered that i created an image pull task for this host - deleted the task and the boot menu is back again.
-
RE: Stop at boot.php when creating capture task
I did now - but unfortunately i am not able to test it now. Can do tomorrow morning
-
RE: Stop at boot.php when creating capture task
okay i will change the default.ipxe (it should not help)
Ah - its a Debian and completely fresh.
@george1421 A screen full of text
-
Stop at boot.php when creating capture task
Hey folks,
i update on the current trunk (like 1 hour ago) and now the bootloader stucks at “http://fogserver//fog/service…” , Mind the “//”, i cannot make it bold unfortunately. Is this an error in my configuration or is this a bug in the trunk?
Thanks
Chrisedit: a capture task is created for this machine - with the task cancelled the boot menu shows up without any issues
-
RE: hostname.php stays emtpy
Yeah i found the actual problem, i dont know why we did this
option tftp-server-name "xxx.xxx.xxx.xxx"
This renders your variable “next-server” more or less useless.
Fixed it and its running like a charme.
And i have a update to the other issue (with the client) aswell. After reinstalling everything the hostname changer is working too
So thank you very much for your support guys! If you have any questions please contact me
-
RE: hostname.php stays emtpy
@Sebastian-Roth said:
@christianu said:
unfortunately when i boot up the system now it asks me for the TFTP Server IP
That’s interesting! We have changed the iPXE embedded script lately and this might have to do with it. Is your client normal BIOS or UEFI? And more importantly where is your DHCP server/do you use proxy DHCP???
Good mornin!
currently its still BIOS i will try to switch this to UEFI asap. We have proxy DHCP, so the FOG server is not the DHCP.
Aunt Edit: I just tested and entered the TFTP IP and hey - it still works, so i there is some things up with the CHAIN load. Can you give me a hint where to look for the fix?
-
RE: hostname.php stays emtpy
Okay this is doing fine for now, unfortunately when i boot up the system now it asks me for the TFTP Server IP, i think the config was overwritten in one reinstall attempt.
We ran a “own” version with atftpd and not tftpd-hpa, so i would say moving this
pxelinux.0 -> pxelinux.0.old
back to
pxelinux.0 -> undionly.kpxe
should help. I will test everything tomorrow and will get back to you.
-
RE: hostname.php stays emtpy
Update Reinstall done - unfortunately now i get an
Invalid MAC Address! E8:B1:FC:03:F7:CD|E8:B1:FC:03:F7:CE|54:EE:75:2D:AC:1F|E8:B1:FC:03:F7:D1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|94:87:B3:5B:56:5A
error
With the correct MAC
http://xxx.xxx.xxx.xxx/fog/service/hostname.php?moduleid=hostnamechanger&mac=54:EE:75:2D:AC:1F&newService=1
address i get
#!ihc
and without newSerivce=1 i´ll get this
#!ok=HOSTNAME #AD= #ADDom= #ADOU= #ADUser= #ADPass=
-
RE: hostname.php stays emtpy
Okay will do - can i somehow deactivate the TFTP install stuff? I configured everything with ATFTP and everytime i reinstall fog it cleans everything up
-
RE: hostname.php stays emtpy
Puh i was rly stupid - should have looked there too …
[Wed Nov 11 09:53:58.509286 2015] [:error] [pid 26265] [client xxx.xxx.xxx.xxx:49169] PHP Fatal error: Call to undefined method HostnameChanger::setAD() in /var/www/html/fog/lib/client/HostnameChanger.class.php on line 16```
-
RE: hostname.php stays emtpy
Yeah that is the point. This is the error message from the client service
------------------------------------------------------------------------------ --------------------------------HostnameChanger------------------------------- ------------------------------------------------------------------------------ 11.11.2015 12:30 Client-Info Version: 0.9.5 11.11.2015 12:30 HostnameChanger Running... 11.11.2015 12:30 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/servicemodule-active.php?moduleid=hostnamechanger&mac=E8:B1:FC:03:F7:CD|E8:B1:FC:03:F7:CE|54:EE:75:2D:AC:1F|E8:B1:FC:03:F7:D1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|94:87:B3:5B:56:5A&newService=1 11.11.2015 12:30 Middleware::Communication Response: Success 11.11.2015 12:30 Middleware::Communication URL: http://xxx.xxx.xxx.xxx/fog/service/hostname.php?moduleid=hostnamechanger&mac=E8:B1:FC:03:F7:CD|E8:B1:FC:03:F7:CE|54:EE:75:2D:AC:1F|E8:B1:FC:03:F7:D1||00:00:00:00:00:00:00:E0|00:00:00:00:00:00:00:E0|94:87:B3:5B:56:5A&newService=1 11.11.2015 12:30 Middleware::Communication ERROR: Could not contact FOG server 11.11.2015 12:30 Middleware::Communication ERROR: Der Remoteserver hat einen Fehler zurückgegeben: (500) Interner Serverfehler. ------------------------------------------------------------------------------``` When i call the url manually with the browser its just empty. So there is an error but not really an error message.