Packet Fragmentation
-
Hi All,
We are running into a bit of an issue with our fog server. It seems the packet fragmentation that fog does is causing a bottleneck on our firewall, from what our network guy is telling me. He said something about having to modify the rsize and wsize parameters when fog pushes the image out.
Typically how we do it as far as imaging goes is we boot up via pxe to the menu and select “Perform Host Registration and Inventory” and chose to image it at this point.
How and where do I make the necessary config changes to keep our Firewall and Network Admin happy? We’re running Fog on Centos via a VM. Works great when we image from our office, just when we move out of our IT office and image pc’s on the production floor in the locked down zone is when we have issues.
Please help!!!
-
I’m also told that if we can use TCP to push images instead of UDP, then that will resolve the issue as well. I just can’t seem to find where to change these settings…
-
You can use Unicast to send out the images. This is all done using TCP packets. I don’t know what they’re referring to about rsize and wsize unless they’re referring to the cache size connection for the NFS server.
-
[quote=“Tom Elliott, post: 23686, member: 7271”]You can use Unicast to send out the images. This is all done using TCP packets. I don’t know what they’re referring to about rsize and wsize unless they’re referring to the cache size connection for the NFS server.[/quote]
Thank you very much for all of your help on IRC Tom! Everything is working absolutely fantastic now!
Quick question, going to be moving the server and have to change the assigned IP. I read somewhere that all I have to do is use the command after changing the IP on the server OS:
./installfog.sh --no-upgrade
Also, I know you’re partial to 33
but how stable is it? Would it be OK in a production environment? We only use it for imaging and I’ll be incorporating adding the pc’s to AD as well… -
Glad I could be of help.
You could also just change the IP to the new IP in the /opt/fog/.fogsettings file.
0.33b is pretty stable, but still considered in beta phase. I wouldn’t recommend using it in production, though I can’t imagine it causing any issues as the main imaging of WIndows 7, XP seem to be just fine.
-
Sorry to bother you again Tom, but I’m stuck once again…this time putting up a new server. Centos 6.5 with .32 but I keep running up against a dependency issue. Apparently the gcc package needs an older version of glibc-common that what is installed with 6.5.
Requires: glibc-common = 2.12-1.107.el6_4.5 Installed: glibc-common-2.12-1.132.el6.x86_64 (@anaconda-CentOS-201311272149.x86_64/6.5)
-
Can you update gcc?
-
[root@fog bin]# yum update gcc
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile- elrepo: mirror.symnds.com
- epel: fedora.mirror.nexicom.net
- remi: mirrors.mediatemple.net
Setting up Update Process
Package(s) gcc available, but not installed.
No Packages marked for Update
[root@fog bin]#
nope, doesn’t look like it. this is a brand new server, just installed it today and the only things I installed was wget, yum, mlocate…
-
Try yum -y install gcc
-
yum -y install gcc
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile- elrepo: mirror.symnds.com
- epel: fedora.mirror.nexicom.net
- remi: mirrors.mediatemple.net
Setting up Install Process
Resolving Dependencies
–> Running transaction check
—> Package gcc.x86_64 0:4.4.7-3.el6 will be installed
–> Processing Dependency: libgomp = 4.4.7-3.el6 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: cpp = 4.4.7-3.el6 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: cloog-ppl >= 0.15 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: libgomp.so.1()(64bit) for package: gcc-4.4.7-3.el6.x86_64
–> Running transaction check
—> Package cloog-ppl.x86_64 0:0.15.7-1.2.el6 will be installed
–> Processing Dependency: libppl_c.so.2()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64
–> Processing Dependency: libppl.so.7()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64
—> Package cpp.x86_64 0:4.4.7-3.el6 will be installed
–> Processing Dependency: libmpfr.so.1()(64bit) for package: cpp-4.4.7-3.el6.x86_64
—> Package glibc-devel.x86_64 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: glibc-headers = 2.12-1.107.el6_4.5 for package: glibc-devel-2.12-1.107.el6_4.5.x86_64
–> Processing Dependency: glibc = 2.12-1.107.el6_4.5 for package: glibc-devel-2.12-1.107.el6_4.5.x86_64
–> Processing Dependency: glibc-headers for package: glibc-devel-2.12-1.107.el6_4.5.x86_64
—> Package libgomp.x86_64 0:4.4.7-3.el6 will be installed
–> Running transaction check
—> Package glibc.i686 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: glibc-common = 2.12-1.107.el6_4.5 for package: glibc-2.12-1.107.el6_4.5.i686
–> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.107.el6_4.5.i686
–> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.107.el6_4.5.i686
—> Package glibc-headers.x86_64 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.12-1.107.el6_4.5.x86_64
–> Processing Dependency: kernel-headers for package: glibc-headers-2.12-1.107.el6_4.5.x86_64
—> Package mpfr.x86_64 0:2.4.1-6.el6 will be installed
—> Package ppl.x86_64 0:0.10.2-11.el6 will be installed
–> Running transaction check
—> Package glibc.i686 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: glibc-common = 2.12-1.107.el6_4.5 for package: glibc-2.12-1.107.el6_4.5.i686
—> Package kernel-headers.x86_64 0:2.6.32-358.23.2.el6 will be installed
—> Package nss-softokn-freebl.i686 0:3.14.3-3.el6_4 will be installed
–> Finished Dependency Resolution
Error: Package: glibc-2.12-1.107.el6_4.5.i686 (updates)
Requires: glibc-common = 2.12-1.107.el6_4.5
Installed: glibc-common-2.12-1.132.el6.x86_64 (@anaconda-CentOS-201311272149.x86_64/6.5)
glibc-common = 2.12-1.132.el6
Available: glibc-common-2.12-1.107.el6.x86_64 (base)
glibc-common = 2.12-1.107.el6
Available: glibc-common-2.12-1.107.el6_4.2.x86_64 (updates)
glibc-common = 2.12-1.107.el6_4.2
Available: glibc-common-2.12-1.107.el6_4.4.x86_64 (updates)
glibc-common = 2.12-1.107.el6_4.4
Available: glibc-common-2.12-1.107.el6_4.5.x86_64 (updates)
glibc-common = 2.12-1.107.el6_4.5
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
-
try these commands:
[code]rpm -e --nodeps glibc-common
yum -y install glibc-common gcc[/code] -
[root@fog bin]# rpm -e --nodeps glibc-common
[root@fog bin]# yum -y install glibc-common gcc
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile-
elrepo: mirror.symnds.com
-
remi: mirrors.mediatemple.net
Setting up Install Process
Resolving Dependencies
–> Running transaction check
—> Package gcc.x86_64 0:4.4.7-3.el6 will be installed
–> Processing Dependency: libgomp = 4.4.7-3.el6 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: cpp = 4.4.7-3.el6 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: cloog-ppl >= 0.15 for package: gcc-4.4.7-3.el6.x86_64
–> Processing Dependency: libgomp.so.1()(64bit) for package: gcc-4.4.7-3.el6.x86_64
—> Package glibc-common.x86_64 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: glibc = 2.12-1.107.el6_4.5 for package: glibc-common-2.12-1.107.el6_4.5.x86_64
–> Running transaction check
—> Package cloog-ppl.x86_64 0:0.15.7-1.2.el6 will be installed
–> Processing Dependency: libppl_c.so.2()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64
–> Processing Dependency: libppl.so.7()(64bit) for package: cloog-ppl-0.15.7-1.2.el6.x86_64
—> Package cpp.x86_64 0:4.4.7-3.el6 will be installed
–> Processing Dependency: libmpfr.so.1()(64bit) for package: cpp-4.4.7-3.el6.x86_64
—> Package glibc.i686 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.107.el6_4.5.i686
–> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.107.el6_4.5.i686
—> Package glibc-devel.x86_64 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: glibc-headers = 2.12-1.107.el6_4.5 for package: glibc-devel-2.12-1.107.el6_4.5.x86_64
–> Processing Dependency: glibc-headers for package: glibc-devel-2.12-1.107.el6_4.5.x86_64
—> Package libgomp.x86_64 0:4.4.7-3.el6 will be installed
–> Running transaction check
—> Package glibc-headers.x86_64 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: kernel-headers >= 2.2.1 for package: glibc-headers-2.12-1.107.el6_4.5.x86_64
–> Processing Dependency: kernel-headers for package: glibc-headers-2.12-1.107.el6_4.5.x86_64
—> Package mpfr.x86_64 0:2.4.1-6.el6 will be installed
—> Package nss-softokn-freebl.i686 0:3.14.3-3.el6_4 will be installed
—> Package ppl.x86_64 0:0.10.2-11.el6 will be installed
–> Running transaction check
—> Package kernel-headers.x86_64 0:2.6.32-358.23.2.el6 will be installed
–> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:1. You have an upgrade for glibc which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of glibc of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude glibc.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of glibc installed, but yum can only see an upgrade for one of those arcitectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of glibc installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: glibc-2.12-1.107.el6_4.5.i686 != glibc-2.12-1.132.el6.x86_64
Error: Protected multilib versions: nss-softokn-freebl-3.14.3-3.el6_4.i686 != nss-softokn-freebl-3.14.3-9.el6.x86_64
You could try using --skip-broken to work around the problem
** Found 4 pre-existing rpmdb problem(s), ‘yum check’ output follows:
MAKEDEV-3.24-6.el6.x86_64 has missing requires of /usr/bin/getent
glibc-2.12-1.132.el6.x86_64 has missing requires of glibc-common = (‘0’, ‘2.12’, ‘1.132.el6’)
rpcbind-0.2.0-11.el6.x86_64 has missing requires of glibc-common
udev-147-2.51.el6.x86_64 has missing requires of /usr/bin/getent -
-
LOL, might be just easier to use an older version of centos…
-
try just:
[code]yum -y install glibc-common; yum update[/code]You may have to reboot the system once complete.
-
no joy
[root@fog bin]# yum -y install glibc-common; yum update
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile-
elrepo: mirror.symnds.com
-
remi: mirrors.mediatemple.net
Setting up Install Process
Resolving Dependencies
–> Running transaction check
—> Package glibc-common.x86_64 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: glibc = 2.12-1.107.el6_4.5 for package: glibc-common-2.12-1.107.el6_4.5.x86_64
–> Running transaction check
—> Package glibc.i686 0:2.12-1.107.el6_4.5 will be installed
–> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.12-1.107.el6_4.5.i686
–> Processing Dependency: libfreebl3.so for package: glibc-2.12-1.107.el6_4.5.i686
–> Running transaction check
—> Package nss-softokn-freebl.i686 0:3.14.3-3.el6_4 will be installed
–> Finished Dependency Resolution
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:1. You have an upgrade for glibc which is missing some dependency that another package requires. Yum is trying to solve this by installing an older version of glibc of the different architecture. If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). You can try redoing the upgrade with --exclude glibc.otherarch ... this should give you an error message showing the root cause of the problem. 2. You have multiple architectures of glibc installed, but yum can only see an upgrade for one of those arcitectures. If you don't want/need both architectures anymore then you can remove the one with the missing update and everything will work. 3. You have duplicate versions of glibc installed already. You can use "yum check" to get yum show these errors. ...you can also use --setopt=protected_multilib=false to remove this checking, however this is almost never the correct thing to do as something else is very likely to go wrong (often causing much more problems). Protected multilib versions: glibc-2.12-1.107.el6_4.5.i686 != glibc-2.12-1.132.el6.x86_64
Error: Protected multilib versions: nss-softokn-freebl-3.14.3-3.el6_4.i686 != nss-softokn-freebl-3.14.3-9.el6.x86_64
You could try using --skip-broken to work around the problem
** Found 4 pre-existing rpmdb problem(s), ‘yum check’ output follows:
MAKEDEV-3.24-6.el6.x86_64 has missing requires of /usr/bin/getent
glibc-2.12-1.132.el6.x86_64 has missing requires of glibc-common = (‘0’, ‘2.12’, ‘1.132.el6’)
rpcbind-0.2.0-11.el6.x86_64 has missing requires of glibc-common
udev-147-2.51.el6.x86_64 has missing requires of /usr/bin/getent
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile- elrepo: mirror.symnds.com
- epel: fedora.mirror.nexicom.net
- remi: mirrors.mediatemple.net
Setting up Update Process
No Packages marked for Update
-
-
-
Then try:
[code]yum -y update[/code] -
Thanks for the help again. You left before I could tell you that! FYI, I’m the one that sucked…lol
-
You’re fine man. Thanks for attempting. Hopefully all works well tomorrow. Try using the wiki though to install. It may help a little bit.
-
I’m going to fire up that mobile version I made last week and go through the history. It only took a little bit and I had it up and running, there’s just something I either messed up bad or am missing. I’ll get it figured out.
