Dave,
> On Mon, Nov 9, 2009 at 2:19 PM, John Mendenhall wrote:
> > I have several openbsd 4.4 boxes, all of which are running
> > spamd. I have a cron job which runs a script, which has the
> > following commands in it:
>
> Well, sort is obviously calling fwrit
Peter,
> John Mendenhall writes:
> > oldest spamdb grey entry date timestamp:
> > sort: fwrite: Broken pipe
> >
> Just to eliminate the obvious - how much dis
pid I am doing wrong that is easy to fix.
Please point me in the direction to find the solution for
this issue. Thanks in advance!
JohnM
--
john mendenhall
j...@surfutopia.net
surf utopia
internet services
On Thu, 12 Jul 2007, Jason McIntyre wrote:
> On Wed, Jul 11, 2007 at 06:21:43PM -0500, Jacob Yocom-Piatt wrote:
> >
> > the term "rathered" comes to mind.
> >
>
> what does it mean?
"Dan Rather"-ed
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
os
on them. None of them found the card.
I reseated the card. No go.
I tried another card I had, same model. Nothing.
I am doing this in a 1U box, so there is a pci 1u
riser card. Could it be the riser is bad? Or,
could the pci slot itself be bad?
What is the best way to test the pci slot?
Thanks!
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
ore functional than they were last time I looked.
Understood.
Thanks so much for your input.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
ffed netmask ffed ttymask ffef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
--
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
set the bios timings and power levels.
I reset the bios timings. However, the only choices were
optimal and high performance.
Same error.
I will look for a bios upgrade, if one exists...
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
els.
JohnM
> On Tue, 12 Jun 2007, John Mendenhall wrote:
>
> >openbsd gurus,
> >
> >As my saga continues...
> >I have a newly built server on which I am attempting to install
> >openbsd 4.0. Problems occurred on install of sets, where comp
> >set keeps th
ding the sets via ftp, same error, same location.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
oard,
the cables are connected to the std ide0 and ide1
connectors on the motherboard. When you say IDE
bus, are you referring to another connector?
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
hat
> was bad. Replacing cdrom with DVD drive from my workstation helped.
Could that explain the errors I am seeing?
It appears the error is on the write, not the read,
though I could be wrong.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
server up and running so I
can move on to the next one. No time pressure, though.
Thank you in advance for any pointers you can provide.
Thanks!
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
dmesg doesn't help anybody. Sorry for bringing it up :(
This is the 4.0 release. I usually run a release behind. And, I have
not ordered a 4.1 yet. I will in the next week or two.
I do have v3.9 and earlier releases available.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
probing for pckbc0 succeeded
pckbc0 at isa0 port 0x60/5
>>> probing for pckbd*
>>> pckbd probe returned 2
>>> probing for pms*
>>> pms probe returned 0
>>> probing for pmsi*
>>> pmsi probe returned 0
>>> pckbd probe won
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
>>> probing for wskbd*
>>> wskbd probe returned 1
>>> wskbd probe won
wskbd0 at pckbd0: console keyboard, using wsdisplay0
>>> probing for pckbd*
>>> pckbd probe returned 0
>>> probing for pms*
>>> pms probe returned 0
>>> probing for pmsi*
>>> pmsi probe returned 0
>>> no winning probe
>>> probing for vga0
>>> probing for vga0 failed
>>> probing for pcdisplay0
>>> probing for pcdisplay0 failed
>>> probing for bha0
>>> probing for bha0 failed
>>> probing for aic0
>>> probing for aic0 failed
>>> probing for aha0
>>> probing for aha0 failed
>>> probing for aha1
>>> probing for aha1 failed
>>> probing for uha0
>>> probing for uha0 failed
>>> probing for wdc0
>>> probing for wdc0 failed
>>> probing for wdc1
>>> probing for wdc1 failed
>>> probing for lc0
>>> probing for lc0 failed
>>> probing for lc1
>>> probing for lc1 failed
>>> probing for ne0
>>> probing for ne0 failed
>>> probing for ne1
>>> probing for ne1 failed
>>> probing for ne2
>>> probing for ne2 failed
>>> probing for we0
>>> probing for we0 failed
>>> probing for we1
>>> probing for we1 failed
>>> probing for ec0
>>> probing for ec0 failed
>>> probing for ep0
>>> probing for ep0 failed
>>> probing for ep*
>>> probing for ep* finished
>>> probing for ie0
>>> probing for ie0 failed
>>> probing for ex0
>>> probing for ex0 failed
>>> probing for le0
>>> probing for le0 failed
>>> probing for sm0
>>> probing for sm0 failed
>>> probing for mpu*
>>> probing for mpu* finished
>>> probing for sb0
>>> probing for sb0 failed
>>> probing for pas0
>>> probing for pas0 failed
>>> probing for pss0
>>> probing for pss0 failed
>>> probing for wss0
>>> probing for wss0 failed
>>> probing for gus0
>>> probing for gus0 failed
>>> probing for pcppi0
>>> probing for pcppi0 succeeded
pcppi0 at isa0 port 0x61
>>> probing for midi*
>>> midi probe returned 1
>>> probing for spkr0
>>> spkr probe returned 1
>>> midi probe won
midi0 at pcppi0:
>>> probing for midi*
>>> midi probe returned 0
>>> probing for spkr0
>>> spkr probe returned 1
>>> spkr probe won
spkr0 at pcppi0
>>> probing for midi*
>>> midi probe returned 0
>>> no winning probe
>>> probing for lpt0
>>> probing for lpt0 succeeded
lpt0 at isa0 port 0x378/4 irq 7
>>> probing for lpt1
>>> probing for lpt1 failed
>>> probing for lpt2
>>> probing for lpt2 failed
>>> probing for lm0
>>> probing for lm0 failed
>>> probing for nsclpcsio*
>>> probing for nsclpcsio* finished
>>> probing for nsclpcsio*
>>> probing for nsclpcsio* finished
>>> probing for gscsio*
>>> probing for gscsio* finished
>>> probing for gscsio*
>>> probing for gscsio* finished
>>> probing for it0
>>> probing for it0 failed
>>> probing for it1
>>> probing for it1 failed
>>> probing for it2
>>> probing for it2 failed
>>> probing for viasio*
>>> probing for viasio* finished
>>> probing for viasio*
>>> probing for viasio* finished
>>> probing for aps0
>>> probing for aps0 failed
>>> probing for npx0
>>> probing for npx0 succeeded
npx0 at isa0 port 0xf0/16: using exception 16
>>> probing for pccom0
>>> probing for pccom0 succeeded
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
>>> probing for pccom1
>>> probing for pccom1 failed
>>> probing for pccom2
>>> probing for pccom2 failed
>>> probing for lms0
>>> probing for lms0 failed
>>> probing for lms1
>>> probing for lms1 failed
>>> probing for mms0
>>> probing for mms0 failed
>>> probing for mms1
>>> probing for mms1 failed
>>> probing for fdc0
>>> probing for fdc0 succeeded
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
>>> probing for fd*
>>> fd probe returned 0
>>> no winning probe
>>> probing for fd*
>>> fd probe returned 0
>>> no winning probe
>>> probing for fd*
>>> fd probe returned 0
>>> no winning probe
>>> probing for fd*
>>> fd probe returned 0
>>> no winning probe
>>> probing for isapnp0
>>> probing for isapnp0 failed
>>> probing for pcic0
>>> probing for pcic0 failed
>>> probing for pcic1
>>> probing for pcic1 failed
>>> probing for pcic2
>>> probing for pcic2 failed
biomask fb6d netmask fb6d ttymask fbef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
-
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
> On Wed, May 16, 2007 at 09:30:44AM -0700, John Mendenhall wrote:
> > If anyone knows of a tool I can use to determine the ATA
> > controller, or any other hw things I need to find out,
> > please post any pointers.
>
> dmesg(8)
Well, I posted the dmesg at the beginn
tried, haven't looked anything up.
Anyone know how to boot with more messages?
man boot doesn't show any verbose options.
> We are definately narrowing down the culprit, and I just hope we come
> to a solid conclusion.
Amen.
Thanks!
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
hunderboot ultimate boot cd.
Any hints on which tool could get the ata controller the box is using?
I can see the ATA-# supported (6,5,4,3,2). Lots of other information.
I don't see a model/version number yet.
I will keep checking all the tools on here.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
and greps the output to make sure it is stopped
(looks for 'not running')
+ if I don't find not running, pages me
+ run apachectl startssl
This is all in a wrapper script which then calls awstats
after a successful rotate and restart.
Works for us.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
st
> step.
Already done that. No errors.
See previous thread, subject 'openbsd 4.0 server, new setup,
getting panics', dated 5/1-5/3.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
t swapping out cables, hard disks, motherboard,
etc? Any hints or suggestions are appreciated.
Thanks in advance!
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
Tim,
> > > - Quote --
> > > Date: Mon, 7 May 2007 10:29:50 -0700
> > > From: "John Mendenhall" <[EMAIL PROTECTED]>
> > > To: "Artur Grabowski" <[EMAIL PROTECTED]>
> > > CC: mis
Tim,
On Tue, 08 May 2007, Tim Judd wrote:
> - Quote --
> Date: Mon, 7 May 2007 10:29:50 -0700
> From: "John Mendenhall" <[EMAIL PROTECTED]>
> To: "Artur Grabowski" <[EMAIL PROTECTED]>
> CC: misc@openbsd.org
> Subject:
he entire thing. Unless someone
wants me to try something else.
Thanks!
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
?
Thanks in advance!
JohnM
On Fri, 04 May 2007, John Mendenhall wrote:
> > Does this indicate I have a bad drive? Or, does it
> > just need fsck run on it? I just installed openbsd 4.0
> > on this box a few days ago. It rebuilt the file systems
> > from scratch. Do I
, using wsdisplay0
> pcppi0 at isa0 port 0x61
> midi0 at pcppi0:
> spkr0 at pcppi0
> lpt0 at isa0 port 0x378/4 irq 7
> npx0 at isa0 port 0xf0/16: using exception 16
> pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
> fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
> biomask fb6d netmask fb6d ttymask fbef
> pctr: user-level cycle counter enabled
> mtrr: Pentium Pro MTRR support
> dkcsum: wd0 matches BIOS drive 0x80
> dkcsum: wd1 matches BIOS drive 0x81
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
> WARNING: / was not properly unmounted
> -
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
on 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask fb6d netmask fb6d ttymask fbef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
WARNING: / was not properly unmounted
-
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
e fsb speed.
I modified the bios as follows:
- sdram timing by spd enabled
- auto detect pci clock enabled
- clk spread spectrum enabled
I retested the memory, ran it overnight using memtest86+.
No errors.
I don't know which of the above fixed the problem.
However, it is not causing any memory errors now.
Thanks so much for the pointers.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
front side bus to be 200, instead of 266 and
am re-running the memory tests.
> ...
> > rl0 at pci0 dev 10 function 0 "Realtek 8139" rev 0x10: irq 12, address
> > 00:e0:06:f6:bf:3e
> > rlphy0 at rl0 phy 0: RTL internal PHY
> ...
>
> That looks bad. IRQ1
0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
biomask fb6d netmask fb6d ttymask fbef
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive
ant.
My initial assumption is, there must be a hardware problem.
How do I determine where the problem is so I can start
diagnosing it?
Thanks in advance for any assistance or pointers or search
terms to use.
JohnM
--
john mendenhall
[EMAIL PROTECTED]
surf utopia
internet services
31 matches
Mail list logo