Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
Jerry Vonau wrote: Reuben K. Caron wrote: Martin Langhoff wrote: On Thu, Dec 11, 2008 at 7:06 PM, Reuben K. Caron reu...@laptop.org wrote: yum repolist --enablerepo=* repolist: 0 ... This is on an upgrade from 0.4 Doesn't sound good. Some more questions -- - can you email me any install / upgrade logs in /root/ ? attached - what does /etc/yum.conf say? attached Reuben, is there an /etc/yum.conf.rpmnew present on your box? If so, did you modify your /etc/yum.conf prior to the upgrade in anyway? Yes, there is a yum.conf.rpmnew present (attached) No, it has never been touched. ### OLPC School server yum configuration ### ### NOTE: yum.conf.in is the master file. Edit ### the master file if you want your changes to persist. ### After editing the master file, do ### ### `make -f xs-config.make targetfile` ### ### Also see /usr/share/doc/xs-config-version/README for more ### details, including how to RECOVER changes you have made if ### they are overwritten. ### [main] cachedir=/var/cache/yum keepcache=0 debuglevel=2 logfile=/var/log/yum.log exactarch=1 obsoletes=1 gpgcheck=1 plugins=1 metadata_expire=1800 # PUT YOUR REPOS IN separate files named file.repo in... reposdir=/etc/yum.repos.olpc.d ### NOTE that we use an alternative ### repo directory until http://dev.laptop.org/ticket/8033 ### is fixed. So the default ## reposdir /etc/yum.repos.d ### is not enabled. That is the old yum.conf from F7, don't think the test $SHA1SUM = $BADSHA1SUM to move the yum.conf.rpmnew to yum.conf was matched. - have you got files in /etc/yum.repos.d named olpcxs* ? [r...@schoolserver etc]# ls /etc/yum.repos.d/ fedora-rawhide.repo fedora-updates-newkey.repo olpcxs.repo fedora.repo fedora-updates-testing-newkey.repo olpcxs-testing.repo looks good. Jerry ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel [main] cachedir=/var/cache/yum keepcache=0 debuglevel=2 logfile=/var/log/yum.log exactarch=1 obsoletes=1 gpgcheck=1 plugins=1 installonly_limit=3 # This is the default, if you make this bigger yum won't see if the metadata # is newer on the remote and so you'll gain the bandwidth of not having to # download the new metadata and pay for it by yum not having correct # information. # It is esp. important, to have correct metadata, for distributions like # Fedora which don't keep old packages around. If you don't like this checking # interupting your command line usage, it's much better to have something # manually check the metadata once an hour (yum-updatesd will do this). # metadata_expire=90m # PUT YOUR REPOS HERE OR IN separate files named file.repo # in /etc/yum.repos.d ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Fri, Dec 12, 2008 at 6:10 PM, Reuben K. Caron reu...@laptop.org wrote: Yes, there is a yum.conf.rpmnew present (attached) No, it has never been touched. I've tested this today, and what you're finding is right - the upgrade leaves the old yum.conf -- now, I saw this problem early and added a workaround. Look at http://dev.laptop.org/git?p=projects/xs-config;a=blob;f=xs-config.spec.in;h=0cdd22d2626283959e503e0c9cfb61c2d1a9371a;hb=0ec20a942b52be2c5dd0d448f2565faadcacc102#l177 The question is why that code isn't taking care of it. I think I know why -- the sha1sum doesn't match on my test machine... researchign a bit... it turns out that there have been 2 different yum.conf files, depending in the vintage of your XS install. One in the releases before 0.4 and then the one we shipped for xs-0.4. The sha1 listed there is the right one for pre-0.4 (167, etc). The sha1s -- taken from GIT, but corroborated on my test XS installs here are ## From XS build 167 $ git checkout v0.2.10 $ sha1sum fsroot.olpc.img/etc/yum.conf 2f12835cb11f100be169abcc8bff72525a25cff7 fsroot.olpc.img/etc/yum.conf # from XS 0.4 $ git checkout v0.3.6 $ sha1sum altfiles/etc/yum.conf.in 8970c4d97f3f90eb17520ea3d8590b24bc7f4691 altfiles/etc/yum.conf.in Reuben, can you confirm that your /etc/yum.conf matches mine (8970c...)? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
Yes it matches: [r...@schoolserver ~]# sha1sum /etc/yum.conf 8970c4d97f3f90eb17520ea3d8590b24bc7f4691 /etc/yum.conf Martin Langhoff wrote: On Fri, Dec 12, 2008 at 6:10 PM, Reuben K. Caron reu...@laptop.org wrote: Yes, there is a yum.conf.rpmnew present (attached) No, it has never been touched. I've tested this today, and what you're finding is right - the upgrade leaves the old yum.conf -- now, I saw this problem early and added a workaround. Look at http://dev.laptop.org/git?p=projects/xs-config;a=blob;f=xs-config.spec.in;h=0cdd22d2626283959e503e0c9cfb61c2d1a9371a;hb=0ec20a942b52be2c5dd0d448f2565faadcacc102#l177 The question is why that code isn't taking care of it. I think I know why -- the sha1sum doesn't match on my test machine... researchign a bit... it turns out that there have been 2 different yum.conf files, depending in the vintage of your XS install. One in the releases before 0.4 and then the one we shipped for xs-0.4. The sha1 listed there is the right one for pre-0.4 (167, etc). The sha1s -- taken from GIT, but corroborated on my test XS installs here are ## From XS build 167 $ git checkout v0.2.10 $ sha1sum fsroot.olpc.img/etc/yum.conf 2f12835cb11f100be169abcc8bff72525a25cff7 fsroot.olpc.img/etc/yum.conf # from XS 0.4 $ git checkout v0.3.6 $ sha1sum altfiles/etc/yum.conf.in 8970c4d97f3f90eb17520ea3d8590b24bc7f4691 altfiles/etc/yum.conf.in Reuben, can you confirm that your /etc/yum.conf matches mine (8970c...)? cheers, m -- Reuben K. Caron Country Support Engineer One Laptop per Child Mobile: +1-617-230-3893 reu...@laptop.org Deployments Support http://wiki.laptop.org/go/Deployments_Support ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
Alright, so I am still seeing problems. yum --enablerepo=olpcxstesting install xs-config , did not work for me. So I: -wget http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-config-0.5.7.g11aaacf-1.noarch.rpm -yum localinstall xs-config-0.5.7.g11aaacf-1.noarch.rpm --nogpgcheck - reran domain config -check hostname -restart log file still shows: Dec 11 09:33:06 schoolserver kernel: bonding: lanbond0 is being created... Dec 11 09:33:06 schoolserver kernel: ADDRCONF(NETDEV_UP): lanbond0: link is not ready until I issue the: -ifenslave lanbond0 eth1 which results in: Dec 11 09:52:47 schoolserver kernel: bonding: lanbond0: enslaving eth1 as an active interface with an up link. Dec 11 09:52:47 schoolserver kernel: ADDRCONF(NETDEV_CHANGE): lanbond0: link becomes ready and then dhcp works. Martin Langhoff wrote: On Wed, Dec 10, 2008 at 6:09 PM, Martin Langhoff I spotted exactly the same difference and tested it -- does not seem to work. Hope to get to the bottom of it. Alright, fixed. Credit to Anna and Jerry for narrowing down on the issue. The actual problem is laughably simple -- late in the dev cycle of 0.5 a typo sneaked in. A minor edit of ifcfg-eth1 fixes it, see: http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=acd64ab3d2342fbda08a944e31878db6b3b563f2 In any case, you can grab the rpm with the fix from http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-config-0.5.7.g11aaacf-1.noarch.rpm or perform yum --enablerepo=olpcxstesting install xs-config thanks everyone -- specially Anna -- for you help and patience. cheers, martin -- Reuben K. Caron Country Support Engineer One Laptop per Child Mobile: +1-617-230-3893 [EMAIL PROTECTED] Deployments Support http://wiki.laptop.org/go/Deployments_Support ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Thu, Dec 11, 2008 at 12:54 PM, Reuben K. Caron [EMAIL PROTECTED] wrote: Alright, so I am still seeing problems. yum --enablerepo=olpcxstesting install xs-config , did not work for me. Missing hyphen, my fault. Try yum --enablerepo=olpcxs-testing install xs-config which if you try now will bring xs-config-0.5.9.g13a7973-1.noarch.rpm which has two fixes. This has a further typo fix (that I had made in the script I tested, but forgot to include) and also sets it to be HOTPLUG=yes so if eth1 is slow to come up, it should work once it's up. let me know if it helps... m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Thu, Dec 11, 2008 at 3:55 PM, Anna ascho...@gmail.com wrote: It worked for me, however, it looks like it returns a bunch of config files to their pristine state, which isn't a big deal on this particular test machine, as I had only edited sshd_config.in and sshd_config to allow for password authentication. This might be something users might want to be aware of if they've been testing other stuff and have tweaked some of these files. Good to hear it works for you! Yes, we do override some files -- including sshd_config. However - we store a copy in git to be able to retrieve it later - we do respect sshd_config.in -- if you edit sshd_config.in, your changes will be preserved, and any new sshd_config.in we want to deploy will be written as sshd_config.in.rpmnew cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Thu, Dec 11, 2008 at 10:09 AM, Martin Langhoff martin.langh...@gmail.com wrote: yum --enablerepo=olpcxs-testing install xs-config which if you try now will bring xs-config-0.5.9.g13a7973-1.noarch.rpm which has two fixes. This has a further typo fix (that I had made in the script I tested, but forgot to include) and also sets it to be HOTPLUG=yes so if eth1 is slow to come up, it should work once it's up. let me know if it helps... It worked for me, however, it looks like it returns a bunch of config files to their pristine state, which isn't a big deal on this particular test machine, as I had only edited sshd_config.in and sshd_config to allow for password authentication. This might be something users might want to be aware of if they've been testing other stuff and have tweaked some of these files. Downloading Packages: xs-config-0.5.9.g13a7973-1.noarch.rpm| 106 kB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : xs-config [1/1] /etc / # It may be dirty xs-commitchanged -m 'Dirty state' rsyslog.conf # Overwrite cp -p rsyslog.conf.in rsyslog.conf xs-commitchanged -m Made from rsyslog.conf.in rsyslog.conf # It may be dirty xs-commitchanged -m 'Dirty state' motd # Overwrite cp -p motd.in motd xs-commitchanged -m Made from motd.in motd xs-commitchanged -m 'Dirty state' sysctl.conf cp -p sysctl.conf.in sysctl.conf xs-commitchanged -m Made from sysctl.conf.in sysctl.conf sysctl -p sysctl.conf net.ipv4.ip_forward = 1 net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.default.accept_source_route = 0 kernel.sysrq = 1 kernel.core_uses_pid = 1 net.ipv4.tcp_syncookies = 1 kernel.shmmax = 268435456 # It may be dirty xs-commitchanged -m 'Dirty state' ssh/sshd_config # Overwrite cp -p ssh/sshd_config.in ssh/sshd_config xs-commitchanged -m Made from ssh/sshd_config.in ssh/sshd_config Created commit bb554ba: Made from ssh/sshd_config.in - changed file /etc/ssh/sshd_config 1 files changed, 3 insertions(+), 3 deletions(-) # It may be dirty xs-commitchanged -m 'Dirty state' sysconfig/named # Overwrite cp -p sysconfig/named.in sysconfig/named xs-commitchanged -m Made from sysconfig/named.in sysconfig/named # It may be dirty xs-commitchanged -m 'Dirty state' sysconfig/init # Overwrite cp -p sysconfig/init.in sysconfig/init xs-commitchanged -m Made from sysconfig/init.in sysconfig/init # It may be dirty xs-commitchanged -m 'Dirty state' sysconfig/iptables-config # Overwrite cp -p sysconfig/iptables-config.in sysconfig/iptables-config xs-commitchanged -m Made from sysconfig/iptables-config.in sysconfig/iptables-config # It may be dirty xs-commitchanged -m 'Dirty state' sysconfig/squid # Overwrite cp -p sysconfig/squid.in sysconfig/squid xs-commitchanged -m Made from sysconfig/squid.in sysconfig/squid touch sudoers.tmp chmod 640 sudoers.tmp cat-parts sudoers.d sudoers.tmp chmod 440 sudoers.tmp xs-commitchanged -m 'Dirty state' sudoers mv -f sudoers.tmp sudoers xs-commitchanged -m Made from sudoers.d sudoers # It may be dirty xs-commitchanged -m 'Dirty state' rssh.conf # Overwrite cp -p rssh.conf.in rssh.conf xs-commitchanged -m Made from rssh.conf.in rssh.conf # It may be dirty xs-commitchanged -m 'Dirty state' php.ini # Overwrite cp -p php.ini.in php.ini xs-commitchanged -m Made from php.ini.in php.ini # It may be dirty xs-commitchanged -m 'Dirty state' sysconfig/httpd # Overwrite cp -p sysconfig/httpd.in sysconfig/httpd xs-commitchanged -m Made from sysconfig/httpd.in sysconfig/httpd # It may be dirty xs-commitchanged -m 'Dirty state' init.d/squid # Overwrite cp -p init.d/squid.in init.d/squid xs-commitchanged -m Made from init.d/squid.in init.d/squid # It may be dirty xs-commitchanged -m 'Dirty state' sysconfig/ejabberd # Overwrite cp -p sysconfig/ejabberd.in sysconfig/ejabberd xs-commitchanged -m Made from sysconfig/ejabberd.in sysconfig/ejabberd xs-commitchanged -m 'Dirty state' sysconfig/network-scripts/ifcfg-eth0 cp -p sysconfig/olpc-scripts/ifcfg-eth0 sysconfig/network-scripts/ifcfg-eth0 xs-commitchanged -m Made from olpc-scripts sysconfig/network-scripts/ifcfg-eth0 xs-commitchanged -m 'Dirty state' sysconfig/network-scripts/ifcfg-eth1 cp -p sysconfig/olpc-scripts/ifcfg-eth1 sysconfig/network-scripts/ifcfg-eth1 xs-commitchanged -m Made from olpc-scripts sysconfig/network-scripts/ifcfg-eth1 # It may be dirty xs-commitchanged -m 'Dirty state' httpd/conf.d/proxy_ajp.conf # Overwrite cp -p httpd/conf.d/proxy_ajp.conf.in httpd/conf.d/proxy_ajp.conf xs-commitchanged -m Made from httpd/conf.d/proxy_ajp.conf.in httpd/conf.d/proxy_ajp.conf # It may be dirty xs-commitchanged -m 'Dirty state' httpd/conf.d/ssl.conf # Overwrite cp -p httpd/conf.d/ssl.conf.in httpd/conf.d/ssl.conf xs-commitchanged -m Made from httpd/conf.d/ssl.conf.in httpd/conf.d/ssl.conf Using default domain name Setting the base dns name to random.xs.laptop.org find: ./domain_config.d/:
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Thu, Dec 11, 2008 at 12:04 PM, Martin Langhoff martin.langh...@gmail.com wrote: - we do respect sshd_config.in -- if you edit sshd_config.in, your changes will be preserved, and any new sshd_config.in we want to deploy will be written as sshd_config.in.rpmnew Well, I did edit sshd_config.in and then did the make xs-config thing like I was supposed to. My changes were preserved in /etc/ssh/sshd_config.in.rpmsave. But going forward, and since I'm looking at possibly installing XS 0.5 on quite a few machines here, before I burn the CD again, can I edit /etc/sysconfig/network-scripts/ifcfg-eth1 on the iso like so: (Edit this line to look like this) if [ foo$XS_LANBOND_MAINXS_IPADDR != foo ]; then (Add this line) HOTPLUG=yes Will that work? I need to keep the install steps to a minimum and I'd rather make the changes to the iso. Anna Schoolfield Birmingham ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
Will a new ISO (XS-0.5.1?) be released to address this issue? On Wed, 2008-12-10 at 18:51 -0200, Martin Langhoff wrote: On Wed, Dec 10, 2008 at 6:09 PM, Martin Langhoff I spotted exactly the same difference and tested it -- does not seem to work. Hope to get to the bottom of it. Alright, fixed. Credit to Anna and Jerry for narrowing down on the issue. The actual problem is laughably simple -- late in the dev cycle of 0.5 a typo sneaked in. A minor edit of ifcfg-eth1 fixes it, see: http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=acd64ab3d2342fbda08a944e31878db6b3b563f2 In any case, you can grab the rpm with the fix from http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-config-0.5.7.g11aaacf-1.noarch.rpm or perform yum --enablerepo=olpcxstesting install xs-config thanks everyone -- specially Anna -- for you help and patience. cheers, martin ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Thu, Dec 11, 2008 at 4:19 PM, Anna ascho...@gmail.com wrote: Will that work? I need to keep the install steps to a minimum and I'd rather make the changes to the iso. If you just grab the rpm and put it in the iso, it should work. However, I might spin a 0.5.1 in the coming days. Just want to see if there's any other major issue... cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list server-de...@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Thu, Dec 11, 2008 at 5:37 PM, Reuben K. Caron reu...@laptop.org wrote: I get : Error getting repository data for olpcxs-testing, repository not found That's kind of bizarre. Maybe the machine is not on the internet? What does the command below say? (it may take a couple of minutes...) yum repolist --enablerepo=* it should list a lot of repositories, including olpcxs, olpcxs-testing and -source variants for those 2. If not, there's a problem in /etc/yum.conf or /etc/yum.repos.d- is this a 0.5 install or an upgrade from 0.4? cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Thu, Dec 11, 2008 at 7:06 PM, Reuben K. Caron reu...@laptop.org wrote: yum repolist --enablerepo=* repolist: 0 ... This is on an upgrade from 0.4 Doesn't sound good. Some more questions -- - can you email me any install / upgrade logs in /root/ ? - what does /etc/yum.conf say? - have you got files in /etc/yum.repos.d named olpcxs* ? - what does 'rpm -qa xs-release' say? Also after installing xs-config-0.5.9.g13a7973-1.noarch.rpm, I get the following when running /etc/sysconfig/olpc-scripts/domain_config: Setting the base dns name to xs4.org find: ./domain_config.d/: No such file or directory I cannot repro that problem either in a clean xs-0.5 with the latest xs-config, so I'm installing 0.4, going to configure it, upgrade to 0.5, update xs-config, and see what happens. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
Anna wrote: This is probably far from ideal, but it works for me and I'm putting it out there in case you're messing with XS 0.5 and need to have eth1 working now so you can test other stuff. I'm sure there's a more elegant solution. Put this in /etc/rc.local ifenslave lanbond0 eth1 That's odd, the network init scripts should be doing that ifenslave part, I think we're missing some small option in the ifcfg-eth1 file. Reboot. And there we go: [EMAIL PROTECTED] ~]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0D:56:05:7C:DA UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:4348 errors:0 dropped:0 overruns:0 frame:0 TX packets:5381 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:368480 (359.8 KiB) TX bytes:6433735 (6.1 MiB) I've connected a few XOs to my test platform so far and haven't seen any unexpected issues. I don't know if you have to edit /etc/modprobe.d/xs_bonding with Jerry's suggestion below, but I've got that in there. options lanbond0 mode=active-backup miimon=100 options mshbond0 mode=active-backup miimon=100 options mshbond1 mode=active-backup miimon=100 options mshbond2 mode=active-backup miimon=100 Of course, you can just run ifenslave lanbond0 eth1, but it doesn't persist on reboot. Could you try adding HOTPLUG=yes to the ifcfg-eth1 file and disable your rc.local routine and retest please. That is only difference that I can spot between your non-working wired and working mesh lan. Jerry ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
In my tests the following works on a fresh installation without modifying the xs_bonding: Put this in /etc/rc.local ifenslave lanbond0 eth1 Reboot. And there we go: Anna wrote: This is probably far from ideal, but it works for me and I'm putting it out there in case you're messing with XS 0.5 and need to have eth1 working now so you can test other stuff. I'm sure there's a more elegant solution. Put this in /etc/rc.local ifenslave lanbond0 eth1 Reboot. And there we go: [EMAIL PROTECTED] ~]# ifconfig eth1 eth1 Link encap:Ethernet HWaddr 00:0D:56:05:7C:DA UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:4348 errors:0 dropped:0 overruns:0 frame:0 TX packets:5381 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:368480 (359.8 KiB) TX bytes:6433735 (6.1 MiB) I've connected a few XOs to my test platform so far and haven't seen any unexpected issues. I don't know if you have to edit /etc/modprobe.d/xs_bonding with Jerry's suggestion below, but I've got that in there. options lanbond0 mode=active-backup miimon=100 options mshbond0 mode=active-backup miimon=100 options mshbond1 mode=active-backup miimon=100 options mshbond2 mode=active-backup miimon=100 Of course, you can just run ifenslave lanbond0 eth1, but it doesn't persist on reboot. Anna Schoolfield Birmingham ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel ___ Server-devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Wed, Dec 10, 2008 at 2:37 PM, Jerry Vonau [EMAIL PROTECTED] wrote: Anna wrote: ifenslave lanbond0 eth1 That's odd, the network init scripts should be doing that ifenslave part, I think we're missing some small option in the ifcfg-eth1 file. I am starting to agree -- we are either seeing an issue with timing _or_ a configuration issue. Perhaps our config for eth1 is broken. It'd be strange since I tested it quite a bit in the run up to the release, but it's also true that I was making subtle changes to the very same configs. Good news is: I can repro the problem on a machine I have here. Could you try adding HOTPLUG=yes to the ifcfg-eth1 file I spotted exactly the same difference and tested it -- does not seem to work. Hope to get to the bottom of it. (Apologies for the delay in getting into reproduce-and-debug -- I've had a hell of a time getting hardware I could play with for this, as I'm not @ my usual office, city or continent ;-) ) cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
Re: [Server-devel] Amateurish Workaround to Get Bonding to Work With eth1
On Wed, Dec 10, 2008 at 6:09 PM, Martin Langhoff I spotted exactly the same difference and tested it -- does not seem to work. Hope to get to the bottom of it. Alright, fixed. Credit to Anna and Jerry for narrowing down on the issue. The actual problem is laughably simple -- late in the dev cycle of 0.5 a typo sneaked in. A minor edit of ifcfg-eth1 fixes it, see: http://dev.laptop.org/git?p=projects/xs-config;a=commitdiff;h=acd64ab3d2342fbda08a944e31878db6b3b563f2 In any case, you can grab the rpm with the fix from http://xs-dev.laptop.org/xsrepos/testing/olpc/9/i386/xs-config-0.5.7.g11aaacf-1.noarch.rpm or perform yum --enablerepo=olpcxstesting install xs-config thanks everyone -- specially Anna -- for you help and patience. cheers, martin -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
