Latest FOG 0.33b
-
jbscim,
I am aware that there are issues in the task management page. I added those menu options there for familiarity sake, yet I haven’t actually “fixed” the coding to make them actually work. The TasksManagementPage does not have a deploy_post method introduced yet, but the link is still trying to reference that. The link should be along the lines of ?nodes=group&sub=deploy-post, but right now it’s set something like ?nodes=tasks&sub=deploy-post, which is why you’re seeing the errors.
RIght now I’m trying to get Multicast working. So my mind isn’t fully vested into the task management page issues. I hope this is understandable, those errors are relatively simple to fix. Right now Multicast doesn’t even sort of work, so I hope you understand my focus right now.
-
I completely understand, your work is much appreciated. I’m happy to help where I can.
John -
It, from all appearances, I have gotten Multicast Tasks working finally.
At least from the individual standpoint.
r1102 has this all set. Also, progress information displays on multicast and under the active multicast tasks list.
It’s not perfect, but it is, for now, somewhat operational.
-
r1103 released.
Fixed the links in the TaskManagementPage so they, seemingly, work properly now.
Multicast now works, as far as I can tell, properly. Groups, Host, and from the Task page.
Will work on updating Capone to use the classes I’ve created.
-
Found an issue in the MulticastTask in that it never stores or gets the PID of the process being created. Maybe somebody can help?
-
r1105 released. Doesn’t fix the pid issue yet, but has capone using class based methods. @jbscim, I kept osID field in capone, but it doesn’t reference off of hostOS, it references off of images.osID. All other changes (-i removed from fog.capone) updated init.gz and buildroot script, have been implemented.
-
r1106 released. Fixes an issue where an individual host multicast task creates two jobs.
-
I think its about time to do another write up of the things I’ve fixed/added/modified so we have a working inventory of what’s been performed. It will take a little while as I don’t remember everything that I’ve done since the beginning. I’ll be working off of a sort of TODO list and if there’s anything I’ve missed so far, please let me know.
Thank you,
-
[quote=“VincentJ, post: 21362, member: 8935”]Any word on the early hostname change for windows 7 or the client being made to change the hostname again?
(Been a couple of weeks since my last test so a bit out dated.)[/quote]Just an update I got host name changer to work… also my images are working successfully. but hostname changer only works for me after the image and not before. It even changes the name on the computer if the name in the database is changed.
But I do have a question for you Tom, When trying to do a memtest from fog I get the following error “cannot load ramdisk with an old kernel image” and also when doing a hard drive surface test it says checking for bad blocks (red-only test): but does not look like its going any where I have been waiting an hour so far and nothing…
-
That doesn’t make sense to me. I haven’t had any issues running memtest on my systems. I use it to quickly restart my VM’s as they’re running from virtualbox. it’s quicker to (from the menu) choose memtest then right when it starts, press escape to restart for. I’ve never seen that error. That said, it makes me wonder how old your memtest kernel is as it shouldn’t be creating a ramdisk anyway, that I’m aware of. memtest is it’s own utility to my understanding.
You say you got hostname changer to work, was there any steps for this or did it just start working?
I’ve tested, slightly, with testdisk surface test, but not much. It appeared to work fine to me, so I just let be. I’ll do more testing.
-
Multicast Tasks, Works. Seemingly it works properly now. Will try to add element to kill/recreate task if another host with the same image tries to startup. However I haven’t a clear plan on how to implement that, so may have to wait for a little.
Services (FOG Settings) settings are now called by class based methods over the old MySQL style requests. It’s still sql based, but uses the classes as I imagine is supposed to be the intent.
ClientServiceManager uses more classed based methods.
Snapin Deploy works, only from host/group deploy for now. Will work on Task Host/Group deploy elements, may just remove the snapin parts from them entirely. They work, but either one or the other will always deploy all snapins associated with the particular host.
WakeOnLan works.
Host Performs much of the image/task needs now. I think this is appropriate as it’s ultimately the hosts doing the tasks anyway.
Service scripts (fogwebdir/service) now falls more in line with class based elements as well. Less need to call database. Not all scripts are done yet, but still working as I can. blame.php, man.hostexists.php, auto.register.php, oslisting.php, imagelisting.php, Post_Wipe.php, usercleanup-users.php, updates.php, inventory.php, auto.delete.php, PrinterManager.php, snapins.file.php, dircleanup-dirs.php, displaymanager.php, hostname.php, hostlookupbymac.php, av.php, debug.php, alo-bg.php, Post_Stage2.php, progress.php, Pre_Stage1.php, mc_checkin.php, Post_Stage3.php, and capone.php that I can find.
Groups have ability to add hosts, Hosts can join to groups.
Configuration Save (export/import) features. This basically just saves the fog database, as I don’t imagine much else needs to be stored. That’s not to day I shouldn’t, at the least, work on getting the fogwebdir/commons/config.php .fogsettings and /opt/fog/service/etc/config.php, but I don’t know the best route for that yet. SORRY!
Capone now uses more refined methods. Basically the same as the old, but uses classes where possible.
That’s all I can think of for now. What else is needed?
-
[quote=“Tom Elliott, post: 21557, member: 7271”]That doesn’t make sense to me. I haven’t had any issues running memtest on my systems. I use it to quickly restart my VM’s as they’re running from virtualbox. it’s quicker to (from the menu) choose memtest then right when it starts, press escape to restart for. I’ve never seen that error. That said, it makes me wonder how old your memtest kernel is as it shouldn’t be creating a ramdisk anyway, that I’m aware of. memtest is it’s own utility to my understanding.
You say you got hostname changer to work, was there any steps for this or did it just start working?
I’ve tested, slightly, with testdisk surface test, but not much. It appeared to work fine to me, so I just let be. I’ll do more testing.[/quote]
Ok so I figured out the memtest thing if you do it from the PXE boot menu it works, but if you deplay it from a basic task it gives you the error I told you about. Also for the host name changer I think I just had to encrypt my password in fog… but thats just what I remeber. I have to build another server so I will go through my steps again and report everything I did to get it working. I am trying the surface test in a VM as of now and it says…
[QUOTE]
Starting Disk Surface Test on
/dev/sdaChecking blocks 0 to 62914559
Checking for bad blocks (read-only test):
[/QUOTE]but it just stopps there the blocks does not increase or anything.
And the last thing under Active Snapins I am getting this
[QUOTE]
FOG ERROR: Snapin: Record not found, Error: No data array or ID passed!
FOG ERROR: Host: Record not found, Error: No data array or ID passed!
FOG ERROR: Host: Record not found, Error: No data array or ID passed!
FOG ERROR: Snapin: Record not found, Error: No data array or ID passed!
FOG ERROR: Host: Record not found, Error: No data array or ID passed!
FOG ERROR: Host: Record not found, Error: No data array or ID passed!
FOG ERROR: Snapin: Record not found, Error: No data array or ID passed!
FOG ERROR: Host: Record not found, Error: No data array or ID passed!
FOG ERROR: Host: Record not found, Error: No data array or ID passed
[/QUOTE] -
I’m not seeing an issue with Snapins. What revision are you on? What steps can I do to get the same results?
Fixed the memtest issue. It’s due to the fact the ramdisk option is being set. Remember, none of the task associations were setup so something where missed. I just corrected the memdisk issue by, basically, keeping the append options off. I’ll post the revision shortly.
I imagine this same issue is what we’re seeing on surface checks, and possibly, other task types as well. I’ll have to dedicate time to each one to get each one working properly.
-
During testing, it seems like badblocks is being checked. I performed the same tasks that are performed on the system during this particular task and killed the task just to see if I’d get any info.
Don’t forget, this surface test performs the surface test from each block on the system, so I expect that it would take it a while to perform. I didn’t write the program, but it looks like there is a progress indicator. I’ll add that to the fog.surfacetest script. and post in a moment.Hopefully this two items (from a tasking standpoint) will work for you now.
-
r1109 released. Should add progress information for surfacetest as well as perform checkin on the task. I’ll work on implementing more checkins. The one I can’t is the memtest task as it never loads anything where you have a console.
-
[quote=“Tom Elliott, post: 21562, member: 7271”]r1109 released. Should add progress information for surfacetest as well as perform checkin on the task. I’ll work on implementing more checkins. The one I can’t is the memtest task as it never loads anything where you have a console.[/quote]
Thanks I will try it what is the easist way to check the revision I just did an update this morning so I know it is recent. I just was testing pusing out some snapins and it says successfully deployed, but then on the client side it says it has an image task waiting so I have to cancel the task under active task and usually they deploy but now its giving me that error instead.
I am thinking a task is corrupt in the database is there anyway to go in and clear out all task that may be pending?
-
I think you need to delete all tasks with a stateID of 1,2,3
Something like
DELETE FROM tasks WHERE taskStateID IN (‘1’,‘2’,‘3’);Then delete the 01- files relating to those tasks.
-
To check which revision you’re at, I’m assuming you’re using SVN?
From the trunk folder perform:
[code]svn info | grep “Revision” | awk ‘{print $2}’[/code] -
[quote=“Tom Elliott, post: 21564, member: 7271”]I think you need to delete all tasks with a stateID of 1,2,3
Something like
DELETE FROM tasks WHERE taskStateID IN (‘1’,‘2’,‘3’);Then delete the 01- files relating to those tasks.[/quote]
I am still having issues its not in active task though it is in snapin task I am uploading a pdf (screenshot) of the issue).
[url=“/_imported_xf_attachments/0/499_Active Snapins _ Task Management _ FOG _ Open Source Computer Cloning Solution.pdf?:”]Active Snapins _ Task Management _ FOG _ Open Source Computer Cloning Solution.pdf[/url]
-
[quote=“Troye Johnson, post: 21566, member: 3048”]I am still having issues its not in active task though it is in snapin task I am uploading a pdf (screenshot) of the issue).[/quote]
Also I was on 1097 when this occurred.
