Bugs in FOG 0.33
-
dag’s repo typically install clamav and freshclam in different locations that the elrepo packages. At least when I’ve had to play with my mailserver clamav setup!
-
I’ve uploaded a new revision to try addressing these issues. I don’t know if it’s all fixed, but the rpcbind/nfs issue should be now!
-
[quote=“Tom Elliott, post: 18435, member: 7271”]I’ve uploaded a new revision to try addressing these issues. I don’t know if it’s all fixed, but the rpcbind/nfs issue should be now![/quote]
Thanks, works now except one: line 288 setupFreshClam: command not found on Centos 6.4 and elrepo defined.
-
for htmldoc, install rpmforge repo. I installed on clean install of centos 6.4 and had no issue.
-
[quote=“pmonstad, post: 18432, member: 17422”]Chinese language?? After installing (testing user interface) most menues seams to appear in Chinese language? Why, I have not entered any setting about this?[/quote]
You can choose the locale to use on the login screen, maybe it has the wrong one selected?
-
Hi!
This may not be a bug as such, but more of a request for help on a Windows 8 deployment issue I’m having in fog 0.33 during testing. Hope that’s ok!
I have successfully uploaded an image of a Windows 8 laptop (disabled secure boot and changed to legacy BIOS before upload), however I swap out the hard drive for a brand new blank disk, but when i deploy the image (again, secure boot disabled and legacy BIOS) the task completes instantly following the ‘Checking Hard Disks’ section of the deploy process. It passes the ‘Restoring MBR’ section, then passes the ‘Checking Hard Disks’ section and comes back with ‘Task Completed’ instantly, no image progress screen.
I’m guessing this is because the new disk is not pre formatted/partitioned, but i assumed FOG would take care of that from the existing image that i uploaded?
Can anyone please confirm for me?
Many Thanks
LA -
I’ve not, fully, tested Windows 8 and imaging yet, but I would venture to guess you’re saying the drive has never been initialized quite yet. What revision of FOG are you working with? Is it a partimage or partclone setup?
I ask because I’ve had to make a few changes to how the partitions are created, and it sounds like it’s failing in creating the partitions when it needs to.
Everything I’ve tested with many of the latest changes seems to have worked well, but I have not quite yet gotten to test Windows 8, which I’m sorry.
-
I am using fog0.33b latest build as far as I know ( not sure how to check through) I have manged to upload a windows 8 image , using legacy boot devices, and have then deployed that image to another pc, worked ok. however each time I deploy an image after the partclone bit the the pc updates database , get cat:co.txt:no such file or directory…followed repeatedly by no active task found for host…( attached image) also I dont believe multicast is working with 0.33b , any update or help with any of these issues would be appriciated , thanks everyone !!
[url=“/_imported_xf_attachments/0/475_20140110_131704_resized.jpg?:”]20140110_131704_resized.jpg[/url]
-
Correct - brand new drive that hasn’t been initialized. Working on FOG rev 1016, so I can upgrade to latest revision and try that if there have been fixes with partitioning since. Will give that a go and let you know.
Thanks!
LA -
That would be awesome, I’ve made quite a few discoveries/changes since then.
Please try updating, 1080 - 1083 had a few changes (1080 had a typo, 1081 had a space where it shouldn’t be, 1082, found another misstep on my part, 1083, added a few more quick changes.)
-
Still the same after update to revision 1083 unfortunately. Skips the partimage process and goes to task complete. I have been trying to find which file deals with the partitioning but unsure.
Thanks
LA -
/bin/fog in the init.gz file.
-
Thanks Tom, I have updated to r1083, imaged pc.s no longer hang on no active task found for host…, and pc reboots after image getts deployed. Multicasting does not work yet, , many Thanks again for your help, trying to learn and understand fog better and hopefully can one day help contribute…THanks
-
forgot to add, the issue seen when trying to multicast is that pc.s in the group stay on screen display partclone, but they never start,
see attached image, incase its of any help to anyone. Thanks[url=“/_imported_xf_attachments/0/476_partclone.jpg?:”]partclone.jpg[/url]
-
I have not written the code yet, and neither did Blackout, for Multicast. I’m aware that creating a multicast task fails at the moment. I have just been trying to get everything else working more fluidly.
-
Denis,
Keep it on that screen and give me a printout of the /var/log/httpd/error_log or /var/log/apache2/error.log file.
-
Hi Tom, below are messages seen in /var/log/apache2/error.log file
Let me know if you need the whole file, thanks
[Fri Jan 10 17:09:00 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:10 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:11 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:13 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:15 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:17 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:19 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:21 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:23 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:25 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:27 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:29 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:31 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url]
[Fri Jan 10 17:09:33 2014] [error] [client 10.10.6.31] PHP Notice: Constant WEB_ROOT already defined in /var/www/fog/commons/config.php on line 92, referer: [url]http://10.10.6.97/fog/management/index.php?node=home[/url] -
If you update to the latest and greatest of fog, the already defined messages should stop.
Other than that, based on what you’ve provided here, I don’t see anything that’s useful yet.
-
Tom,
Just had a look into to bin/fog and found the section relating to the image type I’m using (mps), the process seems to be failing at some point between these commands when imaging to a blank HDD. I’ve attached the relevant section in a text file for you.
My guess is at lines 32 to 42 in the attached, unless Partprobe cannot read the partition table on line 28 (though ‘Checking hard disks’ returns ‘Done’). It seems to skip everything after line 30 right down to line 89 for ‘Task Complete’.
Can you see anything that would prevent the blank HDD from being partitioned correctly? I’m at a loss currently!
Thanks
LA[url=“/_imported_xf_attachments/0/478_fog_mps.txt?:”]fog_mps.txt[/url]
-
Luke,
What are you trying to image? Linux/Windows? I ask because the lines you seem to be referencing look to be for linux OS’s. If this is the case, then I’d recommend doing a debug mode and actually creating a temporary partitioning scheme for your Hard disk.
What I mean by this, is, though it typically creates the partitions for you, sometimes uninitialized drives are completely uninitialized. This means it’s never had any type of partitioning table and FOG can’t recognize the drive in even it’s simplest of forms.
Typically drives that are initialized with even the most simple of data, (a simple
[code]fdisk /dev/sda >> EOF
m
p
1
+100M
m
p
2+3000M
t
1
7
a
1
w
EOF[/code]While this may look tricky, it really is simple. All it does is create the 100M 1st partition (win 7) and creates a second partion with 3GB. It will be overwritten when FOG starts its imaging process. This also sets the 1st partition as the bootable section as well. Though I doubt we need that fine of adjustments. The fogpartinfo, as far as I can tell, can’t tell what the drive partitions are and fails because of this. It’s simple because the drive can’t give any information appropriately to the program and fails miserably.
Give these steps a shot, and let me know how it works. If it works, I’ll try to add it to the codebase so we don’t have this issue any more.
Will generally do the trick to allow FOG to write to the drive with little issue. I suppose
