sendmail-sasl port not work
Dear all: I find the sendmail-sasl port will not compile with the option SASLv2 and I can not get SMTP Auth. The port will install TLS and Cyrus-SASL but as I use the command --sendmail -d0.1 -bv root | grep SASL-- I can not find it compiled with SASL. Any solution to fix it. THX. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: internal compiler error: segmentation fault: 11
On Wed, May 24, 2006 at 01:51:19PM +1200, Mark Kirkwood wrote.. Jonathan Chen wrote: On Tue, May 23, 2006 at 09:03:06PM -0400, Dave wrote: Hello, I'm trying to compile 6.0-stable on a release box, prior to upgrade. I've tried several times and all end with an internal compiler error: segmentation fault: 11. And then i'm told to submit a bug report. My problem is when this occurs it's not always at the same spot or the same file. One time it even core dumped, though only once. This is a prime-indicator of dodgy memory. Yeah - but it can easily be power supply or motherboard age. I suffered the latter late last year with a Tyan Thunder LE, I'm using the same power supply and memory in a Supermicro P3TDER and it is rock solid. CPU fan or chipset fan is also a possibility. -- Wilko Bulte [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: quota and snapshots in 6.1-RELEASE
Dmitriy Kirhlarov wrote: Hi! On Tue, May 23, 2006 at 04:35:21PM -0400, Kris Kennaway wrote: 6.1-STABLE after 6.1-RELEASE is releases. So I think you may want If you use snapshots with your quotas, update to 6.1-STABLE. If you Sorry, guys. You are mean RELENG_6_1 or RELENG_6? WBR RELENG_6. However, the changes will likely make their way into RELENG_6_1 in a few weeks as part of an errata update. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendmail-sasl port not work
Did you change your make.conf? Dear all: I find the sendmail-sasl port will not compile with the option SASLv2 and I can not get SMTP Auth. The port will install TLS and Cyrus-SASL but as I use the command --sendmail -d0.1 -bv root | grep SASL-- I can not find it compiled with SASL. Any solution to fix it. THX. ___ 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]
Re: 6.1-stable crash
On Tue, 2006-May-23 19:04:18 +, Hunter Fuller wrote: Am I the only one who sees the oxymoronity in 6.1-stable crash? Hopefully. As is regularly pointed out, 'stable' refers primarily to the ABI. FreeBSD 6.1-stable is still under active development, though only code that has previously been tested in -current is supposed to be commited. There are also fairly regular postings pointing out that _all_ software has bugs. Some of these bugs will cause crashes. -- Peter Jeremy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: internal compiler error: segmentation fault: 11
Dave wrote: Hello, I'm trying to compile 6.0-stable on a release box, prior to upgrade. I've tried several times and all end with an internal compiler error: segmentation fault: 11. And then i'm told to submit a bug report. My problem is when this occurs it's not always at the same spot or the same file. One time it even core dumped, though only once. At this point i would appreciate any suggestions, i'm hoping this is not the indicator of a problem. Thanks. Dave. I'd say in most cases it means that either your memory or your CPU get too hot. Open the case of your machine. If the problem disappears or at least appears less often, consider better cooling for your computer. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendmail-sasl port not work
* Paul.LKW [EMAIL PROTECTED]: Dear all: I find the sendmail-sasl port will not compile with the option SASLv2 and I can not get SMTP Auth. The port will install TLS and Cyrus-SASL but as I use the command --sendmail -d0.1 -bv root | grep SASL-- I can not find it compiled with SASL. Did you follow the instructions in /usr/ports/mail/sendmail/pkg-message and invoke the right sendmail (ie. preferably with full path in case you're unsure)? Volker -- http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME FIFA go home! ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: quota and snapshots in 6.1-RELEASE
On Tue, 2006-05-23 at 16:35 -0400, Kris Kennaway wrote: If you use snapshots with your quotas, update to 6.1-STABLE. If you don't use snapshots, 6.1-R should be fine. This was discussed in excruciating depth a few weeks back, so please read the archives for more. Probably I've to stress the box a little more but here seems to work correctly. The box is going production really soon so we will see. Thanks to all guys involved for the very good work! -- Massimo There are more way to do things, one is the bsd-way the others are wrong ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL uses more memory on 6.1?
On Tue, 2006-05-23 at 16:36 -0500, Kirk Strauser wrote: On Tuesday 23 May 2006 16:19, Jung-uk Kim wrote: I meant 'kern.ipc.shmall', which used to be 'kern.ipc.shmmaxpgs'. :-( That did it! Bumping kern.ipc.shmall to 65536 got me back up and running with enough shared_memory to get my jobs done. So what changed? Why this changes have to happen between upgrade to -STABLE from a three months old -STABLE? -- Massimo.run(); ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sendmail-sasl port not work
There are no problems with Postfix. http://wiki.botka.homeunix.org/bin/view/Main/PostfixSaslTls Cheers, -vlado D000 On Wed, 24 May 2006, Paul.LKW wrote: Dear all: I find the sendmail-sasl port will not compile with the option SASLv2 and I can not get SMTP Auth. The port will install TLS and Cyrus-SASL but as I use the command --sendmail -d0.1 -bv root | grep SASL-- I can not find it compiled with SASL. Any solution to fix it. THX. ___ 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]
Re: 5.4=6.1 regression: nforce2 vs. APIC [+fix]
on 19/05/2006 18:35 Andriy Gapon said the following: on 19/05/2006 17:54 [LoN]Kamikaze said the following: Andriy Gapon wrote: [Disclaimer, just in case: I do mean APIC, not ACPI] Based on that info and the linux patch in that thread I came up with the following PCI fixup. Now I am running 6.1 with both APIC and C1 disconnect enabled for 2 days without any problems. Did you file a PR with your fix? Not yet. I wanted to receive some feedback and test results first (and kinda hoped that this will get included without a PR). I've created a PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=97785 Thanks again to John Baldwin for his very much improved version of the patch. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
state of fs/udf
It seems that UDF fs has been in not-well-supported state for a while now. It seems that Scott Long, original author and maintainer, has moved on to other more important (and, perhaps, interesting) things. (perhaps - because RE does not seem to be too exciting on the first glance) Meanwhile, there are several bugs still opened for UDF. Some of them are pretty obvious, some with good patches, some not so trivial, some unhelpful and some are mine :-) I think the following PRs are good candidates for review and possible inclusion into source: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77234 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78987 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92040 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84983 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90521 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/97786 Also, from our private conversations I know that Bruce Evans has even more fixes for more problems and better fixes for some bugs described in the above PRs. Those patches that I personally submitted do WorkForMe (TM), but I think that Bruce has much better understanding of VFS stuff and done much better job. Would some committer be so kind to adopt UDF, review the PRs and fix at least the most obvious bugs before 6.2 ? I personally promise to help with testing and discussing things. -- Andriy Gapon ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL uses more memory on 6.1?
On May 23, 2006, at 4:31 PM, Kirk Strauser wrote: Has anyone else seen this behavior when upgrading from 6.0 to 6.1? Any ideas for a fix? no. not seen it. did you have a custom kernel with higher SHM settings on 6.0? In any case, here is what you do: in /etc/sysctl.conf add these: kern.ipc.shm_use_phys=1 kern.ipc.shmmax=1073741824 kern.ipc.shmall=262144 kern.ipc.semmsl=512 kern.ipc.semmap=256 and in /boot/loader.conf add these: kern.ipc.semmni=32 kern.ipc.semmns=512 the sem variables are really only needed if you want a lot of connections, say 100. The shm settings will cover you for tens of thousands of shared buffers in postgres. You can obviously tune those down to your taste.
semi-custom kernel (was Re: PostgreSQL uses more memory on 6.1?)
On May 24, 2006, at 2:34 AM, Claus Guttesen wrote: Thank you. I wasn't aware that one could alter sysctl's. I might dive into that, makes kernel-maintenance a tiny bit easier. Boy does it. I've recently combined all my custom kernels into a single semi-custom configuration (actually two, one for SMP and one for UP) and adjust the sysctls either at sysctl.conf or at loader.conf depending on which needs to be where to adjust resources needed by certain servers. For example, the DB servers I set the SHM and SEM settings, on the internal not-connected-to-internet boxes, I disable the firewall via sysctl, etc. I also push into kld's the rarely used devices such as CD-ROM, floppy drive, USB keyboard, gmirror, which are used on only a handful of machines. Then I load the ones I need via loader.conf so they are probed at boot. The CDROM and floppy modules are loaded on demand (ie, basically never on a server)
Re: state of fs/udf
[ CC: Bruce ] Bruce, On Wed, 24 May 2006, 16:17+0300, Andriy Gapon wrote: It seems that UDF fs has been in not-well-supported state for a while now. It seems that Scott Long, original author and maintainer, has moved on to other more important (and, perhaps, interesting) things. (perhaps - because RE does not seem to be too exciting on the first glance) Meanwhile, there are several bugs still opened for UDF. Some of them are pretty obvious, some with good patches, some not so trivial, some unhelpful and some are mine :-) I think the following PRs are good candidates for review and possible inclusion into source: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/77234 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/78987 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/92040 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/84983 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/90521 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/97786 Also, from our private conversations I know that Bruce Evans has even more fixes for more problems and better fixes for some bugs described in the above PRs. Those patches that I personally submitted do WorkForMe (TM), but I think that Bruce has much better understanding of VFS stuff and done much better job. Would some committer be so kind to adopt UDF, review the PRs and fix at least the most obvious bugs before 6.2 ? I personally promise to help with testing and discussing things. Why don't you just commit these fixes? -- Maxim Konovalov ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1-RELEASE amd64 panic: bad pte
Hi, I've just seen the following panic on a dual cpu amd64 box: FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:15:57 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP amd64 Panic happened during cd /usr/port/databases/mysql4-server make install - box was otherwise idle. TPTE at 0x840028c8 IS ZERO @ VA 800519000 panic: bad pte cpuid = 1 Uptime: 7d0h12m25s Dumping 2047 MB (2 chunks) chunk 0: 1MB (150 pages) ... ok chunk 1: 2047MB (523888 pages) 2031 2015 1999 1983 1967 1951 1935 1919 1903 1887 1871 1855 1839 1823 1807 1791 1775 1759 1743 1727 1711 1695 1679 1663 1647 1631 1615 1599 1583 1567 1551 1535 1519 1503 1487 1471 1455 1439 1423 1407 1391 1375 1359 1343 1327 1311 1295 1279 1263 1247 1231 1215 1199 1183 1167 1151 1135 1119 1103 1087 1071 1055 1039 1023 1007 991 975 959 943 927 911 895 879 863 847 831 815 799 783 767 751 735 719 703 687 671 655 639 623 607 591 575 559 543 527 511 495 479 463 447 431 415 399 383 367 351 335 319 303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15 ... ok Dump complete As this is a -RELEASE kernel, no kernel.debug exits. As an aside, what happened to the idea of generating these and putting them on the CD or the ftp site? (kgdb) bt #0 0x803d204d in doadump () #1 0x803d2074 in doadump () #2 0x0004 in ?? () #3 0x803d2677 in boot () #4 0x0019 in ?? () #5 0x0fd2cf65 in ?? () #6 0xff005d789260 in ?? () #7 0x0104 in ?? () #8 0x in ?? () Previous frame identical to this frame (corrupt stack?) # this is the TPTE pointer from the panic printf (kgdb) x/20 0x840028c8 0x840028c8: Cannot access memory at address 0x840028c8 # This address appears in the backtrace (kgdb) x/40 0xff005d789260 0xff005d789260: 0x5bf62000 0xff00 0x7b9867e0 0xff00 0xff005d789270: 0x 0x 0x5bf62020 0xff00 0xff005d789280: 0x 0x 0x7b9867f8 0xff00 0xff005d789290: 0x 0x 0x62981a80 0xff00 0xff005d7892a0: 0x 0x 0xb420b890 0x 0xff005d7892b0: 0x 0x 0x 0x 0xff005d7892c0: 0x 0x 0x5d7892c0 0xff00 0xff005d7892d0: 0x62981a80 0xff00 0x628d8500 0xff00 0xff005d7892e0: 0x60e06b80 0xff00 0x000186f4 0x05010002 0xff005d7892f0: 0x 0x 0x 0x Pointers to this structure are littered throughout the memory following the stack pointer - it seems to be a thread pointer. The first value (0xff005bf62000) appears to be a pointer to struct proc, but I'm not sure if there's anything useful that can be found from that either. The process was grep, pid 84450, p_flags are P_EXEC|P_WEXIT|P_CONTROLT - so it happened while the process was exiting, which makes sense given the panic is called from pmap_remove_pages(). I'm happy to do more digging if there are any lines of investigation anyone can suggest. Possibly-relevant bits of dmesg: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Sun May 7 04:15:57 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP ACPI APIC Table: PTLTD APIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Opteron(tm) Processor 248 (2193.76-MHz K8-class CPU) Origin = AuthenticAMD Id = 0xf5a Stepping = 10 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 AMD Features=0xe0500800SYSCALL,NX,MMX+,LM,3DNow+,3DNow real memory = 2146893824 (2047 MB) avail memory = 2062053376 (1966 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 1.1 irqs 0-23 on motherboard ioapic1 Version 1.1 irqs 24-27 on motherboard ioapic2 Version 1.1 irqs 28-31 on motherboard I have the coredump available for further analysis if anyone wants it, but without a debug kernel I appreciate it may not be useful. I'm going to compile one up, in case it happens again. Gavin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6-STABLE crashes when surfing via modem
Hello! I am running FreeBSD 6-STABLE (last update 14.5.06) on a Fujitsu Siemens Amilo A notebook. This machine has internet access via kppp and a Creative ModemBlaster V.92 serial modem. Sometimes when surfing on the internet (most times with Opera 8.51 AFAIR) the system completly locks up and reboots. I found http://www.at.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html and tried to analysis the crash dump in /var/crash but I am totally new to these things. kgdb kernel.debug /var/crash/vmcore.2 on my system gives the following output: [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] (...) Unread portion of the kernel message buffer: Fatal trap 12: page fault while in kernel mode fault virtual address = 0x29 fault code = supervisor write, page not present instruction pointer = 0x20:0xc06ad6a6 stack pointer = 0x28:0xd992f9d0 frame pointer = 0x28:0xd992fa00 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL = 0 current process = 793 (opera) trap number = 12 panic: page fault Uptime: 19m31s Dumping 478 MB (2 chunks) chunk 0: 1MB (159 pages) ... ok chunk 1: 478MB (122352 pages) 462 446 430 414 398 382 366 350 334 318 302 286 270 254 238 222 206 190 174 158 142 126 110 94 (CTRL-C to abort) (CTRL-C to abort) 78 (CTRL-C to abort) (CTRL-C to abort) (CTRL-C to abort) 62 46 30 14 #0 doadump () at pcpu.h:165 165 __asm __volatile(movl %%fs:0,%0 : =r (td)); (kgdb) quit Has anybody an idea what goes wrong on my system? What could I do in order to find out what goes wrong? Many thanks in advance, Michael ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Quotas inside jails
Sometime ago and have setup 5.3-STABLE box with quotas for jailed users. At that time quotas did not work inside jails, so i just created some group on host machine and group with the same ID inside jail and then put a quota upon that group on the host box. That was quotas are observed. However, user iside jail cannot check their quota this way. Do quotas work now (as of 6.1-STABLE) inside jails correctly? Artem ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PostgreSQL uses more memory on 6.1?
On Wednesday 24 May 2006 09:11, Vivek Khera wrote: no. not seen it. did you have a custom kernel with higher SHM settings on 6.0? Nope. I didn't touch the kernel config at all (it includes GENERIC and then adds a couple of nonrelated settings). In any case, here is what you do: Bumping shmall did the trick, but semmsl was pretty low so I bumped it up just in case. Is any of this stuff well documented other than in NOTES? I can see what each setting does, but don't really have a feel for *why* I'd need to increase a given setting, what the drawback is to increasing it, or why it was so low in the first place. For that matter, why does this stuff have to be manually configured? Couldn't the kernel automatically expand a lot of these numbers as needed? -- Kirk Strauser ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd-stable Digest, Vol 159, Issue 6
[EMAIL PROTECTED] ___ 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?
Rong-en Fan [EMAIL PROTECTED] wrote: On 5/14/06, Kris Kennaway [EMAIL PROTECTED] wrote: On Sun, May 14, 2006 at 02:28:55PM -0400, Howard Leadmon wrote: [...] 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 Hi Kris and Howard, As I posted few days ago, I have similar problems like Howard's (some details in the thread 6.1-RELEASE, em0 high interrupt rate and nfsd eats lots of cpu on stable@). After binary searching the source tree, I found that RELENG_6_1, 2006.04.30.03.57 ok RELENG_6_1, 2006.04.30.04.00 bad The only commit is kern/vfs_lookup.c, an MFC of rev 1.90 and 1.91. With 04.30 03.57's source + manaully patched vfs_lookup.c rev 1.90, the same problem occurs. [...] Confirmed! I can create the problem here at will. Setup 1: NFS server 'testido' FreeBSD 6.1-STABLE as of 15. May 2006 with sys/kern/vfs_lookup.c 1.80.2.7, NFS schurks FreeBSD 6.1-STABLE as of 15. May 2006. /usr/src from testido mounted on /mnt on schurks. running 'cd /mnt ; du /dev/null' two times (first after fresh boot of testido second when all served data is in memory of testido): joerg @ schurks cd /mnt joerg @ schurks time du /dev/null 86.09s real 0.14s user 1.91s system joerg @ schurks time du /dev/null 205.10s real 0.20s user 1.92s system joerg @ schurks Screenfull output of top on testido AFTER both tests (testido stopped responding to screen output sometimes, especially during the second test): last pid: 329; load averages: 4.14, 2.77, 1.25up 0+00:07:30 18:44:47 29 processes: 1 running, 28 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 8420K Active, 28M Inact, 72M Wired, 110M Buf, 880M Free Swap: 4000M Total, 4000M Free PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 201 root1 40 1232K 792K -4:42 116.31% nfsd 329 joerg 1 960 2404K 1676K RUN 0:00 0.00% top 168 root1 1150 2456K 1760K select 0:00 0.00% sshd 313 root1 960 1428K 1168K select 0:00 0.00% rlogind 194 root1 1150 1556K 1256K select 0:00 0.00% mountd 299 root1 80 1720K 1436K wait 0:00 0.00% login 314 root1 80 1748K 1460K wait 0:00 0.00% login 298 root1 960 1304K 1048K select 0:00 0.00% rlogind 199 root1 40 1356K 1040K accept 0:00 0.00% nfsd 256 root1 960 2892K 1760K select 0:00 0.00% ntpd 315 joerg 1 200 1448K 1020K pause0:00 0.00% ksh 300 root1 50 1448K 996K ttyin0:00 0.00% ksh 158 root1 960 1332K 940K select 0:00 0.00% syslogd 163 root1 960 1448K 1128K select 0:00 0.00% inetd 176 root1 960 1408K 1044K select 0:00 0.00% rpcbind 185 root1 960 1476K 1148K select 0:00 0.00% ypbind 261 root1 1150 1304K 952K select 0:00 0.00% lpd Setup 2: NFS server 'testido' FreeBSD 6.1-STABLE as of 15. May 2006 with sys/kern/vfs_lookup.c 1.80.2.6, NFS schurks FreeBSD 6.1-STABLE as of 15. May 2006. Same tests as before: joerg @ schurks time du /dev/null 22.63s real 0.15s user 1.82s system joerg @ schurks time du /dev/null 16.52s real 0.17s user 1.68s system joerg @ schurks Screenfull output of top on testido AFTER both tests (testido responded fine during both tests): last pid: 329; load averages: 0.49, 0.26, 0.10up 0+00:01:50 18:35:30 29 processes: 1 running, 28 sleeping CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 100% idle Mem: 8424K Active, 28M Inact, 72M Wired, 110M Buf, 880M Free Swap: 4000M Total, 4000M Free PID USERNAME THR PRI NICE SIZERES STATETIME WCPU COMMAND 201 root1 40 1232K 792K -0:03 3.76% nfsd 168 root1 1150 2456K 1760K select 0:00 0.00% sshd 329 joerg 1 960 2404K 1676K RUN 0:00 0.00% top 313 root1 960 1428K 1168K select 0:00 0.00% rlogind 194 root1 1150 1556K 1256K select 0:00 0.00% mountd 299 root1 80 1720K 1440K wait 0:00 0.00% login 314 root1 80 1748K 1464K wait 0:00 0.00% login 298 root1 960 1304K 1048K select 0:00 0.00% rlogind 199 root1 40 1356K 1040K accept 0:00 0.00% nfsd 315 joerg 1 200 1448K 1020K pause0:00 0.00% ksh 256 root1 960 2892K 1760K select 0:00 0.00% ntpd 300 root1 50 1448K 996K ttyin0:00 0.00% ksh 158 root1 960 1332K 940K select 0:00 0.00% syslogd 163 root1 960 1448K 1128K select 0:00
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: nve0: device timeout
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Damian Gerow wrote: Thus spake O. Hartmann ([EMAIL PROTECTED]) [22/05/06 20:23]: : Is there a solution on its way? What is about the Berkeley native nfe-code? As someone already pointed out, the fix is already in -CURRENT. A patch for -STABLE has been posted recently, but I don't remember if it was to stable@ or [EMAIL PROTECTED] FWIW, I'd recommend if_nfe. It's proven a little more stable for me, and I haven't had any issues with device timeouts at all. http://www.se.hiroshima-u.ac.jp/~shigeaki/software/freebsd-nfe.html All right, I did as recommended an now: Voila, I have a usable computersystem! Without any patch or the new nfe driver a system based on the ASUS A8N32-SLI is unusable! The box get stuck every few minutes for a second a loose keyboard input and corrupt DVD/DVD+-RW or CD-R/CD-RW while burning. Hope the nfe driver will find it's way into stable as fast as possible ... oh -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEdKPY9PZHcThI6nsRAivbAJ0UE9sbLeL+0sLlRcti3jA3m4iP0wCfXNdG OmlR2KW1bSxhrDrYiw1dYjE= =Elyt -END PGP SIGNATURE- ___ 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?
Another data point: One of our NFS servers is an amd64 based system serving a cluster of web and email servers. Under 6.1-RCx it gave us the same (or better) performance than the server it replaced (which was 4.11). The server load hovered between 0.x and 1.x But after upping it to 6.1-STABLE the load now hovers between 5.x and 6.x with spikes as high as 8.x, and there has been no change at all in the NFS client traffic or other loading factors that we can tell. This in turn makes for slower NFS client accesses. I am going to try reverting to an earlier src tree and see if that helps. Mark -- Mark Morley Owner / Administrator Islandnet.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
6.1 troubles -- cannot install buildworld
On an older i386 box (Pentium III), used as a workstation, we have been running FreeBSD_4.x and 5.x for a long time without problems. Now, using cvsup, we updated FreeBSD source from 5.4p14 (default release=cvs tag=RELENG_5_4) to 6.1 (default release=cvs tag=RELENG_6_1_0_RELEASE) and updated the system according to the canonical method: # cd /usr/src # make buildworld # make buildkernel # make installkernel # mergemaster -p # shutdown # cd /usr/src/ # make installworld But that last step won't run. Output is: # make installworld mkdir -p /tmp/install.e6Vg3aX8 for prog in [ awk cap_mkdb cat chflags chmod chown date echo egrep find grep install-info ln lockf make mkdir mtree mv pwd_mkdb rm sed sh sysctl test true uname wc zic; do cp `which $prog` /tmp/install.e6Vg3aX8; done cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=i386 MACHINE=i386 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/tmp/install.e6Vg3aX8 make -f Makefile.inc1 reinstall -- Making hierarchy -- cd /usr/src; make -f Makefile.inc1 hierarchy cd /usr/src/etc;make distrib-dirs mtree -eU -f /usr/src/etc/mtree/BSD.root.dist -p / mtree -eU -f /usr/src/etc/mtree/BSD.var.dist -p /var mtree -eU -f /usr/src/etc/mtree/BSD.usr.dist -p /usr mtree -eU -f /usr/src/etc/mtree/BSD.include.dist -p /usr/include mtree -deU -f /usr/src/etc/mtree/BIND.chroot.dist -p /var/named mtree -deU -f /usr/src/etc/mtree/BSD.sendmail.dist -p / cd /; rm -f /sys; ln -s usr/src/sys sys cd /usr/share/man/en.ISO8859-1; ln -sf ../man* . cd /usr/share/man; set - `grep ^[a-zA-Z] /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done cd /usr/share/openssl/man; set - `grep ^[a-zA-Z] /usr/src/etc/man.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done cd /usr/share/openssl/man/en.ISO8859-1; ln -sf ../man* . cd /usr/share/nls; set - `grep ^[a-zA-Z] /usr/src/etc/nls.alias`; while [ $# -gt 0 ] ; do rm -rf $1; ln -s $2 $1; shift; shift; done -- Installing everything -- cd /usr/src; make -f Makefile.inc1 install === share/info (install) === include (install) creating osreldate.h from newvers.sh touch: not found *** Error code 127 Stop in /usr/src/include. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Wonder whether anyone else has had any experience similar, or any insight on what to do about it. dmesg is: Copyright (c) 1992-2006 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 6.1-RELEASE #0: Wed May 24 18:48:01 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (664.51-MHz 686-class CPU) Origin = GenuineIntel Id = 0x683 Stepping = 3 Features=0x383fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 267386880 (255 MB) avail memory = 252182528 (240 MB) MPTable: COMPAQ Deskpro ioapic0: Changing APIC ID to 8 ioapic0: Assuming intbase of 0 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 cpu0 on motherboard pcib0: MPTable Host-PCI bridge pcibus 0 on motherboard pci0: PCI bus on pcib0 agp0: Intel 82815 (i815 GMCH) SVGA controller mem 0x4400-0x47ff,0x4030-0x4037 irq 16 at device 2.0 on pci0 pcib1: MPTable PCI-PCI bridge at device 30.0 on pci0 pci2: PCI bus on pcib1 fxp0: Intel 82801BA/CAM (ICH2/3) Pro/100 Ethernet port 0x1000-0x103f mem 0x4000-0x4fff irq 20 at device 8.0 on pci2 miibus0: MII bus on fxp0 inphy0: i82562EM 10/100 media interface on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:02:a5:26:1e:a5 isab0: PCI-ISA bridge at device 31.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel ICH2 UDMA100 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x2460-0x246f at device 31.1 on pci0 ata0: ATA channel 0 on atapci0 ata1: ATA channel 1 on atapci0 uhci0: Intel 82801BA/BAM (ICH2) USB controller USB-B port 0x2440-0x245f irq 23 at device 31.4 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82801BA/BAM (ICH2) USB controller USB-B on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self
Re: PostgreSQL uses more memory on 6.1?
On May 24, 2006, at 12:14 PM, Kirk Strauser wrote: Is any of this stuff well documented other than in NOTES? I can see what each setting does, but don't really have a feel for *why* I'd need to increase a given setting, what the drawback is to increasing it, or why it was so low in the first place. SYSV IPC falls into the black art part of the universe, unfortunately. You really have to dig into the application (ie, postgres in this case) to determine how much of those resources it wants. For that matter, why does this stuff have to be manually configured? Couldn't the kernel automatically expand a lot of these numbers as needed? Some are only settable at boot time because they make fixed sized structures (yes, still in this day and age...) I don't know the drawbacks of making them larger than necessary, but with multi-gig RAM servers I don't worry about it too much.
Re: PostgreSQL uses more memory on 6.1?
Kirk Strauser wrote: Bumping shmall did the trick, but semmsl was pretty low so I bumped it up just in case. Is any of this stuff well documented other than in NOTES? I can see what each setting does, but don't really have a feel for *why* I'd need to increase a given setting, what the drawback is to increasing it, or why it was so low in the first place. For the configuration of IPC for Postgresql, see: http://www.postgresql.org/docs/8.1/static/kernel-resources.html#SYSVIPC And scroll down to the section for FreeBSD. Unfortunately, that whole section on kernel resources is a bit hidden away - it usually takes me a couple of attempts to find it! cheers Mark ___ 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-stable crash
On 24 May 2006, at 7:28 AM, Peter Jeremy wrote: On Tue, 2006-May-23 19:04:18 +, Hunter Fuller wrote: Am I the only one who sees the oxymoronity in 6.1-stable crash? Hopefully. As is regularly pointed out, 'stable' refers primarily to the ABI. I was just trying to make people chuckle :( FreeBSD 6.1-stable is still under active development, though only code that has previously been tested in -current is supposed to be commited. There are also fairly regular postings pointing out that _all_ software has bugs. Some of these bugs will cause crashes. -- Peter Jeremy ___ 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
Re: Trouble with NFSd under 6.1-Stable, any ideas?
On Wed, May 24, 2006 at 11:48:53PM -0400, Howard Leadmon wrote: 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. Yep, unfortunately this commit was necessary to fix other bugs. Jeff said he should have time to look at it next week. Kris pgpjfHm2NRHm6.pgp Description: PGP signature
