Latest FOG 0.33b
-
[quote=“fabritrento, post: 21837, member: 21607”]i’m testing image upload right now, in some minutes i say to you if patch worked…[/quote]
there is a problem, the blkid inclluded in init.gz don’t print the fstype.
on my server:
blkid
/dev/loop0: UUID=“04291dff-b6e6-4815-8549-b1a83d66f145” TYPE=“ext2”
/dev/sda1: UUID=“b842abee-3fbf-4347-a451-ec9e0b3b3aa8” TYPE=“ext2”
/dev/sda5: UUID=“0Oxvj0-osLb-ilwF-e7d0-oJeK-Za9o-IEsjcW” TYPE=“LVM2_member”
/dev/mapper/fog–vg-root: UUID=“b3e21764-e54a-4bbb-9907-0b9d05555c58” TYPE=“ext4”
/dev/mapper/fog–vg-swap_1: UUID=“82810d84-f19c-40ee-a3e8-fa51d6f6e84f” TYPE=“swap”on the client started with init.gz:
blkid
/dev/sda1: UUID=“b842abee-3fbf-4347-a451-ec9e0b3b3aa8”
/dev/sda2: UUID=“0Oxvj0-osLb-ilwF-e7d0-oJeK-Za9o-IEsjcW”i try to copy the binary of blkid by hand from server and re-run fog script.
-
That probably won’t work, but I’ll add it to the init.gz when I get a chance.
-
I am getting this error with out any snapins being deployed
Unable to determain snapin status because the MAC address was not correctly formated.
-
Is it because in fog the MAC address are using : and not -. I am not sure if that is the cause of the formatting error.
-
No, if you look at the access.log on your fog server, you can actually see the command being sent. I think, in my testing late last night, I set up different error tags to see if I could get things working, or see where they were failing. #!im was the error as it was easily identifiable. I may have forgotten to remove it from the snapins.checkin.php. I’ll be updating here shortly.
-
r1132 released.
Rewrite of the servicemodule-active script. Multiple snapins in deploy job works now. Error codes should be fixed.
-
Hey Tom,
Still getting invalid MAC error I attached fog service log.
[url=“/_imported_xf_attachments/0/513_fog2.txt?:”]fog2.txt[/url]
-
What’s your fog servers accesslog display for the snapins.checkin.php stuff?
-
I attached the logs and access log is just the end of the log let me know if you need more.
[url=“/_imported_xf_attachments/0/515_error.txt?:”]error.txt[/url][url=“/_imported_xf_attachments/0/516_accessupload.txt?:”]accessupload.txt[/url]
-
Let me guess, you have multi nics on the system?
-
yes I added both to fog though should I try to remove one the problem with hyper-v is they have two types of nics legacy adapter which boots from lan and the regular which I have not found away to have it boot from the lan So i needed to use both.
-
Don’t worry about it right now. I’m reuploading another revision which should separate the file.
-
sounds good sorry for all of the trouble.
-
Have you given this a shot? it seems to work on my end.
-
oh you already did the revision? I will install and try now.
-
Yeah, sorry still tweaking things out so i didn’t post the release.
-
I can see what is going wrong in the capone code, I’ve got the management plugin working correctly, and am looking at the service code, but I’m missing something obvious at the moment.
I’ll post the amended versions when I sort it out. -
Tom it is working I am still getting errors in the log file on the client side but the snapins are deploying.
-
access_log is not an error. It expected so you know what people are accessing. It’s how I figured out snapin’s weren’t working.
It’s also how I was able to determine you had multiple NIC’s on that system.
-
On the client, there is the one I think is more a problem with how fog determines the directory structure. It tries to find the alo-bg.png file from c:\program files\fog\images\alo-bg.png, but on 64 bit systems the real location is:
c:\program files (x86)\fog\images\alo-bg.png.I’m still working on the other errors, though I think they’re ok, for now. Still trying to figure out how Usercleanup is supposed to work.
