Hi @malansanni70, I could help you figure out how to open ports, but to be clear that’s just one step of many that are necessary to get PXE working. Have you already set DHCP options 66 & 67 and ensured your network is traversable for PXE/TFTP (as in, everything is behind a single router or using iphelper on a larger network)?
Flavor and version of your server’s operating system? What’s your end-goal here?
A
Posts made by altitudehack
-
RE: network bootposted in General Problems
-
RE: User Tracking search not workingposted in FOG Problems
@george1421 said in User Tracking search not working:
little gear on original post
I see no gear or settings on the original post, leading me to believe this is a moderator-only feature. Thank you for marking the solution!
-
RE: User Tracking search not workingposted in FOG Problems
@george1421 How the heck do I mark the answer as solved on the forum?
-
RE: User Tracking search not workingposted in FOG Problems
I ended up searching for
memory_limitin /etc/php*:grep -r memory_limit /etc/php*The two active files were /etc/php.ini and /etc/php-fpm.d/www.conf:
/etc/php-fpm.d/www.conf:php_admin_value[memory_limit] = 1024M /etc/php-fpm.d/www.conf:;php_admin_value[memory_limit] = 256M /etc/php.ini:memory_limit = 512M /etc/php.ini:;memory_limit = 128MI duplicated the lines, commented out the original with
;, then quadrupled the values. Restarted the services with:systemctl restart httpd systemctl restart php-fpm.serviceUser Tracking queries now work as expected.
-
RE: User Tracking search not workingposted in FOG Problems
@george1421
You’re right. Thanks for the tip!tail /var/log/httpd/ssl_error_log ... [Thu Dec 02 11:44:24.766930 2021] [php7:error] [pid 24293] [client my_IP:38154] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 16384 bytes) in /var/www/html/fog/lib/fog/fogcontroller.class.php on line 260, -
RE: User Tracking search not workingposted in FOG Problems
The data’s there, and it’s less than 5000 rows, so doesn’t seem like an excessive query:
MariaDB [fog]> select * from userTracking; +------+----------+-------------+----------+---------------------+--------+------------+---------+ | utID | utHostID | utUserName | utAction | utDateTime | utDesc | utDate | utAnon3 | +------+----------+-------------+----------+---------------------+--------+------------+---------+ ... ... | 4816 | 41 | jesie | 1 | 2021-12-02 08:52:08 | | 2021-12-02 | | | 4817 | 6 | magpie | 1 | 2021-12-02 08:59:26 | | 2021-12-02 | | | 4818 | 20 | lennard | 1 | 2021-12-02 09:02:32 | | 2021-12-02 | | | 4819 | 57 | albatros | 1 | 2021-12-02 10:19:25 | | 2021-12-02 | | +------+----------+----------------+----------+---------------------+--------+------------+---------+ 4819 rows in set (0.003 sec)It returns a blank page even when I specify a user and the machine they’re assigned to.
-
User Tracking search not workingposted in FOG Problems
Updated to Version 1.5.9.113 but behavior is still the same. Page never loads, just shows blank.
tail /var/log/php-fpm/error.log shows nothing since I restarted it (the above search was performed after 14:43):
[01-Dec-2021 14:43:58] NOTICE: exiting, bye-bye! [01-Dec-2021 14:43:58] NOTICE: fpm is running, pid 27319 [01-Dec-2021 14:43:58] NOTICE: ready to handle connections [01-Dec-2021 14:43:58] NOTICE: systemd monitor interval set to 10000ms -
RE: unusual network traffic to/from fog clientposted in FOG Problems
@sebastian-roth Perfect. The original install was through a Group Policy .msi push, so I added the newer agent to replace the old one. Appreciate the quick info!
-
RE: unusual network traffic to/from fog clientposted in FOG Problems
I think you nailed it:
---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:04:09 AM Client-Info Client Version: 0.11.19 11/3/2021 7:04:09 AM Client-Info Client OS: Windows 11/3/2021 7:04:09 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:04:10 AM Middleware::Response ERROR: Unable to get subsection 11/3/2021 7:04:10 AM Middleware::Response ERROR: Object reference not set to an instance of an object. ------------------------------------------------------------------------------ ----------------------------------TaskReboot---------------------------------- -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:27:59 AM Client-Info Client Version: 0.11.19 11/3/2021 7:27:59 AM Client-Info Client OS: Windows 11/3/2021 7:27:59 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:27:59 AM Middleware::Response Success 11/3/2021 7:27:59 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:28:00 AM Data::RSA FOG Project cert found 11/3/2021 7:28:00 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:29:27 AM Client-Info Client Version: 0.11.19 11/3/2021 7:29:27 AM Client-Info Client OS: Windows 11/3/2021 7:29:27 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:29:27 AM Middleware::Response Success 11/3/2021 7:29:27 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:29:27 AM Data::RSA FOG Project cert found 11/3/2021 7:29:27 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:30:48 AM Client-Info Client Version: 0.11.19 11/3/2021 7:30:48 AM Client-Info Client OS: Windows 11/3/2021 7:30:48 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:30:48 AM Middleware::Response Success 11/3/2021 7:30:48 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:30:48 AM Data::RSA FOG Project cert found 11/3/2021 7:30:48 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:33:02 AM Client-Info Client Version: 0.11.19 11/3/2021 7:33:02 AM Client-Info Client OS: Windows 11/3/2021 7:33:02 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:33:02 AM Middleware::Response Success 11/3/2021 7:33:02 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:33:02 AM Data::RSA FOG Project cert found 11/3/2021 7:33:02 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:34:16 AM Client-Info Client Version: 0.11.19 11/3/2021 7:34:16 AM Client-Info Client OS: Windows 11/3/2021 7:34:16 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:34:16 AM Middleware::Response Success 11/3/2021 7:34:16 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:34:16 AM Data::RSA FOG Project cert found 11/3/2021 7:34:16 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:36:24 AM Client-Info Client Version: 0.11.19 11/3/2021 7:36:24 AM Client-Info Client OS: Windows 11/3/2021 7:36:24 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:36:24 AM Middleware::Response Success 11/3/2021 7:36:24 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:36:24 AM Data::RSA FOG Project cert found 11/3/2021 7:36:24 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:38:26 AM Client-Info Client Version: 0.11.19 11/3/2021 7:38:26 AM Client-Info Client OS: Windows 11/3/2021 7:38:26 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:38:26 AM Middleware::Response Success 11/3/2021 7:38:26 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:38:26 AM Data::RSA FOG Project cert found 11/3/2021 7:38:26 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:40:10 AM Client-Info Client Version: 0.11.19 11/3/2021 7:40:10 AM Client-Info Client OS: Windows 11/3/2021 7:40:10 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:40:10 AM Middleware::Response Success 11/3/2021 7:40:10 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:40:10 AM Data::RSA FOG Project cert found 11/3/2021 7:40:10 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------ -- ---------------------------------ClientUpdater-------------------------------- ------------------------------------------------------------------------------ 11/3/2021 7:42:38 AM Client-Info Client Version: 0.11.19 11/3/2021 7:42:38 AM Client-Info Client OS: Windows 11/3/2021 7:42:38 AM Client-Info Server Version: 1.5.9.98 11/3/2021 7:42:38 AM Middleware::Response Success 11/3/2021 7:42:38 AM Middleware::Communication Download: http://fogserver/fog/client/SmartInstaller.exe 11/3/2021 7:42:38 AM Data::RSA FOG Project cert found 11/3/2021 7:42:38 AM ClientUpdater ERROR: Update file is not authentic ------------------------------------------------------------------------------Any suggestions on how to address the root cause in case other clients are affected?
Thanks -
unusual network traffic to/from fog clientposted in FOG Problems
A user remoting in over the VPN is complaining of slow performance and network drops. Looking at the ssl firewall traffic, I noticed an odd pattern of a periodic data transfer between the laptop and the fog server:
Time Sent Bytes Received Bytes 11-02 20:49:12 142156 9628152 11-02 20:46:03 141236 9628152 11-02 20:44:13 140556 9628152 11-02 20:42:04 141316 9628152 11-02 20:40:04 142356 9628152 11-02 20:37:28 141636 9628152 11-02 20:34:47 140556 9628152 11-02 20:32:16 141316 9628152 11-02 20:29:04 138676 9628152 11-02 20:27:56 138756 9628152 11-02 20:26:07 138716 9628152 11-02 20:23:46 138636 9628152 11-02 20:21:23 138716 9628152 11-02 20:20:06 138716 9628152 11-02 20:17:58 138756 9628152 11-02 20:16:40 138636 9628152 11-02 20:14:58 139116 9628152 11-02 20:12:45 139156 9628152 11-02 20:10:26 140716 9628152 11-02 20:07:29 139956 9628152I don’t see any pending tasks for the host, and snapins are all marked as completed. Any idea what would cause a ~10M file to transfer every two minutes?
-
RE: Daily wake-up routine not working after updateposted in FOG Problems
@tom-elliott hard to say. Most PCs are left running so I wouldn’t know if they were woken up or not. I can try to find a couple more to monitor.
-
RE: Daily wake-up routine not working after updateposted in FOG Problems
Hi @Tom-Elliott! I’m back again. I haven’t made any changes, but my Group Task doesn’t seem to be running. Logs show it is, but I have a user who’s contacted me a couple times that his PC was not woken up. When I run the wakeup task manually it works. Here’s the scheduler log from around that time:
[07-12-21 6:00:48 am] * 2 tasks found. [07-12-21 6:00:48 am] * 1 scheduled task(s) to run. [07-12-21 6:00:48 am] * 1 power management task(s) to run. [07-12-21 6:00:48 am] * Scheduled Task run time: Mon, 12 Jul 2021 06:00:00 -0500 [07-12-21 6:00:48 am] * This is a cron style task that should run now. [07-12-21 6:00:48 am] * Found a scheduled task that should run. [07-12-21 6:00:48 am] - Is a group based task. [07-12-21 6:00:48 am] - Unicaset task found! [07-12-21 6:00:48 am] - Group Desktop Computers for Work from Home [07-12-21 6:00:48 am] - Task started for group Desktop Computers for Work from Home! [07-12-21 6:00:48 am] * Power Management Task run time: Tue, 13 Jul 2021 05:00:00 -0500 [07-12-21 6:00:48 am] * This is a cron style task that should not run now.. [07-12-21 6:01:48 am] * 2 tasks found. [07-12-21 6:01:48 am] * 1 scheduled task(s) to run. [07-12-21 6:01:48 am] * 1 power management task(s) to run. [07-12-21 6:01:48 am] * Scheduled Task run time: Tue, 13 Jul 2021 06:00:00 -0500 [07-12-21 6:01:48 am] * This is a cron style task that should not run now.Disk usage looks normal.
Updating to the latest version. Will let you know if it recurs.
Thanks! -
RE: Daily wake-up routine not working after updateposted in FOG Problems
@Tom-Elliott
Welp, it worked. I didn’t change anything. Sorry I already ran an update (FOMO is a powerful force!) so don’t have logs from this morning. -
RE: Daily wake-up routine not working after updateposted in FOG Problems
Good morning @Tom-Elliott,
It looks like it’s not working for groups. I have a single task to wake my desktop, and that’s working, but the groups target is not receiving wake-up packets.The scheduled task exists and looks correct:
The database entries are summarized in my last note and I haven’t made any changes.
The schedule logs contain this at the witching hour:[05-13-21 6:00:44 am] * 2 tasks found. [05-13-21 6:00:44 am] * 1 scheduled task(s) to run. [05-13-21 6:00:44 am] * 1 power management task(s) to run. [05-13-21 6:00:44 am] * Scheduled Task run time: Thu, 13 May 2021 06:00:00 -0500 [05-13-21 6:00:44 am] * This is a cron style task that should run now. [05-13-21 6:00:44 am] * Found a scheduled task that should run. [05-13-21 6:00:44 am] - Is a group based task. [05-13-21 6:00:44 am] - Unicaset task found! [05-13-21 6:00:44 am] - Group Desktop Computers for Work from Home [05-13-21 6:00:44 am] - Task started for group Desktop Computers for Work from Home! [05-13-21 6:00:44 am] * Power Management Task run time: Fri, 14 May 2021 05:00:00 -0500 [05-13-21 6:00:44 am] * This is a cron style task that should not run now..However computers in the target group are still off after 6am. I can run the group task manually and it does start up. I tested both via the power-management tab and also the Basic Tasks --> Advanced --> Wake-up option and they both work.
I did update in the past couple days so am on dev-branch version: 1.5.9.87
Thanks! -
RE: Daily wake-up routine not working after updateposted in FOG Problems
@Tom-Elliott so I truncated the tables and re-created the jobs - one I created via Basic Tasks -> Advanced -> Wake up, and one I created through the Power Management window. Here’s the resulting database entries for Day of Week and Day of Month from both:
MariaDB [fog]> select stDOM,stDOW from scheduledTasks\G *************************** 1. row *************************** stDOM: * stDOW: 1-5 1 row in set (0.001 sec) MariaDB [fog]> select pmDom,pmDow from powerManagement\G *************************** 1. row *************************** pmDom: * pmDow: 1-5 1 row in set (0.000 sec)So it’s looking good now. As you can see in my previous database entry, I had
1-5entered under pmDom, which was likely the issue. I’m giving this point to user error.
Thanks again for your help! -
RE: Daily wake-up routine not working after updateposted in FOG Problems
@tom-elliott Sorry I’ve been quiet, because it had been working
However this morning it looks like it did not fire. It’s after 8am here and there’s no entry for these two at 6am on the morning of 05-06:
[Cent-7:root@fog ~]# grep stacy /var/log/fog/fogscheduler.log [05-01-21 6:00:54 am] | Task sent to stacy-pc [05-02-21 6:00:44 am] | Task sent to stacy-pc [05-03-21 6:00:36 am] | Task sent to stacy-pc [05-04-21 6:00:27 am] | Task sent to stacy-pc [05-05-21 6:00:18 am] | Task sent to stacy-pc [Cent-7:root@fog ~]# grep luke /var/log/fog/fogscheduler.log [05-01-21 6:00:54 am] | Task sent to luke-pc [05-02-21 6:00:44 am] | Task sent to luke-pc [05-03-21 6:00:35 am] | Task sent to luke-pc [05-04-21 6:00:27 am] | Task sent to luke-pc [05-05-21 6:00:18 am] | Task sent to luke-pcI ran your
mvcommands and re-ran the installer.
Then I get 21 rows of this:MariaDB [fog]> select * from powerManagement \G *************************** 1. row *************************** pmID: 1 pmHostID: 14 pmMin: 0 pmHour: 6 pmDom: 1-5 pmMonth: * pmDow: * pmAction: wol pmOndemand: 0 *************************** 2. row *************************** pmID: 2 pmHostID: 26 pmMin: 0 pmHour: 6 pmDom: 1-5 pmMonth: * pmDow: * pmAction: wol pmOndemand: 0 ... ... ... *************************** 21. row *************************** pmID: 21 pmHostID: 36 pmMin: pmHour: pmDom: pmMonth: pmDow: pmAction: reboot pmOndemand: 1 21 rows in set (0.000 sec)and:
MariaDB [fog]> select * from scheduledTasks\G *************************** 1. row *************************** stID: 8 stName: Wake-Up Task stDesc: stType: C stTaskTypeID: 14 stMinute: 0 stHour: 5 stDOM: * stMonth: * stDOW: 1-5 stIsGroup: stGroupHostID: 49 stImageID: 0 stShutDown: stOther1: stOther2: -1 stOther3: fog stOther4: 1 stOther5: stDateTime: 0 stActive: 1 *************************** 2. row *************************** stID: 5 stName: Single Snapin Task stDesc: stType: S stTaskTypeID: 13 stMinute: stHour: stDOM: stMonth: stDOW: stIsGroup: stGroupHostID: 36 stImageID: 0 stShutDown: stOther1: stOther2: 13 stOther3: fog stOther4: stOther5: stDateTime: 1618063200 stActive: 0 2 rows in set (0.001 sec) -
RE: Daily wake-up routine not working after updateposted in FOG Problems
MariaDB [fog]> SELECT * FROM powerManagement LIMIT 1 \G *************************** 1. row *************************** pmID: 1 pmHostID: 14 pmMin: 0 pmHour: 6 pmDom: 1-5 pmMonth: * pmDow: * pmAction: wol pmOndemand: 0 1 row in set (0.000 sec)So it looks like I mixed up dow & dom, explaining the May 1 schedule. It showed a scheduled start time of 2021-05-03 06:15.
I deleted the entry from tasks > scheduled tasks, but it still returns the above. What’s the best way to purge this? -
RE: Daily wake-up routine not working after updateposted in FOG Problems
@tom-elliott Looks like the time/date is still confused:
[04-30-21 8:06:09 am] * 21 tasks found. [04-30-21 8:06:09 am] * 1 scheduled task(s) to run. [04-30-21 8:06:09 am] * 20 power management task(s) to run. [04-30-21 8:06:09 am] * Scheduled Task run time: Mon, 03 May 2021 06:15:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1620040500 [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:06:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:06:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * 21 tasks found. [04-30-21 8:07:09 am] * 1 scheduled task(s) to run. [04-30-21 8:07:09 am] * 20 power management task(s) to run. [04-30-21 8:07:09 am] * Scheduled Task run time: Mon, 03 May 2021 06:15:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1620040500 [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. [04-30-21 8:07:09 am] * Power Management Task run time: Sat, 01 May 2021 06:00:00 -0500 [04-30-21 8:07:09 am] * This is a cron style task that should run at: 1619866800. -
RE: Daily wake-up routine not working after updateposted in FOG Problems
@tom-elliott I just meant that before whatever caused the wake-up task(s) to stop (presumably an update prior to mid-March), I also did not have the FOG timezone set, and it was waking them up at the expected time. Which is kinda weird when I think about it…maybe it was waking them up five hours early? No one would have noticed if it was.