Hi @sebastian-roth
FOG 1.5.9 on Debian 10
Posts made by Florent
-
RE: Wake on lan difference between basic tasks and power management ?
-
Wake on lan difference between basic tasks and power management ?
Hi,
I have problem with Wake on lan in Power Management.
If i launch Wake on lan from Host or Group / Basic tasks / advanced / wake-up it’s work fine.
But if i use on Power Management to schedule, it’s not work.
Power Management work for Reboot.
Any ideas ?Regards
-
RE: Update initrd (of live pxe)
@sebastian-roth Yes curl -k works, but if i can avoid this.
Intersting nobody never asked this. -
RE: Update initrd (of live pxe)
@sebastian-roth Hi,
Sorry i poorly explained.
We are on FOG 1.5.9
When computer boot on PXE after cloning, there is “postdownload” bash script.
In this script we try to get an external URL (not FOG) who have “Geant” certificate but https verification failed.
If i test on classic computer it’s work.
I go to try to update the init.xz -
Update initrd (of live pxe)
Hi,
Is it possible to update initrd (of live PXE) for the next upgrade of FOG ?
We have Geant certificates that have not recognize by curl. I think it’s need the last ca-certificates ? -
RE: Wakeonlan where ?
Don"t worry it’s not for copy
I use FOG, just want to see (untderstand) how wakeonlan is send by FOG. (etherwake or wakeonlan, with options or not etc)
When i have try grep i do mistake syntax this explain why i found nothing on my server.
Sorry thanks for the tips -
Wakeonlan where ?
Hi,
I want to see how wakeonlan is implementend in code source.
I have search on github “wakeonlan” or “etherwake” but find nothing.
Don’t find wol.php in /fogCan you help me ?
-
Multicast - Sometimes a few host not update database
Hi,
Other problem with multicast but not blocking.
Sometimes a few host not update database.
At the end of imaging with Partclone, postinstall script do various tasks (copy of drivers for example).
I have the feeling that my computers not take the same time to execute this postinstall scripts. And “active task” disappear
This not create problem but only Database not update.
In “Image History” host, not see the last imaging date.Not possible to adjust timeout or other things ?
Regards
-
RE: Interface not ready, waiting for it to come up
Sorry i have found the problem.
In FOG Settings / Web Server / Web Host i have set the same result ofcat /etc/hostname
Because before i have here an network alias.
Regards.
-
RE: Interface not ready, waiting for it to come up
This not resolve for me
All my FOG* service areActive: active (running)
correctly
Upload and download image work.
Just schedule tasks (for example wakeonlan with cron) and multicast not work. -
Interface not ready, waiting for it to come up
Hi,
Since i have upgrade to 1.5.8 i have problem with multicast and fogscheduler.In all my logs file (fogscheduler.log, multicast.log etc) i have this line repaeted :
Interface not ready, waiting for it to come up: mydomain.fr
I have verify this :
-ip addr show => eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
-Fog Configuration -> Fog Settings -> Multicast settings -> UPDCAST INTERFACE => eth0
-Storage -> Default storage node -> Interface => eth0I have try to reboot my server.
Have you idea ?
-
Multiple Spanning Tree Protocol (MSTP)
Hi,
Is it preview in the next version, FOG being 100% compatible with Multiple Spanning Tree Protocol (MSTP) ?
Regards -
RE: Display bug on webinterface / Hosts / Image History
@Fernando-Gietz
Thanks.
You can set status to solved -
RE: Display bug on webinterface / Hosts / Image History
Oups sorry we are in 1.5.5
-
Display bug on webinterface / Hosts / Image History
Hi,
I think there is a little bug in fog webinterface / Hosts / Image History.
We are many technician.In the hosts if i go to the menu “Image History” i see in the first column “Engineer” always my name (instead if not me who have deploy image on this host).
While if i go to the mysql database i see the good technician name.Regards
-
RE: Power Management - Day of week usage differ from cron
@Sebastian-Roth
Ok thanks.
Waiting, workaround for us is to use SUN, MON, TUE, WED, THU, FRI, SAT instead of number for Shutdown and Reboot