Re: [Astlinux-users] NTP Mixup :: the sequel
Darrick, et al: Did as suggested. Updated to 2155, whacked build_i586 and toolchain_build_i586. Still flamed out on iptables build. I'm going to investigate further and see if I can spot the problem, but here is where it heads south: /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIPT_LIB_DIR=\/usr/lib/iptables\ -static -o iptables-restore iptables-restore.c iptables.o extensions/libext.a libiptc/libiptc.a /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIP6T_LIB_DIR=\/usr/lib/iptables\ -static -o ip6tables ip6tables-standalone.c ip6tables.o extensions/libext6.a libiptc/libiptc.a /tmp/ccdNp1uR.o: In function `main': iptables-standalone.c:(.text+0x7e): undefined reference to `iptc_commit' iptables-standalone.c:(.text+0x98): undefined reference to `iptc_strerror' iptables.o: In function `for_each_chain': iptables.c:(.text+0x622): undefined reference to `iptc_first_chain' iptables.c:(.text+0x63c): undefined reference to `iptc_next_chain' At first blush, it doesn't appear to be environmental (i.e. my box), but that's still the leading suspect, to be sure. Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 7:47 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip Prindeville wrote: Joy? Or no joy? Ron Byer Jr. wrote: Sorry. I don't know how that came out to be 2041. Twice, no less. Intended to say 2136. I think the latest was 2140 when I pulled it, and I scrambled that to 2041. Ron, Please update to the lastest 0.6 svn and rebuild. I would start by blowing away the build_i586 directory and possibly the toolchain_build_i586 directory (start with the first and if you still have build problems, blow away both and start fresh). I've been using 2147 here since yesterday. If you update, you'll get at least 2149 which has some ipsec fixes and a newer version of the web gui too. Darrick -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.15/1835 - Release Date: 12/7/2008 4:56 PM -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP Mixup :: the sequel
This is for a net5501? Or some other target? Currently trunk only builds for the net5501 -Philip Ron Byer Jr. wrote: Darrick, et al: Did as suggested. Updated to 2155, whacked build_i586 and toolchain_build_i586. Still flamed out on iptables build. I'm going to investigate further and see if I can spot the problem, but here is where it heads south: /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIPT_LIB_DIR=\/usr/lib/iptables\ -static -o iptables-restore iptables-restore.c iptables.o extensions/libext.a libiptc/libiptc.a /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIP6T_LIB_DIR=\/usr/lib/iptables\ -static -o ip6tables ip6tables-standalone.c ip6tables.o extensions/libext6.a libiptc/libiptc.a /tmp/ccdNp1uR.o: In function `main': iptables-standalone.c:(.text+0x7e): undefined reference to `iptc_commit' iptables-standalone.c:(.text+0x98): undefined reference to `iptc_strerror' iptables.o: In function `for_each_chain': iptables.c:(.text+0x622): undefined reference to `iptc_first_chain' iptables.c:(.text+0x63c): undefined reference to `iptc_next_chain' At first blush, it doesn't appear to be environmental (i.e. my box), but that's still the leading suspect, to be sure. Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 7:47 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip Prindeville wrote: Joy? Or no joy? Ron Byer Jr. wrote: Sorry. I don't know how that came out to be 2041. Twice, no less. Intended to say 2136. I think the latest was 2140 when I pulled it, and I scrambled that to 2041. Ron, Please update to the lastest 0.6 svn and rebuild. I would start by blowing away the build_i586 directory and possibly the toolchain_build_i586 directory (start with the first and if you still have build problems, blow away both and start fresh). I've been using 2147 here since yesterday. If you update, you'll get at least 2149 which has some ipsec fixes and a newer version of the web gui too. Darrick -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP Mixup :: the sequel
Yes. for the net5501. What I've found so far: - the include paths for the iptables* builds are: -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ There is an include of iptables.h, which I would think it the issue. I have two instances of iptables.h: /opt/astlinux-0.6/build_i586/iptables-1.3.8/include/iptables.h /opt/astlinux-0.6/build_i586/linux-2.6.20.21- astlinux/include/config/ip6/nf/iptables.h /opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include/config/ip/nf/i ptables.h The config/ip/nf/iptables.h cannot match either -I statement, so that's out. (Just as well, it's a 0 length file). The remaining iptables.h could match the -I statement(s), and it includes libiptc/libiptc.h, which is present, in the right place, and has the prototypes for the iptc entry points. Can't be that hard to figure out. I'm going to scale back on the parallel compiles to make sure I see which one is actually having a problem -- though it looks like all the iptable binaries at present. rb -Original Message- From: Philip Prindeville [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 1:19 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel This is for a net5501? Or some other target? Currently trunk only builds for the net5501 -Philip Ron Byer Jr. wrote: Darrick, et al: Did as suggested. Updated to 2155, whacked build_i586 and toolchain_build_i586. Still flamed out on iptables build. I'm going to investigate further and see if I can spot the problem, but here is where it heads south: /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIPT_LIB_DIR=\/usr/lib/iptables\ -static -o iptables-restore iptables-restore.c iptables.o extensions/libext.a libiptc/libiptc.a /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIP6T_LIB_DIR=\/usr/lib/iptables\ -static -o ip6tables ip6tables-standalone.c ip6tables.o extensions/libext6.a libiptc/libiptc.a /tmp/ccdNp1uR.o: In function `main': iptables-standalone.c:(.text+0x7e): undefined reference to `iptc_commit' iptables-standalone.c:(.text+0x98): undefined reference to `iptc_strerror' iptables.o: In function `for_each_chain': iptables.c:(.text+0x622): undefined reference to `iptc_first_chain' iptables.c:(.text+0x63c): undefined reference to `iptc_next_chain' At first blush, it doesn't appear to be environmental (i.e. my box), but that's still the leading suspect, to be sure. Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 7:47 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip Prindeville wrote: Joy? Or no joy? Ron Byer Jr. wrote: Sorry. I don't know how that came out to be 2041. Twice, no less. Intended to say 2136. I think the latest was 2140 when I pulled it, and I scrambled that to 2041. Ron, Please update to the lastest 0.6 svn and rebuild. I would start by blowing away the build_i586 directory and possibly the toolchain_build_i586 directory (start with the first and if you still have build problems, blow away both and start fresh). I've been using 2147 here since yesterday. If you update, you'll get at least 2149 which has some ipsec fixes and a newer version of the web gui too. Darrick -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.15/1835 - Release Date: 12/7/2008 4:56 PM -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com
Re: [Astlinux-users] NTP Mixup :: the sequel
Philip, He's not building trunk, he's building 0.6 svn. Ron, I'm not seeing those same issues. What OS are you using as your host build system. Darrick Philip Prindeville wrote: This is for a net5501? Or some other target? Currently trunk only builds for the net5501 -Philip Ron Byer Jr. wrote: Darrick, et al: Did as suggested. Updated to 2155, whacked build_i586 and toolchain_build_i586. Still flamed out on iptables build. I'm going to investigate further and see if I can spot the problem, but here is where it heads south: /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIPT_LIB_DIR=\/usr/lib/iptables\ -static -o iptables-restore iptables-restore.c iptables.o extensions/libext.a libiptc/libiptc.a /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIP6T_LIB_DIR=\/usr/lib/iptables\ -static -o ip6tables ip6tables-standalone.c ip6tables.o extensions/libext6.a libiptc/libiptc.a /tmp/ccdNp1uR.o: In function `main': iptables-standalone.c:(.text+0x7e): undefined reference to `iptc_commit' iptables-standalone.c:(.text+0x98): undefined reference to `iptc_strerror' iptables.o: In function `for_each_chain': iptables.c:(.text+0x622): undefined reference to `iptc_first_chain' iptables.c:(.text+0x63c): undefined reference to `iptc_next_chain' At first blush, it doesn't appear to be environmental (i.e. my box), but that's still the leading suspect, to be sure. Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 7:47 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip Prindeville wrote: Joy? Or no joy? Ron Byer Jr. wrote: Sorry. I don't know how that came out to be 2041. Twice, no less. Intended to say 2136. I think the latest was 2140 when I pulled it, and I scrambled that to 2041. Ron, Please update to the lastest 0.6 svn and rebuild. I would start by blowing away the build_i586 directory and possibly the toolchain_build_i586 directory (start with the first and if you still have build problems, blow away both and start fresh). I've been using 2147 here since yesterday. If you update, you'll get at least 2149 which has some ipsec fixes and a newer version of the web gui too. Darrick -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP Mixup :: the sequel
Darrick, Centos5 kernel 2.6.18-92.1.17.el5 gcc 4.1.2 I restarted with a straight serial build -- no parallel compiles going on. I'm sure this will end up being some noob problem since this is the first time I've building ... I should be able to figure it out. (though not without some questions, I'm sure). rb Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 3:00 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip, He's not building trunk, he's building 0.6 svn. Ron, I'm not seeing those same issues. What OS are you using as your host build system. Darrick Philip Prindeville wrote: This is for a net5501? Or some other target? Currently trunk only builds for the net5501 -Philip Ron Byer Jr. wrote: Darrick, et al: Did as suggested. Updated to 2155, whacked build_i586 and toolchain_build_i586. Still flamed out on iptables build. I'm going to investigate further and see if I can spot the problem, but here is where it heads south: /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIPT_LIB_DIR=\/usr/lib/iptables\ -static -o iptables-restore iptables-restore.c iptables.o extensions/libext.a libiptc/libiptc.a /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIP6T_LIB_DIR=\/usr/lib/iptables\ -static -o ip6tables ip6tables-standalone.c ip6tables.o extensions/libext6.a libiptc/libiptc.a /tmp/ccdNp1uR.o: In function `main': iptables-standalone.c:(.text+0x7e): undefined reference to `iptc_commit' iptables-standalone.c:(.text+0x98): undefined reference to `iptc_strerror' iptables.o: In function `for_each_chain': iptables.c:(.text+0x622): undefined reference to `iptc_first_chain' iptables.c:(.text+0x63c): undefined reference to `iptc_next_chain' At first blush, it doesn't appear to be environmental (i.e. my box), but that's still the leading suspect, to be sure. Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 7:47 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip Prindeville wrote: Joy? Or no joy? Ron Byer Jr. wrote: Sorry. I don't know how that came out to be 2041. Twice, no less. Intended to say 2136. I think the latest was 2140 when I pulled it, and I scrambled that to 2041. Ron, Please update to the lastest 0.6 svn and rebuild. I would start by blowing away the build_i586 directory and possibly the toolchain_build_i586 directory (start with the first and if you still have build problems, blow away both and start fresh). I've been using 2147 here since yesterday. If you update, you'll get at least 2149 which has some ipsec fixes and a newer version of the web gui too. Darrick -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.15/1835 - Release Date: 12/7/2008 4:56 PM -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web
Re: [Astlinux-users] NTP Mixup :: the sequel
32 or 64 bit? Can you cp astlinux.config to .config then do make oldconfig? On Mon, 8 Dec 2008 14:52:24 -0600, Ron Byer Jr. wrote: Darrick, Centos5 kernel 2.6.18-92.1.17.el5 gcc 4.1.2 I restarted with a straight serial build -- no parallel compiles going on. I'm sure this will end up being some noob problem since this is the first time I've building ... I should be able to figure it out. (though not without some questions, I'm sure). rb Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Monday, December 08, 2008 3:00 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip, He's not building trunk, he's building 0.6 svn. Ron, host build system. Darrick Philip Prindeville wrote: This is for a net5501? Or some other target? Currently trunk only builds for the net5501 -Philip Ron Byer Jr. wrote: Darrick, et al: Did as suggested. Updated to 2155, whacked build_i586 and toolchain_build_i586. Still flamed out on iptables build. I'm going to investigate further and see if I can spot the problem, but here is where it heads south: /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIPT_LIB_DIR=\/usr/lib/iptables\ -static -o iptables-restore iptables-restore.c iptables.o extensions/libext.a libiptc/libiptc.a /opt/astlinux-0.6/build_i586/staging_dir/bin/i586-linux-uclibc-gcc -Os -pipe -fomit-frame-pointer -Wall -Wunused -I/opt/astlinux-0.6/build_i586/linux-2.6.20.21-astlinux/include -Iinclude/ -DIPTABLES_VERSION=\1.3.8\ -DNO_SHARED_LIBS=1 -DIP6T_LIB_DIR=\/usr/lib/iptables\ -static -o ip6tables ip6tables-standalone.c ip6tables. /tmp/ccdNp1uR.o: In function `main': iptables-standalone.c:(.text+0x7e): undefined reference to `iptc_commit' iptables-standalone.c:(.text+0x98): undefined reference to `iptc_strerror' iptables.o: In function `for_each_chain': iptables.c:(.text+0x622): undefined reference to `iptc_first_chain' iptables.c:(.text+0x63c): undefined reference to `iptc_next_chain' At first blush, it doesn't appear to be environmental (i.e. my box), but that's still the leading suspect, to be sure. Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Darrick Hartman [mailto:[EMAIL PROTECTED] Sent: Sunday, December 07, 2008 7:47 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Philip Prindeville wrote: Joy? Or no joy? Ron Byer Jr. wrote: Sorry. I don't know how that came out to be 2041. Twice, no less. Intended to say 2136. I think the latest was 2140 when I pulled it, and I scrambled that to 2041. Ron, Please update to the lastest 0.6 svn and rebuild. I would start by blowing away the build_i586 directory and possibly the toolchain_build_i586 directory (start with the first and if you still have build problems, blow away both and start fresh). I've been using 2147 here since yesterday. If you update, you'll get at least 2149 which has some ipsec fixes and a newer version of the web gui too. Darrick -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.15/1835 - Release Date: 12/7/2008 4:56 PM
Re: [Astlinux-users] NTP Mixup :: the sequel
Joy?
Or no joy?
Ron Byer Jr. wrote:
Sorry. I don't know how that came out to be 2041. Twice, no less. Intended
to say 2136. I think the latest was 2140 when I pulled it, and I scrambled
that to 2041.
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 3:05 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Why 2041?
Ron Byer Jr. wrote:
#1)
I'm building 2041, which will take a while.
#2)
Regarding modprobe -l mis-use:
Possibly so, but lsmod makes a mess on the console during boot time. It
still shows ipv6 loaded upon boot.
Status at present:
- With IPV6 commented out in rc.conf, lsmod | grep ipv6 shows ipv6 as a
loaded module, and ntpd bails out.
- For grins, I renamed ipv6.ko in the kernel modules path. Then lsmod |
grep
ipv6 shows no ipv6 loaded, and ntpd starts and works.
- I will try #2041 with ipv6 renamed back when it is cooked.
- I'm still missing something obviously, but I've got a hack-workaround at
present that will keep me quiet and off the list gr.
rb
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 6:55 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
We'll talk about 2131 off-line... :-)
Pick up #2133. This might fix your issue.
-Philip
Darrick Hartman wrote:
Ron,
I've confirmed two things. If ipv6 is NOT enabled, ntpd runs fine.
(restart did not work--fixed in SVN 2131).
You would also have to have IPV6=YES uncommented in rc.conf (it's not
used by default). If you enable IPV6, ntpd does indeed fail.
Darrick
Ron Byer Jr. wrote:
My log entries seem to make it clear that the failure to bind is the
reason. I had read the earlier NTP mixup posts and had decided to post
this when it appeared to be different. It doesn't appear to get that
far. (to comparing time differences).
/var/log/messages
Mar 3 14:28:03 sk3 daemon.info ntpd[1518]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:03 sk3 daemon.err ntpd[1518]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
Mar 3 14:28:04 sk3 daemon.notice ntpd[1520]: ntpd [EMAIL PROTECTED] Sat
Nov 15 06:25:14 UTC 2008 (1)
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: signal_no_reset: signal 13
had flags 400
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: precision = 1.686 usec
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: ntp_io: estimated max
descriptors: 1024, initial socket boundary: 16
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:04 sk3 daemon.err ntpd[1522]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
The end result is a couple of ntpd zombies and a date back in March
1980.
sk3 log # ps -w | grep ntpd
1521 rootZ [ntpd]
1522 rootZ [ntpd]
I modified the ntpd startup script to strace ntpd and found the
following relevant system calls and status:
if nslookup $first /dev/null; then
# Set the clock (large change) and exit
strace -f ntpd -g -q -c /etc/ntpd.conf
sleep 1
# Maintain the clock (small changes)
strace -f ntpd -c /etc/ntpd.conf
The results were as follows. Note the two bind calls IPV4 - works, and
IPV6 - which fails with the EADDRINUSE
setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(16, {sa_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr(0.0.0.0)}
, 16) = 0
setsockopt(16, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
fcntl(16, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
rt_sigaction(SIGPIPE, {0xb7f49762, [], SA_RESTORER, 0xb7f4db48},
{SIG_IGN}, 8)
=
0
time([320960202]) = 320960202
open(/etc/TZ, O_RDONLY) = 4
read(4, EST5EDT\n, 68)= 8
read(4, , 60) = 0
close(4)= 0
getpid()= 1631
write(3, 30Mar 3 14:36:42 ntpd[1631]: ..., 89) = 89
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
close(4)= 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 4
getsockname(4, {sa_family=AF_INET6, sin6_port=htons(0),
inet_pton(AF_INET6, ::
,
sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
close(4)= 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
fcntl(4, F_DUPFD, 16) = 17
close(4
Re: [Astlinux-users] NTP Mixup :: the sequel
Philip Prindeville wrote:
Joy?
Or no joy?
Ron Byer Jr. wrote:
Sorry. I don't know how that came out to be 2041. Twice, no less. Intended
to say 2136. I think the latest was 2140 when I pulled it, and I scrambled
that to 2041.
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 3:05 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Why 2041?
Ron Byer Jr. wrote:
#1)
I'm building 2041, which will take a while.
#2)
Regarding modprobe -l mis-use:
Possibly so, but lsmod makes a mess on the console during boot time. It
still shows ipv6 loaded upon boot.
Status at present:
- With IPV6 commented out in rc.conf, lsmod | grep ipv6 shows ipv6 as a
loaded module, and ntpd bails out.
- For grins, I renamed ipv6.ko in the kernel modules path. Then lsmod |
grep
ipv6 shows no ipv6 loaded, and ntpd starts and works.
- I will try #2041 with ipv6 renamed back when it is cooked.
- I'm still missing something obviously, but I've got a hack-workaround at
present that will keep me quiet and off the list gr.
rb
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 6:55 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
We'll talk about 2131 off-line... :-)
Pick up #2133. This might fix your issue.
-Philip
Darrick Hartman wrote:
Ron,
I've confirmed two things. If ipv6 is NOT enabled, ntpd runs fine.
(restart did not work--fixed in SVN 2131).
You would also have to have IPV6=YES uncommented in rc.conf (it's not
used by default). If you enable IPV6, ntpd does indeed fail.
Darrick
Ron Byer Jr. wrote:
My log entries seem to make it clear that the failure to bind is the
reason. I had read the earlier NTP mixup posts and had decided to post
this when it appeared to be different. It doesn't appear to get that
far. (to comparing time differences).
/var/log/messages
Mar 3 14:28:03 sk3 daemon.info ntpd[1518]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:03 sk3 daemon.err ntpd[1518]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
Mar 3 14:28:04 sk3 daemon.notice ntpd[1520]: ntpd [EMAIL PROTECTED] Sat
Nov 15 06:25:14 UTC 2008 (1)
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: signal_no_reset: signal 13
had flags 400
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: precision = 1.686 usec
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: ntp_io: estimated max
descriptors: 1024, initial socket boundary: 16
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:04 sk3 daemon.err ntpd[1522]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
The end result is a couple of ntpd zombies and a date back in March
1980.
sk3 log # ps -w | grep ntpd
1521 rootZ [ntpd]
1522 rootZ [ntpd]
I modified the ntpd startup script to strace ntpd and found the
following relevant system calls and status:
if nslookup $first /dev/null; then
# Set the clock (large change) and exit
strace -f ntpd -g -q -c /etc/ntpd.conf
sleep 1
# Maintain the clock (small changes)
strace -f ntpd -c /etc/ntpd.conf
The results were as follows. Note the two bind calls IPV4 - works, and
IPV6 - which fails with the EADDRINUSE
setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(16, {sa_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr(0.0.0.0)}
, 16) = 0
setsockopt(16, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
fcntl(16, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
rt_sigaction(SIGPIPE, {0xb7f49762, [], SA_RESTORER, 0xb7f4db48},
{SIG_IGN}, 8)
=
0
time([320960202]) = 320960202
open(/etc/TZ, O_RDONLY) = 4
read(4, EST5EDT\n, 68)= 8
read(4, , 60) = 0
close(4)= 0
getpid()= 1631
write(3, 30Mar 3 14:36:42 ntpd[1631]: ..., 89) = 89
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
close(4)= 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 4
getsockname(4, {sa_family=AF_INET6, sin6_port=htons(0),
inet_pton(AF_INET6, ::
,
sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
close(4)= 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
fcntl(4, F_DUPFD, 16) = 17
close(4
Re: [Astlinux-users] NTP Mixup :: the sequel
#1)
I'm building 2041, which will take a while.
#2)
Regarding modprobe -l mis-use:
Possibly so, but lsmod makes a mess on the console during boot time. It
still shows ipv6 loaded upon boot.
Status at present:
- With IPV6 commented out in rc.conf, lsmod | grep ipv6 shows ipv6 as a
loaded module, and ntpd bails out.
- For grins, I renamed ipv6.ko in the kernel modules path. Then lsmod | grep
ipv6 shows no ipv6 loaded, and ntpd starts and works.
- I will try #2041 with ipv6 renamed back when it is cooked.
- I'm still missing something obviously, but I've got a hack-workaround at
present that will keep me quiet and off the list gr.
rb
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 6:55 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
We'll talk about 2131 off-line... :-)
Pick up #2133. This might fix your issue.
-Philip
Darrick Hartman wrote:
Ron,
I've confirmed two things. If ipv6 is NOT enabled, ntpd runs fine.
(restart did not work--fixed in SVN 2131).
You would also have to have IPV6=YES uncommented in rc.conf (it's not
used by default). If you enable IPV6, ntpd does indeed fail.
Darrick
Ron Byer Jr. wrote:
My log entries seem to make it clear that the failure to bind is the
reason. I had read the earlier NTP mixup posts and had decided to post
this when it appeared to be different. It doesn't appear to get that
far. (to comparing time differences).
/var/log/messages
Mar 3 14:28:03 sk3 daemon.info ntpd[1518]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:03 sk3 daemon.err ntpd[1518]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
Mar 3 14:28:04 sk3 daemon.notice ntpd[1520]: ntpd [EMAIL PROTECTED] Sat
Nov 15 06:25:14 UTC 2008 (1)
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: signal_no_reset: signal 13
had flags 400
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: precision = 1.686 usec
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: ntp_io: estimated max
descriptors: 1024, initial socket boundary: 16
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:04 sk3 daemon.err ntpd[1522]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
The end result is a couple of ntpd zombies and a date back in March 1980.
sk3 log # ps -w | grep ntpd
1521 rootZ [ntpd]
1522 rootZ [ntpd]
I modified the ntpd startup script to strace ntpd and found the
following relevant system calls and status:
if nslookup $first /dev/null; then
# Set the clock (large change) and exit
strace -f ntpd -g -q -c /etc/ntpd.conf
sleep 1
# Maintain the clock (small changes)
strace -f ntpd -c /etc/ntpd.conf
The results were as follows. Note the two bind calls IPV4 - works, and
IPV6 - which fails with the EADDRINUSE
setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(16, {sa_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr(0.0.0.0)}
, 16) = 0
setsockopt(16, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
fcntl(16, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
rt_sigaction(SIGPIPE, {0xb7f49762, [], SA_RESTORER, 0xb7f4db48},
{SIG_IGN}, 8)
=
0
time([320960202]) = 320960202
open(/etc/TZ, O_RDONLY) = 4
read(4, EST5EDT\n, 68)= 8
read(4, , 60) = 0
close(4)= 0
getpid()= 1631
write(3, 30Mar 3 14:36:42 ntpd[1631]: ..., 89) = 89
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
close(4)= 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 4
getsockname(4, {sa_family=AF_INET6, sin6_port=htons(0),
inet_pton(AF_INET6, ::
,
sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
close(4)= 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
fcntl(4, F_DUPFD, 16) = 17
close(4)= 0
setsockopt(17, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(17, {sa_family=AF_INET6, sin6_port=htons(123), inet_pton(AF_INET6,
::, s
in6_addr),
sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EADDRINUSE (Address
alrea
dy in use)
close(17) = 0
rt_sigaction(SIGPIPE, {0xb7f49762, [], SA_RESTORER, 0xb7f4db48},
{SIG_IGN}, 8) =
0
time([320960202]) = 320960202
open(/etc/TZ, O_RDONLY) = 4
read
Re: [Astlinux-users] NTP Mixup :: the sequel
Sorry. I don't know how that came out to be 2041. Twice, no less. Intended
to say 2136. I think the latest was 2140 when I pulled it, and I scrambled
that to 2041.
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Friday, December 05, 2008 3:05 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Why 2041?
Ron Byer Jr. wrote:
#1)
I'm building 2041, which will take a while.
#2)
Regarding modprobe -l mis-use:
Possibly so, but lsmod makes a mess on the console during boot time. It
still shows ipv6 loaded upon boot.
Status at present:
- With IPV6 commented out in rc.conf, lsmod | grep ipv6 shows ipv6 as a
loaded module, and ntpd bails out.
- For grins, I renamed ipv6.ko in the kernel modules path. Then lsmod |
grep
ipv6 shows no ipv6 loaded, and ntpd starts and works.
- I will try #2041 with ipv6 renamed back when it is cooked.
- I'm still missing something obviously, but I've got a hack-workaround at
present that will keep me quiet and off the list gr.
rb
-Original Message-
From: Philip Prindeville [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 6:55 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
We'll talk about 2131 off-line... :-)
Pick up #2133. This might fix your issue.
-Philip
Darrick Hartman wrote:
Ron,
I've confirmed two things. If ipv6 is NOT enabled, ntpd runs fine.
(restart did not work--fixed in SVN 2131).
You would also have to have IPV6=YES uncommented in rc.conf (it's not
used by default). If you enable IPV6, ntpd does indeed fail.
Darrick
Ron Byer Jr. wrote:
My log entries seem to make it clear that the failure to bind is the
reason. I had read the earlier NTP mixup posts and had decided to post
this when it appeared to be different. It doesn't appear to get that
far. (to comparing time differences).
/var/log/messages
Mar 3 14:28:03 sk3 daemon.info ntpd[1518]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:03 sk3 daemon.err ntpd[1518]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
Mar 3 14:28:04 sk3 daemon.notice ntpd[1520]: ntpd [EMAIL PROTECTED] Sat
Nov 15 06:25:14 UTC 2008 (1)
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: signal_no_reset: signal 13
had flags 400
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: precision = 1.686 usec
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: ntp_io: estimated max
descriptors: 1024, initial socket boundary: 16
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:04 sk3 daemon.err ntpd[1522]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
The end result is a couple of ntpd zombies and a date back in March
1980.
sk3 log # ps -w | grep ntpd
1521 rootZ [ntpd]
1522 rootZ [ntpd]
I modified the ntpd startup script to strace ntpd and found the
following relevant system calls and status:
if nslookup $first /dev/null; then
# Set the clock (large change) and exit
strace -f ntpd -g -q -c /etc/ntpd.conf
sleep 1
# Maintain the clock (small changes)
strace -f ntpd -c /etc/ntpd.conf
The results were as follows. Note the two bind calls IPV4 - works, and
IPV6 - which fails with the EADDRINUSE
setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(16, {sa_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr(0.0.0.0)}
, 16) = 0
setsockopt(16, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
fcntl(16, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
rt_sigaction(SIGPIPE, {0xb7f49762, [], SA_RESTORER, 0xb7f4db48},
{SIG_IGN}, 8)
=
0
time([320960202]) = 320960202
open(/etc/TZ, O_RDONLY) = 4
read(4, EST5EDT\n, 68)= 8
read(4, , 60) = 0
close(4)= 0
getpid()= 1631
write(3, 30Mar 3 14:36:42 ntpd[1631]: ..., 89) = 89
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
close(4)= 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 4
getsockname(4, {sa_family=AF_INET6, sin6_port=htons(0),
inet_pton(AF_INET6, ::
,
sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
close(4)= 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
fcntl(4, F_DUPFD, 16) = 17
close(4)= 0
setsockopt(17, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(17, {sa_family=AF_INET6
Re: [Astlinux-users] NTP Mixup :: the sequel
Philip, Thanks for the suggestion. I did the modprobe ipv6 and it had little/no effect. Still failing on the bind (AF_INET6) call. I guess there are two mysteries here, though I would be happy to solve only one of them :: why is it doing the v6 bind call, and, why it is failing. I'm going to do some review of the modules in the trunk-1725 vs the 0.6.2 versions. They both appear to be the same kernel version (2.6.20.21) rb Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Philip Prindeville [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 9:32 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel Ron Byer Jr. wrote: Additional info: ##Master NTP server(s). This is the NTP server that AstLinux will sync against ##upon bootup. It is also the server that the running ntpd process will use ##to maintain that time sync. NTPSERVS=us.pool.ntp.org #NTPSERVS=europe.pool.ntp.org From rc.conf. And us.pool.ntp.org resolves and is reachable: sk3 kd # nslookup us.pool.ntp.org Server: 4.2.2.1 Address 1: 4.2.2.1 vnsc-pri.sys.gtei.net Name: us.pool.ntp.org Address 1: 64.247.17.248 Address 2: 64.247.17.254 Address 3: 65.255.217.202 www.broadbandjam.com Address 4: 66.246.229.52 keeleysam.com Address 5: 64.202.112.75 ntp.your.org sk3 kd # ping us.pool.ntp.org PING us.pool.ntp.org (64.202.112.75): 56 data bytes 64 bytes from 64.202.112.75: seq=0 ttl=54 time=32.928 ms 64 bytes from 64.202.112.75: seq=1 ttl=54 time=32.010 ms 64 bytes from 64.202.112.75: seq=2 ttl=54 time=32.085 ms 64 bytes from 64.202.112.75: seq=3 ttl=54 time=34.437 ms 64 bytes from 64.202.112.75: seq=4 ttl=54 time=32.256 ms Thanks for any insight. What happens if you do a modprobe ipv6 just before starting ntpd? -Philip - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.13/1827 - Release Date: 12/3/2008 5:41 PM - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP Mixup :: the sequel
Lonnie, et al: Do you have the NTP startup issue ? I'm stumped by why this doesn't have more pervasive impact. I'm always ready to find out that it's a cockpit error on my part. Trunk-1725 didn't have the ipv6 module loaded, and there are updates to both rc.conf and /etc/init.d/network to support the loading of the ipv6 module. Attempts to remove the ipv6 modules from the cmd line after boot have been thwarted: modprobe -r ipv6 FATAL: Module ipv6 is in use. I've been fiddling with the network startup script: # IPv6 echo ipv6 is $IPV6... modprobe -l ipv6 if [ -n $IPV6 ]; then echo loading ipv6... modprobe ipv6 else echo removing ipv6... modprobe -r ipv6 fi modprobe -l ipv6 It appears that ipv6 is pre-loaded prior to this, and manages to avoid unloading it. the modprobe -l ipv6 before and after both report that is it loaded. rb -Original Message- From: Lonnie Abelbeck [mailto:[EMAIL PROTECTED] Sent: Thursday, December 04, 2008 12:11 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel On Dec 4, 2008, at 9:11 AM, Ron Byer Jr. wrote: Philip, Thanks for the suggestion. I did the modprobe ipv6 and it had little/ no effect. Still failing on the bind (AF_INET6) call. I guess there are two mysteries here, though I would be happy to solve only one of them :: why is it doing the v6 bind call, and, why it is failing. I'm going to do some review of the modules in the trunk-1725 vs the 0.6.2 versions. They both appear to be the same kernel version (2.6.20.21) rb It does appear IP6 is causing problems... (0.6.2) Simple example: pbx ~ # nslookup localhost Server:10.10.50.1 Address 1: 10.10.50.1 gw-xtra.priv.abelbeck.com Name: localhost Address 1: 7f00:1:f069:aebf:: Address 2: 127.0.0.1 localhost pbx ~ # wget http://localhost Connecting to localhost ([7f00:1:c0b8:bfbf::100:0]:80) wget: socket(AF_INET6): Address family not supported by protocol pbx ~ # telnet localhost telnet: socket(AF_INET6): Address family not supported by protocol Lonnie - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.13/1827 - Release Date: 12/3/2008 5:41 PM - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP Mixup :: the sequel
No change. Still fails on the ipv6 bind. Ron Byer Jr. NetWeave Integrated Solutions, Inc. +1.732.786.8830 x120 -Original Message- From: Lonnie Abelbeck [mailto:[EMAIL PROTECTED] Sent: Thursday, December 04, 2008 2:11 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel On Dec 4, 2008, at 12:38 PM, Ron Byer Jr. wrote: Lonnie, et al: Do you have the NTP startup issue ? I'm stumped by why this doesn't have more pervasive impact. I'm always ready to find out that it's a cockpit error on my part. No problem here, but I run my own NTP server with only IPv4 DNS. Try a single server like ntp3.cs.wisc.edu and see if that works for you. Lonnie - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED] No virus found in this incoming message. Checked by AVG. Version: 7.5.552 / Virus Database: 270.9.13/1827 - Release Date: 12/3/2008 5:41 PM -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP Mixup :: the sequel
Ron Byer Jr. wrote: Lonnie, et al: Do you have the NTP startup issue ? I'm stumped by why this doesn't have more pervasive impact. I'm always ready to find out that it's a cockpit error on my part. Trunk-1725 didn't have the ipv6 module loaded, and there are updates to both rc.conf and /etc/init.d/network to support the loading of the ipv6 module. Attempts to remove the ipv6 modules from the cmd line after boot have been thwarted: modprobe -r ipv6 FATAL: Module ipv6 is in use. I've been fiddling with the network startup script: # IPv6 echo ipv6 is $IPV6... modprobe -l ipv6 if [ -n $IPV6 ]; then echo loading ipv6... modprobe ipv6 else echo removing ipv6... modprobe -r ipv6 fi modprobe -l ipv6 It appears that ipv6 is pre-loaded prior to this, and manages to avoid unloading it. the modprobe -l ipv6 before and after both report that is it loaded. rb -Original Message- From: Lonnie Abelbeck [mailto:[EMAIL PROTECTED] Sent: Thursday, December 04, 2008 12:11 PM To: AstLinux Users Mailing List Subject: Re: [Astlinux-users] NTP Mixup :: the sequel On Dec 4, 2008, at 9:11 AM, Ron Byer Jr. wrote: Philip, Thanks for the suggestion. I did the modprobe ipv6 and it had little/ no effect. Still failing on the bind (AF_INET6) call. I guess there are two mysteries here, though I would be happy to solve only one of them :: why is it doing the v6 bind call, and, why it is failing. I'm going to do some review of the modules in the trunk-1725 vs the 0.6.2 versions. They both appear to be the same kernel version (2.6.20.21) rb It does appear IP6 is causing problems... (0.6.2) Simple example: pbx ~ # nslookup localhost Server:10.10.50.1 Address 1: 10.10.50.1 gw-xtra.priv.abelbeck.com Name: localhost Address 1: 7f00:1:f069:aebf:: Address 2: 127.0.0.1 localhost pbx ~ # wget http://localhost Connecting to localhost ([7f00:1:c0b8:bfbf::100:0]:80) wget: socket(AF_INET6): Address family not supported by protocol pbx ~ # telnet localhost telnet: socket(AF_INET6): Address family not supported by protocol Lonnie Once sockets are open in the AF_INET6 space, it can't be closed because its reference count will be non-zero. Hmmm... too bad we don't have lsof as part of the standard distro. -Philip -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP Mixup :: the sequel
My log entries seem to make it clear that the failure to bind is the reason.
I had read the earlier NTP mixup posts and had decided to post this when it
appeared to be different. It doesn't appear to get that far. (to comparing
time differences).
/var/log/messages
Mar 3 14:28:03 sk3 daemon.info ntpd[1518]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:03 sk3 daemon.err ntpd[1518]: unable to bind to wildcard socket
address :: - another process may be running - EXITING
Mar 3 14:28:04 sk3 daemon.notice ntpd[1520]: ntpd [EMAIL PROTECTED] Sat Nov 15
06:25:14 UTC 2008 (1)
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: signal_no_reset: signal 13 had
flags 400
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: precision = 1.686 usec
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: ntp_io: estimated max
descriptors: 1024, initial socket boundary: 16
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:04 sk3 daemon.err ntpd[1522]: unable to bind to wildcard socket
address :: - another process may be running - EXITING
The end result is a couple of ntpd zombies and a date back in March 1980.
sk3 log # ps -w | grep ntpd
1521 rootZ [ntpd]
1522 rootZ [ntpd]
I modified the ntpd startup script to strace ntpd and found the following
relevant system calls and status:
if nslookup $first /dev/null; then
# Set the clock (large change) and exit
strace -f ntpd -g -q -c /etc/ntpd.conf
sleep 1
# Maintain the clock (small changes)
strace -f ntpd -c /etc/ntpd.conf
The results were as follows. Note the two bind calls IPV4 - works, and IPV6
- which fails with the EADDRINUSE
setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(16, {sa_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr(0.0.0.0)}
, 16) = 0
setsockopt(16, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
fcntl(16, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
rt_sigaction(SIGPIPE, {0xb7f49762, [], SA_RESTORER, 0xb7f4db48}, {SIG_IGN},
8) =
0
time([320960202]) = 320960202
open(/etc/TZ, O_RDONLY) = 4
read(4, EST5EDT\n, 68)= 8
read(4, , 60) = 0
close(4)= 0
getpid()= 1631
write(3, 30Mar 3 14:36:42 ntpd[1631]: ..., 89) = 89
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 4
close(4)= 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 4
getsockname(4, {sa_family=AF_INET6, sin6_port=htons(0), inet_pton(AF_INET6,
::
, sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 0
close(4)= 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_IP) = 4
fcntl(4, F_DUPFD, 16) = 17
close(4)= 0
setsockopt(17, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(17, {sa_family=AF_INET6, sin6_port=htons(123), inet_pton(AF_INET6,
::, s
in6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EADDRINUSE (Address
alrea
dy in use)
close(17) = 0
rt_sigaction(SIGPIPE, {0xb7f49762, [], SA_RESTORER, 0xb7f4db48}, {SIG_IGN},
8) =
0
time([320960202]) = 320960202
open(/etc/TZ, O_RDONLY) = 4
read(4, EST5EDT\n, 68)= 8
read(4, , 60) = 0
close(4)= 0
getpid()= 1631
write(3, 27Mar 3 14:36:42 ntpd[1631]: ..., 120) = 120
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
_exit(1)= ?
Process 1631 detached
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message-
From: Tod Fitch [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 3:47 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
I don't have access to my net5501 AstLinux box from here. I will get
around to reconfiguring my VPN sometime, I promise. :)
So this is from memory...
I believe that my ntpd was also unable to bind to ipv6, but that is
not what was causing it to quit. What was causing it to quit was that
the hardware clock time was more than 1000 seconds different from the
correct time. The work around was to stop zaptel, start rtc, set the
date to something close the correct time, use hwclock to write the
good time into the hardware clock then start up ntpd and zaptel.
Do your log entries show that failing to bind to the ipv6 port caused
the daemon to exit or did it exit later with a time error too large
type of error?
--Tod
On Dec 4, 2008, at 12:30 PM, Ron Byer Jr. wrote:
No change. Still fails on the ipv6 bind.
Ron Byer Jr.
NetWeave Integrated Solutions, Inc.
+1.732.786.8830 x120
-Original Message
Re: [Astlinux-users] NTP Mixup :: the sequel
Ron Byer Jr. wrote:
Darrick,
Thanks for the response. I'm sorry to be using up so much list bandwidth
today.
I *think* that's a bit different than I'm seeing. I stumbled across this
issue with the vanilla setting for IPV6 in rc.conf (commented out). I then
tried uncommenting it and setting it to NO (IPV6=NO), to no avail. The test
in the network (etc/init.d/network) script made it pretty clear that it
needs to be either NULL or undefined.
You said you verified it, and I certainly believe you. I've just got to see
what the difference is between the two environments.
What I'm seeing is that the module ipv6 is already loaded when I come into
the network script. (see below).
A simple question is as follows:
If IPV6 is commented out in rc.conf, then should ipv6 be loaded ?
==
# IPv6
echo ipv6 is $IPV6...
modprobe -l ipv6
if [ -n $IPV6 ]; then
echo loading ipv6...
modprobe ipv6
else
echo removing ipv6...
modprobe -r ipv6
fi
modprobe -l ipv6
produces
ipv6 is ...
/lib/modules/2.6.20.21-astlinux/kernel/net/ipv6/ipv6.ko
removing ipv6...
/lib/eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
modules/2.6.20.21-astlinux/kernel/net/ipv6/ipv6.eth0: link up, 10Mbps,
half-dup1
ko
=
I'll keep digging for insight into this.
Whoa! Hang on there! I think you're confused about what modprobe -l
does.
It's the same as a modinfo (just less verbose, i.e. modinfo xxx | awk
'/^filename:/ { print $2; }').
You want lsmod | grep ipv6 As in:
[EMAIL PROTECTED] ~/kernel]$ lsmod | grep nf_conntrack_sane
[EMAIL PROTECTED] ~/kernel]$ modprobe -l nf_conntrack_sane
/lib/modules/2.6.25.14-69.fc8/kernel/net/netfilter/nf_conntrack_sane.ko
[EMAIL PROTECTED] ~/kernel]$ lsmod | grep nf_conntrack_sane
[EMAIL PROTECTED] ~/kernel]$ modinfo nf_conntrack_sane
filename:
/lib/modules/2.6.25.14-69.fc8/kernel/net/netfilter/nf_conntrack_sane.ko
description:SANE connection tracking helper
author: Michal Schmidt [EMAIL PROTECTED]
license:GPL
srcversion: AE4A999ADC6D20AC4B75C43
depends:nf_conntrack
vermagic: 2.6.25.14-69.fc8 SMP mod_unload 686 4KSTACKS
parm: ports:array of ushort
[EMAIL PROTECTED] ~/kernel]$
rb
-Original Message-
From: Darrick Hartman [mailto:[EMAIL PROTECTED]
Sent: Thursday, December 04, 2008 5:00 PM
To: AstLinux Users Mailing List
Subject: Re: [Astlinux-users] NTP Mixup :: the sequel
Ron,
I've confirmed two things. If ipv6 is NOT enabled, ntpd runs fine.
(restart did not work--fixed in SVN 2131).
You would also have to have IPV6=YES uncommented in rc.conf (it's not
used by default). If you enable IPV6, ntpd does indeed fail.
Darrick
Ron Byer Jr. wrote:
My log entries seem to make it clear that the failure to bind is the
reason. I had read the earlier NTP mixup posts and had decided to post
this when it appeared to be different. It doesn't appear to get that
far. (to comparing time differences).
/var/log/messages
Mar 3 14:28:03 sk3 daemon.info ntpd[1518]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:03 sk3 daemon.err ntpd[1518]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
Mar 3 14:28:04 sk3 daemon.notice ntpd[1520]: ntpd [EMAIL PROTECTED] Sat
Nov 15 06:25:14 UTC 2008 (1)
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: signal_no_reset: signal 13
had flags 400
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: precision = 1.686 usec
Mar 3 14:28:04 sk3 daemon.debug ntpd[1522]: ntp_io: estimated max
descriptors: 1024, initial socket boundary: 16
Mar 3 14:28:04 sk3 daemon.info ntpd[1522]: Listening on interface #0
wildcard, 0.0.0.0#123 Disabled
Mar 3 14:28:04 sk3 daemon.err ntpd[1522]: unable to bind to wildcard
socket address :: - another process may be running - EXITING
The end result is a couple of ntpd zombies and a date back in March 1980.
sk3 log # ps -w | grep ntpd
1521 rootZ [ntpd]
1522 rootZ [ntpd]
I modified the ntpd startup script to strace ntpd and found the
following relevant system calls and status:
if nslookup $first /dev/null; then
# Set the clock (large change) and exit
strace -f ntpd -g -q -c /etc/ntpd.conf
sleep 1
# Maintain the clock (small changes)
strace -f ntpd -c /etc/ntpd.conf
The results were as follows. Note the two bind calls IPV4 - works, and
IPV6 - which fails with the EADDRINUSE
setsockopt(16, SOL_SOCKET, SO_REUSEADDR, [0], 4) = 0
bind(16, {sa_family=AF_INET, sin_port=htons(123),
sin_addr=inet_addr(0.0.0.0)}
, 16) = 0
setsockopt(16, SOL_SOCKET
[Astlinux-users] NTP Mixup :: the sequel
Additional info: ##Master NTP server(s). This is the NTP server that AstLinux will sync against ##upon bootup. It is also the server that the running ntpd process will use ##to maintain that time sync. NTPSERVS=us.pool.ntp.org #NTPSERVS=europe.pool.ntp.org From rc.conf. And us.pool.ntp.org resolves and is reachable: sk3 kd # nslookup us.pool.ntp.org Server:4.2.2.1 Address 1: 4.2.2.1 vnsc-pri.sys.gtei.net Name: us.pool.ntp.org Address 1: 64.247.17.248 Address 2: 64.247.17.254 Address 3: 65.255.217.202 www.broadbandjam.com Address 4: 66.246.229.52 keeleysam.com Address 5: 64.202.112.75 ntp.your.org sk3 kd # ping us.pool.ntp.org PING us.pool.ntp.org (64.202.112.75): 56 data bytes 64 bytes from 64.202.112.75: seq=0 ttl=54 time=32.928 ms 64 bytes from 64.202.112.75: seq=1 ttl=54 time=32.010 ms 64 bytes from 64.202.112.75: seq=2 ttl=54 time=32.085 ms 64 bytes from 64.202.112.75: seq=3 ttl=54 time=34.437 ms 64 bytes from 64.202.112.75: seq=4 ttl=54 time=32.256 ms Thanks for any insight. image001.jpg- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP mixup
Tod Fitch wrote: On Nov 28, 2008, at 11:10 AM, Michael Keuter wrote: For AstLinux v0.6.2, I was attempting to setup my box as a firewall/router. Ran into troubles (worry about that later) then reconfigured as best I could back to having only an EXT_IF with static IP to resume use as only a Asterisk server. But now the NTP setting does not appear to work. I have the default us.pool.ntp.org server set but the box insists that it is February of 1980. Here is the /etc/ntpd.conf file that is on the box and it looks okay to me pbx ~ # more /etc/ntpd.conf # Autogenerated. Do not edit. restrict default noquery nopeer notrap nomodify restrict 127.0.0.1 # NTPd server us.pool.ntp.org driftfile /var/db/ntpd.drift # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. server127.127.1.0# local clock fudge127.127.1.0 stratum 10 pbx ~ # date Fri Feb 1 12:59:48 PST 1980 I don't see ntpdate or the other tools I am used to working with in the path, so am a little bit slow on this. Any ideas? Thanks! Hi Tod, just for info, are you using the geni386-image? Because I also had this ntp problems in the past (starting with a runnix based Astlinux) but only on geni386. The net4801 and net5501 versions (in the same network (all with static IP)) had no problems. Michael This was with the 0.6.2 net5501 image file. Everything was working well until I started trying to set up the box to replace my firewall and I got it bollixed up. There might be follow on queries about setting up a dual WAN firewall. :) So, at present, the box is setup to have a static address on my LAN with the firewall disabled. Calls are working fine, so I'd rather not re-image the machine and start over on the configuration. Thanks! Tod Which firewall are you using, and is UDP port 123 open? If you're using Arno's firewall, then set OPEN_UDP=123 in /etc/arno-iptables-firewall/firewall.conf ... Also, did you try setting your hardware clock to the correct time? You can set the time manually with date, and then run hwclock -wu after doing a /etc/init.d/zaptel stop ... -Philip - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP mixup
On Nov 29, 2008, at 8:33 AM, Philip Prindeville wrote: Which firewall are you using, and is UDP port 123 open? If you're using Arno's firewall, then set OPEN_UDP=123 in /etc/arno-iptables-firewall/firewall.conf ... Also, did you try setting your hardware clock to the correct time? You can set the time manually with date, and then run hwclock -wu after doing a /etc/init.d/zaptel stop ... -Philip I am back to running with no firewall but it would be good to remember to open up the NTP port when running one. hwclock fails on this net5501, there is no /dev/misc directory on this system: pbx ~ # hwclock -wu hwclock: can't open '/dev/misc/rtc': No such file or directory From the man page for hwclock it looks like /dev/rtc is where it will attempt to access the hardware clock. That exists but is busy even if I stop the ntpd service. Since ntpd is now running and the time has been accurate and stable overnight, I think I will take a wait and monitor stance on this. Thank you for you help. --Tod smime.p7s Description: S/MIME cryptographic signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP mixup
Tod Fitch wrote: On Nov 29, 2008, at 8:33 AM, Philip Prindeville wrote: Which firewall are you using, and is UDP port 123 open? If you're using Arno's firewall, then set OPEN_UDP=123 in /etc/arno-iptables-firewall/firewall.conf ... Also, did you try setting your hardware clock to the correct time? You can set the time manually with date, and then run hwclock -wu after doing a /etc/init.d/zaptel stop ... -Philip I am back to running with no firewall but it would be good to remember to open up the NTP port when running one. hwclock fails on this net5501, there is no /dev/misc directory on this system: pbx ~ # hwclock -wu hwclock: can't open '/dev/misc/rtc': No such file or directory From the man page for hwclock it looks like /dev/rtc is where it will attempt to access the hardware clock. That exists but is busy even if I stop the ntpd service. Since ntpd is now running and the time has been accurate and stable overnight, I think I will take a wait and monitor stance on this. Zaptel has to be stopped or it will block updating the hwclock. It looks like 'rtc' is not being loaded (the module). If you do a 'modprobe rtc' you'll have the rtc loaded properly. (this appears to happen on all architectures--so we'll have to fix that). The /etc/rc script has a line that reads: ' if [ -r /dev/rtc ]; then modprobe rtc hwclock -sl fi' Well since we're using udev, the device is created AFTER the module is inserted. We'll have to update the rc file to handle this properly. Darrick - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
[Astlinux-users] NTP mixup
For AstLinux v0.6.2, I was attempting to setup my box as a firewall/ router. Ran into troubles (worry about that later) then reconfigured as best I could back to having only an EXT_IF with static IP to resume use as only a Asterisk server. But now the NTP setting does not appear to work. I have the default us.pool.ntp.org server set but the box insists that it is February of 1980. Here is the /etc/ntpd.conf file that is on the box and it looks okay to me pbx ~ # more /etc/ntpd.conf # Autogenerated. Do not edit. restrict default noquery nopeer notrap nomodify restrict 127.0.0.1 # NTPd server us.pool.ntp.org driftfile /var/db/ntpd.drift # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. server127.127.1.0# local clock fudge127.127.1.0 stratum 10 pbx ~ # date Fri Feb 1 12:59:48 PST 1980 I don't see ntpdate or the other tools I am used to working with in the path, so am a little bit slow on this. Any ideas? Thanks! smime.p7s Description: S/MIME cryptographic signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP mixup
Tod Fitch wrote: For AstLinux v0.6.2, I was attempting to setup my box as a firewall/router. Ran into troubles (worry about that later) then reconfigured as best I could back to having only an EXT_IF with static IP to resume use as only a Asterisk server. But now the NTP setting does not appear to work. I have the default us.pool.ntp.org server set but the box insists that it is February of 1980. Here is the /etc/ntpd.conf file that is on the box and it looks okay to me pbx ~ # more /etc/ntpd.conf # Autogenerated. Do not edit. restrict default noquery nopeer notrap nomodify restrict 127.0.0.1 # NTPd server us.pool.ntp.org driftfile /var/db/ntpd.drift # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. server127.127.1.0# local clock fudge127.127.1.0 stratum 10 pbx ~ # date Fri Feb 1 12:59:48 PST 1980 I don't see ntpdate or the other tools I am used to working with in the path, so am a little bit slow on this. Any ideas? Thanks! Is name service up and running at that point? It might not be able to resolve us.pool.ntp.org ... - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP mixup
Content-Type: multipart/signed; boundary=Apple-Mail-1-476342321; micalg=sha1; protocol=application/pkcs7-signature For AstLinux v0.6.2, I was attempting to setup my box as a firewall/router. Ran into troubles (worry about that later) then reconfigured as best I could back to having only an EXT_IF with static IP to resume use as only a Asterisk server. But now the NTP setting does not appear to work. I have the default us.pool.ntp.org server set but the box insists that it is February of 1980. Here is the /etc/ntpd.conf file that is on the box and it looks okay to me pbx ~ # more /etc/ntpd.conf # Autogenerated. Do not edit. restrict default noquery nopeer notrap nomodify restrict 127.0.0.1 # NTPd server us.pool.ntp.org driftfile /var/db/ntpd.drift # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. server127.127.1.0# local clock fudge127.127.1.0 stratum 10 pbx ~ # date Fri Feb 1 12:59:48 PST 1980 I don't see ntpdate or the other tools I am used to working with in the path, so am a little bit slow on this. Any ideas? Thanks! Hi Tod, just for info, are you using the geni386-image? Because I also had this ntp problems in the past (starting with a runnix based Astlinux) but only on geni386. The net4801 and net5501 versions (in the same network (all with static IP)) had no problems. Michael -- Email: mailto:[EMAIL PROTECTED] - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP mixup
On Nov 28, 2008, at 11:10 AM, Michael Keuter wrote: For AstLinux v0.6.2, I was attempting to setup my box as a firewall/router. Ran into troubles (worry about that later) then reconfigured as best I could back to having only an EXT_IF with static IP to resume use as only a Asterisk server. But now the NTP setting does not appear to work. I have the default us.pool.ntp.org server set but the box insists that it is February of 1980. Here is the /etc/ntpd.conf file that is on the box and it looks okay to me pbx ~ # more /etc/ntpd.conf # Autogenerated. Do not edit. restrict default noquery nopeer notrap nomodify restrict 127.0.0.1 # NTPd server us.pool.ntp.org driftfile /var/db/ntpd.drift # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. server127.127.1.0# local clock fudge127.127.1.0 stratum 10 pbx ~ # date Fri Feb 1 12:59:48 PST 1980 I don't see ntpdate or the other tools I am used to working with in the path, so am a little bit slow on this. Any ideas? Thanks! Hi Tod, just for info, are you using the geni386-image? Because I also had this ntp problems in the past (starting with a runnix based Astlinux) but only on geni386. The net4801 and net5501 versions (in the same network (all with static IP)) had no problems. Michael This was with the 0.6.2 net5501 image file. Everything was working well until I started trying to set up the box to replace my firewall and I got it bollixed up. There might be follow on queries about setting up a dual WAN firewall. :) So, at present, the box is setup to have a static address on my LAN with the firewall disabled. Calls are working fine, so I'd rather not re-image the machine and start over on the configuration. Thanks! Tod smime.p7s Description: S/MIME cryptographic signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
Re: [Astlinux-users] NTP mixup
On Nov 28, 2008, at 10:19 AM, Philip Prindeville wrote: Tod Fitch wrote: For AstLinux v0.6.2, I was attempting to setup my box as a firewall/router. Ran into troubles (worry about that later) then reconfigured as best I could back to having only an EXT_IF with static IP to resume use as only a Asterisk server. But now the NTP setting does not appear to work. I have the default us.pool.ntp.org server set but the box insists that it is February of 1980. Here is the /etc/ntpd.conf file that is on the box and it looks okay to me pbx ~ # more /etc/ntpd.conf # Autogenerated. Do not edit. restrict default noquery nopeer notrap nomodify restrict 127.0.0.1 # NTPd server us.pool.ntp.org driftfile /var/db/ntpd.drift # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. server127.127.1.0# local clock fudge127.127.1.0 stratum 10 pbx ~ # date Fri Feb 1 12:59:48 PST 1980 I don't see ntpdate or the other tools I am used to working with in the path, so am a little bit slow on this. Any ideas? Thanks! Is name service up and running at that point? It might not be able to resolve us.pool.ntp.org ... It looks like ntpd is dead at the moment. Here are the last /var/log/ messages entries associated with ntp: Feb 1 01:19:42 pbx daemon.info ntpd[1367]: synchronized to LOCAL(0), stratum 10 Feb 1 01:19:42 pbx daemon.notice ntpd[1367]: time slew +0.00 s Feb 1 01:19:43 pbx daemon.notice ntpd[1371]: ntpd [EMAIL PROTECTED] Wed Nov 26 06:26:44 UTC 2008 (1) Feb 1 01:19:43 pbx daemon.debug ntpd[1373]: signal_no_reset: signal 13 had flags 400 Feb 1 01:19:43 pbx daemon.info ntpd[1373]: precision = 1.941 usec Feb 1 01:19:43 pbx daemon.debug ntpd[1373]: ntp_io: estimated max descriptors: 1024, initial socket boundary: 16 Feb 1 01:19:43 pbx daemon.info ntpd[1373]: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled Feb 1 01:19:43 pbx daemon.info ntpd[1373]: Listening on interface #1 lo, 127.0.0.1#123 Enabled Feb 1 01:19:43 pbx daemon.info ntpd[1373]: Listening on interface #2 eth2, 10.7.52.131#123 Enabled Feb 1 01:19:43 pbx daemon.info ntpd[1373]: kernel time sync status 0040 Feb 1 01:22:56 pbx daemon.info ntpd[1373]: synchronized to LOCAL(0), stratum 10 Feb 1 01:22:56 pbx daemon.notice ntpd[1373]: kernel time sync status change 0001 Feb 1 01:24:02 pbx daemon.info ntpd[1373]: synchronized to 64.113.33.2, stratum 2 Feb 1 01:24:02 pbx daemon.err ntpd[1373]: time correction of 909604803 seconds exceeds sanity limit (1000); set clock manually to the correct UTC time. It looks like ntpd is dead at the moment, which fits with my recollection on what ntpd would do if the jump is too big. It is also my recollection that date does not set things up correctly for ntpd which is why I was looking for ntpdate. And the time server is accessible: pbx ~ # ps -w | grep ntp 1652 root 1040 S grep ntp pbx ~ # ping us.pool.ntp.org PING us.pool.ntp.org (64.247.17.250): 56 data bytes 64 bytes from 64.247.17.250: seq=1 ttl=48 time=109.185 ms 64 bytes from 64.247.17.250: seq=2 ttl=49 time=102.013 ms 64 bytes from 64.247.17.250: seq=3 ttl=48 time=100.480 ms 64 bytes from 64.247.17.250: seq=4 ttl=49 time=99.754 ms 64 bytes from 64.247.17.250: seq=5 ttl=48 time=99.503 ms I have manually set the date to be close using the date command and then did a service ntpd start. Maybe that will be enough to get things going properly. Thanks for the suggestions! smime.p7s Description: S/MIME cryptographic signature - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
