Hi guys,
when I try to update a snapin in Snapin Management Edit and upload new file (ps1 or zip or whatever) the file got renamed to “1” and stored in /opt/fog/snapins. If I edit two snapins, they share file “1”.
The only workaround now is to delete end recreate snapin to get proper filename.
I would love to debug but I need to know where to look 
I am on updated Debian 11.4, FOG 1.5.9.154
Thanks for help
Peter Michalčík
Thanks a lot,
@Sebastian-Roth !
Can confirm. In 1.5.9.159 Snapin update is working as expected.
Peter
Thanks a lot,
@Sebastian-Roth !
Can confirm. In 1.5.9.159 Snapin update is working as expected.
Peter
Hi,
I force computers (with UEFI) to boot from HDD (Windows bootloader) with this command in snapin:
#Booot from HDD
#Snapin works only with Powershell x64 Snapin Template?
#Use at your own risk! No warranty!
c:\windows\system32\bcdedit.exe /set “{fwbootmgr}” displayorder “{bootmgr}”
We use it after imaging because PXE boot is too slow.
Peter
Thanks for looking into it @Sebastian-Roth and @JJ-Fullmer:
Updated to 1.5.9.156 and this issue still exists:
Hi guys,
when I try to update a snapin in Snapin Management Edit and upload new file (ps1 or zip or whatever) the file got renamed to “1” and stored in /opt/fog/snapins. If I edit two snapins, they share file “1”.
The only workaround now is to delete end recreate snapin to get proper filename.
I would love to debug but I need to know where to look
I am on updated Debian 11.4, FOG 1.5.9.154
Thanks for help
Peter Michalčík
@altitudehack
Hi again,
Apache+PHP are creating WOL packets. We had problems with HTTPS on. Now (1.5.9.78) Scheduled and Power Tasks are working. I am on Debian 10.
I always reboot fogserver after dev-branch upgrade and all services are running properly as far as I know.
I kept Tasks from MASTER before fog upgrade and fogscheduler picked them up with no hiccup (after restart).
Peter
Thank you all. It is solved now in 1.5.9.78 with HTTPS on.
/var/log/apache2/other_vhosts_access.log
80 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 302 599
443 "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111
443 "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111
/opt/fog/log/fogscheduler.log for Power Management Task
[04-29-21 6:16:25 am] * 1 task found.
[04-29-21 6:16:25 am] * 0 scheduled task(s) to run.
[04-29-21 6:16:25 am] * 1 power management task(s) to run.
[04-29-21 6:16:25 am] * Power Management Task run time: Thu, 29 Apr 2021 06:16:00 +0000
[04-29-21 6:16:25 am] * This is a cron style task that should run at: 1619676960.
[04-29-21 6:16:25 am] * Found a wake on lan task that should run.
[04-29-21 6:16:25 am] | Task sent to fcaa-https
/opt/fog/log/fogscheduler.log for Scheduled Task:
[04-29-21 6:22:26 am] * 1 task found.
[04-29-21 6:22:26 am] * 1 scheduled task(s) to run.
[04-29-21 6:22:26 am] * 0 power management task(s) to run.
[04-29-21 6:22:26 am] * Scheduled Task run time: Thu, 29 Apr 2021 06:22:00 +0000
[04-29-21 6:22:26 am] * This is a cron style task that should run at: 1619677320
[04-29-21 6:22:26 am] * Found a scheduled task that should run.
[04-29-21 6:22:26 am] - Is a host based task.
[04-29-21 6:22:26 am] - Unicaset task found!
[04-29-21 6:22:26 am] - Host fcaa-https
[04-29-21 6:22:26 am] - Task started for host fcaa-https!
Thank you again! Now our school can wake-up on Schedule
Peter
@tom-elliott
I confirm 1.9.5.77 is waking up computers on schedule again.
OS: Debian 10
FOG: dev-branch 1.9.5.77, no https.
I just noticed way longer Downloading kernel, init and fog-client binaries during update process. Takes approx 10 times longer 10-20 minutes) compare to stable. Sometimes even not finishing and timing out. Maybe problems getting client from fogproject.org?
Anyway, great and quick debugging. Thank you,Tom!
Peter
@tom-elliott Thanks for reply and your great work, Tom.
I am looking into it again with more detail.
HTTP Cron WOL
port 80, POST, status 200
HTTP Cron WOL working
x.x.x.x:80 x.x.x.x - - [28/Apr/2021:02:51:07 -0400] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 5068 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"
HTTPS instant WOL
port 443, POST, status 200
HTTPS Instant WOL working
x.x.x.x:443 x.x.x.x - - [28/Apr/2021:03:17:13 -0400] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"
HTTPS Cron WOL
port 80, POST, status 302
and
port 443 GET,status 200
HTTPS Cron WOL not working
x.x.x.x:80 x.x.x.x - - [28/Apr/2021:03:23:20 -0400] "POST /fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 302 580 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"
x.x.x.x:443 x.x.x.x - - [28/Apr/2021:03:23:20 -0400] "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"
Is POST with status 302 on port 80 ok? It may be redirection to https, I guess.
I think GET for HTTPS is wrong. It gives 200 but I think server doesnt have enough info what to wake up.
Or am I wrong?
Peter
What about this (from other_vhosts_access.log)?
x.x.x.x:443 x.x.x.x - - [27/Apr/2021:10:30:11 -0400] "GET //fog/management/index.php?node=client&sub=wakeEmUp HTTP/1.1" 200 9111 "-" "Mozilla/5.0 (Linux x86_64; rv:80.0) Gecko/20100101 Firefox/80.0"
Double leading forward slashes (//fog/…).
A typo? Or is it correct? Just a guess
Source: web/lib/fog/fogbase.class.php
$url = '%s://%s/fog/management/index.php?';
$url .= 'node=client&sub=wakeEmUp';
Peter