Latest FOG 0.33b

[Tom Elliott]

[quote=“fabritrento, post: 21609, member: 21607”]for some reasons, instead of “xxx.xxx.xxx.xx” “inet xxx.xxx.xxx.xxx” are assumed as default. I think that is taked from /etc/network/interfaces config file.

my file:
#----------------------

The loopback network interface

auto lo
iface lo inet loopback

The primary network interface

auto eth0
iface eth0 inet static
address 192.168.0.3
netmask 255.255.255.0
gateway 192.168.0.1
dns-nameservers 192.168.0.2
#----------------------[/quote]

It’s actually taken by the command:
[code]ifconfig | grep “inet addr:” | head -n 1 | cut -d’:’ -f2 | cut -d’ ’ -f1[/code]

I have a feeling, something like:
[code]ifconfig | grep “inet addr:” | head -n 1 | awk -F’:’ ‘{print $2}’|awk ‘{print $1}’[/code]

Would work better as it ensure’s the whitespace is removed, where cut only removes a single space (based on the -d’ ').

[fabritrento]

[quote=“Tom Elliott, post: 21611, member: 7271”]It’s actually taken by the command:
[code]ifconfig | grep “inet addr:” | head -n 1 | cut -d’:’ -f2 | cut -d’ ’ -f1[/code]

I have a feeling, something like:
[code]ifconfig | grep “inet addr:” | head -n 1 | awk -F’:’ ‘{print $2}’|awk ‘{print $1}’[/code]

Would work better as it ensure’s the whitespace is removed, where cut only removes a single space (based on the -d’ ').[/quote]

i have no “addr:” ifconfig output :

this works:
ifconfig | grep “inet” | head -n 1 | awk -F’:’ ‘{print $2}’|awk ‘{print $1}’

and also this:
ifconfig | grep “inet” | head -n 1 | cut -d’:’ -f2 | cut -d’ ’ -f1

[fabritrento]

first bug.

i created a image as multiple partitions, single disk.
then upload the image.

the disk has 3 partitions:
sda1 ntfs
sda2 ext4
sda3 linux_swap

but on the server only first image is upladed:

administrator@fog:/images/labciro$ ls -la
totale 6602576
drwxrwxrwx 2 root root 4096 gen 20 14:21 .
drwxrwxrwx 4 root root 4096 gen 20 14:21 …
-rwxrwxrwx 1 root root 512 gen 20 12:50 d1.mbr
-rwxrwxrwx 1 root root 6761011164 gen 20 14:20 d1p1.img
-rwxrwxrwx 1 root root 20 gen 20 14:20 d1p2.img
-rwxrwxrwx 1 root root 20 gen 20 14:21 d1p3.img
administrator@fog:/images/labciro$
the second and third is only 20 byte sized.

how i can debug more this problem?

[Tom Elliott]

How big is the ext4 partition?

[fabritrento]

Is 25-30GB (about)

[Tom Elliott]

What’s the OS type for the image being uploaded?

[fabritrento]

[quote=“Tom Elliott, post: 21625, member: 7271”]What’s the OS type for the image being uploaded?[/quote]
First partition win xp second partition linux

[Tom Elliott]

No, i mean from the image page.

You can’t assign two OS’s to the image name. If you’re trying to image a dual boot, you need to setup RAW image type versus MPS/MPA/SDR

[Troye Johnson]

Hey Tom snapins are still acting a little strange when I deploy any snapin at first it shows currectly under active task but then after a few min the task duplicates and it keeps duplicating I am attaching an screen shot.

[url=“/_imported_xf_attachments/0/501_fogerror.pdf?:”]fogerror.pdf[/url]

[Tom Elliott]

Is the snapin actually running?

I see many different items.

Can you show me log of /var/log/apache2/error.log or /var/log/httpd/error_log

[Troye Johnson]

That’s the issue if you look its all the same snapin I launched it once and for some reason its duplicating the task it is running but it is running muiltiple times and not just once. attached is the error.log from apache2 thanks for looking into it.

[url=“/_imported_xf_attachments/0/502_error.txt?:”]error.txt[/url]

[Tom Elliott]

r1119 released.

Please give this a try. I don’t know why it keeps generating a new snapin-task for you. I’ve not added that to the Task mangement page. I think i found the issue though. The way the class was being called it was actually saving which would create that particular issue.

Just run:
TRUNCATE table snapinTasks;
TRUNCATE table snapinJobs;

Then retry to send the task.

[Tom Elliott]

r1120 released to hopefully fix the same error for active-multitasks during the state lookup.

[lanfeu]

Hi Tom
i make some modification on fog script to support gpt partition
for resize partition, all partition and all disk
resize with gpt was working but for now don’t take in consideration all the case
all part and all disk don’t work for now,
i put the file only for you to see them.
do you think you can use them (after debug)

[url=“/_imported_xf_attachments/0/505_fog.zip?:”]fog.zip[/url]

[Troye Johnson]

the issue is still happing I tried a different snapin also just to ensure it was not the application it self. attached is the screen shot of the page do you need the error.log again?

[url=“/_imported_xf_attachments/0/506_fogchromeerror.pdf?:”]fogchromeerror.pdf[/url]

[Tom Elliott]

I’m trying to replicate this issue, but so far I’m getting nothing.

[Troye Johnson]

do you think dropping the database and reinstalling fog may help? I would have to start everything all over but it may be worth it if it fixes the issue what kind of snapins are you trying. it only happens after it deploys on the ws.

[Troye Johnson]

Just a feature request because I am rebuilding everything from scratch now… Is there a way to be able to export the snapin part of the data base or all of your fog settings? I know you can with the inventory. but I think it would be nice for people who have more then 10 snapins if they ever had to rebuild.

[lanfeu]

i debug the file ,
multi part, and all part work now with different partition type
i will test tomorrow gpt part

[url=“/_imported_xf_attachments/0/507_fog.zip?:”]fog.zip[/url]

[Tom Elliott]

I’m currently rewriting the Service scripts that deals with handling the snapin tasks. I’m in the midst of testing. I think it was creating a new entry when it wasn’t really necessary. I could set all the task/snapin task variables (theoretically) by the service scripts them selves, rather than having to use the ClientServiceManager.class.php file. It seems like this is the culprit to your particular issue Troye. It means, however, that things are neater and more in place. I can actually, hopefully, remove ClientServiceManager altogether and still get things to work. Less code, easier to troubleshoot and maintain. It does, however, mean reenabling the Task creation part of the snapin deploy job, though I imagine it will be easier to cancel the task by the active tasks. I just need a way of making sure it doesn’t fail out because you’ve set a deploy to the job, then want to upload the image when you’re done deploying. That’s for the future though.