Scheduled tasks are not starting in FOG 1.2.0
-
Added some errors from apache error log
-
Am I the only one having this problem? This is super frustrating and i’m not sure where to look to start fixing this.
-
I’m having the same problem, I’ve just updated to the last SVN version but it hasn’t solve it
-
What is SVN? How do you update ?
-
[quote=“Axel, post: 40814, member: 686”]What is SVN? How do you update ?[/quote]
-
‘trunk’ is the proper name for the “lastest” release. SVN is a service that helps deploy the ‘trunk’ and is an easy way to get the most up-to-date ‘trunk’ of fog.
[url]http://www.fogproject.org/wiki/index.php/Upgrade_to_trunk[/url]
-
Did you ever get this fixed? I recently reverted to the 1.2 release and the only thing NOT working is scheduled tasks.
Appreciate knowing the fix, thanks.
-
I don’t know if I can say its 100% fixed, but its temperamental for me at best. We use FOG as part of our backup solution by uploading images so we can download them back to bare-metal in a hard drive failure. I know this isn’t exactly what FOG was meant to do…but it does it and it works for us. I’ve found that adding some system restart instructions to rc.local has helped to keep fog services,mysql, apache all running. I’ve recently started using cron tasks and they were not working but that was because they were particular with the syntax (and it was my first time messing with cron tasks anyways.
What OS are you using for fog? in Ubuntu server 12 we have to change some date/time entry in a couple of php files.
-
Ubuntu 12.04 Fog 1.2.
What PHP files? It takes the task, but never moves them to active.
-
@NT_Tech, can you upgrade back to trunk?
There are likely some things that have been fixed and many more things I KNOW have been fixed.
I’d really prefer to work out the kinks in it. I know there was a period where things were all out of wack, but I’m ready to say those things are hopefully long gone. There may be a few kwirks here and there, but I can’t fix what I don’t know about.
-
My assistant thinks I would be nuts to try trunk again! We just rebuilt every image back to 1.2 base after a slew of issues with the trunk version. The ONLY thing not working for us in 1.2 is the scheduled imaging feature. Can you pinky swear to me that trunk is stable enough? And can you keep my assistant from sneaking up behind me and whacking me with a pc power supply if it isn’t?
-
[quote=“NT_Tech, post: 47402, member: 27178”]My assistant thinks I would be nuts to try trunk again! We just rebuilt every image back to 1.2 base after a slew of issues with the trunk version. The ONLY thing not working for us in 1.2 is the scheduled imaging feature. Can you pinky swear to me that trunk is stable enough? And can you keep my assistant from sneaking up behind me and whacking me with a pc power supply if it isn’t?[/quote]
I probably can’t keep your assistant from sneaking up behind you. I know that it is stable enough, though I’m not going to guarantee there aren’t ANY issues. The issues I was absolutely aware of (image upload resizing, boot up problems, etc…), but again I don’t know if every single facet of issue that was faced is now fixed. i won’t know until somebody who was having these problems is able to test.
Rather than upgrade your production to trunk, maybe a test environment could be used?
-
i can give you instructions on how to redirect a specific computer or two to the test server without effecting your production server’s operation
-
[quote=“Junkhacker, post: 47412, member: 21583”]i can give you instructions on how to redirect a specific computer or two to the test server without effecting your production server’s operation[/quote]
Go ahead and spill the beans.
-
edit the default.ipxe file in the root of your tftpboot directory with these kinds of edits
[CODE]#!ipxe
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac0 ${net0/mac}
param arch ${arch}
param product ${product}
param manufacturer ${product}
param ipxever ${version}
param filename ${filename}
isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme
isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme:bootme
redirected to dev server for testing
##redirect by serial number
iseq ${serial} <host-serial> && chain http://<alternate-fog-server>/fog/service/ipxe/boot.php##params ||
##redirect by mac address
iseq ${net0/mac} <mac-address-for-host> && chain http://<alternate-fog-server>/fog/service/ipxe/boot.php##params ||
##redirect all efi systems
iseq ${platform} efi && chain http://<alternate-fog-server>/fog/service/ipxe/boot.php##params ||normal fog server
chain http://<main-fog-server>/fog/service/ipxe/boot.php##params
[/CODE] -
So literally you just put in the host serial and mac address and the dev server’s IP and that’s it?
That’s pretty sweet, I gotta say.
-
[quote=“Wayne Workman, post: 47472, member: 28155”]So literally you just put in the host serial and mac address and the dev server’s IP and that’s it?
That’s pretty sweet, I gotta say.[/quote]
yep, that’s all you have to do
