Re: named.conf restored to hint zone for the root by default
Doug Barton wrote: > Oliver Fromme wrote: > > > By the way, I have changed from hints to slaves on the DNS > > servers for a large server farm (just testing right now; > > I might go back to hints if I don't feel it's worth it). > > Depending on how many name servers you have you might get a bigger win > by slaving the root to one server, then slaving it to the others from > your "local master." If you're only talking about a few name servers > it's probably not worth it though. It's three name servers, and they're intended to be completely independent of each other. That's why I've configured each of them to retrieve the root zone of its own. > > It _seems_ a few applications run with lower latency, but > > I'll need to run some benchmarks in order to get some hard > > numbers. > > If your stuff is relatively well behaved, and generally only queries a > few TLDs you might not get much of a benefit in terms of reduced > latency. In this scenario the main advantage is better resilience to a > root DDoS. > > Where this technique really works well is a scenario where you are > answering a lot of "random" queries that could potentially include > invalid TLDs and other "junk." Not sending those queries to the roots > helps reduce traffic for them and for you, and gives you much better > latency on the inevitable NXDOMAIN response. The farm contains several mail servers with spam and virus scanners, http proxies with (roughly) several thousands of users, a few dozen web servers and other things. I think especially the mail scanners and the proxies generate some amount of dns "junk" queries. Thanks for your suggestions! Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "I made up the term 'object-oriented', and I can tell you I didn't have C++ in mind." -- Alan Kay, OOPSLA '97 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Fatal error 'mutex is on list'
Hi, I am trying to install EyeDB OODBMS but when I try to initialize the database I get the following error: amber2::root:/opt> ./share/eyedb/tools/eyedb-postinstall.sh Starting EyeDB server Starting EyeDB Server Version V2.8.1 Compiled Aug 4 2007 22:20:02 Architecture i386-unknown-freebsd6.2 Program Pid 56463 Creating EYEDBDBM database Setting EYEDBDBM database permissions Fatal error 'mutex is on list' at line 540 in file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 0) EyeDB aborting [pid = 56711] I have looked at the sources at the line but I am not any wiser. Any ideas what's wrong? -- VH ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problem adding new slices
I am running 6.2 STABLE and am having an issue adding new slices to a disk on a running system. The drive ad0 is 160GB and my original plan was to add slices as I needed them. I have successfully created slice ad0s1 for all typical mount points, and was even able to create ad0s2d for mount point /c. The problem now is that I am unable to create a third slice, ad0s3d, on mount point /d. I've tried using sysinstall to do this, and in the Label editor the final message is: Error mounting /dev/ad0s3d on /d : No such file or directory. I checked /dev, and sure enough ad0s3d is not in there. It just never gets created. I have tried doing this in several ways; rebooting after using fdisk to create the partition, then running Label editor but the result is always the same. I even tried moving all the files I had on /c to another machine, deleting that slice (originally 15GB) and creating a much larger one in its place (now 60GB), but the end result of that is the "new" slice is the same size of the old one, even though in the Label editor it shows the new larger size I created. If anyone has any suggestions, even bypassing sysinstall entirely and using other utilities, please let me know the exact steps to take. Thanks, -Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem adding new slices
> Date: Sun, 05 Aug 2007 10:24:21 -0700 > From: Jason Edward Kocol <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > I am running 6.2 STABLE and am having an issue adding new slices to a > disk on a running system. The drive ad0 is 160GB and my original plan > was to add slices as I needed them. I have successfully created slice > ad0s1 for all typical mount points, and was even able to create ad0s2d > for mount point /c. The problem now is that I am unable to create a > third slice, ad0s3d, on mount point /d. I've tried using sysinstall to > do this, and in the Label editor the final message is: > > Error mounting /dev/ad0s3d on /d : No such file or directory. > > I checked /dev, and sure enough ad0s3d is not in there. It just never > gets created. > > I have tried doing this in several ways; rebooting after using fdisk to > create the partition, then running Label editor but the result is always > the same. I even tried moving all the files I had on /c to another > machine, deleting that slice (originally 15GB) and creating a much > larger one in its place (now 60GB), but the end result of that is the > "new" slice is the same size of the old one, even though in the Label > editor it shows the new larger size I created. > > If anyone has any suggestions, even bypassing sysinstall entirely and > using other utilities, please let me know the exact steps to take. A bit of a lack of information in yo9ur report. Please provide the output of 'fdisk ad0' and 'bsdlabel /dev/ad0s3'. My suspicion is that there is a problem in the slicing, but there is not any real data in the report on which I can to base that. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgp9sEMqnL6vj.pgp Description: PGP signature
Re: Problem adding new slices
Kevin Oberman wrote: Date: Sun, 05 Aug 2007 10:24:21 -0700 From: Jason Edward Kocol <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] I am running 6.2 STABLE and am having an issue adding new slices to a disk on a running system. The drive ad0 is 160GB and my original plan was to add slices as I needed them. I have successfully created slice ad0s1 for all typical mount points, and was even able to create ad0s2d for mount point /c. The problem now is that I am unable to create a third slice, ad0s3d, on mount point /d. I've tried using sysinstall to do this, and in the Label editor the final message is: Error mounting /dev/ad0s3d on /d : No such file or directory. I checked /dev, and sure enough ad0s3d is not in there. It just never gets created. I have tried doing this in several ways; rebooting after using fdisk to create the partition, then running Label editor but the result is always the same. I even tried moving all the files I had on /c to another machine, deleting that slice (originally 15GB) and creating a much larger one in its place (now 60GB), but the end result of that is the "new" slice is the same size of the old one, even though in the Label editor it shows the new larger size I created. If anyone has any suggestions, even bypassing sysinstall entirely and using other utilities, please let me know the exact steps to take. A bit of a lack of information in yo9ur report. Please provide the output of 'fdisk ad0' and 'bsdlabel /dev/ad0s3'. My suspicion is that there is a problem in the slicing, but there is not any real data in the report on which I can to base that. Thank you, here is that information: /root> fdisk ad0 *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=232581 heads=16 sectors/track=63 (1008 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 30716217 (14998 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 1023/ head 254/ sector 63 The data for partition 2 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 30716280, size 122865120 (59992 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 3 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 153581400, size 61432560 (29996 Meg), flag 80 (active) beg: cyl 1023/ head 255/ sector 63; end: cyl 1023/ head 254/ sector 63 The data for partition 4 is: /root> bsdlabel /dev/ad0s3 bsdlabel: /dev/ad0s3: No such file or directory ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem adding new slices
Sorry. I read that there was no /dev/ad0s3, so there was no reason to ask for the bsdlabel output. First, the slicing looks good. All of the numbers are reasonable and add up correctly. I now must suspect it's a GEOM issue. It looks like GEOM is not tasting the drive properly, but this gets out of my realm of expertise. I would suggest getting the dmesg from a verbose boot and posting it along with your kernel config somewhere so that people can examine them. And let us know when the sources were updated. I suspect I will not be the one to find anything, though. Everything looks fine to me...except that it does not work. :-( -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpgsUN5DNNhJ.pgp Description: PGP signature
Re: Problem adding new slices
Kevin Oberman wrote: Sorry. I read that there was no /dev/ad0s3, so there was no reason to ask for the bsdlabel output. First, the slicing looks good. All of the numbers are reasonable and add up correctly. I now must suspect it's a GEOM issue. It looks like GEOM is not tasting the drive properly, but this gets out of my realm of expertise. I would suggest getting the dmesg from a verbose boot and posting it along with your kernel config somewhere so that people can examine them. And let us know when the sources were updated. I suspect I will not be the one to find anything, though. Everything looks fine to me...except that it does not work. :-( I don't know what I did differently this time, but I finally got it to work. Here are the steps I took. May not be the best method but it got the slice created and mountable. I didn't like all the reboots but they seemed to make a difference. 1) Ran sysinstall. Created slice ad0s3 in fdisk using the remaining portion of the disk (just so I don't have to go through this again). Wrote changes here. Rebooted. 2) Checked /dev. /dev/ad0s3 and /dev/ad0s3c finally exist, therefore off to a better start. 3) Ran sysinstall again. Created /d partition in label editor. Wrote changes. Rebooted. 4) Checked /dev. /dev/ad0s3d is now there. It was at this point that I tried to mount the partition, which failed with an incorrect super block error. Then it occurred to me that I never actually saw newfs run from sysinstall like it usually does during a fresh install or adding a new disk. So I did one more step: 5) newfs /dev/ad0s3d. The partition was able to be mounted. Here are some caveats to this whole thing, for those that are interested: - Needed to run 'sysctl kern.geom.debugflag=16' every time I needed to write a change to the disk after a fresh boot, since it was a new partition on the disk for the running system. - sysinstall reported that the geometry was incorrect for this disk, so it used a "more likely geometry." I don't remember the values it chose, but when I tried to put in the ones that my BIOS reported it didn't like those either. So your suspicions of a GEOM issue may have been well-founded initially. I would post a verbose dmesg and kernel config as suggested, but since everything works now I don't know how useful or necessary it would be to anyone else who might encounter this problem. The whole thing was rather mysterious to me from the get-go, quite honestly. Thanks, -Jason ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem adding new slices
> Date: Sun, 05 Aug 2007 17:30:34 -0700 > From: Jason Edward Kocol <[EMAIL PROTECTED]> > > Kevin Oberman wrote: > > Sorry. I read that there was no /dev/ad0s3, so there was no reason to > > ask for the bsdlabel output. > > > > First, the slicing looks good. All of the numbers are reasonable and add > > up correctly. > > > > I now must suspect it's a GEOM issue. It looks like GEOM is not tasting > > the drive properly, but this gets out of my realm of expertise. I would > > suggest getting the dmesg from a verbose boot and posting it along with > > your kernel config somewhere so that people can examine them. And let us > > know when the sources were updated. > > > > I suspect I will not be the one to find anything, though. Everything > > looks fine to me...except that it does not work. :-( > > I don't know what I did differently this time, but I finally got it to > work. Here are the steps I took. May not be the best method but it got > the slice created and mountable. I didn't like all the reboots but they > seemed to make a difference. > > 1) Ran sysinstall. Created slice ad0s3 in fdisk using the remaining > portion of the disk (just so I don't have to go through this again). > Wrote changes here. Rebooted. > 2) Checked /dev. /dev/ad0s3 and /dev/ad0s3c finally exist, therefore > off to a better start. > 3) Ran sysinstall again. Created /d partition in label editor. Wrote > changes. Rebooted. > 4) Checked /dev. /dev/ad0s3d is now there. > > It was at this point that I tried to mount the partition, which failed > with an incorrect super block error. Then it occurred to me that I > never actually saw newfs run from sysinstall like it usually does during > a fresh install or adding a new disk. So I did one more step: > > 5) newfs /dev/ad0s3d. > > The partition was able to be mounted. > > Here are some caveats to this whole thing, for those that are interested: > > - Needed to run 'sysctl kern.geom.debugflag=16' every time I needed to > write a change to the disk after a fresh boot, since it was a new > partition on the disk for the running system. > - sysinstall reported that the geometry was incorrect for this disk, so > it used a "more likely geometry." I don't remember the values it chose, > but when I tried to put in the ones that my BIOS reported it didn't like > those either. So your suspicions of a GEOM issue may have been > well-founded initially. > > I would post a verbose dmesg and kernel config as suggested, but since > everything works now I don't know how useful or necessary it would be to > anyone else who might encounter this problem. The whole thing was > rather mysterious to me from the get-go, quite honestly. If it's done, there is probably no reason to post anything else. As far as newfs(8) is concerned, you need to use 'T' on any partition you want to have newfs(8) run on. If you choose auto, it is set by default. You probably want to always set up new partitions with newfs and softupdates. Of course, if you know that the disk will be mostly large files or lots of small files, you may want to adjust newfs parameters for greater efficiency. In the future, it seems like zfs will be a better option for this sort of thing, but it won't be available until V7 is out and, even then, will work far better on 64 bit systems. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: [EMAIL PROTECTED] Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 pgpamTH6f4ahs.pgp Description: PGP signature
Re: Fatal error 'mutex is on list'
Vaclav Haisman wrote: Hi, I am trying to install EyeDB OODBMS but when I try to initialize the database I get the following error: amber2::root:/opt> ./share/eyedb/tools/eyedb-postinstall.sh Starting EyeDB server Starting EyeDB Server Version V2.8.1 Compiled Aug 4 2007 22:20:02 Architecture i386-unknown-freebsd6.2 Program Pid 56463 Creating EYEDBDBM database Setting EYEDBDBM database permissions Fatal error 'mutex is on list' at line 540 in file /usr/src/lib/libpthread/thread/thr_mutex.c (errno = 0) EyeDB aborting [pid = 56711] I have looked at the sources at the line but I am not any wiser. Any ideas what's wrong? -- VH In most time, this means the program is abusing mutex in child process or signal handler. Regards, David Xu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpd just sits there and does nothing
In message: <[EMAIL PROTECTED]> Oliver Fromme <[EMAIL PROTECTED]> writes: : [LoN]Kamikaze <[EMAIL PROTECTED]> wrote: : > My original intention was just to say that openntpd works just out of the box, : > while ntpd doesn't. : : That's just plain wrong. ntpd _does_ work out of the box : (unless your configuration is broken), and it seems to be : more accurate than openntpd. : : Demanding to replace ntpd with openntpd in the FreeBSD : base system because you cannot get the configuration right : is ridiculous. Especially since my company builds stratum 1 ntp servers that get time from GPS, Loran and Hp5071A cesium standards. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Problem adding new slices
On Sun, Aug 05, 2007 at 05:30:34PM -0700, Jason Edward Kocol wrote: > I don't know what I did differently this time, but I finally got it to > work. Here are the steps I took. May not be the best method but it got > the slice created and mountable. I didn't like all the reboots but they > seemed to make a difference. There is no mystery here, it is actually a FAQ. <...> The deciding moment was this: > - Needed to run 'sysctl kern.geom.debugflag=16' every time I needed to > write a change to the disk after a fresh boot, since it was a new partition > on the disk for the running system. If you have any partition within a slice mounted, then you absolutely must either umount all partitions within that slice, or set this sysctl for any changes to the disklabel to take effect. Same game with fdisk, only in that case not with partitions but with slices. So, if you already have ad0s1 and ad0s2 say, and want to edit the label for ad0s2, then you can have partitions in ad0s1 mounted, but you either have to umount anything within ad0s2 or set the sysctl you mentioned. Otherwise, the bsdlabel command will appear to work but the changes will not be saved to the disk. If you have the same situation but want to use fdisk, then you cannot have anything mounted within ad0, or you have to set the sysctl, otherwise your changes will not be written to disk. All the reboots were probably unneeded, btw, but a good test that the changes you made survived. > - sysinstall reported that the geometry was incorrect for this disk, so it > used a "more likely geometry." I don't remember the values it chose, but > when I tried to put in the ones that my BIOS reported it didn't like those > either. So your suspicions of a GEOM issue may have been well-founded > initially. As far as I am aware, sysinstall has been reporting this for every disk that was larger than a specific size, which means to pretty much every disk for years now. It can be ignored. I am glad it worked for you eventually, though. -- Regards: Szilveszter ADAM Budapest Hungary ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
