Re: named.conf: query-source address
On Fri, 18 Jul 2008, Mark Andrews wrote: > To: Matthew Seaman <[EMAIL PROTECTED]> > > query-source is only ever used by recursive or stub resolvers -- > > instances of named that will go out and make queries on the net on your=20 > > behalf. Authoritative servers really don't need it. > > Actually authoritative servers make queries to work out > where to send notify messages. While sending a notify to > the wrong place is not that bad. It is good practice to > see that authoritative servers are also fixed now rather > than later. Servers have a habit of changing roles and > when that happens not everyone will looks in options to see > if query source is correct. > > Also at some point I'd like to be able to get rid of masters > clauses or at least go from IP addresses to hostnames. The > slave / stub zones would then have to go out and discover > the ip address on the fly. Re the latter point, I can see the advantage of being able to move a primary server to a new IP address without needing slave/s to update their config. On the other hand I can see possible chicken/egg issues in some instances, for example testing axfrs before a new domain comes online, or a domain disappearing even temporarily ([re-]registration problems, politics or other upstream failures) where specifying masters by IP address keeps things rolling. At least consider keeping config-time hostname resolution of masters optional? And I guess the same principles apply to allow-transfer, forwarders and other address lists? cheers, Ian ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB stall with creative nomad
Mark Kirkwood wrote: I wrote: Mar 27 13:32:30 zmori kernel: da0: Removable Direct Access SCSI-4 device Mar 27 13:32:30 zmori kernel: da0: 1.000MB/s transfers Mar 27 13:32:30 zmori kernel: da0: 125MB (256001 512 byte sectors: 64H 32S/T 125C) Mar 27 13:32:39 zmori kernel: umass0: BBB reset failed, STALLED Mar 27 13:32:39 zmori kernel: umass0: BBB bulk-in clear stall failed, STALLED ...and this is already logged as usb/119481, sorry missed it when searching gnats previously. Actually that above pr is for a stall on different hardware - the correct one is: usb/78984 There is a patch included there for RELENG_7, which basically applies an off-by-1 quirk to the particular device. It was commented in (one of) the related prs that this should not be necessary as Linux does not quirk any of its Nomad entries. Interestingly, it actually needs to - the 128MB Nomad does not work in Linux either! 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: named.conf: query-source address
> query-source is only ever used by recursive or stub resolvers -- > instances of named that will go out and make queries on the net on your=20 > behalf. Authoritative servers really don't need it. Actually authoritative servers make queries to work out where to send notify messages. While sending a notify to the wrong place is not that bad. It is good practice to see that authoritative servers are also fixed now rather than later. Servers have a habit of changing roles and when that happens not everyone will looks in options to see if query source is correct. Also at some point I'd like to be able to get rid of masters clauses or at least go from IP addresses to hostnames. The slave / stub zones would then have to go out and discover the ip address on the fly. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [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: Following upgrade 6.3 >7.0 /usr/libexec/save-entropy query
David Southwell wrote: Receiving Automated message from cron No such messages under 6.3 Is there anything I need to attend to here? Subject: Cron <...> /usr/libexec/save-entropy Date: Thursday 17 July 2008 From: Cron Daemon To: >[EMAIL PROTECTED] unlink: /var/db/entropy/saved-entropy.8: No such file or directory mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory mv: /var/db/entropy/saved-entropy.1: No such file or directory Looks like some of those files went missing, but not all. This problem will correct itself in roughly 88 minutes, but if it hasn't, or if it's annoying you, just 'rm /var/db/entropy/*' and let it start from scratch. hth, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Following upgrade 6.3 >7.0 /usr/libexec/save-entropy query
Receiving Automated message from cron No such messages under 6.3 Is there anything I need to attend to here? Subject: Cron <...> /usr/libexec/save-entropy Date: Thursday 17 July 2008 From: Cron Daemon To: >[EMAIL PROTECTED] unlink: /var/db/entropy/saved-entropy.8: No such file or directory mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory mv: /var/db/entropy/saved-entropy.1: No such file or directory David unlink: /var/db/entropy/saved-entropy.8: No such file or directory mv: /var/db/entropy/saved-entropy.7: No such file or directory mv: /var/db/entropy/saved-entropy.5: No such file or directory mv: /var/db/entropy/saved-entropy.1: 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]"
Using IP aliases, was: named.conf: query-source address
On Jul 17, 2008, at 7:00 AM, Eugene Grosbein wrote: About the only common reason to set up multiple aliases on an interface is when you're doing something like hosting multiple SSL webservers on a single box which actually need to have distinct IPs as a consequence. Other than that, using public IPs for aliases is usually wasteful of IP address space. YMMV... Think about multiple IP-based services (not HTTP "virtual" servers) at one physical host that should use distinct IP addresses for some reasons (local policy/billing/monitoring/etc.) I'll reply to this particular message, but let me generalize against some of the other responses as well. If your organization does billing based on traffic, or wants to do traffic shaping or bandwidth limitation, great; but IPFW+Dummynet or PF +ALTQ don't care whether you recognize traffic by IP alone or by IP +port(s), so long as the ports are distinct for each billing category or packet queue you want to run. If you want to organize specific services on specific ports which have different backend hosts handling them to distribute load or allow you to rebalance your hardware to meet changing demand, by all means. You can have a hardware load-balancer like a NetScaler, or even use the RFC-2391 capabilities of IPFW+natd or "RDR ROUND ROBIN" with PF. But if you do that, you might as well put the actual backend machines on a RFC-1918 subnet and you might well end up using fewer public IPs than you would if all machines had public IPs. I don't have any problem with people deciding for themselves how they want to manage their services and their networks. It's just that, too often, people use IP aliases to do things like make a single physical machine appear as two so they don't actually bother to provide two actual machines for hosting DNS services with proper redundancy. Even for the shared webhosting case, where you need separate IPs per SSL cert as HTTPS doesn't support name-based virtual hosts, I'm a little dubious about the notion that having a single machine hosting lots of distinct websites, probably for different clients, is a good idea from the standpoint of security. Regards, -- -Chuck ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: taskqueue timeout [SOLVED]
> Steve Bertrand wrote: > The only other box I have with four SATA ports on it is my actual > workstation. The board is ASUS P5GD1, and has an Intel 82801FR SATA > controller. I transferred the SATA disks to the above board, loaded up the zpool, and I can not reproduce the problem :) Currently, for the last 15 minutes, I'm writing 80MB/s to the zpool with no problems. Thanks all, Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: taskqueue timeout
Steve Bertrand wrote: I'm wondering if the problems described in the following link have been resolved: http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2008-02/msg00211.html I've got four 500GB SATA disks in a ZFS raidz pool, and all four of them are experiencing the behavior. Thanks to all who have provided patches off list. Unfortunately, none of them helped. The only other box I have with four SATA ports on it is my actual workstation. The board is ASUS P5GD1, and has an Intel 82801FR SATA controller. I despise the thought that if this works, I'll have to rebuild my workstation, but heres to sacrificing my Windows PC in the name of ruling out the problem. In the meantime, can anyone provide any feedback on the board I mentioned in regards to FreeBSD? Steve ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: HP Pavilion dv2000 laptop wont boot off install cd
On Thu, 17 Jul 2008 08:31:37 -0400 Kevin K <[EMAIL PROTECTED]> wrote: > For 7.0-RELEASE, it > seemed to hang at "Trying to mount root from ufs:/dev/md0". How long did you wait? If you didn't wait 10 or 15 minutes, please do. Various tests / probes take a long time to time out on some hardware. HTH -- Regards, Torfinn Ingolfsen ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portsclean doesnt like my upgrade from 6.3 > 7.0
On Thursday 17 July 2008 07:32:11 Andrew D wrote: > David Southwell wrote: > > On Thursday 17 July 2008 06:39:26 Kris Kennaway wrote: > >> David Southwell wrote: > >>> It looks as though I have missed something!! > >>> FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul > >>> 16 09:27:38 PDT 2008 > >>> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 > >>> > >>> [EMAIL PROTECTED] ~]# portsclean > >>> FFaattaall eeoorr ''Thread is not system scope. > >>> Thread is not system scope. > >>> '' aatt lliinnee 331199 iinn > >>> ffiillee > >>> /usr/src/lib/libpthread/thread/thr_sig.c/usr/src/lib/libpthread/thread/ > >>>th r_sig.c ((eennoo == 22)) > >>> > >>> Segmentation fault: 11 (core dumped) > >>> > >>> Ok where do I go from here?? > >> > >> Find out which port(s) you didnt recompile as part of the upgrade (e.g. > >> check mtime in /usr/local), and do that now. You may need to also > >> recompile the ports that depend on them to undo the damage. > >> > >> Kris > >> ___ > > > > Thanks Kris > > I have been unable to find instructions in the manual about recompiling > > ports as part of a system upgrade process. There seems to be no reference > > to it. The upgrade from 6.1 to 6.3 seemed to work OK once I sorted out a > > problem with perl. However 6.3 to 7.0 seems to produce more difficulties > > than I bargained for!!! > > > > How can I best reconfigure and recompile all th installed ports? > > > > As you can see from below: > > [EMAIL PROTECTED] ~]# portupgrade -a > > Fatal error 'Thread is not system scope. > > ' at line 319 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = > > 2) Segmentation fault: 11 (core dumped) > > I saw this not too long ago, The culprit was ruby. > > Go into each of these ports and > 'make clean && make && make deinstall reinstall' them > > lang/ruby18 (I assume) > databases/ruby-bdb > ports-mgmt/portupgrade > > you might have blow away /var/db/pkg/pkgdb.db a couple of times for it > to work. > > Then portupgrade should work fine :) > Right on the nail !! I now have portupgrade -af fulfilling its magic Thank you and everyone else. David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
iLO virtual Drive setup help
Hi, I was trying to mount virtual CDROM using Intel RMM module. RMM module is capable of redirecting four iso images or drives, and looking in to /dev my filesystem FreeBSD has labeled those as /cd0, /cd1, /cd2, /cd3. Once I boot the system connecting virtual drive, it boots from that drive and after that it's asking about to select drive to boot from (here cd0, cd1, cd2, acd0), after that it is not going further. My "camcontrol devlist" output reflects following. at scbus0 target 0 lun 0 (cd0,pass0) at scbus1 target 0 lun 0 (cd1,pass1) at scbus2 target 0 lun 0 (cd2,pass2) at scbus3 target 0 lun 0 (cd3,pass3) When I try to mount cdrom with "mount_cd9660 /dev/cd0 /cdrom" it gives me following error G_vfs_done():cd0[READ(offset=32768, length-2048)]error = 5 Mount_cd9660: /dev/cd0: Input/output error My part of /etc/fstab file reads like following ** ** /dev/cd0/cdrom4 cd9660 ro,noauto 0 0 /dev/cd1/cdrom1 cd9660 ro,noauto 0 0 /dev/cd2/cdrom2 cd9660 ro,noauto 0 0 /dev/cd3/cdrom3 cd9660 ro,noauto 0 0 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 ** * ** I am a newbie to FreeBSD, so any help really appreciated. Sincerely yours, M. Bhavsar ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portsclean doesnt like my upgrade from 6.3 > 7.0
David Southwell wrote: On Thursday 17 July 2008 06:39:26 Kris Kennaway wrote: David Southwell wrote: It looks as though I have missed something!! FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 09:27:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~]# portsclean FFaattaall eeoorr ''Thread is not system scope. Thread is not system scope. '' aatt lliinnee 331199 iinn ffiillee /usr/src/lib/libpthread/thread/thr_sig.c/usr/src/lib/libpthread/thread/th r_sig.c ((eennoo == 22)) Segmentation fault: 11 (core dumped) Ok where do I go from here?? Find out which port(s) you didnt recompile as part of the upgrade (e.g. check mtime in /usr/local), and do that now. You may need to also recompile the ports that depend on them to undo the damage. Kris ___ Thanks Kris I have been unable to find instructions in the manual about recompiling ports as part of a system upgrade process. There seems to be no reference to it. The upgrade from 6.1 to 6.3 seemed to work OK once I sorted out a problem with perl. However 6.3 to 7.0 seems to produce more difficulties than I bargained for!!! It was clearly mentioned in the release announcement :) How can I best reconfigure and recompile all th installed ports? As you can see from below: [EMAIL PROTECTED] ~]# portupgrade -a Fatal error 'Thread is not system scope. ' at line 319 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) Segmentation fault: 11 (core dumped) Try pkg_deleting portupgrade and ruby* and reinstalling them, then proceed with portupgrade -fa (note -f!) or -faP. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portsclean doesnt like my upgrade from 6.3 > 7.0
David Southwell wrote: On Thursday 17 July 2008 06:39:26 Kris Kennaway wrote: David Southwell wrote: It looks as though I have missed something!! FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 09:27:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~]# portsclean FFaattaall eeoorr ''Thread is not system scope. Thread is not system scope. '' aatt lliinnee 331199 iinn ffiillee /usr/src/lib/libpthread/thread/thr_sig.c/usr/src/lib/libpthread/thread/th r_sig.c ((eennoo == 22)) Segmentation fault: 11 (core dumped) Ok where do I go from here?? Find out which port(s) you didnt recompile as part of the upgrade (e.g. check mtime in /usr/local), and do that now. You may need to also recompile the ports that depend on them to undo the damage. Kris ___ Thanks Kris I have been unable to find instructions in the manual about recompiling ports as part of a system upgrade process. There seems to be no reference to it. The upgrade from 6.1 to 6.3 seemed to work OK once I sorted out a problem with perl. However 6.3 to 7.0 seems to produce more difficulties than I bargained for!!! How can I best reconfigure and recompile all th installed ports? As you can see from below: [EMAIL PROTECTED] ~]# portupgrade -a Fatal error 'Thread is not system scope. ' at line 319 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) Segmentation fault: 11 (core dumped) I saw this not too long ago, The culprit was ruby. Go into each of these ports and 'make clean && make && make deinstall reinstall' them lang/ruby18 (I assume) databases/ruby-bdb ports-mgmt/portupgrade you might have blow away /var/db/pkg/pkgdb.db a couple of times for it to work. Then portupgrade should work fine :) HTH cya Andrew I have definitely omitted a vital step ___ 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: RELENG_7: /boot/loader command prompt mode broken?
On Tuesday 08 July 2008 09:54:29 am Kelly Black wrote: > >Message: 4 > >Date: Mon, 07 Jul 2008 14:10:45 -0700 > >From: "Kevin Oberman" <[EMAIL PROTECTED]> > >Subject: Re: RELENG_7: /boot/loader command prompt mode broken? > >To: Eugene Grosbein <[EMAIL PROTECTED]> > >Cc: [EMAIL PROTECTED] > >Message-ID: <[EMAIL PROTECTED]> > >Content-Type: text/plain; charset="us-ascii" > > > >> Date: Mon, 7 Jul 2008 18:21:47 +0800 > >> From: Eugene Grosbein <[EMAIL PROTECTED]> > >> Sender: [EMAIL PROTECTED] > >> > >> Hi! > >> > >> Today I've updated my 7.0-STABLE system using source upgrade path. > >> loader(8) boots it just fine but it's impossible to issue commands > >> using its command prompt mode (N.B.: beastie_disable="YES" > >> and autoboot_delay="2" are in my /boot/loader.conf). > >> > >> At boot time, I hit "Space" button to reach its command prompt - that works. > >> While typing of a command, I observe one of bad things: > >> > >> 1) it just hangs solid (keyboard LEDs do not switch) after a couple > >> of characters entered, or > >> 2) system spontaneously reboots while typing, or > >> 3) it shows endless flow of hex dump, presumably from BTX. > >> > >> Most of time it hangs, a couple of times I've got reboot > >> and once there was hex dump. I use vidconsole with PS/2 keyboard. > >> > >> Seldom I've allowed to type 'boot -s' and hit enter without a problem - > >> it boots system OK then. So, I assume there is a problem > >> with vidconsole input/output routines. > >> > [Snip ... ] > >> > > I am having a similar problem. I removed the config.boot file with no > change. Someone in this list posted the following links: Are you using a serial console? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Multi-machine mirroring choices
On Tue, 2008-07-15 at 16:20 +0100, Pete French wrote: > > However, I must ask you this: why are you doing things the way you are? > > Why are you using the equivalent of RAID 1 but for entire computers? Is > > there some reason you aren't using a filer (e.g. NetApp) for your data, > > thus keeping it centralised? > > I am not the roiginal poster, but I am doing something very similar and > can answer that question for you. Some people get paranoid about the > whole "single point of failure" thing. I originally suggestted that we buy > a filer and have identical servers so if one breaks we connect the other > to the filer, but the response I got was "what if the filer breaks?". So > in the end I had to show we have duplicate independent machines, with the > data kept symetrical on them at all times. > > It does actually work quite nicely actually - I have an "'active" database > machine, and a "passive". The opassive is only used if the active fails, > and the drives are run as a gmirror pair with the remote one being mounted > using ggated. It also means I can flip from active to passive when I want > to do an OS upgrade on the active machine. Switching takes a few seconds, > and this is fine for our setup. > > So the answer is that the descisiuon was taken out of my hands - but this > is not uncommon, and as a roll-your-own cluster it works very nicely. > > -pete. > ___ I have for now gone with using ggate[cd] along with zpool and so far it's not bad. I can fail the master, stop ggated on the slave at which point geom reads the glabeled disks. From there I can zpool import to an alternate root. When the master comes back up I can zpool export and then, on the master, zpool import at which point zfs handles the resilvering. The *big* issue I have right now is dealing with the slave machine going down. Once the master no longer has a connection to the ggated devices, all processes trying to use the device hang in D status. I have tried pkill'ing ggatec to no avail and ggatec destroy returns a message of gctl being busy. Trying to ggatec destroy -f panics the machine. Does anyone know how to successfully time out a failed ggatec connection so that I can zpool detach or somehow have zfs removed the unavailable drive? Sven signature.asc Description: This is a digitally signed message part
Re: Portsclean doesnt like my upgrade from 6.3 > 7.0
On Thursday 17 July 2008 06:39:26 Kris Kennaway wrote: > David Southwell wrote: > > It looks as though I have missed something!! > > FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 > > 09:27:38 PDT 2008 > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 > > > > [EMAIL PROTECTED] ~]# portsclean > > FFaattaall eeoorr ''Thread is not system scope. > > Thread is not system scope. > > '' aatt lliinnee 331199 iinn > > ffiillee > > /usr/src/lib/libpthread/thread/thr_sig.c/usr/src/lib/libpthread/thread/th > >r_sig.c ((eennoo == 22)) > > > > Segmentation fault: 11 (core dumped) > > > > Ok where do I go from here?? > > Find out which port(s) you didnt recompile as part of the upgrade (e.g. > check mtime in /usr/local), and do that now. You may need to also > recompile the ports that depend on them to undo the damage. > > Kris > ___ Thanks Kris I have been unable to find instructions in the manual about recompiling ports as part of a system upgrade process. There seems to be no reference to it. The upgrade from 6.1 to 6.3 seemed to work OK once I sorted out a problem with perl. However 6.3 to 7.0 seems to produce more difficulties than I bargained for!!! How can I best reconfigure and recompile all th installed ports? As you can see from below: [EMAIL PROTECTED] ~]# portupgrade -a Fatal error 'Thread is not system scope. ' at line 319 in file /usr/src/lib/libpthread/thread/thr_sig.c (errno = 2) Segmentation fault: 11 (core dumped) I have definitely omitted a vital step ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named.conf: query-source address
On Wed, Jul 16, 2008 at 09:06:33PM -0700, Chuck Swiger wrote: > >Isn't this common to have multiple aliases at an interface? > >Sometimes only one of them should be used for all DNS traffic. > > About the only common reason to set up multiple aliases on an > interface is when you're doing something like hosting multiple SSL > webservers on a single box which actually need to have distinct IPs as > a consequence. Other than that, using public IPs for aliases is > usually wasteful of IP address space. YMMV... Think about multiple IP-based services (not HTTP "virtual" servers) at one physical host that should use distinct IP addresses for some reasons (local policy/billing/monitoring/etc.) Eugene Grosbein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to get more logging from GEOM?
On Thu, Jul 17, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote: > > -- Original message -- > From: "Ben Kaduk" <[EMAIL PROTECTED]> >> >> You don't need to compile the kernel on the same machine that you use it >> on -- you can copy the compiled kernel into /boot/kernel.new >> > But how do you handle the issue of differences in contents on the board where > you don't have exact identical hardwares? > The kernel configuration file specifies which device drivers will be included in the compiled kernel; if those devices aren't present in the system, the relevant code is present but doesn't get used. For example, the GENERIC kernel has the majority of device drivers included, so that most devices will be recognized out-of-the-box. A more difficult problem to solve is when you want to compile a kernel for a different architecture; say, to compile a kernel for x86 on an amd64 build machine. This can still be done, but it requires a fair amount more work. -Ben Kaduk ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portsclean doesnt like my upgrade from 6.3 > 7.0
David Southwell wrote: It looks as though I have missed something!! FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 09:27:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~]# portsclean FFaattaall eeoorr ''Thread is not system scope. Thread is not system scope. '' aatt lliinnee 331199 iinn ffiillee /usr/src/lib/libpthread/thread/thr_sig.c/usr/src/lib/libpthread/thread/thr_sig.c ((eennoo == 22)) Segmentation fault: 11 (core dumped) Ok where do I go from here?? Find out which port(s) you didnt recompile as part of the upgrade (e.g. check mtime in /usr/local), and do that now. You may need to also recompile the ports that depend on them to undo the damage. Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Portsclean doesnt like my upgrade from 6.3 > 7.0
It looks as though I have missed something!! FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 09:27:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 [EMAIL PROTECTED] ~]# portsclean FFaattaall eeoorr ''Thread is not system scope. Thread is not system scope. '' aatt lliinnee 331199 iinn ffiillee /usr/src/lib/libpthread/thread/thr_sig.c/usr/src/lib/libpthread/thread/thr_sig.c ((eennoo == 22)) Segmentation fault: 11 (core dumped) Ok where do I go from here?? David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dragon_Saver Error 19 Freebsd 7.0 AMD64
On Thursday 17 July 2008 02:24:34 Jeremy Chadwick wrote: > On Thu, Jul 17, 2008 at 02:17:12AM -0700, Jeremy Chadwick wrote: > > On Thu, Jul 17, 2008 at 02:08:58AM -0700, David Southwell wrote: > > > Just upgraded from Freebsd 6.3 to 7.0 > > > > > > uname -a > > > FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul > > > 16 09:27:38 PDT 2008 > > > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 > > > Have the following entry in > > > > > > /var/log/essages: > > > > > > Jul 17 01:28:46 dns1 kernel: dragon_saver: the console does not support > > > M_VGA_CG320 > > > Jul 17 01:28:46 dns1 kernel: module_register_init: MOD_LOAD > > > (dragon_saver, 0xadf7a140, 0) error 19 > > > > That looks to be some kind of screen-saver for VGA consoles, similar to > > daemon_saver or green_saver. Look at the splash(4) manpage. > > > > There is no 'dragon_saver' that comes with FreeBSD 7.0, however. And I > > don't remember reading about it on FreeBSD 6.x either. > > > > Usually things like that are loaded via rc.conf or loader.conf. > > I stand corrected -- it appears to come with FreeBSD since the 4.x > days: http://lists.freebsd.org/pipermail/cvs-all/2003-July/017624.html > > I've still never heard of it though, and it's not mentioned in the > applicable manpages either. > > But there's an amusing part, too: > > You posted this exact question on freebsd-questions 1.5 years ago, > where you were running FreeBSD 6.1. So this problem has little to do > with your 6.3 --> 7.0 upgrade. > > http://lists.freebsd.org/pipermail/freebsd-questions/2007-January/139096.ht >ml RTFM Well I cant remember -- It must have gone away on 6.3 -holding stomach as I roar with laughter Well done... Ah well as you will see from my next posting I have something alittle bit odder to report!! David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: named.conf: query-source address
On Wed, Jul 16, 2008 at 10:11:03PM -0700, Doug Barton wrote: > Jeremy Chadwick wrote: > > > The config parms we use are necessary. > > That's all you had to say. :) I see a lot of people attempt to > over-engineer stuff with named that leads to complications later. If > you are doing things for a good reason, keep doing them. > Doug, et al, i for one appreciate this "over-engieered" responce because it has given me (and those like me) a chance to get answers to questions that we have asked for over a year in my case, about this whole bind setup issue. as an asideo, it would be better for people coming in cold could find a better source of who to setup support services such as bind and all teh others for a woring freebsd based network .. i don't mean teh existant 'engineering speak that assumes we all know everything .. this is clearly not teh case to a whole lot of people coming to freebsd. kind regards jonathan -- powered by .. QNX, OS9 and freeBSD -- http://caamora com au/operating system === appropriate solution in an inappropriate world === ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: HP Pavilion dv2000 laptop wont boot off install cd
> I just tried to boot off the latest 8.0-CURRENT amd64 snapshot. > According to > documentation, if you hold the spacebar as it is loading > /boot/default/loader.conf you can get to the boot menu. Pressing 6 and > entering : > > > set hint.apic.0.disabled=1 > set hint.sio.0.disabled=1 > set hint.sio.1.disabled=1 Just tried the above with 6.3-RELEASE amd64 snapshot (200806) , as well as 7.0-RELEASE amd64 snapshot (200806), with pressing the spacebar, pressing 6 at boot screen and typing the above options. For 6.3-RELEASE, it actually got to sysinstall. For 7.0-RELEASE, it seemed to hang at "Trying to mount root from ufs:/dev/md0". When I have time (tonight perhaps), I will try to do a full install of 6.3-RELEASE and see how that functions. Unfortunately there are no amd64 snapshots for 200807, so if I cant install 6.3 I may wait until more updated snapshots come out. ~k ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: HP Pavilion dv2000 laptop wont boot off install cd
I just tried to boot off the latest 8.0-CURRENT amd64 snapshot. According to documentation, if you hold the spacebar as it is loading /boot/default/loader.conf you can get to the boot menu. Pressing 6 and entering : set hint.apic.0.disabled=1 set hint.sio.0.disabled=1 set hint.sio.1.disabled=1 Gets the laptop to boot. It crashing during the boot process however : Lock order reversal: (sleepable after non-sleepable) 1st 0xff000226e878 bufobj interlock (bufobj interlock) @ /usr/src/sys/kern/vfs_bio.c:2442 2nd 0x9a7a3040 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:2456 KDB: stack backtrace: Db_trace_self_wrapper() at db_trace_self_wrapper+0x2a Witness_checkorder() at witness_checkorder+0x609 __lockmgr_args() at __lockmgr_args+0x502 getblk() at getblk+0xe3 breadn() at breadn+0x3f bread() at bread+0x1e ffs_blkatoff() at ffs_blkatoff+0x61 ufs_lookup() at ufs_lookup+0x5f3 vfs_cache_lookup() at vfs_cache_lookup+0xf8 VOP_LOOKUP_APV() at VOP_LOOKUP_APV+0x95 Lookup() at lookup+0x4b2 namei() at namei+0x43f kern_unlinkat() at kern_unlinkat+0x9d vfs_mountroot_try() at vfs_mountroot_try+0x402 vfs_mountroot() at vfs_mountroot+0x40b start_init() at start_init+0x62 fork_exit() at fork_exit+0x12a fork_trampoline() at fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0x8142fd30, rbp = 0 --- Sorry if theres typos in the above as I had to type out manually. ~k ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Failure building apache22 and mysql51
Roland Smith wrote: On Wed, Jul 16, 2008 at 11:20:13PM +0100, Chris Rees wrote: 2008/7/14 Sorin P�nca <[EMAIL PROTECTED]>: I'm sorry for my late response, I was on vacation. I think this was the case (although I thought we have only amd64 machines). Is there a way to recover from this situation by ssh access only? Thank you! Sorin. Chris Rees wrote: Date: Mon, 23 Jun 2008 18:43:04 +0300 From: Sorin P?nca <[EMAIL PROTECTED]> Hello people! I recently upgraded a amd64 machine from FreeBSD-6.2-RELEASE-p11 to FreeBSD-7.0-RELEASE-p2 using the tutorial found at http://www.daemonology.net/blog/2007-11-11-freebsd-major-version-upgrade.html All went well with the base system. I don't want to patronise, but are you sure you were running FreeBSD/amd64-6.2 before? Looks kinda like you've tried to upgrade from 6.2/i386 to 7.0/amd64. In case you have, you can't do that. Check you haven't disabled and processor-specific extensions in your BIOS, like SSE, that would also create problems if you have optimised your ports. Chris I thought devel/linuxthreads was using some old library so I tried to rebuild it: # cd ../../devel/linuxthreads && make install clean # portupgrade -f wouldn't do anything ===> linuxthreads-2.2.3_23 is only for i386, while you are running amd64. *** Error code 1 Stop in /usr/ports/devel/linuxthreads. Any ideas what to do next? Thank you! Sorin. If I understand you correctly, you want to revert to FreeBSD/i386; in which case I'd advise that you are *extremely* careful, and make sure that everything important is recompiled in i386; FreeBSD/amd64 can run binaries from FreeBSD/i386, but not vice-versa. I *think* that you should be ok running a source update (csup sources, make buildworld installworld kernel) with arch as i386, then reboot, pkg_delete -f portupgrade\*, pkg_add -r portupgrade, portupgrade -faP etc Installworld is supposed to be done after a reboot, in this case (cross-build) you'll have a 32-bit kernel stuck with a 64-bit userland. That won't work. If you do the installworld before the reboot with a cross-buils, it will be the other way around. I'm not sure if the installworld will even complete; every system binary that is replaced will be of the wrong architecture. Don't take my word for it, it is beyond my expertise, I've deliberately made it obtuse; get someone with more knowledge to elucidate :P If you have a spare partition, you could install the new kernel and userland there, and then switch partitions. If that's not an option, make backups of your data and re-install with the i386 version. It's quicker and probably less painfull. :) For changing architectures you'll also have to remove all ports/packages and re-compile/install them for the new architecture. But you should do that anyway when going from 6.x to 7. Roland Actually I want to run on amd64 architecture on that system (let's call it system0). And recently I had a similar system running FreeBSD-6.2 (amd64 - I'm sure about this one; let's call it system1) and tried to upgrade it to FreeBSD-7.0. To my surprise I had the same errors with missing PIC flag for libpthread. While for system0 I was able to fix the issue by installing devel/pth and symlinking the binary in proper locations, I experimented a little with system1 until I rendered it unusable. My question now is: what happend to the second system? Why did the upgrade fail on this one? Unfortunatly I had to reinstall it ASAP using a FreeBSD CD, because system1 is a production system and I really can't investigate further. I still have other four systems waiting to be upgraded from 6.1 or 6.2 to 7.0 or 7.1 and even they are production, they are replaceable. So I might have the chance to experiment on them, if you think this issue should be chased down. Sorin. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to get more logging from GEOM?
-- Original message -- From: "Ben Kaduk" <[EMAIL PROTECTED]> > On Wed, Jul 16, 2008 at 5:40 PM, Jo Rhett <[EMAIL PROTECTED]> wrote: > > On Jul 11, 2008, at 4:48 AM, Ronald Klop wrote: > >> > >> You can try going into the kernel debugger to see where it is hanging. > >> Debugging via a serial cable is also very easy. > >> I don't know the details, but there is a lot of info in the Freebsd > >> handbook. Put this in google 'freebsd handbook kernel debug'. > > > > > > Thanks for the reply. I'm familiar with these options, but as the system is > > currently running GENERIC and trying to compile a kernel would guarantee to > > cause the problem to occur... I could probably keep hacking at it until I > > finally get everything compiled, but... > > > > Ugh. I guess this option doesn't appeal very much. Are there any other > > options available? > > > > You don't need to compile the kernel on the same machine that you use it > on -- you can copy the compiled kernel into /boot/kernel.new > But how do you handle the issue of differences in contents on the board where you don't have exact identical hardwares? SJK www.sulima.com <> > -Ben Kaduk > ___ > 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: Dragon_Saver Error 19 Freebsd 7.0 AMD64
On Thu, Jul 17, 2008 at 02:17:12AM -0700, Jeremy Chadwick wrote: > On Thu, Jul 17, 2008 at 02:08:58AM -0700, David Southwell wrote: > > Just upgraded from Freebsd 6.3 to 7.0 > > > > uname -a > > FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 > > 09:27:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > > amd64 > > Have the following entry in > > > > /var/log/essages: > > > > Jul 17 01:28:46 dns1 kernel: dragon_saver: the console does not support > > M_VGA_CG320 > > Jul 17 01:28:46 dns1 kernel: module_register_init: MOD_LOAD (dragon_saver, > > 0xadf7a140, 0) error 19 > > That looks to be some kind of screen-saver for VGA consoles, similar to > daemon_saver or green_saver. Look at the splash(4) manpage. > > There is no 'dragon_saver' that comes with FreeBSD 7.0, however. And I > don't remember reading about it on FreeBSD 6.x either. > > Usually things like that are loaded via rc.conf or loader.conf. I stand corrected -- it appears to come with FreeBSD since the 4.x days: http://lists.freebsd.org/pipermail/cvs-all/2003-July/017624.html I've still never heard of it though, and it's not mentioned in the applicable manpages either. But there's an amusing part, too: You posted this exact question on freebsd-questions 1.5 years ago, where you were running FreeBSD 6.1. So this problem has little to do with your 6.3 --> 7.0 upgrade. http://lists.freebsd.org/pipermail/freebsd-questions/2007-January/139096.html -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Dragon_Saver Error 19 Freebsd 7.0 AMD64
On Thu, Jul 17, 2008 at 02:08:58AM -0700, David Southwell wrote: > Just upgraded from Freebsd 6.3 to 7.0 > > uname -a > FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 > 09:27:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC > amd64 > Have the following entry in > > /var/log/essages: > > Jul 17 01:28:46 dns1 kernel: dragon_saver: the console does not support > M_VGA_CG320 > Jul 17 01:28:46 dns1 kernel: module_register_init: MOD_LOAD (dragon_saver, > 0xadf7a140, 0) error 19 That looks to be some kind of screen-saver for VGA consoles, similar to daemon_saver or green_saver. Look at the splash(4) manpage. There is no 'dragon_saver' that comes with FreeBSD 7.0, however. And I don't remember reading about it on FreeBSD 6.x either. Usually things like that are loaded via rc.conf or loader.conf. > Can anyone please point me in the right direction http://www.hrwiki.org/index.php/Trogdor -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Dragon_Saver Error 19 Freebsd 7.0 AMD64
Just upgraded from Freebsd 6.3 to 7.0 uname -a FreeBSD dns1.vizion2000.net 7.0-STABLE FreeBSD 7.0-STABLE #0: Wed Jul 16 09:27:38 PDT 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC amd64 Have the following entry in /var/log/essages: Jul 17 01:28:46 dns1 kernel: dragon_saver: the console does not support M_VGA_CG320 Jul 17 01:28:46 dns1 kernel: module_register_init: MOD_LOAD (dragon_saver, 0xadf7a140, 0) error 19 Can anyone please point me in the right direction Thanks David ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
