Latest FOG 0.33b
-
r1115 released,
Hostname_early appears to work properly for windows 7 systems. XP already worked, but 7 didn’t. Should be good now.
Still don’t know about the changer from FOGClient, but I’ll try to look into it tomorrow.
-
r1116 released.
Truncates hostname to 15 characters. Also added a service script that verifies that the hostname is valid/unused. This way less confusion between GUI and Fog registration scheme.
-
Aha, I understand the issue around the double equals sign now.
This is on Ubuntu 12.04 LTS, I haven’t tried on Fedora 20.
If I call “sh installfog.sh” it uses dash, which doesn’t support the “==” operator, and flags an error.
If I call ./installfog.sh it uses bash which does support “==”. -
small esthetic bug in 0.33b:
when you do ./installfog.sh
…
What is the IP address to be used by this FOG Server? [inet:192.168.0.3] [enter]
Invalid IP address!What is the IP address to be used by this FOG Server? [inet:192.168.0.3]192.168.0.3
……
On a Windows DHCP server you must set:
option 066 & 067
we can specify also that in 066 user must set the ip of fog, and in 067 “pxelinux.0”
…i edit this message today to post all bugs that i found…
-
So I’ll check the loop for the ip. Then you just want me to add the info of what the options do?
-
fabritreno,
What OS did you install this on? I’ve never seen any issues with this particular issue, as it already checks if the entry is null, but the [] part is filled out, use the [] part.
Then it tests if either the suggested IP or the entered IP is valid. If it’s not valid (extra spaces included) then it fails with that message. My guess is something is a little different on your server.
-
r1118 released.
Adds information for Option 066 and Option 067 per fabritreno’s suggestion above.
trims the last / off of the path name when deploying a multicast image.
-
[quote=“Tom Elliott, post: 21602, member: 7271”]So I’ll check the loop for the ip. Then you just want me to add the info of what the options do?[/quote]
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 loopbackThe 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=“Tom Elliott, post: 21604, member: 7271”]fabritreno,
What OS did you install this on? I’ve never seen any issues with this particular issue, as it already checks if the entry is null, but the [] part is filled out, use the [] part.
Then it tests if either the suggested IP or the entered IP is valid. If it’s not valid (extra spaces included) then it fails with that message. My guess is something is a little different on your server.[/quote]
is a ubuntu server edition 12.04 LTS virtualized on a win2008srv with virtualbox installed
-
[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 loopbackThe 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’ ').
-
[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 -
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_swapbut 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?
-
How big is the ext4 partition?
-
Is 25-30GB (about)
-
What’s the OS type for the image being uploaded?
-
[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 -
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
-
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]
-
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
-
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]
