FOG Hangouts group

Greg Plamondon

I switched back to the dev-branch because fearing there may be a schema mismatch, but i still have the same issues with all the services being globally disabled.

Fogsnapinrep.log
[02-25-26 2:44:26 pm] Interface Ready with IP Address: x.x.x.x
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 10fogserver
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.0.1
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.1.1
[02-25-26 2:44:26 pm] * Starting SnapinReplicator Service
[02-25-26 2:44:26 pm] * Checking for new items every 600 seconds
[02-25-26 2:44:26 pm] * Starting service loop
[02-25-26 2:44:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:44:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:44:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:54:26 pm] * * Snapin replication is globally disabled
[02-25-26 2:54:26 pm] | Sleep time has changed to seconds
[02-25-26 3:04:26 pm] * * Snapin replication is globally disabled
[02-25-26 3:04:26 pm] | Sleep time has changed to seconds

fogreplicator.log
[02-25-26 2:44:26 pm] Interface Ready with IP Address: x.x.x.x
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 10fogserver
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.0.1
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.1.1
[02-25-26 2:44:26 pm] * Starting ImageReplicator Service
[02-25-26 2:44:26 pm] * Checking for new items every 600 seconds
[02-25-26 2:44:26 pm] * Starting service loop
[02-25-26 2:44:26 pm] * * Image replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:44:26 pm] * * Image replication is globally disabled
[02-25-26 2:44:26 pm] * * Image replication is globally disabled
[02-25-26 2:44:26 pm] | Sleep time has changed to seconds
[02-25-26 2:54:26 pm] * * Image replication is globally disabled
[02-25-26 2:54:26 pm] | Sleep time has changed to seconds
[02-25-26 3:04:26 pm] * * Image replication is globally disabled
[02-25-26 3:04:26 pm] | Sleep time has changed to seconds

fogscheduler.log
[02-25-26 2:44:26 pm] Interface Ready with IP Address: x.x.x.x
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 10fogserver
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.0.1
[02-25-26 2:44:26 pm] Interface Ready with IP Address: 127.0.1.1
[02-25-26 2:44:26 pm] * Starting TaskScheduler Service
[02-25-26 2:44:26 pm] * Checking for new items every 60 seconds
[02-25-26 2:44:26 pm] * Starting service loop
[02-25-26 2:44:26 pm] * No tasks found!
[02-25-26 2:45:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:45:26 pm] | Sleep time has changed to seconds
[02-25-26 2:46:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:46:26 pm] | Sleep time has changed to seconds
[02-25-26 2:47:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:47:26 pm] | Sleep time has changed to seconds
[02-25-26 2:48:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:48:26 pm] | Sleep time has changed to seconds
[02-25-26 2:49:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:49:26 pm] | Sleep time has changed to seconds
[02-25-26 2:50:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:50:26 pm] | Sleep time has changed to seconds
[02-25-26 2:51:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:51:26 pm] | Sleep time has changed to seconds
[02-25-26 2:52:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:52:26 pm] | Sleep time has changed to seconds
[02-25-26 2:53:26 pm] * Task Scheduler is globally disabled
[02-25-26 2:53:26 pm] | Sleep time has changed to seconds
[02-25-26 2:54:26 pm] * Task Scheduler is globally disabled

The same for these logs as well.
fogimagesize.log
fogsnapinhash.log
fogsnapinrep.log
pinghost.log

I have checked the mysql DB

SELECT settingID, settingKey, settingValue
FROM globalSettings
WHERE settingKey LIKE '%ENABLED%';

"settingID"	"settingKey"	"settingValue"
"33"	"FOG_CLIENT_DIRECTORYCLEANER_ENABLED"	"0"
"35"	"FOG_CLIENT_USERCLEANUP_ENABLED"	"0"
"36"	"FOG_CLIENT_GREENFOG_ENABLED"	"0"
"37"	"FOG_CLIENT_AUTOLOGOFF_ENABLED"	"0"
"38"	"FOG_CLIENT_DISPLAYMANAGER_ENABLED"	"0"
"45"	"FOG_CLIENT_HOSTNAMECHANGER_ENABLED"	"1"
"46"	"FOG_CLIENT_SNAPIN_ENABLED"	"1"
"48"	"FOG_CLIENT_CLIENTUPDATER_ENABLED"	"0"
"49"	"FOG_CLIENT_HOSTREGISTER_ENABLED"	"1"
"50"	"FOG_CLIENT_PRINTERMANAGER_ENABLED"	"0"
"51"	"FOG_CLIENT_TASKREBOOT_ENABLED"	"1"
"52"	"FOG_CLIENT_USERTRACKER_ENABLED"	"1"
"58"	"FOG_PLUGINSYS_ENABLED"	"1"
"121"	"FOG_REGISTRATION_ENABLED"	"1"
"156"	"FOG_CLIENT_POWERMANAGEMENT_ENABLED"	"1"
"174"	"IMAGEREPLICATORGLOBALENABLED"	"1"
"175"	"SNAPINREPLICATORGLOBALENABLED"	"1"
"176"	"SNAPINHASHGLOBALENABLED"	"1"
"177"	"PINGHOSTGLOBALENABLED"	"1"
"178"	"SCHEDULERGLOBALENABLED"	"1"
"179"	"MULTICASTGLOBALENABLED"	"1"
"182"	"IMAGESIZEGLOBALENABLED"	"1"
"187"	"FOG_TASKING_ADV_SHUTDOWN_ENABLED"	"0"
"188"	"FOG_TASKING_ADV_WOL_ENABLED"	"1"
"189"	"FOG_TASKING_ADV_DEBUG_ENABLED"	"0"
"190"	"FOG_API_ENABLED"	"1"
"197"	"FOG_SNAPIN_LOCATION_SEND_ENABLED"	"1"
"200"	"FOG_REPLICATOR_GLOBAL_ENABLED"	"1"
"201"	"FOG_SNAPINREPLICATOR_GLOBAL_ENABLED"	"1"
"203"	"FOG_TASK_SCHEDULER_ENABLED"	"1"

Any hepl would greatly be appreciated…
Thanks!
P.S. I am not apposed to restarting from scratch as long as i can save my snapins and images.

Greg Plamondon

@Tom-Elliott
That may be my problem Tom. I switched to the Stable build, I may have inconsistant DB schema between the two?
The GUI says I am on Version 1.5.10.1763

hammerc807

Hello,

I’ve ran into a problem. When upgrading from Debian 12 to Debian 13 I no longer can get to the webpage for fog. I get a 503 service unavailable. After seeing that I decided to re-run the installer to see if that would help but then I get the following dependency conflicts and was wondering if anyone has ran into this yet with Debian 13 Trixie.

The following information may help to resolve the situation:

The following packages have unmet dependencies:
systemd-sysv : Conflicts: initscripts but 3.14-4 is to be installed
Conflicts: insserv but 1.26.0-1 is to be installed
Conflicts: startpar but 0.66-1 is to be installed
Conflicts: sysv-rc but 3.14-4 is to be installed
Conflicts: sysvinit-core but 3.14-4 is to be installed
sysvinit-core : Conflicts: systemd-sysv but 257.9-1~deb13u1 is to be installed
Recommends: orphan-sysvinit-scripts but it is not going to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: The following information from --solver 3.0 may provide additional context:
Unable to satisfy dependencies. Reached two conflicting decisions:

sysvinit-core:amd64 is not selected for install because:
1. systemd-sysv:amd64 is selected for install
2. systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2
  [selected systemd-sysv:amd64=257.9-1~deb13u1 for install]
3. sysvinit-core:amd64 Conflicts systemd-sysv
  [selected systemd-sysv:amd64=257.9-1~deb13u1]
  For context, additional choices that could not be installed:
- In systemd-sysv:amd64 is available in versions 257.9-1~deb13u1, 257.8-1~deb13u2:
  - systemd-sysv:amd64=257.8-1~deb13u2 is not selected for install
sysvinit-core:amd64 is selected for install because:
1. sysv-rc-conf:amd64=0.99-10 is selected for install
2. sysv-rc-conf:amd64 Depends sysvinit-core

Greg Plamondon

Unfortunately, HTTP boot still requires a dhcp server.

JJ Fullmer

@CanadienITGuy Just for your and anyone’s fyi the autoexec.ipxe... Not Found is not an error. It’s more of an info message than a warning or error.
I actually have tested adding an autoexec.ipxe, even just an empty file to remove that message but even an empty file or a file that is even just a symlink or copy/paste of our normal ipxe/boot menu files causes things to break in the process.
The autoexec.ipxe is meant for adding customization to the ipxe process without needing to re-build the ipxe binary. But my testing with it within the fog workflow was that it’s best to just let that message exist and to see it as it being not found means the process will not be altered from your expected Fog ipxe workflow

rogalskij

@george1421 Thank you for this suggestion. This disabling of “fastboot” worked PERFECTLY! I interrupted the OOBE with Shift + F10 and got the command line window. I shutdown using the “shutdown.exe -s -t 0” command you suggested. Then after booting up, the FOG capture task I had already started took over and it captured 100% as it should have.

Essentially, I had forgotten to disable fastboot like I normally do on EVERY computer I have. So when it “rebooted” it technically wasn’t rebooting the device since fastboot is a misguided absurd hibernation feature Microsoft developed. The error I got was nearly identical to the one in the original post.

Thanks so much for this suggestion George and all!

JJ Fullmer

@siarkowski I believe I have found the cause of this.
A while back, right after the version you reverted too, we added an improved queueing system which is working perfectly in 1.6. However when we ported it backwards into 1.5.10.x I made a simple syntax error (the wrong $task->id vs $task->get('id') ). I have fixed this in the latest dev-branch.

This should also greatly improve the experience of the imaging task queue (see also https://github.com/FOGProject/fogproject/issues/736 and https://github.com/FOGProject/fogproject/issues/691) I thought I also wrote a post somewhere in the forum walking through the updated process that fixed some longstanding date math issues, but I can’t find that now.

Point being, if you would be so kind as to update to the latest dev-branch version and see if it fixes the issue, that would be very helpful.

JJ Fullmer

@eliaspereira This should be fully fixed in the stable release of 1.5.10.x coming on the 15th of this month and in the dev-branch as of now.
I thought it was already fixed back in September, and it has been working in 1.6 since then but we just got a report of a related issue here https://forums.fogproject.org/topic/18081 which I believe I just fixed.

JJ Fullmer

@tian @DBailey635 @eliaspereira Apologies for missing this post. This was fixed in August-ish of last year, see also:
https://github.com/FOGProject/fogproject/issues/736

I found this searching for a post I wrote about it, as I’m pushing another fix for this for a bug just found in 1.5.10.x

If you update to the latest dev-branch (or what will be stable on the 15th of this month) or give the working-1.6 branch aka 1.6-beta a try, you’ll find the queuing problems fixed.

JJ Fullmer

@bond007fink @jayrehme
By “Latest Update” do you mean the December updates for Win 11 or do you mean the latest release version of 25H2 ? I haven’t tested 25H2 yet.

J	Joe Schmitt
G	Greg Plamondon
S	soscrafts01
O	oelked
M	Mr_____T
B	broodbaron
R	rcalayan
H	hammerc807
D	dyacishyn
L	lukebarone
M	Melisa
Y	yushin
B	brechtvervaeke
A	abasto
E	emreonder
R	rogalskij
M	mkoliva15
C	carltoncortez
A	alvin.bayani
K	kguevarra

FOG Hangouts

Posts

Member List