Bugs in FOG 0.33
-
I just pulled the latest SVN and was able to confirm the blank loading. With display_errors = On in php.ini:
[CODE]Warning: call_user_method_array() expects exactly 3 parameters, 2 given in /var/www/fog/lib/fog/FOGPageManager.class.php on line 133 [/CODE]
Loads directly below the Dashboard header. -
[quote=“astrouga, post: 3489, member: 907”]
I fixed it by changing the line to:
call_user_method_array($method, $class,array($args));
Now the pages are displaying properly.
[/QUOTE]After the change above, I only had one issue more issue. It is possible that others won’t experience it, but I’ll mention it anyway. The first host I added got an hostID=0 in the hosts table. Every time I tried to do anything Fog spit back an error about the ID being “0”. I wasn’t able to add any more hosts or upload/download an image until I manually changed the ID to “1” in the hosts table. Then everything worked.
Imaging of a Windows 7 disk “multiple partition image - single disk (not resizeable)” worked like a charm. I imaged a Dell Latitude D830. Image uploaded fine, client rebooted properly, task was removed. Download was fine, client rebooted, task removed. Also, for some reason, all of the speed issues I was encountering disappeared. Everything worked better than it ever has in our environment. I’ll have to test a desktop or two and see if everything is OK.
This is real progress. Thanks for the work.
–astrouga
-
While testing 0.33 you should have the following in your ‘php.ini’
error_reporting = E_ALL & ~E_NOTICE & ~E_DEPRECATED
display_errors = OnI have fixed the call_user_method_array() issue.
872
- FOGPageManager: render(): Replaced deprecated call_user_method_array() call with call_user_func() - dropped argument pass as PHP Strict was throwing errors if the FOGPage class did not expect the $argument - $this->arguments is accessible in FOGPageManager but should not be required
- schemaupdater: Fixed wrong field type on Task State name field - this fixes ‘state’ icons no showing correctly - need to write a better schema updater to sync my dev server with svn
-
I looked into the ID issue but i could not replicate it. I tested emptying my Hosts table and creating a new host via the GUI.
This worked as intended giving the first host an ID of 1. I have no tested this on a fresh install, but it did work as intended as of ~860How did you add the host? Via the GUI or another means?
Great to hear it’s all working well. The latest tools provide a good performance boost by properly aligning drive sectors.
Windows XP has some issues with the aligning etc as it’s installer still uses start sector 63.
If someone could test an NTFS re sizable image for Windows 7 that would help a lot.
-
[quote=“Blackout, post: 3538, member: 1”]@astrouga
I looked into the ID issue but i could not replicate it. I tested emptying my Hosts table and creating a new host via the GUI.
This worked as intended giving the first host an ID of 1. I have no tested this on a fresh install, but it did work as intended as of ~860How did you add the host? Via the GUI or another means?
[/quote]
I used the gui. It was strange because I added a host, then pulled an image from the host to the server. When I went to add another host, it over-wrote my first host. I didn’t realize this at first, but this is when I started seeing the ID issue. I’ll load 872 and see if I can reproduce.[quote]
If someone could test an NTFS re sizable image for Windows 7 that would help a lot.[/quote]I’ll give this a go too. I tried it on 871, and the imaging process seemed to work, but the host I downloaded the image to did not boot. I’ll pay closer attention on the next test.
-astrouga
-
Blackout:
Can you give us your recommended setting for a Windows 7 image? Specifically, for testing purposes, should I keep the 100MB Windows partition on my Windows 7 images and set OS to “windows 7”? If I don’t keep the 100MB partition, do I need to change the OS setting for the host to “vista”? I hadn’t heard this before, but it was mentioned here:
[url]http://fogproject.org/forum/threads/windows-7-no-100mb-partition.670/[/url]
I’d just like to make sure that we are on the same page so that my feedback is useful to you.
Thanks,
–astrouga
-
Just did a clean install of trunk 872 on Ubuntu 12.04.
During the initial “Database Scheme Installer/Updater” you have one syntax error. It produces this error:
"The following errors occured
Update ID: 32 - 1
Database Error:
Column count doesn’t match value count at row 1
Database SQL:INSERT INTO
fog.taskStates(tsID,tsName,tsDescription) VALUES
(1, ‘Queued’, ‘Task has been created and FOG is waiting for the Host to check-in.’, ‘1’),
(2, ‘In-Progress’, ‘Host is currently Imaging.’, ‘2’),
(3, ‘Complete’, ‘Imaging has been completed.’, ‘3’);
"You left off the
tsOrdercolumn name in your INSERT statement. It should be “INSERT INTOfog.taskStates(tsID,tsName,tsDescription,tsOrder)…”I didn’t have any issues with the hostID this time.
Windows 7 64-bit (with the 100 MB system partition) imaged just fine on a Dell Optiplex 745 using the “Multiple Partition Image - Single Disk (Not Resizable)” option. I don’t ever use the single partition option, but I tried it. I imaged the same config as a “Single Parition (NTFS, Resizable)” and got a “Windows Boot Manager” screen when I download the image. A repair did not work.
–astrouga
-
[quote=“astrouga, post: 3543, member: 907”]Can you give us your recommended setting for a Windows 7 image? Specifically, for testing purposes[/quote]
If set to Multi-partition, it does not matter if there is 1 or 2 partitions.For NTFS Resizable there are checks made to determine the amount of partitions, meaning both should work.
In saying this, both will need to be tested. Personally i use 1 partition
[quote=“astrouga, post: 3557, member: 907”]Windows 7 64-bit (with the 100 MB system partition) imaged just fine on a Dell Optiplex 745 using the “Multiple Partition Image - Single Disk (Not Resizable)” option. I don’t ever use the single partition option, but I tried it. I imaged the same config as a “Single Parition (NTFS, Resizable)” and got a “Windows Boot Manager” screen when I download the image. A repair did not work.[/quote]
There are NTFS resizable deploy issues to sort out still.
Could you please test if Windows 7 works after you have Uploaded an image? (dont deploy, does it boot after uploading?)
There is resizing performed before and after the image is uploaded, knowing if the OS is still boot able means that resizing is working correctly and i have a bug in the deploy some where.
Thanks for the reporting, keep them coming! The less testing i have to do, the more development i can do
Some times i wish there was a “Microsoft frequent installer rewards program”
-
[quote=“Blackout, post: 3567, member: 1”]
In saying this, both will need to be tested. Personally i use 1 partition
[/quote]I go with 1 usually too, good to know that both are supported, as there seemed to be some confusion. Thanks for responding to that thread.
[quote]
Could you please test if Windows 7 works after you have Uploaded an image? (dont deploy, does it boot after uploading?)
[/quote]
I am sure that the machine I uploaded my image from did indeed reboot properly after the image was uploaded. I did it several times while I was testing different systems. I’ll double-check it first thing in the morning though.[quote]
Thanks for the reporting, keep them coming! The less testing i have to do, the more development i can do
Some times i wish there was a “Microsoft frequent installer rewards program” :D[/quote] I’m just glad to be helping out. The specific requests are helpful – I am learning a quite a bit about the imaging process as I go along, so it is useful stuff.Cheers,
–astrouga -
trunk 873…I ran two tests with the Single Partition (NTFS Only, Resizable) image type.
A Windows 7 host with two partitions (100 MB system and OS) seemed to work fine. Both partitions were recognized, the image uploaded and the host rebooted fine.
A Windows 7 with one partition (didn’t have the 100 MB boot partition) did not work. The process completed, but the image upload process (blue screen that shows progress status) took less than 2 seconds. The image file on the server is about 500 KB. The client did reboot successfully though.A minor bug to note: I noticed that the task status icon that shows up on the Task Management screen does not change during an image upload. It always shows “queued” even on multiple refreshes of the page. However, the status does change and appears to be correct for image downloads.
–astrouga
-
[quote=“astrouga, post: 3578, member: 907”]A Windows 7 with one partition (didn’t have the 100 MB boot partition) did not work. The process completed, but the image upload process (blue screen that shows progress status) took less than 2 seconds. The image file on the server is about 500 KB. The client did reboot successfully though.[/quote]
Could you please verify that this wasnt a file system issue by running chkdsk a few times and trying the single partition upload. I havent changed any of the Windows 7 code, so there shouldnt be any issues if 2 partition works.
[quote=“astrouga, post: 3578, member: 907”]A minor bug to note: I noticed that the task status icon that shows up on the Task Management screen does not change during an image upload. It always shows “queued” even on multiple refreshes of the page. However, the status does change and appears to be correct for image downloads.[/quote]
I will change this so the status update. In previous versions, upload tasks never checked; they never done anything really. I think this was done so upload tasks didnt take up a slot, but i have other ways around that now. (i.e. excluding upload tasks from getActiveTasks())
-
Is there anyway to force snapins to start? I still find freshly imaged machines will sit for a long time before fog starts to deploy snapins? I don’t know how often the client checks the server for updates? Or does the fog client wait for a certain time? Would be great if you could “force start” snapins to deploy, is this in 33?
-
I’ve just committed some code that will make upload tasks check-in.
-
[quote=“andyroo54, post: 3604, member: 267”]Is there anyway to force snapins to start? I still find freshly imaged machines will sit for a long time before fog starts to deploy snapins? I don’t know how often the client checks the server for updates? Or does the fog client wait for a certain time? Would be great if you could “force start” snapins to deploy, is this in 33?[/quote]
I have lowered the initial snapin client wait from ~5.5minutes - 8.3minutes to 30seconds - 60seconds.This is in the latest revision. Though you will need to check it out from SVN, compile it and distribute (the snapin clients .dll file) to your machines.
Please see [url]http://fogproject.org/forum/threads/how-to-modify-your-snapinclient-dll-file-to-check-in-more-quickly-on-a-reboot.613[/url] for more details on this.
Please keep FEATURE REQUESTS out of this thread as it is for BUG REPORTS.
-
I have installed FOG trunk 875 (Ubuntu 12.04 Server) and unable to access any Fog Configuration pages error: [CODE]FOG DEBUG: FOGPageManager: Class: FOGConfigurationPage, Method: kernel, Error: Method not found in class, defaulting to index()[/CODE]
-
[SIZE=11px]astrouga said:[/SIZE]
A Windows 7 with one partition (didn’t have the 100 MB boot partition) did not work. The process completed, but the image upload process (blue screen that shows progress status) took less than 2 seconds. The image file on the server is about 500 KB. The client did reboot successfully though.I’ve had similar problems with a window 7 single partition image. The only why I got a round it was setting the OS type to vista.
-
FOG trunk 875 (Ubuntu 12.04 Server)
windows 7 ie9/firefox as can be seen below the IMAGE NAME and actual image name overlap
[IMG]http://db.tt/eJPwkmOD[/IMG]
also just uploaded a Windows 7 Image (normal install with 100mb) with the above settings ( OS: Windows 7 || Image Type: Single Partition (resizable)) The image uploaded successfully (right size on server) and the original machine restored mbr and restarted fine.
when deploying the uploaded image to a pc it only deploys the 100mb partition says its complete and restarts
-
[quote=“Blackout, post: 3603, member: 1”]Could you please verify that this wasnt a file system issue by running chkdsk a few times and trying the single partition upload. I havent changed any of the Windows 7 code, so there shouldnt be any issues if 2 partition works.[/quote]
Trunk 875. I can’t get “Single Partition” imaging to upload. I tried two different Win7 64-bit systems with no 100MB partition. I ran chkdsk 3 to 5 times on each before attempting to upload. In both cases, the blue progress screen flashes for a fraction of a second. No file is actually written to the server. The clients reboot and come up fine.
After the failed “Single Partition” efforts, I tried imaging both systems using the “Multiple Partition - Single Disk” Option and both tasks worked perfectly. Image stored on server, client rebooted and came up OK.
Suggestions?
Thanks for making the task upload status change. It works and is useful.
–astrouga
-
Have u tried setting the OS type to Vista.
-
[quote=“Dean211, post: 3621, member: 411”]@astrouga
Have u tried setting the OS type to Vista.[/quote]Yeah, I changed the OS setting in the image definition to Vista, just to test. Blue screen flashes, like the others, except it tries to write to the images directory and fails. It spit out an ftp error. I didn’t look at it closely because though. I’ll see what it says in a bit.
UPDATE: OK, if I change the OS to Vista, things proceed as I mentioned above. Right after the “* Resizing NTFS…Done” message, I get the following messages looping:
[code]- unable to move /Images/dev/macaddress to /images/imagename
FTP Host: (server IpAddress here), Error: ftp_rename(): RNFR command failed.
[/code]
This just goes on until I manually power-cycle the client.
I think if this trick ever works, it really isn’t meant to.
–astrouga
- unable to move /Images/dev/macaddress to /images/imagename
