Posts made by Petěrko

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:

1. Go to existing Snapin
2. Browse and upload new file
3. Snapin gets updated
4. Open Snapin again and it says (unfortunately) the attached file name is 1.
5. In /opt/fog/snapins: original file stays (with original name), new file is named 1.
6. After update I see one difference, in a group:
   v154: fogproject:www-data
   v156: fogproject:fogproject
7. If you update more Snapins, the file named 1 get rewritten again and again as all updated Snapins refer to this file.

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

@tom-elliott
@Sebastian-Roth

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

Update: Same on 1.5.9.77
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

Hi @tom-elliott and @altitudehack!

I can confirm on new install. Debian 10 KVM (no https because Scheduled Power Tasking with https didnt work).

Scheduled Power Management Task is working on Master branch, not working on dev-branch (1.5.9.75).

Master:

[04-27-21 12:42:25 pm]  * 1 task found.
[04-27-21 12:42:25 pm]  * Task run time: Tue, 27 Apr 2021 12:42:00 +0000
[04-27-21 12:42:25 pm]  * Found a wake on lan task that should run.
[04-27-21 12:42:25 pm]  | Task sent to fcaa148962ce

And looking for tasks every minute.

Dev-branch:

[04-27-21 1:15:12 pm]  * 1 task found.
[04-27-21 1:15:12 pm]  * 0 scheduled task(s) to run.
[04-27-21 1:15:12 pm]  * 1 power management task(s) to run.

No more lines in log. Finishes here. No more checking for tasks in log.

Peter

@sebastian-roth
I can confirm now. Https setting during install is the culprit.

Debian10 VM 1.5.9
http - instant WOL OK, scheduled WOL - working
https - instant WOL OK, scheduled WOL - not working

Peter

@sebastian-roth Hi, today I found time to install Ubuntu Server 20.04.2 on Bare Metal and KVM (Proxmox). With HTTPS enabled and disabled. Master and DEV-branch. It looks like https problem but I will test it once more to be sure.

Scheduled WOL is working on:
1.5.9 on Ubuntu (KVM/Baremetal) with https DISABLED

Scheduled WOL is not working on:
1.5.9 on Ubuntu with https ENABLED
19.5.75 on Ubuntu with https ENABLED

I will continue on that in @altitudehack 's topic.

Peter

Found one more table:

INSERT INTO `powerManagement` VALUES (3,1,'20','*','*','*','*','wol','0'),(2,1,'','','','','','shutdown','1');

Peter

@sebastian-roth Thanks for reply, Sebastian!

I am not sure what settings would you like to see. Fog Settings? I can upload globalSettings table, if it helps…

When I export settings I get this for Power Task:

INSERT INTO `scheduledTasks` VALUES (1,'Wake-Up Task','','S',14,'','','','','','',1,0,'','','-1','fog','1','',1619075220,'0');

This is log for Scheduled Power WOL Task:

[04-22-21 10:19:02 am]  * 1 task found.
[04-22-21 10:19:02 am]  * Task run time: Thu, 22 Apr 2021 10:58:00 +0200
[04-22-21 10:20:02 am]  * 1 task found.
[04-22-21 10:20:02 am]  * Task run time: Thu, 22 Apr 2021 10:20:00 +0200
[04-22-21 10:20:02 am]  * Found a wake on lan task that should run.
[04-22-21 10:20:02 am]  | Task sent to test-mmu
[04-22-21 10:21:02 am]  * 1 task found.
[04-22-21 10:21:02 am]  * Task run time: Thu, 22 Apr 2021 11:20:00 +0200

SQL for Scheduled Wake-Up Task looks bit better but still doesn’t work:

INSERT INTO `scheduledTasks` VALUES (2,'Wake-Up Task','','C',14,'44','*','*','*','*','',1,0,'','','-1','fog','1','',0,'1');

Peter

Hi again,

today I tried CentOS 7 + FOG dev-branch. Later upgraded to working-1.6 branch. Still no success.

Should fogscheduler.log report this when waking PCs from scheduled task?

[01-18-20 10:35:05 pm]  * Sending 1 wake on lan request.
[01-18-20 10:35:05 pm]  * 1 total mac attempting to wake up.

It is not showing in my log…
Is the process/code for WOL Perform Immediately and cron-style same or different?

May the problem be network related? Subnets? VLANs?
Or KVM related? I run OSes as Virtual Machines on Proxmox.
WOL Perform Immediately is working fine.

Thank you for any help!
Peter

Hallo all!

OS: Debian 10. Fresh install.
FOG: 1.5.9. (tried dev branch 1.5.9.65 too).

I can not make Scheduled WOL work. Wake on Lan via Power Management option “Perform Immediately” is working perfectly. Tried group/host tasks, tried power management, Wake-up task…

File /opt/fog/log/fogscheduler.log shows:

For Power Management Cron task:

[04-21-21 1:04:12 pm]  * 1 task found.
[04-21-21 1:04:12 pm]  * Task run time: Wed, 21 Apr 2021 13:04:00 +0200
[04-21-21 1:04:12 pm]  * Found a wake on lan task that should run.
[04-21-21 1:04:12 pm]  | Task sent to XXXXX

For Wake-up Task:

[04-21-21 1:06:12 pm]  * 1 task found.
[04-21-21 1:06:12 pm]  * Task run time: Wed, 21 Apr 2021 13:06:00 +0200
[04-21-21 1:06:12 pm]  * Found a task that should run.
[04-21-21 1:06:12 pm]            - Is a host based task.
[04-21-21 1:06:12 pm]            - Unicast task found!
[04-21-21 1:06:12 pm]            - Host XXXXX
[04-21-21 1:06:12 pm]            - Tasks started for host XXXXX!

But it never shows:

[01-18-20 10:35:05 pm]  * Sending 1 wake on lan request.
[01-18-20 10:35:05 pm]  * 1 total mac attempting to wake up.

Any idea why FOG is not waking computers up when scheduled?

Thanks!
Peter