Re: problems with Hitachi 1TB SATA drives
On Tue, 24 Jul 2007, Jeremy Chadwick wrote: > On Mon, Jul 23, 2007 at 07:40:21PM -0700, Bill Swingle wrote: > > Doh, I knew I forgot something in my original email. > > Here's the full dmesg: http://dub.net/rum.dub.net.dmesg > > Actually you did include this in your original Email. I think Daniel > overlooked it. :-) Oops, maybe it was an attachment I forgot to read. As you say later - it would be good to know what mode the chipset is in. Might be worth trying AHCI mode if you have it (although maybe ICH5 is too old for that?) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Re: problems with Hitachi 1TB SATA drives
On Mon, Jul 23, 2007 at 07:40:21PM -0700, Bill Swingle wrote: > Doh, I knew I forgot something in my original email. > Here's the full dmesg: http://dub.net/rum.dub.net.dmesg Actually you did include this in your original Email. I think Daniel overlooked it. :-) After looking at your dmesg and your claim, I got confused because your initial statement included the use of a 3ware card. A verbose description of your configuration: * ad0: 43979MB at ata0-master UDMA100 -- hooked to: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: on atapci0 ata1: on atapci0 * ad4: 953869MB at ata2-master SATA150 * ad6: 953869MB at ata3-master SATA150 -- both hooked to: atapci1: port 0xec00-0xec07,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc0f irq 18 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 * twed0: on twe0 twed0: 583440MB (1194885120 sectors) -- hoooked to: twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xb800-0xb80f mem 0xfeaffc00-0xfeaffc0f,0xfe00-0xfe7f irq 17 at device 2.0 on pci3 twe0: [GIANT-LOCKED] twe0: 4 ports, Firmware FE7X 1.05.00.063, BIOS BE7X 1.08.00.048 I have to assume that atapci0 is actually using IRQ 14 even though it's not shown (weird...). Additionally your ICH5 SATA controller is sharing an IRQ with a couple other devices on the PCI bus; this isn't bad, but I'm noting it here in case this turns out to be some weird interrupt problem: em0: port 0xac00-0xac1f mem 0xfd9e-0xfd9f irq 18 at device 1.0 on pci2 uhci2: port 0xd400-0xd41f irq 18 at device 29.2 on pci0 On to this: > Jul 21 00:21:45 rum kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) > LBA=54194911 > Jul 21 00:22:20 rum kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) > LBA=107260543 > Jul 21 00:22:57 rum kernel: ad4: FAILURE - device detached > Jul 21 00:22:57 rum kernel: subdisk4: detached > Jul 21 00:22:57 rum kernel: ad4: detached > Jul 21 00:24:19 rum kernel: ad6: FAILURE - device detached > Jul 21 00:24:19 rum kernel: subdisk6: detached > Jul 21 00:24:19 rum kernel: ad6: detached > > ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1456106111 > ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=1456106111 > ad4: FAILURE - WRITE_DMA48 timed out LBA=1456106111 > ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=54194911 > ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=461407775 > ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=461407775 > ad4: FAILURE - WRITE_DMA48 timed out LBA=461407775 But then: > When trying to newfs them both eventually failed with DMA READ or > WRITE timeouts. Now I'm confused. :-) I only see evidence of a failure on ad4. The ad6 disk disconnecting from the bus could be caused by the controller getting wedged while waiting for certain transactions sent to ad4 (which are failing). I've seen this scenario happen many times. The panic you got is probably also induced by the same issue. Does the WRITE_DMA/DMA48 problem happen for you when newfs'ing a slice on ad6? > I've read that bad SATA cables could cause this, the cables I'm using > are brand new but are probably pretty cheap. For testing purposes swap them out with some other cables. It may not be the cables at all, so keep the originals around. Also might try using some of that canned air to blow out any dust around the SATA connector ends on the cables, drives, and motherboard. Remaining questions I have: Q: Is your ICH5 controller actually ICH5R and you've turned on some Intel RAID option in the BIOS? Maybe turning it on but leaving the disks in a JBOD fashion (not defining an array)? The reason I ask is that you said you're going to use the Hitachi drives as "a pair of 1TB synchronised drives", which implies RAID-1, yet I don't see use of gmirror or ccd or anything else. :-) Q: What motherboard and model is this? Looks like an Intel. Q: If an Intel, have you gone looking at Intel's site for BIOS updates for that board? Intel is the one company who is thorough about documenting BIOS changes in their Release Notes. It would not surprise me if this turned out to be some kind of weird BIOS bug. Q: Some motherboards let you toggle certain "compatibility" mode stuff for the SATA controller in the BIOS. You might want to flip that to see what happens (if compatibility, try the opposite. And vice-versa of course). Q: Have you searched Google for issues others have reported (such as in Linux) with the HDS721010KLA330 or similar (differently-sized) models? -- | 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-st
Re: problems with Hitachi 1TB SATA drives
Doh, I knew I forgot something in my original email. Here's the full dmesg: http://dub.net/rum.dub.net.dmesg Here's the controller info: atapci1: port 0xec00-0xec07,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc0f irq 18 at device 31.2 on pci0 ata2: on atapci1 ata3: on atapci1 -Bill Daniel O'Connor wrote: On Tue, 24 Jul 2007, Bill Swingle wrote: I've read that bad SATA cables could cause this, the cables I'm using are brand new but are probably pretty cheap. Unlike they're both faulty too.. You need to post your dmesg otherwise we have no idea what controller you're using.. -- -=| Bill Swingle - [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: problems with Hitachi 1TB SATA drives
On Tue, 24 Jul 2007, Bill Swingle wrote: > I've read that bad SATA cables could cause this, the cables I'm using > are brand new but are probably pretty cheap. Unlike they're both faulty too.. You need to post your dmesg otherwise we have no idea what controller you're using.. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
problems with Hitachi 1TB SATA drives
Hello all, I've run across a problem that I hope someone can aid me with. I have a fileserver that currently has a 4-disc raid connected to an IDE 3ware card. I had hoped to replace this dying system with a pair of synchronized 1TB SATA drives. When trying to newfs them both eventually failed with DMA READ or WRITE timeouts. Here's some infos: FreeBSD rum.dub.net 6.2-STABLE FreeBSD 6.2-STABLE #2: Sat Jul 21 09:05:25 PDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 ad0: 43979MB at ata0-master UDMA100 <-- system disk ad4: 953869MB at ata2-master SATA150 ad6: 953869MB at ata3-master SATA150 twed0: on twe0 twed0: 583440MB (1194885120 sectors) A complete dmesg is at http://dub.net/rum.dub.net.dmesg Initially the attempted newfs would cause this: Jul 21 00:21:45 rum kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=54194911 Jul 21 00:22:20 rum kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=107260543 Jul 21 00:22:57 rum kernel: ad4: FAILURE - device detached Jul 21 00:22:57 rum kernel: subdisk4: detached Jul 21 00:22:57 rum kernel: ad4: detached Jul 21 00:24:19 rum kernel: ad6: FAILURE - device detached Jul 21 00:24:19 rum kernel: subdisk6: detached Jul 21 00:24:19 rum kernel: ad6: detached After several tries I was able to get both disks newfs'd and mounted but they quickly fell down with DMA timeouts. On one occasion the machine actually panic'd too: ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=1456106111 ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=1456106111 ad4: FAILURE - WRITE_DMA48 timed out LBA=1456106111 ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=54194911 ad4: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=461407775 ad4: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=461407775 ad4: FAILURE - WRITE_DMA48 timed out LBA=461407775 Fatal trap 12: page fault while in kernel mode fault virtual address = 0x66 fault code = supervisor read, page not present instruction pointer = 0x20:0xc07253c3 stack pointer = 0x28:0xd9724b9c frame pointer = 0x28:0xd9724ba4 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 = 779 (mdnsd) trap number = 12 panic: page fault I've read that bad SATA cables could cause this, the cables I'm using are brand new but are probably pretty cheap. Help freebsd-stable, you're my only hope! :) -Bill -- -=| Bill Swingle - [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: Issues with Bootloader & Vista
On Tue, 24 Jul 2007, Kris Moore wrote: > We've released our 1.4 BETA of PC-BSD this week, and one of the > issues which has come up is the broken support for dual-booting with > a Vista system. Apparently the FreeBSD boot loader messes up some of > Vista's boot process. Here's what one of our users tracked it down > to: > > . >.. If a user wises to re size the Vista partition then dual boot the > user maybe surprised to find Vista will fail to boot from the BSD > boot loader with the following error message: > > "The file /Windows/system32/winload.exe can not be found or is > corrupt." > > This is due to the BSD boot loader overwriting a UUID in the MBR the > Vista OS uses to boot for some reason as it was not in the Beta or > the RC. > . I think this is similar to the signature bytes Windows XP uses to remember which disk is which. I was bitten recently when I reinstalled XP on my laptop - the installer picked E: (NFI why since it was the first partition on the disk) and after I reinstalled the FreeBSD MBR it decided it hadn't seen the disk before and assigned it 'C' and so the swapfile location was invalid which means you can't login (even in safe mode).. I think the solution would be to ensure the 4 bytes it uses are preserved by boot0cfg (although I think sysinstall would need modification too), this page shows the bytes in question.. http://www.multibooters.co.uk/mbr.html I dunno if boot0 has 4 bytes to spare tho :( -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C signature.asc Description: This is a digitally signed message part.
Dell SC440 Onboard LAN
I'm trying to get the onboard NIC working on FreeBSD 6.2, but I'm not having any luck. From what I've read, others have had problems with it as well. I believe it is the Broadcom 5787. Christopher D. Miller CAD Concepts Inc. 1328 Dublin Rd, Suite 201 Columbus, Ohio 43215 Main: 614-485-0670 Direct: 614-827-7410 Fax: 614-485-0677 ___ 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
On Mon, Jul 23, 2007 at 12:18:59PM -0700, Chuck Swiger wrote: > No machine should ever poll faster than once a minute (aka "minpoll 8") to > someone else's timeserver without prior agreement. For an example of a > reasonable client config, MacOS X uses a minpoll of 12 and a maxpoll of 17. And an addendum to this: Our servers use "maxpoll 9" for a very specific reason: it appears to work around an issue where on FreeBSD ntpd continually flips between PLL and FLL mode. The default for maxpoll is 10 (1024 seconds). Taken from our ntp.conf is this comment: # maxpoll 9 is used to work around PLL/FLL flipping, which # happens at exactly 1024 seconds (the default maxpoll value). # Another FreeBSD member recommended using 9 instead. # http://lists.freebsd.org/pipermail/freebsd-stable/2006-December/031512.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: ntpd just sits there and does nothing
On Jul 23, 2007, at 12:22 PM, [LoN]Kamikaze wrote: I wish to second what Oliver has said, only more strongly: using "minpoll 4" is considered abusive and a misuse of the NTP pool. From http://www.pool.ntp.org/use.html That was only for testing. Please use your own timeservers for testing, not the NTP pool. I'm not trying to be mean, but I've got three NTP servers in the pool, and just a handful of misconfigured clients which poll more often than once a minute consume more bandwidth than 60 to 1000 normal clients do -- -Chuck ___ 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
Chuck Swiger wrote: > On Jul 23, 2007, at 7:10 AM, Oliver Fromme wrote: >> [LoN]Kamikaze <[EMAIL PROTECTED]> wrote: >>> server 0.de.pool.ntp.org minpoll 4 maxpoll 8 >>> server 1.de.pool.ntp.org minpoll 4 maxpoll 8 >>> server 2.de.pool.ntp.org minpoll 4 maxpoll 8 >>> server ntp1.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 >>> server ntp2.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 >>> server ntp3.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 >>> server ntp4.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 >>> >>> restrict default ignore >>> restrict 127.0.0.1 >> >> You need to add proper restrict lines for the servers, >> of course. Basically you have configured ntpd to >> ignore all servers. >> >> Also, putting "minpoll 4 maxpoll 8" on all servers is >> somewhat suboptimal and puts an unnecessary burden on the >> servers and networks without reason. I recommend to use >> low polling intervals and the iburst option for one or >> two local servers only (e.g. for NTP servers located in >> your direct upstream or at your ISP), and higher polling >> intervals for other public servers. > > I wish to second what Oliver has said, only more strongly: using > "minpoll 4" is considered abusive and a misuse of the NTP pool. From > http://www.pool.ntp.org/use.html That was only for testing. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpd on a NAT gateway seems to do nothing
> It's deja-vu all over again. > > I found my works NTP service was broken on Friday, just after I started my > holiday. Interesting to hear from someone also using NAt with a very similar problem. Thanks, I am running -STABLE rather than RELENG, but I suspect I will simply try updating to a later STABLE tomorrow and see if that helps. > I'm using IPFW and ipnat, which I believe is somewhat unusual. Ipnat is there > to 'fix' the source IP. Don't ask! :-) once you start playing with NAT things can get odd quite fast I have found! > Anyway; I just did a cleandir x2, rebuild and update to p6, and it's working > again. > > Might be worth a try. I'll try tomorrow, thanks, -pete. ___ 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
On Jul 23, 2007, at 7:10 AM, Oliver Fromme wrote: [LoN]Kamikaze <[EMAIL PROTECTED]> wrote: server 0.de.pool.ntp.org minpoll 4 maxpoll 8 server 1.de.pool.ntp.org minpoll 4 maxpoll 8 server 2.de.pool.ntp.org minpoll 4 maxpoll 8 server ntp1.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp2.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp3.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp4.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 restrict default ignore restrict 127.0.0.1 You need to add proper restrict lines for the servers, of course. Basically you have configured ntpd to ignore all servers. Also, putting "minpoll 4 maxpoll 8" on all servers is somewhat suboptimal and puts an unnecessary burden on the servers and networks without reason. I recommend to use low polling intervals and the iburst option for one or two local servers only (e.g. for NTP servers located in your direct upstream or at your ISP), and higher polling intervals for other public servers. I wish to second what Oliver has said, only more strongly: using "minpoll 4" is considered abusive and a misuse of the NTP pool. From http://www.pool.ntp.org/use.html "Be friendly. Many servers are provided by volunteers, and almost all time servers are really file or mail or webservers which just happen to also run ntp. So don't use more than three time servers in your configuration, and don't play dirty tricks with burst or minpoll - all you will gain is that this project will be stopped sooner or later." No machine should ever poll faster than once a minute (aka "minpoll 8") to someone else's timeserver without prior agreement. For an example of a reasonable client config, MacOS X uses a minpoll of 12 and a maxpoll of 17. -- -Chuck ___ 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
Oliver Fromme wrote: > [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. Obviously I'm too stupid to configure ntpd by myself. Thanks for all the effort. I have watched ntpd do its magic for an hour, now. And it seems to aim at running my clock half a second behind the server clocks. Maybe I just didn't watch long enough, I understand that ntpd is trying to figure out how much my clock goes wrong and only adjusts time very slowly. > Demanding to replace ntpd with openntpd in the FreeBSD > base system because you cannot get the configuration right > is ridiculous. I wasn't really demanding, but saying that I'd (personally) prefer openntpd. And my original argument still stands, it's much simpler than ntpd and though I lack the intelligence to configure ntpd, it suffices for openntpd. Seeing that nobody seems to agree with me, I'm happy with running openntpd from ports. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
geom vs ich through ar device - benchmarks?
Has anyone done any benchmarks in desktop or server environment comparing geom with an ICH controller through the ar device in RAID1 service? Teh google, it seems to pick up grammar school math assignments lots of what may be relevant hits for fortunate speakers of German :( ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Issues with Bootloader & Vista
Hey guys, We've released our 1.4 BETA of PC-BSD this week, and one of the issues which has come up is the broken support for dual-booting with a Vista system. Apparently the FreeBSD boot loader messes up some of Vista's boot process. Here's what one of our users tracked it down to: ... If a user wises to re size the Vista partition then dual boot the user maybe surprised to find Vista will fail to boot from the BSD boot loader with the following error message: "The file /Windows/system32/winload.exe can not be found or is corrupt." This is due to the BSD boot loader overwriting a UUID in the MBR the Vista OS uses to boot for some reason as it was not in the Beta or the RC. ... Is this a known issue, or something we may have fixed in 6-Stable soon? If so it would be great if I could find a fix before we release a final version down the road. -- Kris Moore PC-BSD Software http://www.pcbsd.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ntpd on a NAT gateway seems to do nothing
On Monday 23 July 2007 13:50:09 Pete French wrote: > Just following the similarly names thread with a bit of interest and I > decided to check my own ntp setup and, to my surprise, discovered I also > have a machine which does nothing. What is more surprising to me is that it > has the same config as a number of other machines, all of which work. > > We have a segment of network which is behind a NAT, and there is a BSD box > running 'pf' actiing as the NAT gateway. Running ntpd on the actual > NAT box does not work, but running it on the clients the far side of > the NAT does, or on clients the live side of the NAT. I should probably > exolain that the NAT goes onto another network which is also natted, though > that NAT is out of my control. > > The ntp.conf file looks like this on all machines: > > disable auth > enable ntp > driftfile /etc/ntp.drift > server 10.17.19.0 > server 195.40.0.250 > server 158.43.128.33 > server 158.43.128.66 > server 158.43.192.66 > > The time servers there are for easynet, pipex and an internal machine at > a remote location. ntpdate on the machine can query all the hosts fine, > but ntpdc -p gives: > > remote local st poll reach delay offsetdisp > === > =valliere.ns.eas 172.16.1.8 16 640 0.0 0.00 0.0 > =turpentine.ratt 172.16.1.8 3 1287 0.01451 -0.007633 1.93823 > =ntp2.pipex.net 172.16.1.8 16 640 0.0 0.00 0.0 > =ntp0.pipex.net 172.16.1.8 16 640 0.0 0.00 0.0 > =ntp1.pipex.net 172.16.1.8 16 640 0.0 0.00 0.0 > > As you can see, it can only reach the internal machine. On other machines > behind the NAT it looks like this: > > remote local st poll reach delay offsetdisp > === > =valliere.ns.eas 10.50.50.2 2 256 377 0.00577 -0.004396 0.01192 > =turpentine.ratt 10.50.50.2 3 256 377 0.01534 -0.004566 0.00482 > *ntp2.pipex.net 10.50.50.2 2 256 377 0.00635 -0.004052 0.00899 > =ntp0.pipex.net 10.50.50.2 2 256 377 0.00729 -0.002443 0.01395 > =ntp1.pipex.net 10.50.50.2 2 256 377 0.00768 -0.002426 0.00951 > > But those connections are flowing through the NAT box oon which ntpd > is not connecting! > > Any suggestions ? I assume it has something to do with the NAT, but I am > not sure what. All other TCP connections out from that machine to > external systems work fine, so it is not as if outbound connections from > there are not working at all. > > -pcf. > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" It's deja-vu all over again. I found my works NTP service was broken on Friday, just after I started my holiday. Packets were going out but nothing was coming back. I'm using IPFW and ipnat, which I believe is somewhat unusual. Ipnat is there to 'fix' the source IP. Don't ask! Checking the logs it appears that this broke after I updated from 6.2-RELEASE-p1 to 6.2-RELEASE-p5. I found this in messages. May 30 17:25:31 firewall ntpd[825]: ntpd 4.2.0-a Tue May 29 20:59:19 BST 2007 (1) May 30 17:27:31 firewall ntpd[825]: too many recvbufs allocated (40) ntpq -p would report No Association ID's (from memory) Anyway; I just did a cleandir x2, rebuild and update to p6, and it's working again. Might be worth a try. -- ian j hart ___ 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
On Mon, Jul 23, 2007 at 09:39:32AM -0500, Sean C. Farley wrote: > Do you actually need to open it up that way? I have this on my server > which seems to work: You don't *need* to. The method he described allows you to avoid having to make a "restrict" entry for each matching "server", that's all. Your configuration is correct as well. :-) -- | 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: ntpd just sits there and does nothing
On Mon, 23 Jul 2007, Matthew Seaman wrote: [LoN]Kamikaze wrote: My original intention was just to say that openntpd works just out of the box, while ntpd doesn't. And since openntpd works fine for me, I am not really interested in resolving this. Anyway since so many of you seem to be, here is the requested data: ntp.conf server 0.de.pool.ntp.org minpoll 4 maxpoll 8 server 1.de.pool.ntp.org minpoll 4 maxpoll 8 server 2.de.pool.ntp.org minpoll 4 maxpoll 8 server ntp1.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp2.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp3.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp4.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 restrict default ignore restrict 127.0.0.1 Err.. your configuration says "ignore all NTP servers except localhost". You would need to let ntpd accept a time service from all those machines you've told it are servers. Since you're using pool.ntp.org, you're going to need a blanket 'allow any server' config like: restrict default nomodify nopeer noquery restrict 127.0.0.1 Do you actually need to open it up that way? I have this on my server which seems to work: server 0.us.pool.ntp.org server 1.us.pool.ntp.org server 2.us.pool.ntp.org server 3.us.pool.ntp.org restrict default ignore restrict 0.us.pool.ntp.org nomodify nopeer noquery notrap restrict 1.us.pool.ntp.org nomodify nopeer noquery notrap restrict 2.us.pool.ntp.org nomodify nopeer noquery notrap restrict 3.us.pool.ntp.org nomodify nopeer noquery notrap restrict AAA.BBB.CCC.0 mask 255.255.255.0 nomodify nopeer notrap restrict -6 :::::: mask ::::: nomodify nopeer notrap restrict 127.0.0.1 restrict -6 ::1 # ntpdc -c peers remote local st poll reach delay offsetdisp === =AAA.BBB.CCC.DDD 3 1024 377 0.03639 0.014113 0.01482 *tock.jrc.us AAA.BBB.CCC.DDD 2 1024 377 0.05907 0.000169 0.01485 =nubtail.allbook AAA.BBB.CCC.DDD 3 1024 377 0.05696 0.000660 0.01485 =cletus.pettit.o AAA.BBB.CCC.DDD 2 1024 377 0.11273 -0.004489 0.01482 Sean -- [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: ntpd just sits there and does nothing
[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. > > ntp.conf > > server 0.de.pool.ntp.org minpoll 4 maxpoll 8 > server 1.de.pool.ntp.org minpoll 4 maxpoll 8 > server 2.de.pool.ntp.org minpoll 4 maxpoll 8 > server ntp1.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > server ntp2.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > server ntp3.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > server ntp4.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > > restrict default ignore > restrict 127.0.0.1 You need to add proper restrict lines for the servers, of course. Basically you have configured ntpd to ignore all servers. Also, putting "minpoll 4 maxpoll 8" on all servers is somewhat suboptimal and puts an unnecessary burden on the servers and networks without reason. I recommend to use low polling intervals and the iburst option for one or two local servers only (e.g. for NTP servers located in your direct upstream or at your ISP), and higher polling intervals for other public servers. 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 "Software gets slower faster than hardware gets faster." -- Niklaus Wirth ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: removing external usb hdd without unmounting causes reboot?
Stefan Esser wrote: > Oliver Fromme wrote: > > Momchil Ivanov wrote: > > > I don`t know how things work, but shutting down the system when some > > > mounted fs is no longer present seems like the wrong thing to me. > > > > As Josh wrote, it's expected. The problem is known > > to exist for a long time already (probably as long > > as FreeBSD itself exists), and if there was an easy > > solution, certainly someone would have fixed it. > > I have to check this, but AFAIK this problem exists only for > devices/partitions that are mounted R/W. Do you happen to > know this? (I can not risk to crash my box right now for a > test ;-) I'm afraid the problem affects _all_ mounts, including read-only mounts. > There once was an autofs implementation, but IIRC it has > later been removed. It could not only automatically mount > removable media, but it could also help with the problem > of devices that are rarely written to, but still mounted > R/W just in case for easy write-access. > > Long time ago I had the idea that a clean file system could > be mounted R/O after a short delay. When all dirty buffers > are flushed, the device could be forcefully disconnected > without causing inconsistencies in the kernel. If there are > no open file descriptors, the super-block could be written > with the "clean" flag set, to signal that no fsck is needed > when the partition is mounted next time. > > Internally, the device can be treated as R/O, with the only > exeption that an attempted write is not rejected, but that > it instead triggers the change back to R/W operation (this > means setting the in-RAM copy of the super-block to dirty > before the write is allowed to proceed as normal). That's a very interesting idea. Unfortunately it doesn't solve the problem, because read-only mounts have the same problem, unfortunately. So, currently the best work-around is to use amd with a very short timeout. Or simply remember to umount your removable media manually. 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 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' ___ 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: Setting up rails for "shared hosting" on a dedicated box. . .?
On Mon, 23 Jul 2007 12:16:17 +0300
Nikolay Pavlov <[EMAIL PROTECTED]> wrote:
> On Sunday 22 July 2007 16:32:19 Michael Williams wrote:
> > Hi All,
> >
> > As you may already know, A partner and I recently purchased a
> > dedicated FreeBSD box. We're currently using Plesk (blech!) to
> > manage client domains and such. I'm curious though as to what the
> > best (most manageable) setup/configuration is for supporting Rails
> > for each of our clients. Basically we want to be our own Shared
> > Hosting Rails Provider (for lack of a more appropriate phrase) and
> > need to figure out the best server configuration. Just a bit of an
> > FYI, everything is already running on Apache2 so I'd need to share
> > Apache2 among all programs (e.g. svn, rails, etc); as opposed to
> > splitting tasks between Apache and Apache2.
> >
> > If you could point me in the right direction it would be most
> > appreciated.
> >
> > Regards,
> > Michael
> > ___
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "[EMAIL PROTECTED]"
>
> Hi Michael. I don't think that apache is the best choice to handle rails
> applications. However in case of Share hosting environment it would be fine.
> I see three choices here:
> 1) Apache2 + mod_proxy_balancer + mongrel (The best way IMHO)
> 2) Apache2 + fast_cgi (Could have some problems, due to mostly
> unmaintainable nature of fast_cgi)
> 3) Apache2 + cgi (Absolutely workable, but VERY slow case)
>
Look into Lighty (http://lighttpd.net )
_
{Beto|Norberto|Numard} Meijome
"Ugly programs are like ugly suspension bridges: they're much more liable to
collapse than pretty ones, because the way humans (especially engineer-humans)
perceive beauty is intimately related to our ability to process and understand
complexity. A language that makes it hard to write elegant code makes it hard
to write good code."
Eric Raymond
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
starting hald causes panic
Hello *,
don't know, if I am right here. I've already asked that on the
gnome-list some time ago, but they told me, it is a matter of the
kernel). Now I've recompiled the kernel with debugging info:
uname -a
FreeBSD worf.mydomain.home 6.2-STABLE FreeBSD 6.2-STABLE #35: Thu Jul
19 22:04:13 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ATHLON
i386
The problem is, every time I try to start hald (e.g.
/usr/local/etc/rc.d/hald forcestart) I get a kernel panic.
I have a backtrace here:
-8<--8<--8<--8<--8<-
worf# kgdb kernel.debug vmcore.1
kgdb: kvm_nlist(_stopped_cpus):
kgdb: kvm_nlist(_stoppcbs):
[GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Un
fined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Unread portion of the kernel message buffer:
<118>Jul 19 23:03:48 worf init: /bin/sh on /etc/rc.shutdown terminated abnorma
y, going to single user mode
<118>Jul 19 23:03:48 worf syslogd: exiting on signal 15
<118>Enter full pathname of shell or RETURN for /bin/sh:
<118>#
<118>/dev/ad0s1a on / (ufs, local)
<118>devfs on /dev (devfs, local)
<118>/dev/ufs/usr on /usr (ufs, local, soft-updates)
<118>/dev/ufs/backup on /usr/Backup (ufs, local, soft-updates)
<118>/dev/ufs/var on /var (ufs, local, soft-updates)
<118>/dev/ufs/home on /usr/home (ufs, local, soft-updates)
<118>/dev/ufs/media on /usr/media (ufs, local, soft-updates)
<118>/dev/ufs/ports on /usr/ports (ufs, local, soft-updates)
<118>/dev/ufs/home2 on /usr/home2 (ufs, local, soft-updates)
<118>/dev/md0 on /tmp (ufs, local, soft-updates)
<118>procfs on /proc (procfs, local)
<118>#
<118>#
<118>#
<118>#
<118>#
<118>/dev/ad0s1a on / (ufs, local)
<118>devfs on /dev (devfs, local)
<118>/dev/ufs/usr on /usr (ufs, local, soft-updates)
<118>/dev/ufs/backup on /usr/Backup (ufs, local, soft-updates)
<118>/dev/ufs/var on /var (ufs, local, soft-updates)
<118>/dev/md0 on /tmp (ufs, local, soft-updates)
<118>procfs on /proc (procfs, local)
<118>#
<118>#
<118>Starting hald.
Fatal trap 12: page fault while in kernel mode
fault virtual address = 0x54
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0442fd5
stack pointer = 0x28:0xdd710ad8
frame pointer = 0x28:0xdd710ae8
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 = 1180 (hald-probe-storage)
trap number = 12
panic: page fault
Uptime: 15m18s
Dumping 511 MB (2 chunks)
chunk 0: 1MB (159 pages) ... ok
chunk 1: 511MB (130800 pages) 495 479 463 447 431 415 399 383 367 351 335 31
303 287 271 255 239 223 207 191 175 159 143 127 111 95 79 63 47 31 15
#0 doadump () at pcpu.h:165
165 pcpu.h: No such file or directory.
in pcpu.h
(kgdb) bt
#0 doadump () at pcpu.h:165
#1 0xc04d8112 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:409
#2 0xc04d83a8 in panic (fmt=0xc06111ed "%s")
at /usr/src/sys/kern/kern_shutdown.c:565
#3 0xc05f0a64 in trap_fatal (frame=0xdd710a98, eva=84)
at /usr/src/sys/i386/i386/trap.c:837
#4 0xc05f07cb in trap_pfault (frame=0xdd710a98, usermode=0, eva=84)
at /usr/src/sys/i386/i386/trap.c:745
#5 0xc05f0429 in trap (frame=
{tf_fs = 8, tf_es = 40, tf_ds = 40, tf_edi = 0, tf_esi = -1018177536,
tf_ebp = -579794200, tf_isp = -579794236, tf_ebx = -1019589920, tf_edx =
-1020556800, tf_ecx = 384750786, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip
= -1069273131, tf_cs = 32, tf_eflags = 66182, tf_esp = -1002170368, tf_ss = 0})
at /usr/src/sys/i386/i386/trap.c:435
#6 0xc05de46a in calltrap () at /usr/src/sys/i386/i386/exception.s:139
#7 0xc0442fd5 in amdexecutesrb (arg=0xc33a4ae0, dm_segs=0xc32b8a00, nseg=1,
error=0) at /usr/src/sys/dev/amd/amd.c:314
#8 0xc05dbffd in bus_dmamap_load (dmat=0xc335e800, map=0x0, buf=0xd30d34a0,
buflen=34, callback=0xc0442fc0 , callback_arg=0xc33a4ae0,
flags=0) at /usr/src/sys/i386/i386/busdma_machdep.c:736
#9 0xc04432d0 in amd_action (psim=0xc33a4ae0, pccb=0xc34fd800)
at /usr/src/sys/dev/amd/amd.c:440
#10 0xc0432675 in xpt_run_dev_sendq (bus=0xc337dd80)
at /usr/src/sys/cam/cam_xpt.c:4059
#11 0xc0431b5d in xpt_action (start_ccb=0xc34fd800)
at /usr/src/sys/cam/cam_xpt.c:3153
#12 0xc042e81a in cam_periph_runccb (ccb=0xc34fd800, error_routine=0,
camflags=CAM_RETRY_SELTO, sense_flags=1, ds=0xc34e40f0)
at /usr/src/sys/cam/cam_periph.c:861
#13 0xc043d7f0 in passsendccb (periph=0x0, ccb=0xc34fd800, inccb=0xc33d3c00)
at /us
ntpd on a NAT gateway seems to do nothing
Just following the similarly names thread with a bit of interest and I decided to check my own ntp setup and, to my surprise, discovered I also have a machine which does nothing. What is more surprising to me is that it has the same config as a number of other machines, all of which work. We have a segment of network which is behind a NAT, and there is a BSD box running 'pf' actiing as the NAT gateway. Running ntpd on the actual NAT box does not work, but running it on the clients the far side of the NAT does, or on clients the live side of the NAT. I should probably exolain that the NAT goes onto another network which is also natted, though that NAT is out of my control. The ntp.conf file looks like this on all machines: disable auth enable ntp driftfile /etc/ntp.drift server 10.17.19.0 server 195.40.0.250 server 158.43.128.33 server 158.43.128.66 server 158.43.192.66 The time servers there are for easynet, pipex and an internal machine at a remote location. ntpdate on the machine can query all the hosts fine, but ntpdc -p gives: remote local st poll reach delay offsetdisp === =valliere.ns.eas 172.16.1.8 16 640 0.0 0.00 0.0 =turpentine.ratt 172.16.1.8 3 1287 0.01451 -0.007633 1.93823 =ntp2.pipex.net 172.16.1.8 16 640 0.0 0.00 0.0 =ntp0.pipex.net 172.16.1.8 16 640 0.0 0.00 0.0 =ntp1.pipex.net 172.16.1.8 16 640 0.0 0.00 0.0 As you can see, it can only reach the internal machine. On other machines behind the NAT it looks like this: remote local st poll reach delay offsetdisp === =valliere.ns.eas 10.50.50.2 2 256 377 0.00577 -0.004396 0.01192 =turpentine.ratt 10.50.50.2 3 256 377 0.01534 -0.004566 0.00482 *ntp2.pipex.net 10.50.50.2 2 256 377 0.00635 -0.004052 0.00899 =ntp0.pipex.net 10.50.50.2 2 256 377 0.00729 -0.002443 0.01395 =ntp1.pipex.net 10.50.50.2 2 256 377 0.00768 -0.002426 0.00951 But those connections are flowing through the NAT box oon which ntpd is not connecting! Any suggestions ? I assume it has something to do with the NAT, but I am not sure what. All other TCP connections out from that machine to external systems work fine, so it is not as if outbound connections from there are not working at all. -pcf. ___ 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: Setting up rails for "shared hosting" on a dedicated box. . .?
On Sunday 22 July 2007 16:32:19 Michael Williams wrote: > Hi All, > > As you may already know, A partner and I recently purchased a > dedicated FreeBSD box. We're currently using Plesk (blech!) to > manage client domains and such. I'm curious though as to what the > best (most manageable) setup/configuration is for supporting Rails > for each of our clients. Basically we want to be our own Shared > Hosting Rails Provider (for lack of a more appropriate phrase) and > need to figure out the best server configuration. Just a bit of an > FYI, everything is already running on Apache2 so I'd need to share > Apache2 among all programs (e.g. svn, rails, etc); as opposed to > splitting tasks between Apache and Apache2. > > If you could point me in the right direction it would be most > appreciated. > > Regards, > Michael > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" Hi Michael. I don't think that apache is the best choice to handle rails applications. However in case of Share hosting environment it would be fine. I see three choices here: 1) Apache2 + mod_proxy_balancer + mongrel (The best way IMHO) 2) Apache2 + fast_cgi (Could have some problems, due to mostly unmaintainable nature of fast_cgi) 3) Apache2 + cgi (Absolutely workable, but VERY slow case) -- - Best regards, Nikolay Pavlov. <<<- signature.asc Description: This is a digitally signed message part.
Re: ntpd just sits there and does nothing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 [LoN]Kamikaze wrote: > My original intention was just to say that openntpd works just out of the box, > while ntpd doesn't. And since openntpd works fine for me, I am not really > interested in resolving this. Anyway since so many of you seem to be, here is > the requested data: > >> ntp.conf > > server 0.de.pool.ntp.org minpoll 4 maxpoll 8 > server 1.de.pool.ntp.org minpoll 4 maxpoll 8 > server 2.de.pool.ntp.org minpoll 4 maxpoll 8 > server ntp1.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > server ntp2.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > server ntp3.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > server ntp4.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 > > restrict default ignore > restrict 127.0.0.1 Err.. your configuration says "ignore all NTP servers except localhost". You would need to let ntpd accept a time service from all those machines you've told it are servers. Since you're using pool.ntp.org, you're going to need a blanket 'allow any server' config like: restrict default nomodify nopeer noquery restrict 127.0.0.1 Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGpGwn8Mjk52CukIwRCKcjAJkBuV9WEBjb5XUOTLUGFyrivn/3KgCffnDa 8Ya5zpx5rZlQndLS377fPMA= =5nqc -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: ntpd just sits there and does nothing
My original intention was just to say that openntpd works just out of the box, while ntpd doesn't. And since openntpd works fine for me, I am not really interested in resolving this. Anyway since so many of you seem to be, here is the requested data: > ntp.conf server 0.de.pool.ntp.org minpoll 4 maxpoll 8 server 1.de.pool.ntp.org minpoll 4 maxpoll 8 server 2.de.pool.ntp.org minpoll 4 maxpoll 8 server ntp1.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp2.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp3.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 server ntp4.rz.uni-karlsruhe.de minpoll 4 maxpoll 8 restrict default ignore restrict 127.0.0.1 > ntpdc -p -c kerni -c loopi -c sysi -c syss remote local st poll reach delay offsetdisp === =time.as-compute 192.168.1.1216 2560 0.0 0.00 0.0 =mail.syncronisa 192.168.1.1216 2560 0.0 0.00 0.0 =proxy1.rz.uni-k 192.168.1.1216 2560 0.0 0.00 0.0 =proxy2.rz.uni-k 192.168.1.1216 2560 0.0 0.00 0.0 =proxy3.rz.uni-k 192.168.1.1216 2560 0.0 0.00 0.0 =proxy4.rz.uni-k 192.168.1.1216 2560 0.0 0.00 0.0 =crux.pmsf.net 192.168.1.1216 2560 0.0 0.00 0.0 pll offset: 0 s pll frequency:0.000 ppm maximum error:0.365516 s estimated error: 1.6e-05 s status: 2001 pll nano pll time constant:0 precision:1e-09 s frequency tolerance: 496 ppm offset: 0.00 s frequency:0.000 ppm poll adjust: 0 watchdog timer: 730 s system peer: 0.0.0.0 system peer mode: unspec leap indicator: 11 stratum: 16 precision:-19 root distance:0.0 s root dispersion: 0.01094 s reference ID: [73.78.73.84] reference time: . Thu, Feb 7 2036 7:28:16.000 system flags: auth monitor ntp kernel stats jitter: 0.00 s stability:0.000 ppm broadcastdelay: 0.003998 s authdelay:0.00 s time since restart: 730 time since reset: 730 packets received: 87 packets processed: 0 current version:0 previous version: 0 bad version:0 access denied: 57 bad length or format: 0 bad authentication: 0 rate exceeded: 0 > ntpdate with -q in ntpdate_flags # /etc/rc.d/ntpdate onestart Setting date via ntp. server 193.218.127.251, stratum 2, offset 0.631432, delay 0.04562 server 213.133.123.125, stratum 2, offset 0.630518, delay 0.03748 server 194.25.115.122, stratum 1, offset 0.633518, delay 0.04091 server 129.13.186.4, stratum 0, offset 0.00, delay 0.0 server 129.13.186.3, stratum 0, offset 0.00, delay 0.0 server 129.13.186.2, stratum 0, offset 0.00, delay 0.0 server 129.13.186.1, stratum 0, offset 0.00, delay 0.0 23 Jul 08:55:49 ntpdate[1772]: step time server 194.25.115.122 offset 0.633518 sec > /usr/local/sbin/ntpd -sd # This is openntpd ntp engine ready reply from 84.16.235.165: offset 0.573124 delay 0.011219, next query 8s reply from 87.106.95.189: offset 0.573368 delay 0.014235, next query 8s reply from 212.112.228.242: offset 0.574221 delay 0.014708, next query 7s reply from 88.198.8.101: offset 0.573796 delay 0.015175, next query 6s reply from 212.77.176.178: offset 0.574222 delay 0.016076, next query 5s reply from 195.179.15.118: offset 0.541673 delay 0.022011, next query 5s reply from 85.214.23.162: offset 0.568205 delay 0.022973, next query 9s reply from 194.77.75.99: offset 0.573878 delay 0.033467, next query 8s reply from 212.77.176.178: offset 0.570650 delay 0.014009, next query 7s reply from 195.179.15.118: offset 0.537944 delay 0.020095, next query 5s reply from 88.198.8.101: offset 0.570179 delay 0.013163, next query 9s reply from 84.16.235.165: offset 0.568732 delay 0.009621, next query 6s reply from 212.112.228.242: offset 0.569989 delay 0.013116, next query 5s reply from 87.106.95.189: offset 0.568727 delay 0.013139, next query 6s reply from 194.77.75.99: offset 0.570201 delay 0.029342, next query 6s reply from 85.214.23.162: offset 0.562845 delay 0.021890, next query 9s reply from 195.179.15.118: offset 0.536313 delay 0.021833, next query 7s reply from 212.112.228.242: offset 0.567116 delay 0.012397, next query 7s reply from 212.77.176.178: offset 0.567040 delay 0.014119, next query 7s reply from 84.16.235.165: offset 0.565892 delay 0.010525, next query 6s no reply from 129.13.186.4 received in time, next query 610s no reply from 129.13.186.3 received in time, next query 607s no reply from 129.13.186.2 received in time, next query 624s no reply from 129.13.186.1 received in time, next query 600s reply from 87.106.95.189: offset 0.565603 delay 0.013103, next query 7s reply from 194.77.75.99: offset 0.564807 delay 0.031786, next
