Freebsd 10 to 11 sendmail compile issues..
Hopefully someone can help or give me a pointer to a solution to this one. Running FreeBSD 10.3 and figured I would do a source build and jump to FreeBSD 11.1. For the most part this seemed to be going well, but when it goes to compile sendmail, it spits out the following error: bmake[4]: "/usr/src/share/mk/src.libnames.mk" line 391: /usr/src/libexec/mail.local: These libraries should be LIBADD+=foo rather than DPADD/LDADD+=-lfoo: ssl crypto I have the following flags in /etc/make.conf: SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS SENDMAIL_LDFLAGS= -L/usr/local/lib SENDMAIL_LDADD= -lsasl2 -lssl -lcrypto So I trhought OK, simple enough looking at the error and changed this over to the following: SENDMAIL_CFLAGS= -I/usr/local/include -DSASL=2 -DDNSMAP -DSTARTTLS SENDMAIL_LDFLAGS= -L/usr/local/lib SENDMAIL_LIBADD+= sasl2 ssl crypto After that the error received was that I didn't has sasl2: --- ELF/Arch/AMDGPU.o --- c++ -O2 -pipe -march=nocona -I/usr/src/contrib/llvm/tools/lld/ELF -I/usr/src/contrib/llvm/tools/lld/include -I/usr/obj/usr/src/usr.bin/clang/lld -I/usr/obj/usr/src/lib/clang/libllvm -I/usr/src/lib/clang/include -I/usr/src/contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DNDEBUG -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd11.1\" -DLLVM_HOST_TRIPLE=\"x86_64-unknown-freebsd11.1\" -DDEFAULT_SYSROOT=\"\" -ffunction-sections -fdata-sections -g -MD -MF.depend.ELF_Arch_AMDGPU.o -MTELF/Arch/AMDGPU.o -fstack-protector-strong -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable -Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function -Wno-enum-conversion -Wno-unused-local-typedef -Wno-address-of-packed-member -Wno-switch -Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses -Qunused-arguments -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++ -Wno-c++11-extensions -c /usr/src/contrib/llvm/tools/lld/ELF/Arch/AMDGPU.cpp -o ELF/Arch/AMDGPU.o --- all_subdir_usr.sbin --- deliver.o: In function `endmailer': /usr/src/contrib/sendmail/src/deliver.c:3874: undefined reference to `sasl_dispose' deliver.o: In function `deliver': /usr/src/contrib/sendmail/src/deliver.c:3137: undefined reference to `sasl_getprop' main.o: In function `main': /usr/src/contrib/sendmail/src/main.c:2303: undefined reference to `sasl_server_init' /usr/src/contrib/sendmail/src/main.c:2305: undefined reference to `sasl_errstring' sasl.o: In function `sm_sasl_init': /usr/src/contrib/sendmail/src/sasl.c:146: undefined reference to `sasl_set_alloc' sfsasl.o: In function `sasl_read': /usr/src/contrib/sendmail/src/sfsasl.c:224: undefined reference to `sasl_decode' sfsasl.o: In function `sasl_write': /usr/src/contrib/sendmail/src/sfsasl.c:311: undefined reference to `sasl_getprop' /usr/src/contrib/sendmail/src/sfsasl.c:316: undefined reference to `sasl_encode' srvrsmtp.o: In function `smtp': /usr/src/contrib/sendmail/src/srvrsmtp.c:951: undefined reference to `sasl_server_new' /usr/src/contrib/sendmail/src/srvrsmtp.c:1004: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1018: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1069: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1081: undefined reference to `sasl_setprop' /usr/src/contrib/sendmail/src/srvrsmtp.c:1083: undefined reference to `sasl_setprop' srvrsmtp.o:/usr/src/contrib/sendmail/src/srvrsmtp.c:2254: more undefined references to `sasl_setprop' follow So apparently that change seems to be including ssl and crypto but not sasl2 for some reason. I have googled looking for examples of how to correct it, but everything I find shows the original way I had it to start with, and clearly that is no longer working. Any ideas on how I need to define this would be most appreciated.. --- Howard Leadmon PBW Communications, LLC http://www.pbwcomm.com ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Errors with ports on 9.3..
Thanks for the update, I had the feeling the issue was from it being to old. I have a question, not sure if you know, but I will toss it out. As I mentioned I update using svn for both src and ports, and I am curious to know if I can actually bring my src tree up to the most current 10.x stable, recompile, and install and have it all run? In the past with much older versions, I know file system changes and such make it pretty hard to jump major revisions, so have a little bit of fear about jumping from 9.x to 10.x, and possibly even to 11.x if that is now stable. I am using ZFS, so I guess that would be one thing that is outside the norm, but should be part of the base kernels now anyway. Any input on upgrading would be most appreciated... --- Howard Leadmon PBW Communications, LLC http://www.pbwcomm.com On 6/3/2017 1:08 PM, Mark Saad wrote: Howard There are 3 options . One upgrade to 10.x or 11.x and ports/pkg will work . Support for the 9 series and 10.1 and 10.2 was removed from ports a few months ago . Two check out ports via svn and use the tag RELEASE_9_EOL and use that as your starting point . This is ports before the support for 9 was dropped . It's not up to date but it will work .Lastly you could use pkgsrc from netbsd not Joynet , and do a full rebuild of what you need . Pkgsrc also has a pkgsrc to ports conversion tool if you want the subsequent pkgsrc packages registered in a FreeBSD standard pkg dir . This would work if you haven't converted 9 to use pkgng . https://svnweb.freebsd.org/ports/tags/RELEASE_9_EOL/ https://www.pkgsrc.org/ --- Mark Saad | nones...@longcount.org On Jun 3, 2017, at 11:39 AM, Howard Leadmon <how...@leadmon.net> wrote: I know 9.3 is kinda dated, but it had been running fine so I left the servers alone as they were in a remote location many hours away. That said, if I try and do anything with ports (I keep everything updated using SVN), I get the following error: "/usr/ports/Mk/bsd.port.mk", line 1038: Unknown directive The line is: .export LANG LC_ALL I even tried removing the ports tree, and bringing it all back down, but same error. Maybe my googlefu is failing me, but I couldn't find this exact error listed anyplace. I have a couple FBSD 9.3 machines still in existence, and they all do this with anything in ports now. Any ideas or suggestions? Would just taking SVN to the current 10.x fix this? --- Howard Leadmon PBW Communications, LLC http://www.pbwcomm.com ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Errors with ports on 9.3..
I know 9.3 is kinda dated, but it had been running fine so I left the servers alone as they were in a remote location many hours away. That said, if I try and do anything with ports (I keep everything updated using SVN), I get the following error: "/usr/ports/Mk/bsd.port.mk", line 1038: Unknown directive The line is: .export LANG LC_ALL I even tried removing the ports tree, and bringing it all back down, but same error. Maybe my googlefu is failing me, but I couldn't find this exact error listed anyplace. I have a couple FBSD 9.3 machines still in existence, and they all do this with anything in ports now. Any ideas or suggestions? Would just taking SVN to the current 10.x fix this? --- Howard Leadmon PBW Communications, LLC http://www.pbwcomm.com ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FBSD 8.0 ZFS Issue.. default_perms_for_dir
I just did a cvsup and updated my amd64 8.0-STABLE machine, and after rebooting with the new kernel and all I am seeing the following on directory access: default_perms_for_dir: sys_acl_get_file(., ACL_TYPE_DEFAULT): Invalid argument, falling back on umask default_perms_for_dir: sys_acl_get_file(., ACL_TYPE_DEFAULT): Invalid argument, falling back on umask Now I know it wasn't doing this before, so something has apparently changed since the update and rebuild. Has anyone run into this issue, or machine something that is known in the current STABLE source tree? Just not sure if this is something I got to worry about, but not really sure how to go about fixing it either.. --- Howard Leadmon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: Kernel Build Issues with latest cvsup of both a 7.2 system, and a 6.4 system..
As a follow-up to my original message, and I thank the couple people that did respond with suggestions. I seem to have found the issue, which is apparently cvsup17.FreeBSD.org and some file inconsistency. I was using cvsup17 as it was a very close site hop/ping wise on my various servers, in fact I even ran the cvsup several times against cvsup17 over a couple different days (this has always been fine in the past). Still neither my 7.2 or 6.4 server would compile a kernel without the errors show in my original message. I then changed my cvsup to point to cvsup8.FreeBSD.org, and of course ran a cvsup against the cvsup8 server which did make a batch of updates. After that I then attempted to build a kernel on both my 7.2 and my 6.4 servers, and bingo it all worked perfectly. So I can only assume from this, something is out of sync and not right with the cvsup17 server, not sure if any others are using cvsup17 and having any issues, but I apparently am. Not sure who this should be reported to, so someone can check on the integrity of cvsup17.. --- Howard Leadmon -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Howard Leadmon Sent: Monday, October 12, 2009 7:31 AM To: freebsd-stable@freebsd.org Subject: Kernel Build Issues with latest cvsup of both a 7.2 system,and a 6.4 system.. Not sure if I am just having a run of bad luck here, but I have a bunch of various free BSD boxen on both 6.4-STABLE, and on 7.2-STABLE. I try and make it a point to do a cvsup and update the machines every month or so to keep things current and any updates/patches installed. I decided a couple days ago, it was again time to do this again. So I ran cvsup on the machines, and set out to rebuild, first doing a 'make buildworld', then a 'make installworld', and finally a 'mergemaster' on the servers. That all went well, then time for a kernel update, so I performed a 'make buildkernel KERNCONF=GENERIC' to create the new kernel, which is where things went bad. On my 6.4-STABLE x86 machine, I received the following: cc -c -O -pipe -march=pentium4 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/em -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/kern/kern_event.c /usr/src/sys/kern/kern_event.c:408: warning: no previous prototype for 'knote_fork' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. On my 7.2-STABLE amd64 machine, I received the following: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb - D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding /usr/src/sys/amd64/amd64/genassym.c In file included from /usr/src/sys/vm/pmap.h:82, from /usr/src/sys/amd64/amd64/genassym.c:61: ./machine/pmap.h:323: error: expected declaration specifiers or '...' before 'vm_memattr_t' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 I have rebuilt the above servers many times over, and I must say it's worked great, so was really thrown that not only one version on a server would blow up, but two different versions of the OS would pop at the same moment. Needless to say I haven't tried to rebuild any of my other 6.4 or 7.2 boxen yet, as I want to get the above two attempts sorted out first. Has something changed I am forgetting to do that is not biting me
Kernel Build Issues with latest cvsup of both a 7.2 system, and a 6.4 system..
Not sure if I am just having a run of bad luck here, but I have a bunch of various free BSD boxen on both 6.4-STABLE, and on 7.2-STABLE. I try and make it a point to do a cvsup and update the machines every month or so to keep things current and any updates/patches installed. I decided a couple days ago, it was again time to do this again. So I ran cvsup on the machines, and set out to rebuild, first doing a 'make buildworld', then a 'make installworld', and finally a 'mergemaster' on the servers. That all went well, then time for a kernel update, so I performed a 'make buildkernel KERNCONF=GENERIC' to create the new kernel, which is where things went bad. On my 6.4-STABLE x86 machine, I received the following: cc -c -O -pipe -march=pentium4 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -std=c99 -g -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/dev/em -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -ffreestanding -Werror /usr/src/sys/kern/kern_event.c /usr/src/sys/kern/kern_event.c:408: warning: no previous prototype for 'knote_fork' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. On my 7.2-STABLE amd64 machine, I received the following: cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -march=nocona -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/usr/src/sys -I/usr/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/dev/ath -I/usr/src/sys/dev/ath/ath_hal -I/usr/src/sys/contrib/ngatm -I/usr/src/sys/dev/twa -I/usr/src/sys/gnu/fs/xfs/FreeBSD -I/usr/src/sys/gnu/fs/xfs/FreeBSD/support -I/usr/src/sys/gnu/fs/xfs -I/usr/src/sys/contrib/opensolaris/compat -I/usr/src/sys/dev/cxgb -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding /usr/src/sys/amd64/amd64/genassym.c In file included from /usr/src/sys/vm/pmap.h:82, from /usr/src/sys/amd64/amd64/genassym.c:61: ./machine/pmap.h:323: error: expected declaration specifiers or '...' before 'vm_memattr_t' *** Error code 1 Stop in /usr/obj/usr/src/sys/GENERIC. *** Error code 1 Stop in /usr/src. *** Error code 1 I have rebuilt the above servers many times over, and I must say it's worked great, so was really thrown that not only one version on a server would blow up, but two different versions of the OS would pop at the same moment. Needless to say I haven't tried to rebuild any of my other 6.4 or 7.2 boxen yet, as I want to get the above two attempts sorted out first. Has something changed I am forgetting to do that is not biting me in the backside, or has some bug been introduced I am now aware of currently causing issues?? If anyone can help sort this out, or if you need additional info, please let me know.. --- Howard Leadmon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
FreeBSD DNS Resolver Issues?
OK, now I am a bit stumped, so wanted to post here in hopes someone might have an idea. First off the FBSD machine in question is an x86 server running 6.2-STABLE from a supped from a few weeks ago, so is fairly current. I use said machine to handle all of my eMail and things in general seem to work great, though I have this one mystery. I we try and send mail to [EMAIL PROTECTED] the mail will just set in the queue forever, until it's returned as a failure. Talking with the admins at wtplaw they are swearing their configs are correct, and it's something on our side. Looking at the mailq, I see: l3NEqolY01112428697 Mon Apr 23 10:52 [EMAIL PROTECTED] (Deferred: Name server: mail.wtplaw.com.: host name lookup fa) [EMAIL PROTECTED] So as it's quick an easy I used dig and did a lookup: $ host wtplaw.com wtplaw.com has address 69.20.43.246 wtplaw.com mail is handled by 10 mail.wtplaw.com. Then on mail.wtplaw.com: $ host mail.wtplaw.com mail.wtplaw.com has address 65.111.69.228 mail.wtplaw.com has address 66.166.181.163 Host mail.wtplaw.com not found: 2(SERVFAIL) ;; connection timed out; no servers could be reached As you can see I am getting a failure, which I know will make sendmail blow a gasket over the issue. Oh and use I have the WorkAroundBroken set in my configs. Here is where it gets interesting, and confuses me. I also have a Sun SPARC server running Solaris-10, so figured I would try the same on it. Note that both servers use the same DNS servers for resolution, plus I also tried the above specifying the actual listed nameservers for wtplaw.com and got the same results. OK, so let's try the above on my Solaris-10 server: $ host wtplaw.com wtplaw.com has address 69.20.43.246 wtplaw.com mail is handled by 10 mail.wtplaw.com. and: $ host mail.wtplaw.com mail.wtplaw.com has address 65.111.69.228 mail.wtplaw.com has address 66.166.181.163 Note I am getting no failure messages from my Solaris machine. So I even turned on -v verbose option. Here is from the FreeBSD machine: $ host -v mail.wtplaw.com Trying mail.wtplaw.com ;; -HEADER- opcode: QUERY, status: NOERROR, id: 27765 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1 ;; QUESTION SECTION: ;mail.wtplaw.com. IN A ;; ANSWER SECTION: mail.wtplaw.com.3 IN A 65.111.69.228 mail.wtplaw.com.3 IN A 66.166.181.163 ;; AUTHORITY SECTION: mail.wtplaw.com.85342 IN NS lp2.wtplaw.com. mail.wtplaw.com.85342 IN NS lp1.wtplaw.com. ;; ADDITIONAL SECTION: lp2.wtplaw.com. 85864 IN A 66.166.181.172 Received 117 bytes from 207.114.24.13#53 in 22 ms Trying mail.wtplaw.com Host mail.wtplaw.com not found: 2(SERVFAIL) Received 33 bytes from 207.114.24.13#53 in 80 ms Trying mail.wtplaw.com ;; connection timed out; no servers could be reached Note the failures. I am have to honestly say I am not totally sure what it's trying to do at the end there, maybe someone can explain that one to me. Here is the Solaris-10 machine making the same query: $ host -v mail.wtplaw.com Trying mail.wtplaw.com ;; -HEADER- opcode: QUERY, status: NOERROR, id: 549 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 1 ;; QUESTION SECTION: ;mail.wtplaw.com. IN A ;; ANSWER SECTION: mail.wtplaw.com.3 IN A 65.111.69.228 mail.wtplaw.com.3 IN A 66.166.181.163 ;; AUTHORITY SECTION: mail.wtplaw.com.85225 IN NS lp1.wtplaw.com. mail.wtplaw.com.85225 IN NS lp2.wtplaw.com. ;; ADDITIONAL SECTION: lp2.wtplaw.com. 85747 IN A 66.166.181.172 Received 117 bytes from 207.114.24.13#53 in 40 ms Again, the query seemed fine, no troubles. As stated earlier, talking to the sysadmin of the wtplaw.com site, they are swearing there is nothing wrong, they are responding to queries as they should be, and that we have a configuration problem on our end. If this is true, I'd sure love to know what it is, so I can fix it, and if not I'd love to know what to tell them is wrong with their DNS so I can get it corrected. As right now I am bouncing mail from a few clients to this user, and I can't seem to find any resolution to this issue. When I realized that Solaris seems happy with their DNS, but FBSD is not, it just made this even more of a mystery. If anyone can help shed any light on this it would sure be appreciated.. --- -Howard ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
DNS/Bind Error Help under FBSD 6.2 using Sendmail..
I am seeing an issue with some eMail moving from the server here is one such example: l25F3FJW08259696337 Mon Mar 5 10:03 [EMAIL PROTECTED] (Deferred: Name server: mail.jingmei.com.: host name lookup f) [EMAIL PROTECTED] [EMAIL PROTECTED] OK, so I did a lookup of it's MX, and get: jingmei.com mail is handled by 10 mail.jingmei.com So then I looked up mail.jingmei.com: mail.jingmei.com has address 220.112.41.223 Host mail.jingmei.com not found: 2(SERVFAIL) I see I am getting a returned IP address which can be connected to, but also a SERVFAIL error. Now I am aware of the IPv6 issue, and have the needed setting in my sendmail.cf file: O ResolverOptions=WorkAroundBroken So I would have hoped this would have worked around the issue and permitted mail flow, yet apparently not for some reason. I have googled and looked around, and maybe just not found the right info yet, but if anyone has any idea how to track this down, or resolve the issue it would sure be most appreciated. Most of my mail moves fine, but I have a couple domains I am guessing have something wrong, so I can't seem to get mail out to them... --- Howard http://www.leadmon.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Trouble with NFSd under 6.1-Stable, any ideas?
Hello Rong-en, As an update, I did the below, and I still had the issue with either version of vfs_lookup.c compiled in and running. On the bright side, I didn't realize you could step through the cvs by date, guess I just never paid attention. So I just stepped back to 'tag=RELENG_6 date=2006.04.20.00.00.00' on my server, rebuilt and violla nfs is now running perfect. So backing out something has fixed my problem, now to figure out just what it was. As I don't know what has caused this, I have done complete buildworlds to make sure everything updates which takes a few hours.I am going to start moving the cvs date forward till I get the problem back, once I nail this down a bit more, I'll let you know what I come up with. --- Howard Leadmon http://www.leadmon.net -Original Message- From: Rong-en Fan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 3:09 PM To: Howard Leadmon Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? On 5/23/06, Howard Leadmon [EMAIL PROTECTED] wrote: Hello Rong-en, Thanks for the info on getting the debugger configured, and on the serial console. I will have to try and play with the serial console thing more, I just tried putting in the flags and the damn thing hung, I had to boot from CD and take the stuff back out. One thing you mention below that concerns me is that you have version 1.90 of the vfs_lookup.c file. I just did a less on /usr/src/sys/kern/vfs_lookup.c and I see the following: FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80.2.7 2006/04/30 03:57:46 kris Exp I even did a cvsup (I use cvsup2.FreeBSD.org) to make sure I had the current stuff before rebuilding the kernel just now, and still I see the same thing. Is something fishy going on here, or did you by chance make a typo?? Sorry for the confusion. rev 1.90 is the number for -HEAD. To back out this MFC'ed change for RELENG_6_1, please cvsup to RELENG_6_1 date=2006.04.30.03.57.00. Then you should see it is 1.80.2.6 2006/03/31 07:39:24 kris To verify the effect of this revision. Please run RELENG_6_1 with 2006.04.30.03.57.00 and 2006.04.30.04.00.00. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Trouble with NFSd under 6.1-Stable, any ideas?
I need to follow up to the below, as I am not sure why the below test with the vfs_lookup.c didn't pan out the first time, but with my new found knowledge on cvs I was determined to regress the system till I found the smoking gun so to speak, which I have done. First let me say that instead of running RELENG_6_1 like Rong-en is, I am running the RELENG_6 tree that I know updates more often, but seems to work well for me. OK, so as I said above I started to regress the system a couple days at a time, till suddenly NFS stared working again, so I knew at that point it was a change that was made. So then I started to narrow the time range, till I got to the point that it broke. Sure enough under the RELENG_6 branch, this time was as follows: *default tag=RELENG_6 date=2006.04.30.03.57.00 (Works OK) *default tag=RELENG_6 date=2006.04.30.03.58.00 (Broken) So what's changed at that delta, under the one that works vfs_lookup.c is: Edit src/sys/kern/vfs_lookup.c Add delta 1.80.2.6 2006.03.31.07.39.24 kris Under the one that fails the vfs_lookup.c is: Edit src/sys/kern/vfs_lookup.c Add delta 1.80.2.7 2006.04.30.03.57.46 kris So I stand corrected on my last post, the issue is in fact in this module, as just taking that module back to 1.80.2.6 fixes the problem with my server. I even took multiple NFS clients and gave them a heavy workload, and CPU still remained reasonable, and very responsive. As soon as I rev to the new version, NFS breaks badly and even a single client doing something like a du of a directory structure results in sluggishness and extreme CPU usage. I am not a coder, so not sure why this module was changed, but unless there is some good reason why the changes were needed I would suspect it needs to be rolled back, or something fixed. So Rong-en Fan, I think you were dead on with your analysis that the issue is in fact inside the vfs_lookup.c module. I hope this helps... --- Howard Leadmon - [EMAIL PROTECTED] http://www.leadmon.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Howard Leadmon Sent: Wednesday, May 24, 2006 1:23 PM To: 'Rong-en Fan' Cc: 'Konstantin Belousov'; freebsd-stable@freebsd.org Subject: RE: Trouble with NFSd under 6.1-Stable, any ideas? Hello Rong-en, As an update, I did the below, and I still had the issue with either version of vfs_lookup.c compiled in and running. On the bright side, I didn't realize you could step through the cvs by date, guess I just never paid attention. So I just stepped back to 'tag=RELENG_6 date=2006.04.20.00.00.00' on my server, rebuilt and violla nfs is now running perfect. So backing out something has fixed my problem, now to figure out just what it was. As I don't know what has caused this, I have done complete buildworlds to make sure everything updates which takes a few hours.I am going to start moving the cvs date forward till I get the problem back, once I nail this down a bit more, I'll let you know what I come up with. --- Howard Leadmon http://www.leadmon.net -Original Message- From: Rong-en Fan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 3:09 PM To: Howard Leadmon Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? On 5/23/06, Howard Leadmon [EMAIL PROTECTED] wrote: Hello Rong-en, Thanks for the info on getting the debugger configured, and on the serial console. I will have to try and play with the serial console thing more, I just tried putting in the flags and the damn thing hung, I had to boot from CD and take the stuff back out. One thing you mention below that concerns me is that you have version 1.90 of the vfs_lookup.c file. I just did a less on /usr/src/sys/kern/vfs_lookup.c and I see the following: FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80.2.7 2006/04/30 03:57:46 kris Exp I even did a cvsup (I use cvsup2.FreeBSD.org) to make sure I had the current stuff before rebuilding the kernel just now, and still I see the same thing. Is something fishy going on here, or did you by chance make a typo?? Sorry for the confusion. rev 1.90 is the number for -HEAD. To back out this MFC'ed change for RELENG_6_1, please cvsup to RELENG_6_1 date=2006.04.30.03.57.00. Then you should see it is 1.80.2.6 2006/03/31 07:39:24 kris To verify the effect of this revision. Please run RELENG_6_1 with 2006.04.30.03.57.00 and 2006.04.30.04.00.00. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo
RE: Trouble with NFSd under 6.1-Stable, any ideas?
If there are any thing I can provide to help tracking this down. Please let me know. By the way, I tried with truss/kdump to see what happens when nfsd eats lot of CPUs, but in vain. They do not return anything. I tried your recipe on 7-CURRENT with locally exported fs, remounted over nfs. I did not get the behaviour your described. As noted in my previous thread, I have another 6.1-RELEASE nfs server, which does not have this problem. Could you, please, provide the backtrace for the nfsd that eats the CPU (from the ddb). I think it would be helpful to get several backtraces (i.e., bt nfsd pid, cont, bt nfsd pid ...) to see where it running. I'm afraid that I can not do that. Last time I tried breaking into ddb (on 5.x), it hangs my serial console and the server is miles away :-( . Perhaps we can ask Howard to do that? I am more than willing to do that, as this machine runs here with me, so if needed I can easily get on a console, or perform a reboot. Can one of you shed a little light on exactly what I need to do, and how to do this? I ask as I have never used this ddb stuff, so not clue one on how to go about getting the information your looking to find. Guess I have been lucky, and just never had an issue that took things to this level. Also, just in case, does filesystem that is exported and shows problem, have quotas enabled ? One line of your fstab has userquotas, other does not. As to userquotas, I just tried accessing the NFS mounts here, as some have filesystems with quotas, and some don't, and both are exibiting the exact same problem. So using quotas is for sure not the problem, or should I say not the trigger to the problem. Regards, Rong-En Fan --- Howard Leadmon http://www.leadmon.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Trouble with NFSd under 6.1-Stable, any ideas?
Hello Rong-en, Thanks for the info on getting the debugger configured, and on the serial console. I will have to try and play with the serial console thing more, I just tried putting in the flags and the damn thing hung, I had to boot from CD and take the stuff back out. One thing you mention below that concerns me is that you have version 1.90 of the vfs_lookup.c file. I just did a less on /usr/src/sys/kern/vfs_lookup.c and I see the following: FreeBSD: src/sys/kern/vfs_lookup.c,v 1.80.2.7 2006/04/30 03:57:46 kris Exp I even did a cvsup (I use cvsup2.FreeBSD.org) to make sure I had the current stuff before rebuilding the kernel just now, and still I see the same thing. Is something fishy going on here, or did you by chance make a typo?? --- Howard Leadmon - [EMAIL PROTECTED] http://www.leadmon.net -Original Message- From: Rong-en Fan [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 10:19 AM To: Howard Leadmon Cc: Konstantin Belousov; Kris Kennaway; freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? On 5/23/06, Howard Leadmon [EMAIL PROTECTED] wrote: If there are any thing I can provide to help tracking this down. Please let me know. By the way, I tried with truss/kdump to see what happens when nfsd eats lot of CPUs, but in vain. They do not return anything. I tried your recipe on 7-CURRENT with locally exported fs, remounted over nfs. I did not get the behaviour your described. As noted in my previous thread, I have another 6.1-RELEASE nfs server, which does not have this problem. Could you, please, provide the backtrace for the nfsd that eats the CPU (from the ddb). I think it would be helpful to get several backtraces (i.e., bt nfsd pid, cont, bt nfsd pid ...) to see where it running. I'm afraid that I can not do that. Last time I tried breaking into ddb (on 5.x), it hangs my serial console and the server is miles away :-( . Perhaps we can ask Howard to do that? I am more than willing to do that, as this machine runs here with me, so if needed I can easily get on a console, or perform a reboot. Can one of you shed a little light on exactly what I need to do, and how to do this? I ask as I have never used this ddb stuff, so not clue one on how to go about getting the information your looking to find. Guess I have been lucky, and just never had an issue that took things to this level. At least you have to add the following to your kernel: options KDB options DDB Recompile it, reboot. You would better to setup a serial console so you can easily copy thing from ddb output. To do it, you have to put device sio in your kernel configuration and some files below: /boot.config -Dh /boot/loader.conf comconsole_speed=115200 machdep.conspeed=115200 /etc/ttys ttyd0 /usr/libexec/getty std.115200 cons25 on secure On the other machine, /etc/remote: com1:dv=/dev/cuad0:br#115200:pa=none: Then, use tip com1 to attach the nfs server. The above settings assume your serial console on nfs server is on COM1 and on the client side is also COM1. If that's not the case, please follow Handbook for howto setup a serial console other than COM1. To break into ddb, either use ctrl+alt+esc or send a BREAK (I think ^b will do) via serial line. After that, you should see db Then you first use ps to find out the nfsd pid (better to remember the pid which eats lots of cpu before enter ddb). After that, do what Konstantin suggests. I have never tried cont in db. I guess that will return the execution back to kernel and you need to break into ddb again to do another bt pid. By the way, could you verify that backing out vfs_lookup.c rev 1.90 helps in your situation? If not, maybe we are seeing different problems, and then I have to figure out how to make my serial console work here. Thanks, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Trouble with NFSd under 6.1-Stable, any ideas?
Sorry for delay, ended up sick.. :( You say use tcpdump, is there something I should be looking out for? As NFS is serving files, even more strange is if I kill off the nfsd process it's zippy fast for a moment and then the CPU load goes through the roof, and it starts serving files slowly. So it's actually working, outside of it consumes all available CPU and brings the machine to it knees quickly. Doesn't matter if I access it from my Solaris box, my other FBSD boxes, and so on, it still dogs down terribly and never used. Anything anyone can think of config wise that might cause that, it would be nice to know. I have the following that I can think of that affects NFS configs: # # NFS # nfs_client_enable=NO # This host is an NFS client (or NO). nfs_access_cache=2# Client cache timeout in seconds nfs_server_enable=YES # This host is an NFS server (or NO). nfs_server_flags=-u -t -n 5 # Flags to nfsd (if enabled). mountd_enable=YES # Run mountd (or NO). mountd_flags=-r # Flags to mountd (if NFS server enabled). weak_mountd_authentication=NO # Allow non-root mount requests to be served. nfs_reserved_port_only=YES# Provide NFS only on secure port (or NO). nfs_bufpackets= # bufspace (in packets) for client rpc_lockd_enable=YES # Run NFS rpc.lockd needed for client/server. rpc_statd_enable=YES # Run NFS rpc.statd needed for client/server. rpcbind_enable=YES# Run the portmapper service (YES/NO). rpcbind_program=/usr/sbin/rpcbind # path to rpcbind, if you want a differe rpcbind_flags=# Flags to rpcbind (if enabled). I can't think of anything that should have changed, unless mergemaster updating the default files might have changed something that would have an effect. --- Howard Leadmon http://www.leadmon.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kris Kennaway Sent: Sunday, May 14, 2006 10:50 PM To: Howard Leadmon Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? On Sun, May 14, 2006 at 02:28:55PM -0400, Howard Leadmon wrote: Hello All, I have been running FBSD a long while, and actually running since the 5.x releases on the server I am having troubles with. I basically have a small network and just use NIS/NFS to link my various FBSD and Solaris machines together. This has all been running fine up till a few days ago, when all of a sudden NFS came to a crawl, and CPU usage so high the box appears to freeze almost. When I had 6.1-RC running all seemed well, then came the announcement for the official 6.1 release, so I did the cvs updates, made world, kernel, and ran mergemaster to get everything up to the 6.1 stable version. Now after doing this, something is wrong with NFS. It works, it will return information and open files, just it's very very slow, and while performing a request the CPU spike is astounding. A simple du of my home directory can take minutes, and machine all but locks up if the request is done over NFS. Here is top snip: PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 497 root 1 40 1252K 780K - 2 50:42 188.48% nfsd This is a nice IBM eServer with dual P4-XEON's and a couple GB or RAM on a disk array, and locally is screams, heck NFS used to scream till I updated. I am not really sure what info would be useful in debugging, so won't post tons of misc junk in this eMail, but if anyone has any ideas as to how best to figure out and resolve this issue it would sure be appreicated... Use tcpdump and related tools to find out what traffic is being sent. Also verify that you did not change your system configuration in any way: there have been no changes to NFS since the release, so it is unclear why an update would cause the problem to suddenly occur. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: 6.1-RELEASE, em0 high interrupt rate and nfsd eats lots of cpu
Ahh, this might be my nfs problem I am now seeing, see my other posting to this list about that issue. If anyone knows of a fix for this, outside of downgrading to 6.0 please let me know. It's for sure a nusiance when I have half dozen other machines that NFS to that server. I don't have em0, but do have fxp0, and am seeing massive CPU if I do something like a du on the NFS mount. --- Howard Leadmon http://www.leadmon.net -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rong-en Fan Sent: Monday, May 15, 2006 9:24 PM To: [EMAIL PROTECTED] Subject: Re: 6.1-RELEASE, em0 high interrupt rate and nfsd eats lots of cpu On 5/15/06, Dmitriy Kirhlarov [EMAIL PROTECTED] wrote: On Mon, May 15, 2006 at 02:15:08PM -0400, Rong-en Fan wrote: Hi, After upgrading from 5.5-PRERELEASE to 6.1-RELEASE on one nfs server today, I noticed that the load is very high, ranging from 4.x to 30.x, depends how many nfsd I run. From mrtg traffic graph, I did not notice there is high traffic. This box is 2 physical Xeon CPU w/ I have same situation today on RC2. One client installing world from nfs share. nfsd eat 91% CPU, load average 6-8. Very small disk activitie. I don't look interrupt rate. I, also, have em0. After some digging, I found the cpu-eater nfsd can be triggered by running ``du'' on nfs client (both FreeBSD 6.1-R and Linux box). The nfsd will eat lots of CPU. After the client's du is finished, the nfsd still eat lots of CPU. The workaround is to /etc/rc.d/nfsd restart Everything will be just fine. Besides du, on FreeBSD 6.1-R client, buildkernel over nfs will trigger the same behavior. I just downgraded this box to 6.0-RELEASE and everything works fine. Running du or buildkernel from nfs client do not trigger the same behavior. I will try to do a binary search from 6.0-R to 6.1-R see if I can find out related commits. By the way, I have another nfs server running 6.1-RELEASE, but it does not exhibit this behavior. Kernel conf and sysctl are basically the same for both boxes. Regards, Rong-En Fan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Trouble with NFSd under 6.1-Stable, any ideas?
Hello All, I have been running FBSD a long while, and actually running since the 5.x releases on the server I am having troubles with. I basically have a small network and just use NIS/NFS to link my various FBSD and Solaris machines together. This has all been running fine up till a few days ago, when all of a sudden NFS came to a crawl, and CPU usage so high the box appears to freeze almost. When I had 6.1-RC running all seemed well, then came the announcement for the official 6.1 release, so I did the cvs updates, made world, kernel, and ran mergemaster to get everything up to the 6.1 stable version. Now after doing this, something is wrong with NFS. It works, it will return information and open files, just it's very very slow, and while performing a request the CPU spike is astounding. A simple du of my home directory can take minutes, and machine all but locks up if the request is done over NFS. Here is top snip: PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 497 root 1 40 1252K 780K - 2 50:42 188.48% nfsd This is a nice IBM eServer with dual P4-XEON's and a couple GB or RAM on a disk array, and locally is screams, heck NFS used to scream till I updated. I am not really sure what info would be useful in debugging, so won't post tons of misc junk in this eMail, but if anyone has any ideas as to how best to figure out and resolve this issue it would sure be appreicated... --- Howard Leadmon http://www.leadmon.net ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Trouble with NFSd under 6.1-Stable, any ideas?
Would this just be lockd, or should I disable both lockd and statd? I notice in the rc.conf it claims they are both supposed to be enabled, so not sure what issues I run into if I disable them, if any. As to my servers, I have a bunch of stuff running actually. The Dual XEON server being my fastest machine by far is my main server, off of that I have a SPARC running Solaris10, I have another SPARC running FreeBSD 6.1, I have a DEC Alpha running FreeBSD 4.11, and another old Dual XEON machine running FreeBSD 4.11, and finally another x86 machine running FreeBSD 7 current. This stuff has been doing great, I personally love FBSD, as you can tell from what is loaded on most of the servers. It just blows my mind that now after years of running the network like this, now something breaks. I get no errors in syslog, and it IS serving requests, as I have some web pages on the old 4.11 machine and they come up, just slowly compared to what they used to do. Oh well as they say, in the world of computers it's never easy.. LOL --- Howard Leadmon - [EMAIL PROTECTED] http://www.leadmon.net -Original Message- From: Stephen Hurd [mailto:[EMAIL PROTECTED] Sent: Sunday, May 14, 2006 5:54 PM To: Howard Leadmon Cc: freebsd-stable@freebsd.org Subject: Re: Trouble with NFSd under 6.1-Stable, any ideas? Howard Leadmon wrote: Hello All, I have been running FBSD a long while, and actually running since the 5.x releases on the server I am having troubles with. I basically have a small network and just use NIS/NFS to link my various FBSD and Solaris machines together. This has all been running fine up till a few days ago, when all of a sudden NFS came to a crawl, and CPU usage so high the box appears to freeze almost. When I had 6.1-RC running all seemed well, then came the announcement for the official 6.1 release, so I did the cvs updates, made world, kernel, and ran mergemaster to get everything up to the 6.1 stable version. Now after doing this, something is wrong with NFS. It works, it will return information and open files, just it's very very slow, and while performing a request the CPU spike is astounding. A simple du of my home directory can take minutes, and machine all but locks up if the request is done over NFS. Here is top snip: PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 497 root 1 40 1252K 780K - 2 50:42 188.48% nfsd This is a nice IBM eServer with dual P4-XEON's and a couple GB or RAM on a disk array, and locally is screams, heck NFS used to scream till I updated. I am not really sure what info would be useful in debugging, so won't post tons of misc junk in this eMail, but if anyone has any ideas as to how best to figure out and resolve this issue it would sure be appreicated... Are you running rpc.lockd? I've had very bad luck with it since sometime in the 5.x series... especially with it interoperating with Solaris. I submitted a PR on it, but it's apparently broken in about X ways. If possible, I would suggest living without rpc.lockd for now (if you're currently living with it that is) Other than that issue, NFS itself has been working nicely for me. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Debugging Kernel/System Crashes, can anyone help??
:537
#9 0xc01673ef in sync (p=0xc0297060, uap=0x0) at ../../kern/vfs_syscalls.c:549
#10 0xc013a9b3 in boot (howto=256) at ../../kern/kern_shutdown.c:226
#11 0xc013af94 in poweroff_wait (junk=0xc0259739, howto=0)
at ../../kern/kern_shutdown.c:554
#12 0xc02283d6 in trap_fatal (frame=0xff80df44, eva=0)
at ../../i386/i386/trap.c:926
#13 0xc0227d92 in trap (frame={tf_fs = -1072365544, tf_es = 1174929424,
tf_ds = -1059192816, tf_edi = -194641856, tf_esi = -1059168256,
tf_ebp = -8331372, tf_isp = -8331408, tf_ebx = -1059161408,
tf_edx = 54312, tf_ecx = 0, tf_eax = -194641856, tf_trapno = 29,
tf_err = 0, tf_eip = -1071900421, tf_cs = 8, tf_eflags = 582,
tf_esp = -1059161408, tf_ss = 1074266112}) at ../../i386/i386/trap.c:586
#14 0xc01c18fb in dc_intr (arg=0xc0de6000) at machine/cpufunc.h:331
#15 0xc0230953 in intr_mux (arg=0xc0de7b20)
at ../../i386/isa/intr_machdep.c:569
(kgdb) q
#
---
Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net
ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Re: Debugging Kernel/System Crashes, can anyone help??
Well I actually have two prior crashes that I did save before I turned off the dumpsaves to avoid running out of drive space, and as I am by no means a gdb user if you could tell me what your looking for I'll be happy to fire up gdb and send you the info. Here is what I grabbed out of the /var/crash directory (hopefully this is useful), and I'll set the system to grab a clean dump next time around.. -rw-r--r-- 1 howardl wheel 31 Apr 8 15:44 bounds.0.gz -rw-r--r-- 1 howardl wheel 31 Apr 9 13:39 bounds.1.gz -rw-r--r-- 1 howardl wheel 825413 Apr 8 15:46 kernel.0.gz -rw-r--r-- 1 howardl wheel 825413 Apr 9 13:40 kernel.1.gz -rw-rw-r-- 1 howardl wheel 5 Feb 14 19:08 minfree -rw-r--r-- 1 howardl wheel 111631734 Apr 8 15:46 vmcore.0.gz -rw-r--r-- 1 howardl wheel 110971933 Apr 9 13:40 vmcore.1.gz NOTE - I gzipped the dumps to save space, as with 384M RAM it was leaving some rather large files... Also, thanks for the quick response.. I know I posted a few messages here in the past, but maybe someone who is good at tracking kernel problems can step up and lend a hand. I have a machine running FBSD 4.0-STABLE, and have been experiencing almost daily kernel panics or reboots on the machine. I have replaced ALL of the hardware, and reloaded the OS, but still having troubles. I am at a bit of a loss as to what is going on. From one panic, I thought well maybe this is an SMP issue, but removed one of the CPU's and still the box crashes. As I have basically replaced everything, I am at a loss as to where to go from here, so looking for some type of pointers or help with this.. Indeed. We need to address this issue in some detail. We need both documentation and tools. The other day I was there, and got the following from one of the crashes, as many times I am gone and luckally in some ways the box will just panicboot and go on it's way. Here is what I was able to copy down: Fatal trap 12: page fault while in kernel mode mp_lock=0102; cpuid=1; lapic.id=0100 fault virtual address= 0x30 fault code= supervisor read, page not present instruction pointer= 0x8:0xC01CAF71 stack pointer= 0x10:0xFF80DE48 frame pointer= 0x10:0xFF80DE4C code segment= base 0x0, limit 0xF, type 0x1B = DPL 0, pres 1, def 32, gran 1 processor eflags= interrupt enabled, resume, IOPL=0 current process = idle interupt mask= bio - SMP: XXX trap number= 12 panic: page fault The formatting of it may not be perfect, but the information should be accurate, as I tried to be precise on what I wrote down. Also here are a few previous messages I had posted a while back when I thought this might be network related, but after trying several different NIC's I still have the same issues. I will include the info below, as maybe it will have some value in trying to debunk this problem. The sad thing is that this information is that most of this information is almost useless. I'm thinking of printing out a stack trace instead (comments, anybody?). Without tedious comparison with your kernel namelist, all we can say here is that you died somewhere in the kernel, that you have an SMP machine, and that the block I/O subsystem is probably involved. If this is happening daily, you should build a kernel with debugging symbols enabled and take a dump of the next crash. We can then use gdb to analyse the dump. Hello, I am running a 4.0-STABLE machine which is being used to host an Undernet IRC server, and the machine keeps dying at times, or should I say the networking side of it is at least dying. At first I thought it might have been related to the dc (DEC Chip) based drivers, so I replaced it with a EEpro board using the fxp driver, but the same results. snip If all your dumps have the interrupt mask set to bio, I don't think it's a networking problem. With one possible exception... Mar 27 12:39:00 u2 /kernel: fxp0: device timeout S_ren and I are trying to find out what is causing some weird Vinum problems. He stated that the problem happened more frequently when an fxp board was in the system. I don't believe him, and I've found at least one bug in Vinum that has nothing to do with networking (but does have to do with the bio mask); possibly, however, there's some other problem with the fxp driver. It's possible that the other information will be of use, but I think we first need to look at a dump. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Debugging Kernel/System Crashes, can anyone help??
77 7K 9K 64189K172540 0 32,64,256 cred 9 2K 2K 64189K 12640 0 128 sysctl 0 0K 1K 64189K 7380 0 16,32 bus 36731K 31K 64189K 5030 0 16,32,64,128,256,512,1K,2K eventhandler11 1K 1K 64189K 110 0 32,64 SWAP 2 141K141K 64189K20 0 32,256K ioctlops 0 0K 1K 64189K50 0 512,1K rman50 3K 3K 64189K 790 0 16,64 ttys 41053K 58K 64189K 13070 0 128,256 ptys 2 1K 1K 64189K20 0 512 soname 1 1K 1K 64189K 39676140 0 16,128 pcb50 5K 19K 64189K 7384470 0 16,32,64,2K BIO buffer2628K769K 64189K123080 0 512,1K,2K vfscache 14194 1016K 1016K 64189K182780 0 64,128,128K cluster_save buffer 0 0K 1K 64189K 9810 0 32,64,128 mount 4 2K 2K 64189K60 0 16,128,512 vnodes24 6K 6K 64189K 3270 0 16,32,64,128,256 BPF 3 1K 1K 64189K30 0 32 ifaddr16 2K 2K 64189K 160 0 32,64,128,256 ether_multi 7 1K 1K 64189K70 0 16,32,64 routetbl 6193 871K 6957K 64189K 6630760 0 16,32,64,128,256 in_multi 2 1K 1K 64189K20 0 32 tseg_qent 0 0K 2K 64189K 2203760 0 32 NFS daemon 1 1K 1K 64189K10 0 256 NQNFS Lease 1 1K 1K 64189K10 0 1K NFS hash 164K 64K 64189K10 0 64K p1003.1b 1 1K 1K 64189K10 0 16 pagedep 217K 17K 64189K 320 0 64,16K inodedep 465K 68K 64189K 28130 0 128,64K newblk 1 1K 1K 64189K238340 0 32,256 bmsafemap 3 1K 1K 64189K 46900 0 32 allocdirect 1 1K 2K 64189K 85550 0 64 indirdep 1 1K 25K 64189K 28220 0 32,8K allocindir 1 1K 26K 64189K152780 0 64 freefrag 0 0K 4K 64189K 34640 0 32 freeblks 0 0K 4K 64189K 15200 0 128 freefile 0 0K 1K 64189K 400 0 32 diradd 2 1K 1K 64189K 610 0 32 dirrem 0 0K 1K 64189K 640 0 32 FFS node 13320 3330K 3331K 64189K143730 0 256 UFS ihash 164K 64K 64189K10 0 64K UFS mount 920K 20K 64189K90 0 512,2K,8K VM pgdata 1 128K128K 64189K10 0 128K ZONE18 3K 3K 64189K 180 0 128 isadev11 1K 1K 64189K 110 0 64 ATA generic 0 1K 1K 64189K10 0 512 AD driver 1 1K 2K 64189K 2772660 0 64,1K devbuf81 175K175K 64189K 1130 0 16,32,128,256,512,1K,2K,4K,16K mbuf 128K 28K 64189K10 0 32K memdesc 1 4K 4K 64189K10 0 4K isa_devlist 0 0K 2K 64189K 180 0 16,512,1K atkbddev 2 1K 1K 64189K20 0 16 Memory Totals: In UseFreeRequests 6372K 5380K13003847 All of the above stats were taken while the network card was spitting out errors prior to performing a reboot which brings the box back online. I also tried unplugging the nic and plugging it back in without out any change. I also over time have replaced everything in the box except the case, but still the problem persists, and in fact took the old hardware and built a different machine that works fine. So something related to the heavy use by the IRC programs is killing this thing almost daily, and I am at a loss as to what. If you or anyone here on the list has any ideas, I would sure love to hear them, as it would be nice to get to the bottom of this issue... = Guess thats about it for now, and hopefully someone can give me some pointers, or lend a hand in trying to get this issue resolved as it's driving me nutz.. :) --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
NIS under FreeBSD - HELP
Hello All, I am in the process of trying to make NIS function on a few FreeBSD machines, and think I have everything setup and working for the most part. The one problem I am having is that when I try and perform a login, the auth attempts all fail unless the user is in the local password file, and yes I do have the + entry at the bottom of the passwd and master.passwd files. If I do a 'ypcat passwd' or 'ypcat master.passwd' from the client machine they both come across and look fine. Also doing an ls on some of the NFS mounts, or ypcat's of other other files all work just fine, so ypbind/ypserv are talking to each other. The one other strangeness (maybe) is I tried to do a passwd (yppasswd) of one of the accounts on the master server, and it claimed it changed the password successfully, but in reality nothing happened, as the password remained the same on the master when checked. I have never really tried to debug NIS, so after spending a couple hours looking around, I figured I would post to the lists and see if anyone here could give me some pointers, or maybe some decent config examples to take a peek at over here. FYI, the master is an Intel FBSD 3.4 box, and the client I am testing on is an Alpha FBSD 4.0 machine, but I would hope that isn't causing this trouble. Any ideas, clues, hints, or pointers appreciated... --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Compiler problems with -O2 (was Re: CVS Trouble, even under 4.0-RELEASE(alpha) HELP!)
Actually I have several Alpha's, and one I have to reload due to this, so I will give this a try on the other machine and will let you know if I have good success with it. If this all works, then I agree with you that we want to avoid, or at least note the problem with -O2 as I have been using that when making software on my Intel machines for a long time, so just assumed it was OK to do the same on the Alpha.. Get rid of -O2 in /etc/make.conf; comment out the CFLAGS line. You should NEVER, EVER build _anything_ with -O2 on an alpha. The compiler is very fragile and has been known to do odd things when compiling -O2. I'm starting to think that any optimizations other than -O should probably be disabled in the compiler to keep people from blowing their feet off like you've just done. I'd suggest re-loading the machine from the cd at this point, or building a world on another machine which has a good world doing a make installworld via NFS mounts. Drew -- Andrew Gallatin, Sr Systems Programmerhttp://www.cs.duke.edu/~gallatin Duke University Email: [EMAIL PROTECTED] Department of Computer SciencePhone: (919) 660-6590 --- Howard Leadmon - [EMAIL PROTECTED] - http://www.abs.net ABSnet Internet Services - Phone: 410-361-8160 - FAX: 410-361-8162 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
