running iscontrol at boot time

[David Newman]

How to configure FreeBSD so that an iSCSI initiator will mount a
filesystem on an iSCSI target at boot time?

The /boot/loader.conf file has 'iscsi_initiator_load="YES"' but
iscontrol does not run at boot time.

I believe iscontrol needs to run after the kernel module is loaded but
before a filesystem in /etc/fstab is mounted.

This works fine manually, but a reboot fails because the FreeBSD box
doesn't run iscontrol at boot time, and thus can't mount the filesystem
on the iSCSI target.

Pardon me if this has been asked before, as it seems like a standard
problem, but I couldn't find anything in recent freebsd-scsi  archives
or in the man pages. I asked on freebsd-scsi about 10 days ago, but
never got a response.

The initiator runs a generic FreeBSD 8.3-RELEASE/amd64 kernel.

Thanks!

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Upgrading perl

[David Newman]

On 8/29/12 10:59 AM, David Newman wrote:
> On 8/29/12 8:08 AM, Jack Stone wrote:
>> On 8/29/2012 8:27 AM, Lowell Gilbert wrote:
>>> Jack Stone  writes:
>>>
>>>> uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD
>>>> 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009
>>>>
>>>> Running perl5.10 (yeah, old!)
>>>> This is a production server.
>>>>
>>>>
>>>> Been playing catchup on ports including perl as UPDATING recommends:
>>>> portupgrade -o lang/perl5.12 -f perl-5.10.\*
>>>>
>>>> That has worked on other servers, but not this one. Anyone know what I
>>>> need to do to clean this up??
>>>>
>>>> But, can't get past this fatal error:
>>>> mail# portupgrade -o lang/perl5.12 -f perl-5.10.\*
>>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive
>>>> specification: "WITHOUT_"
>>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive
>>>> specification: "WITHOUT_"
>>>> make: fatal errors encountered -- cannot continue
>>>> ** Makefile possibly broken: lang/perl5.12:
>>> You're almost four years past the end-of-life on the release you're
>>> running, so it's been left behind in terms of support. In this case it
>>> looks (based on a *very* quick look) that you may be running into
>>> changes in how make(1) actually works, in which case backporting the
>>> ports functionality will be more work than it's worth.
>>>
>>> If the machine "can't" be updated, and assuming it's secure (which hard
>>> to be sure about with old software on the Internet), you may be best off
>>> leaving it alone.
>>>
>>> Good luck.
>>>
>>>
>> Thanks for the reply.
>>
>> Actually, on other servers with the same upgrading needs, perl-5.12
>> installed without any issue. My intention is to upgrade perl in
>> increments to get well past EOL.
>>
>> Wonder if I just deinstalled the old perl5-5.10 and then installed the
>> perl5-12 would work. I can do that right from the port: make perl5-12
>> first to see if that works, then:
>> # make deinstall (perl-5.10) then: make install clean
> 
> If you're using portmaster, you should be able to do something like the
> following from /usr/ports:
> 
>   portmaster -o lang/perl5.16 lang/perl5.10
>   portmaster p5-
> 
> and perl automagically will upgrade.

Sorry, I'd missed that you'd tried this and it isn't working.

make has changed since the 7.0 days. I agree with Jack that you're
better off leaving well enough alone. If you really need perl5.16+
capabilities you're much better off moving your program to a more recent
version of FreeBSD.

dn


> 
> This is from /usr/ports/UPDATING. You can also find instructions for
> portupgrade there.
> 
> Don't know about dependencies with 7.0, though.
> 
> dn
> 
> 
>>
>> What do you think? I've got to move up because an important perl program
>> requires a minimum 5.12.
> 
> 
> 
>>
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Upgrading perl

[David Newman]

On 8/29/12 8:08 AM, Jack Stone wrote:
> On 8/29/2012 8:27 AM, Lowell Gilbert wrote:
>> Jack Stone  writes:
>>
>>> uname -a FreeBSD mail.sagedata.net 7.0-RELEASE-p9 FreeBSD
>>> 7.0-RELEASE-p9 #2: Sun Jan 18 19:59:27 CST 2009
>>>
>>> Running perl5.10 (yeah, old!)
>>> This is a production server.
>>>
>>>
>>> Been playing catchup on ports including perl as UPDATING recommends:
>>> portupgrade -o lang/perl5.12 -f perl-5.10.\*
>>>
>>> That has worked on other servers, but not this one. Anyone know what I
>>> need to do to clean this up??
>>>
>>> But, can't get past this fatal error:
>>> mail# portupgrade -o lang/perl5.12 -f perl-5.10.\*
>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive
>>> specification: "WITHOUT_"
>>> "/usr/ports/Mk/bsd.options.mk", line 231: Error in archive
>>> specification: "WITHOUT_"
>>> make: fatal errors encountered -- cannot continue
>>> ** Makefile possibly broken: lang/perl5.12:
>> You're almost four years past the end-of-life on the release you're
>> running, so it's been left behind in terms of support. In this case it
>> looks (based on a *very* quick look) that you may be running into
>> changes in how make(1) actually works, in which case backporting the
>> ports functionality will be more work than it's worth.
>>
>> If the machine "can't" be updated, and assuming it's secure (which hard
>> to be sure about with old software on the Internet), you may be best off
>> leaving it alone.
>>
>> Good luck.
>>
>>
> Thanks for the reply.
> 
> Actually, on other servers with the same upgrading needs, perl-5.12
> installed without any issue. My intention is to upgrade perl in
> increments to get well past EOL.
> 
> Wonder if I just deinstalled the old perl5-5.10 and then installed the
> perl5-12 would work. I can do that right from the port: make perl5-12
> first to see if that works, then:
> # make deinstall (perl-5.10) then: make install clean

If you're using portmaster, you should be able to do something like the
following from /usr/ports:

  portmaster -o lang/perl5.16 lang/perl5.10
  portmaster p5-

and perl automagically will upgrade.

This is from /usr/ports/UPDATING. You can also find instructions for
portupgrade there.

Don't know about dependencies with 7.0, though.

dn


> 
> What do you think? I've got to move up because an important perl program
> requires a minimum 5.12.



> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: portaudit and automake14

[David Newman]

On 8/28/12 11:53 AM, Bryan Drewery wrote:
> On 8/28/2012 1:47 PM, David Newman wrote:
>> 1. On a 8.0-RELEASE system, I'm having a problem with the automake14
>> port, where the portaudit port reports this vulnerability:
>>
>> http://portaudit.freebsd.org/10f38033-e006-11e1-9304-.html
>>
>> Refreshing the ports collection with 'portsnap fetch extract' and then
>> running 'portmaster automake14' returned the same error as before:
>>
>> automake -- Insecure 'distcheck' recipe granted world-writable distdir
>>
>> I then tried to do 'make deinstall && make reinstall' for automake14,
>> but that just deinstalled the port. The system returns the same error as
>> above when trying to reinstall.
>>
>> How to resolve?
>>
>> 2. This system also has a couple of other automake ports installed:
>>
>> automake-1.12.3
>> automake-wrapper-20101119
>>
>> How to determine if these are necessary in addition to automake14?
> 
> 
> automake14 is not vulnerable to this issue. The vuxml was recently
> updated to show that it only affects 1.5 and up.
> 
> http://www.vuxml.org/freebsd/36235c38-e0a8-11e1-9f4d-002354ed89bc.html
> 
> Not sure when portaudit updates, but in the meantime you can ignore that
> error:
> 
> env DISABLE_VULNERABILITIES=1 portmaster ...
> 
> You can also try deinstalling automake14 as it may not even be required
> on your system and the newer 1.12 may automatically be used instead.
> 
> To be clear, automake14 is super old. automake-1.12.3 is current.

Thanks much for this. As noted, I've de-installed automake14 and haven't
noticed any problems as a result. It can be reinstalled using that env
flag you mentioned, but if it's not needed, then that's one less thing
to go wrong. . .

Thanks again.

dn


> 
> 
>>
>> Thanks
>>
>> dn
>>
> 
> Bryan
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

portaudit and automake14

[David Newman]

1. On a 8.0-RELEASE system, I'm having a problem with the automake14
port, where the portaudit port reports this vulnerability:

http://portaudit.freebsd.org/10f38033-e006-11e1-9304-.html

Refreshing the ports collection with 'portsnap fetch extract' and then
running 'portmaster automake14' returned the same error as before:

automake -- Insecure 'distcheck' recipe granted world-writable distdir

I then tried to do 'make deinstall && make reinstall' for automake14,
but that just deinstalled the port. The system returns the same error as
above when trying to reinstall.

How to resolve?

2. This system also has a couple of other automake ports installed:

automake-1.12.3
automake-wrapper-20101119

How to determine if these are necessary in addition to automake14?

Thanks

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

serial console access on ZFS server

[David Newman]

I'm having difficulty gaining serial console access to an 8.2-RELEASE
box running ZFS on its root partition. I would appreciate pointers to
help determine if this is a FreeBSD issue, or something external like
BIOS or cabling.

The server is a vanilla 1U Supermicro motherboard with AMI BIOS. The
BIOS is configured to run headless and to allow remote access via COM1.
There is no monitor, keyboard, or mouse attached.

FreeBSD is configured to use ZFS in all partitions. The server works
fine in all regards except wrt serial access.

/boot/loader.conf has this:

console="comconsole"
zfs_load="YES"
vfs.root.mountfrom="zfs:zroot"
aio_load="YES"

/boot.config has this:

-Dh

and /etc/ttys has this:

ttyu0   "/usr/libexec/getty std.9600"   vt100   on  secure

The machine shows that tty exists:

# ls -l /dev/ttyu0
crw---  1 root  wheel0,  36 Nov 29 14:02 /dev/ttyu0

But there doesn't appear to be a device bound to it:

# grep -i 'irq 4' /var/run/dmesg.boot
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
# ls -l /dev/uart0
ls: /dev/uart0: No such file or directory
# ls -l /dev/acpi0
ls: /dev/acpi0: No such file or directory

I'm attempting to connect via a known-good null modem cable (DB9 on both
ends) and a known-good USB serial dongle attached to my Mac, using the
Zterm program. This setup works fine for other serial devices.

Thanks in advance for troubleshooting clues.

dn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: portmaster upgrade of p5-IO-Socket-SSL fails

[David Newman]

On 1/23/11 10:12 AM, Jens Jahnke wrote:
> Hi,
> 
> On Sun, 23 Jan 2011 09:42:58 -0800
> David Newman  wrote:
> 
> DN> FreeBSD 8.0-RELEASE-p4 amd64
> DN> 
> DN> The command 'portmaster security/p5-IO-Socket-SSL' fails because the
> DN> module is not found in any archive. I've pasted the error output
> DN> below.
> 
> I had this issue on 8.1-RELEASE amd64 but after round about a day the
> module showed up in the archives queried.

Thanks. It only occurred to me after posting to email the maintainer for
this port, who responded that there was a mistake in posting a bad
update. Refreshing ports and rerunning portmaster works fine now.

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

portmaster upgrade of p5-IO-Socket-SSL fails

[David Newman]

FreeBSD 8.0-RELEASE-p4 amd64

The command 'portmaster security/p5-IO-Socket-SSL' fails because the
module is not found in any archive. I've pasted the error output below.

The file /usr/ports/UPGRADING doesn't mention any problem with this module.

Thanks in advance for clues on getting this upgrade to work.

dn

dnewman@merckx ~ 503$ sudo portmaster security/p5-IO-Socket-SSL

===>>> Currently installed version: p5-IO-Socket-SSL-1.37
===>>> Port directory: /usr/ports/security/p5-IO-Socket-SSL

===>>> Gathering distinfo list for installed ports

===>>> Launching 'make checksum' for security/p5-IO-Socket-SSL in background
===>>> Gathering dependency list for security/p5-IO-Socket-SSL from ports
===>>> Initial dependency check complete for security/p5-IO-Socket-SSL

===>>> Starting build for security/p5-IO-Socket-SSL <<<===

===>>> All dependencies are up to date

===>  Cleaning for p5-IO-Socket-SSL-1.38

===>>> Waiting on fetch & checksum for security/p5-IO-Socket-SSL <<<===
===>  Vulnerability check disabled, database not found
===>  License check disabled, port has not defined LICENSE
===>  Found saved configuration for p5-IO-Socket-SSL-1.37
=> IO-Socket-SSL-1.38.tar.gz doesn't seem to exist in
/usr/ports/distfiles//.
=> Attempting to fetch from
ftp://ftp.cpan.org/pub/CPAN/modules/by-module/IO/.


===>>> Waiting on fetch & checksum for security/p5-IO-Socket-SSL <<<===
===>  Vulnerability check disabled, database not found
===>  License check disabled, port has not defined LICENSE
===>  Found saved configuration for p5-IO-Socket-SSL-1.37
=> IO-Socket-SSL-1.38.tar.gz doesn't seem to exist in
/usr/ports/distfiles//.
=> Attempting to fetch from
ftp://ftp.cpan.org/pub/CPAN/modules/by-module/IO/.


===>>> Waiting on fetch & checksum for security/p5-IO-Socket-SSL <<<===
fetch:
http://www.cpan.dk/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz: Not Found
=> Attempting to fetch from
http://ring.nict.go.jp/archives/lang/perl/CPAN/modules/by-module/IO/.
fetch:
http://ring.nict.go.jp/archives/lang/perl/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
Not Found
=> Attempting to fetch from
http://ring.riken.jp/archives/lang/perl/CPAN/modules/by-module/IO/.
fetch:
http://ring.riken.jp/archives/lang/perl/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
Not Found
=> Attempting to fetch from
ftp://ftp.kddlabs.co.jp/lang/perl/CPAN/modules/by-module/IO/.
fetch:
ftp://ftp.kddlabs.co.jp/lang/perl/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from
http://ftp.jaist.ac.jp/pub/CPAN/modules/by-module/IO/.
fetch:
http://ftp.jaist.ac.jp/pub/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
Not Found
=> Attempting to fetch from
ftp://ftp.dti.ad.jp/pub/lang/CPAN/modules/by-module/IO/.


===>>> Waiting on fetch & checksum for security/p5-IO-Socket-SSL <<<===
fetch:
http://ring.riken.jp/archives/lang/perl/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
Not Found
=> Attempting to fetch from
ftp://ftp.kddlabs.co.jp/lang/perl/CPAN/modules/by-module/IO/.
fetch:
ftp://ftp.kddlabs.co.jp/lang/perl/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from
http://ftp.jaist.ac.jp/pub/CPAN/modules/by-module/IO/.
fetch:
http://ftp.jaist.ac.jp/pub/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
Not Found
=> Attempting to fetch from
ftp://ftp.dti.ad.jp/pub/lang/CPAN/modules/by-module/IO/.
fetch:
ftp://ftp.dti.ad.jp/pub/lang/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from
ftp://ftp.sunet.se/pub/lang/perl/CPAN/modules/by-module/IO/.
fetch:
ftp://ftp.sunet.se/pub/lang/perl/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from
ftp://mirror.hiwaay.net/CPAN/modules/by-module/IO/.


===>>> Waiting on fetch & checksum for security/p5-IO-Socket-SSL <<<===
fetch:
http://ftp.jaist.ac.jp/pub/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
Not Found
=> Attempting to fetch from
ftp://ftp.dti.ad.jp/pub/lang/CPAN/modules/by-module/IO/.
fetch:
ftp://ftp.dti.ad.jp/pub/lang/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from
ftp://ftp.sunet.se/pub/lang/perl/CPAN/modules/by-module/IO/.
fetch:
ftp://ftp.sunet.se/pub/lang/perl/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from
ftp://mirror.hiwaay.net/CPAN/modules/by-module/IO/.
fetch:
ftp://mirror.hiwaay.net/CPAN/modules/by-module/IO/IO-Socket-SSL-1.38.tar.gz:
File unavailable (e.g., file not found, no access)
=> Attempting to fetch from
ftp://ftp.mirrorservice.org/sites/ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/IO/.
fetch:
ftp://ftp.mirrorservice.org/sites/ftp.funet.fi/pub/languages/perl/CPAN/modules/by-module/IO/IO-

Re: Portmaster general questions and problems

[David Newman]

On 12/26/10 11:45 AM, Bruce Cran wrote:
> On Sun, 26 Dec 2010 11:39:58 -0800
> "Ron (Lists)"  wrote:
> 
>> ok, so libltdl-2.2.10 is already installed?  Why is that an issue?  
>> Why doesn't portmaster just happily skip it since it's already 
>> installed?  What am I not understanding here?  Or am I using
>> portmaster wrong?
> 
> That's a problem I've come across before too - I'd be interested to
> know what's going wrong too.

This is covered in /usr/ports/UPDATING as part of the autotools cleanup.
Just search for the date '20101208' and follow the instructions in that
note.

It's a good idea to check the UPDATING file before running 'portmaster
-a' or anytime you have problems with portmaster.

dn



___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: jumbo frame support in bge(4) for BCM5704 SOLVED

[David Newman]

On 9/15/10 3:17 PM, David Newman wrote:
> On 9/14/10 7:43 PM, Adam Vande More wrote:
>> On Tue, Sep 14, 2010 at 9:19 PM, David Newman wrote:
>>
>>> 8.0-RELEASE amd64, Tyan S2882-D motherboard, Broadcom BCM5704C gigabit
>>> Ethernet transceivers
>>>
>>> Thanks in advance for any clues on enabling jumbos on this system.
>>>
>>
>> What happens if you boot from a linux live cd and try to enable frames
>> there?
> 
> With Ubuntu 10.04, the system accepts "ifconfig eth1 mtu N" for any
> value of N up to 9000, and shows an MTU of N in response to 'ifconfig'.
> 
> With 8.1-RELEASE (not 8.0 as stated before, sorry), the command
> 'ifconfig bge0 mtu 8000' produces an error:
> 
> ifconfig: ioctl (set mtu): Invalid argument
> 
> Same thing with 'mtu 1500', 'mtu 1400', etc.

I neglected to mention that this system uses link aggregation on the bge
interfaces. Once a lagg interface exists, an MTU cannot be applied to
either the bge or lagg instances.

However, everything works fine if MTUs are applied to bge interfaces
before bringing up the lagg interface:

ifconfig_bge0="mtu 9000 up"
ifconfig_bge1="mtu 9000 up"
cloned_interfaces="lagg0"
ifconfig_lagg0="laggproto lacp laggport bge0 laggport bge1"
ipv4_addrs_lagg0="10.0.0.1/24"

# ifconfig lagg0 | grep mtu
lagg0: flags=8843 metric 0 mtu 9000

One other thing: The maximum value for the BCM5704's mtu is 9000 bytes,
not the more widely used 9216 for jumbo frames. This may reflect a
hardware limit for this controller.

Many thanks to FreeBSD bge(4) maintainer Pyun YongHyeon for contacting
me and spotting my configuration error with the lagg setup.

dn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: jumbo frame support in bge(4) for BCM5704

[David Newman]

On 9/14/10 7:43 PM, Adam Vande More wrote:
> On Tue, Sep 14, 2010 at 9:19 PM, David Newman wrote:
> 
>> 8.0-RELEASE amd64, Tyan S2882-D motherboard, Broadcom BCM5704C gigabit
>> Ethernet transceivers
>>
>> Thanks in advance for any clues on enabling jumbos on this system.
>>
> 
> What happens if you boot from a linux live cd and try to enable frames
> there?

With Ubuntu 10.04, the system accepts "ifconfig eth1 mtu N" for any
value of N up to 9000, and shows an MTU of N in response to 'ifconfig'.

With 8.1-RELEASE (not 8.0 as stated before, sorry), the command
'ifconfig bge0 mtu 8000' produces an error:

ifconfig: ioctl (set mtu): Invalid argument

Same thing with 'mtu 1500', 'mtu 1400', etc.

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

jumbo frame support in bge(4) for BCM5704

[David Newman]

8.0-RELEASE amd64, Tyan S2882-D motherboard, Broadcom BCM5704C gigabit
Ethernet transceivers

Looking for clues on enabling jumbo support on BCM5704 chips.

The bge(4) manpage claims this interface supports jumbo frames, as does
Broadcom's data sheet.

However, 'ifconfig bge0 mtu 9000' returns an error, as does 'ifconfig
bge0 mtu 1500':

ifconfig: ioctl (set mtu): Invalid argument

Also, this thread claims the manpage anddata sheet are in error and that
jumbos aren't supported:

http://lists.freebsd.org/pipermail/freebsd-net/2006-June/010866.html

The Linux tg3 driver for this chip does support jumbos up to 9000 bytes
but that doesn't necessarily answer whether the hardware can get there.

Thanks in advance for any clues on enabling jumbos on this system.

dn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: Online school for FreeBSD

[David Newman]

On 4/10/10 3:08 PM, Chris Whitehouse wrote:
> Roland Smith wrote:
>> On Fri, Apr 09, 2010 at 09:34:59PM -0800, jt wrote:
>>
>>> I've been doing searches for online schools that teach FreeBSD. I've
>>> been
>>> trying to learn on an off for years but when it starts getting
>>> complicated,
>>> I get stuck. The handbook don't do allot of good.
>>
>> You can download the book "The Complete FreeBSD" from
>> http://www.lemis.com/grog/Documentation/CFBSD/
> 
> There is also Absolute FreeBSD
> http://www.absolutefreebsd.com/
> Only available for purchase though.

+1

I've found this and other books by Mr. Lucas to be informative,
accessible and even entertaining, well worth their price.

dn

> 
> Chris
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscr...@freebsd.org"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: php5-filter update fails; possible pcre issue

[David Newman]

On 4/10/10 7:59 AM, Kieran Black wrote:
> According to /usr/ports/MOVED php5-filter is now also part of core php5
> 
> host# grep "php5-filter" /usr/ports/MOVED
> security/pecl-filter|security/php5-filter|2008-12-11|Now bundled in php5

Thanks. Obvious question, but just checking: Would uninstalling
php5-filter and php5-pcre (if installed) and then proceeding with
updating all other php5 ports have the same effect as updating these
ports as if they were standalone, as before?

dn


> 
> Kieran
> 
> On 10/04/2010 15:39, David Newman wrote:
>> 8.0-RELEASE, amd64
>>
>> Running 'portmaster -a' fails to upgrade php5-filter-5.2.12 to
>> php5-filter-5.3.2. Error output below.
>>
>> I would be grateful for clues on a fix.
>>
>> Is this related to the php5-pcre port being moved into core php5?
>>
>> somehost# cd /usr/ports
>> somehost# make search name=php5-pcre
>> Port:   devel/php5-pcre
>> Moved:  lang/php5
>> Date:   2010-04-09
>> Reason: Bundled in core php
>>
>> thanks
>>
>> dn
>>
>> error output during 'portmaster -a' for php5-filter:
>>
>> In file included from
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:25:
>>
>> /usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No such
>> file or directory
>> In file included from
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:25:
>>
>> /usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=', ',',
>> ';', 'asm' or '__attribute__' before '*' token
>> /usr/local/include/php/ext/pcre/php_pcre.h:38: error: expected '=', ',',
>> ';', 'asm' or '__attribute__' before '*' token
>> /usr/local/include/php/ext/pcre/php_pcre.h:44: error: expected
>> specifier-qualifier-list before 'pcre'
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:
>>
>> In function 'php_filter_validate_regexp':
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
>>
>> error: 'pcre' undeclared (first use in this function)
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
>>
>> error: (Each undeclared identifier is reported only once
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
>>
>> error: for each function it appears in.)
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
>>
>> error: 're' undeclared (first use in this function)
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:413:
>>
>> error: 'pcre_extra' undeclared (first use in this function)
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:
>>
>> In function 'php_filter_validate_email':
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:500:
>>
>> error: 'pcre' undeclared (first use in this function)
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:500:
>>
>> error: 're' undeclared (first use in this function)
>> /usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:501:
>>
>> error: 'pcre_extra' undeclared (first use in this function)
>> *** Error code 1
>> 1 error
>> *** Error code 1
>>
>> Stop in /usr/ports/security/php5-filter.
>>
>> ===>>>  make failed for security/php5-filter
>> ===>>>  Aborting update
>>
>> ===>>>  Update for php5-filter-5.2.12 failed
>> ===>>>  Aborting update
>> ___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscr...@freebsd.org"
>>
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscr...@freebsd.org"

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

php5-filter update fails; possible pcre issue

[David Newman]

8.0-RELEASE, amd64

Running 'portmaster -a' fails to upgrade php5-filter-5.2.12 to
php5-filter-5.3.2. Error output below.

I would be grateful for clues on a fix.

Is this related to the php5-pcre port being moved into core php5?

somehost# cd /usr/ports
somehost# make search name=php5-pcre
Port:   devel/php5-pcre
Moved:  lang/php5
Date:   2010-04-09
Reason: Bundled in core php

thanks

dn

error output during 'portmaster -a' for php5-filter:

In file included from
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:25:
/usr/local/include/php/ext/pcre/php_pcre.h:29:18: error: pcre.h: No such
file or directory
In file included from
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:25:
/usr/local/include/php/ext/pcre/php_pcre.h:37: error: expected '=', ',',
';', 'asm' or '__attribute__' before '*' token
/usr/local/include/php/ext/pcre/php_pcre.h:38: error: expected '=', ',',
';', 'asm' or '__attribute__' before '*' token
/usr/local/include/php/ext/pcre/php_pcre.h:44: error: expected
specifier-qualifier-list before 'pcre'
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:
In function 'php_filter_validate_regexp':
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
error: 'pcre' undeclared (first use in this function)
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
error: (Each undeclared identifier is reported only once
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
error: for each function it appears in.)
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:412:
error: 're' undeclared (first use in this function)
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:413:
error: 'pcre_extra' undeclared (first use in this function)
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:
In function 'php_filter_validate_email':
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:500:
error: 'pcre' undeclared (first use in this function)
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:500:
error: 're' undeclared (first use in this function)
/usr/ports/security/php5-filter/work/php-5.3.2/ext/filter/logical_filters.c:501:
error: 'pcre_extra' undeclared (first use in this function)
*** Error code 1
1 error
*** Error code 1

Stop in /usr/ports/security/php5-filter.

===>>> make failed for security/php5-filter
===>>> Aborting update

===>>> Update for php5-filter-5.2.12 failed
===>>> Aborting update
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

istgt write errors

[David Newman]

On an 8.0-RELEASE/amd64 box, I used the net/istgt port to share iSCSI
targets. The installation succeeded, but I'm now seeing write errors
when using the targets:

Mar 16 15:10:26 bettini istgt[1202]: istgt_iscsi.c:
640:istgt_iscsi_write_pdu: ***ERROR*** iscsi_write() failed (errno=32)
Mar 16 15:10:2  6 bettini istgt[1202]:
istgt_iscsi.c:3038:istgt_iscsi_op_scsi: ***ERROR*** iscsi_write_pdu() failed
Mar 16 15:10:26 bettini istgt[1202]:
istgt_iscsi.c:3859:istgt_iscsi_execute: ***ERROR*** iscsi_op_scsi() failed
Mar 16 15:10:26 bettini istgt[1202]: istgt_iscsi.c:4337:worker:
***ERROR*** iscsi_execute() failed
Mar 16 15:10:30 bettini istgt[1202]: Login from 172.31.4.12
(172.31.4.22) on iqn.2010-04.com.example.bettini:bettini4 LU5
(172.31.4.5:3260,1), ISID=23d01, TSIH=4, CID=0, HeaderDigest=off,
DataDigest=off
Mar 16 15:12:10 bettini istgt[1202]: ABORT_TASK
Mar 16 15:14:15 bettini istgt[1202]: ABORT_TASK
Mar 16 15:16:04 bettini last message repeated 2 times

The istgt documentation doesn't offer any help in pinpointing a root
cause for the write errors.

Writes to these targets are extremely slow, too. In case it matters, the
target is a ZFS block device set up with 'zfs create -V 1T tank/bettini4'.

Thanks in advance for clues on the care and feeding of iSCSI on 8.0-RELEASE.

dn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

portmaster upgrade breaks cups-image

[David Newman]

8.0R amd64

Part of the upgrade process from 7.2R requires reinstalling all
third-party software, such as ports. I use portmaster for this,
following the nine-step procedure described in the EXAMPLES section of
the manpage.

During the upgrade, cups-image fails with the error shown below. A
temporary workaround is to disable CUPS support in ghostscript8 and
samba3, but I might want to use this box as a print server in the future.

Thanks in advance for clues on fixing this error.

Also, I believe this is the same issue as in this message:

http://is.gd/57iuU

dn

..

cc -L../cgi-bin -L../cups -L../filter -L../ppdc -L../scheduler
-L/usr/local/lib -Wl,-R/usr/local/lib  -pie -fPIE -Wall -Wno-format-y2k
-fPIC -Os -g -fstack-protector -o bannertops bannertops.o pstext.o
common.o -lcupsimage \
 -lcups   -pthread -lm -lcrypt
/usr/bin/ld: /usr/lib/crt1.o: relocation R_X86_64_32 can not be used
when making a shared object; recompile with -fPIC
/usr/lib/crt1.o: could not read symbols: Bad value
gmake[1]: *** [bannertops] Error 1
gmake[1]: Leaving directory
`/usr/ports/print/cups-image/work/cups-1.4.2/filter'
gmake: *** [all] Error 1
*** Error code 1

Stop in /usr/ports/print/cups-image.
*** Error code 1

Stop in /usr/ports/print/cups-image.

===>>> make failed for print/cups-image
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: libxcb won't compile from ports

[David Newman]

On 9/19/09 8:28 AM, Lowell Gilbert wrote:
> David Newman  writes:
> 
>> On 9/18/09 1:59 AM, Daniel Bye wrote:
>>> On Thu, Sep 17, 2009 at 09:35:55AM -0700, David Newman wrote:
>>>> On 9/17/09 8:10 AM, Daniel Bye wrote:
>>>>> On Thu, Sep 17, 2009 at 07:45:52AM -0700, David Newman wrote:
>>>>>> FreeBSD 7.2-RELEASE, i386
>>>>>>
>>>>>> Running 'make install clean' from /usr/ports/x11/libxcb returns the
>>>>>> patch error pasted below.
>>>>>>
>>>>>> Thanks in advance for clues on resolving this. I did not see anything
>>>>>> helpful in the archives or on Google.
>>>>> Try `make distclean' and then `make && make install'
>>>> This produced the same result. Thanks again for any additional clues in
>>>> resolving this error.
>>>>
>>>> dn
>>>>
>>>>
>>>> o# cd /usr/ports/x11/libxcb/
>>>> somehost# make distclean
>>>> ===>  Cleaning for libxcb-1.4
>>>> ===>  Deleting distfiles for libxcb-1.4
>>>> somehost# make && make install
>>>> ===>  Vulnerability check disabled, database not found
>>>> => libxcb-1.4.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.
>>>> => Attempting to fetch from http://xcb.freedesktop.org/dist/.
>>>> libxcb-1.4.tar.bz2100% of  298 kB   29 kBps
>>>> 00m00s
>>>> ===>  Extracting for libxcb-1.4
>>>> => MD5 Checksum OK for libxcb-1.4.tar.bz2.
>>>> => SHA256 Checksum OK for libxcb-1.4.tar.bz2.
>>>> ===>  Patching for libxcb-1.4
>>>> ===>  Applying FreeBSD patches for libxcb-1.4
>>>> 1 out of 1 hunks failed--saving rejects to src/xcb_auth.c.rej
>>>> => Patch patch-src-xcb_auth.c failed to apply cleanly.
>>>> => Patch(es) patch-Makefile.in applied cleanly.
>>>> *** Error code 1
>>>>
>>>> Stop in /usr/ports/x11/libxcb.
>>> Hmm... I don't have the file patch-src-xcb_auth.c in x11/libxcb/files.
>>> Is your ports tree up to date? Other than that, I'm afraid I'm out of ideas.
>> Me too. Same failure after updating ports.
> 
> That patch file was removed from the port *years* ago.  Remove the whole
> port and update it again (you must have updated -- incorrectly, somehow
> -- at some point to get stale patches with the current Makefile).

Thanks, this helped. Reinstalling ports cleared the issue.

thanks again

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: libxcb won't compile from ports

[David Newman]

On 9/18/09 1:59 AM, Daniel Bye wrote:
> On Thu, Sep 17, 2009 at 09:35:55AM -0700, David Newman wrote:
>> On 9/17/09 8:10 AM, Daniel Bye wrote:
>>> On Thu, Sep 17, 2009 at 07:45:52AM -0700, David Newman wrote:
>>>> FreeBSD 7.2-RELEASE, i386
>>>>
>>>> Running 'make install clean' from /usr/ports/x11/libxcb returns the
>>>> patch error pasted below.
>>>>
>>>> Thanks in advance for clues on resolving this. I did not see anything
>>>> helpful in the archives or on Google.
>>> Try `make distclean' and then `make && make install'
>> This produced the same result. Thanks again for any additional clues in
>> resolving this error.
>>
>> dn
>>
>>
>> o# cd /usr/ports/x11/libxcb/
>> somehost# make distclean
>> ===>  Cleaning for libxcb-1.4
>> ===>  Deleting distfiles for libxcb-1.4
>> somehost# make && make install
>> ===>  Vulnerability check disabled, database not found
>> => libxcb-1.4.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.
>> => Attempting to fetch from http://xcb.freedesktop.org/dist/.
>> libxcb-1.4.tar.bz2100% of  298 kB   29 kBps
>> 00m00s
>> ===>  Extracting for libxcb-1.4
>> => MD5 Checksum OK for libxcb-1.4.tar.bz2.
>> => SHA256 Checksum OK for libxcb-1.4.tar.bz2.
>> ===>  Patching for libxcb-1.4
>> ===>  Applying FreeBSD patches for libxcb-1.4
>> 1 out of 1 hunks failed--saving rejects to src/xcb_auth.c.rej
>> => Patch patch-src-xcb_auth.c failed to apply cleanly.
>> => Patch(es) patch-Makefile.in applied cleanly.
>> *** Error code 1
>>
>> Stop in /usr/ports/x11/libxcb.
> 
> Hmm... I don't have the file patch-src-xcb_auth.c in x11/libxcb/files.
> Is your ports tree up to date? Other than that, I'm afraid I'm out of ideas.

Me too. Same failure after updating ports.

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: libxcb won't compile from ports

[David Newman]

On 9/17/09 8:10 AM, Daniel Bye wrote:
> On Thu, Sep 17, 2009 at 07:45:52AM -0700, David Newman wrote:
>> FreeBSD 7.2-RELEASE, i386
>>
>> Running 'make install clean' from /usr/ports/x11/libxcb returns the
>> patch error pasted below.
>>
>> Thanks in advance for clues on resolving this. I did not see anything
>> helpful in the archives or on Google.
> 
> Try `make distclean' and then `make && make install'

This produced the same result. Thanks again for any additional clues in
resolving this error.

dn


o# cd /usr/ports/x11/libxcb/
somehost# make distclean
===>  Cleaning for libxcb-1.4
===>  Deleting distfiles for libxcb-1.4
somehost# make && make install
===>  Vulnerability check disabled, database not found
=> libxcb-1.4.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from http://xcb.freedesktop.org/dist/.
libxcb-1.4.tar.bz2100% of  298 kB   29 kBps
00m00s
===>  Extracting for libxcb-1.4
=> MD5 Checksum OK for libxcb-1.4.tar.bz2.
=> SHA256 Checksum OK for libxcb-1.4.tar.bz2.
===>  Patching for libxcb-1.4
===>  Applying FreeBSD patches for libxcb-1.4
1 out of 1 hunks failed--saving rejects to src/xcb_auth.c.rej
=> Patch patch-src-xcb_auth.c failed to apply cleanly.
=> Patch(es) patch-Makefile.in applied cleanly.
*** Error code 1

Stop in /usr/ports/x11/libxcb.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

libxcb won't compile from ports

[David Newman]

FreeBSD 7.2-RELEASE, i386

Running 'make install clean' from /usr/ports/x11/libxcb returns the
patch error pasted below.

Thanks in advance for clues on resolving this. I did not see anything
helpful in the archives or on Google.

dn


somehost# cd /usr/ports/x11/libxcb/
somehost# make clean
===>  Cleaning for libxcb-1.4
somehost# make install clean
===>  Vulnerability check disabled, database not found
===>  Extracting for libxcb-1.4
=> MD5 Checksum OK for libxcb-1.4.tar.bz2.
=> SHA256 Checksum OK for libxcb-1.4.tar.bz2.
===>  Patching for libxcb-1.4
===>  Applying FreeBSD patches for libxcb-1.4
1 out of 1 hunks failed--saving rejects to src/xcb_auth.c.rej
=> Patch patch-src-xcb_auth.c failed to apply cleanly.
=> Patch(es) patch-Makefile.in applied cleanly.
*** Error code 1

Stop in /usr/ports/x11/libxcb.


And here is /usr/ports/x11/libxcb/work/libxcb-1.4/src/xcb_auth.c.rej:

***
*** 251,257 

  info->namelen = memdup(&info->name, authptr->name,
authptr->name_length);
  if(info->namelen)
-   ret = compute_auth(info, authptr, sockname);
  if(!ret)
  {
free(info->name);
--- 251,262 

  info->namelen = memdup(&info->name, authptr->name,
authptr->name_length);
  if(info->namelen)
+ {
+ if (getsockname(fd, sockname, &socknamelen) == -1)
+ ret = 0;
+ else
+ ret = compute_auth(info, authptr, sockname);
+ }
  if(!ret)
  {
free(info->name);


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: recovering from a power outage

[David Newman]

On 2/13/09 7:22 AM, Robert Huff wrote:
> 
>>IMHO, if you are running a system where 'power outages' cannot
>>be tolerated, why not install a UPS, they are really quite
>>cheap, and be done with it? I cannot imagine any high end,
>>mission critical system not employing one.
> 
>   Power outages are not the only thing which can cause (directly
> or indirectly) file system corruption.

Hi, I'm the OP :-)

To that point, the system in question is attached to a 5000VA UPS. I did
something stupid with the UPS control software that caused an, er,
unscheduled shutdown. No UPS can help Mr. Fat Finger!

Thanks for all your replies.

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: recovering from a power outage

[David Newman]

On 2/12/09 4:41 PM, Jerry McAllister wrote:
> On Thu, Feb 12, 2009 at 04:06:49PM -0800, David Newman wrote:
> 
>> What's the canonical method for checking ufs file systems on a FreeBSD
>> 7.1/amd64 system after an unscheduled power outage?
> 
> How about fsck 

Right. I'm asking procedurally how that's invoked -- eg., do I need to
boot into single-user mode, what filesystem(s) do I mount and how, what
switches if any do I use with fsck and so on.

thanks!

dn


> 
> jerry
> 
> 
>> thanks
>>
>> dn
>>
>>
>> ___
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

recovering from a power outage

[David Newman]

What's the canonical method for checking ufs file systems on a FreeBSD
7.1/amd64 system after an unscheduled power outage?

thanks

dn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: updating php5-pcre

[David Newman]

On 12/12/08 1:08 AM, Mike Clarke wrote:

>   As of php 5.2.7, pcre extension is distributed with the core php5
>   package, and not as a standalone module anymore."

Thanks much. So, I can safely deinstall the php5-pcre port?

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

updating php5-pcre

[David Newman]

7.0-RELEASE-p6 / i386

Using portmaster to update the php5-pcre port returns this error:

Cannot find config.m4.
Make sure that you run '/usr/local/bin/phpize' in the top level source
directory of the module

I'm not a php guru. Where is the top-level source directory for this
module? Or is there some other remedy for this error?

thanks

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: keyboard!!

[David Newman]

On 7/31/08 2:02 PM, David Gurvich wrote:


So you have also been lusting after one of these keyboards?  Has anyone
actually ordered and used one of these and what is the opinion on them?


I can vouch for the Endurapro, which combines the buckling-spring feel 
of an old AT keyboard with a TrackPoint pointer and a USB connector:


http://pckeyboards.stores.yahoo.net/en104wh.html

The action is slower than on mushmatic keyboards that come with modern 
PCs, but that was always true.


Someone else asked about double-row keyboards like those for 3270 or 
5250 terminals; Unicomp sells those too:


http://pckeyboards.stores.yahoo.net/122keyterkey.html

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd-update says -p3, but i've got -p2

[David Newman]

On 7/19/08 9:50 AM, Matthew Seaman wrote:

Manolis Kiagias wrote:


This is not a problem with freebsd-update. The kernel has not changed
 between -p2 and -p3, so freebsd-update will not get you an updated
one. If you recompile the kernel afterwards, it will show -p3 because
of the change in /usr/src/sys/conf/newvers.sh (this changes everytime
 freebsd-update gets new updates, regardless of whether the kernel is
 updated or not). So, simply by recompiling the kernel you will get
the -p3 indication, though nothing much else in this case.


I had a thought the other day that it should be possible to to provide
the system patch level as data within a very small KLD module.  That way 
freebsd-update could change the value without having to supply a whole

new kernel and without having to reboot.


Something showing what's currently running would be a useful addition 
IMO. Yes, the user can grep /usr/src/sys/conf/newvers.sh to get the 
kernel patch level, but:


1. the user doesn't know if that patch level is currently installed and 
running; and


2. the user may not know version numbers for other pieces of code 
altered by freebsd-update. For example, someone else already pointed out 
that 'named -v' returns '9.4.2', the same version as before running 
freebsd-update.


Port maintenance tools such as portmaster and portupgrade indicate which 
version they're upgrading to; a similar facility in freebsd-update would 
be nice-to-have too.


thanks

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: freebsd-update says -p3, but i've got -p2

[David Newman]

Mark Boolootian wrote:



which leads me to conclude I've got -p3, including the BIND update.
However 'uname -a' says something else:

FreeBSD mumble.ucsc.edu 7.0-RELEASE-p2 FreeBSD 7.0-RELEASE-p2 #0: Wed 
Jun 18 07:33:20 UTC 2008 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386


And although /usr/sbin/named has been updated, it appears not to have
been upgraded:

$ /usr/sbin/named -v
BIND 9.4.2

Thoughts?

  


You've got p3, don't worry. There was no kernel update in p3, hence 
you got the p2 GENERIC kernel. If you want uname to actually show p3,

you will have to recompile your kernel


Shouldn't freebsd-update do this, not only for the kernel and named and 
whatever else it updates?


I'm relatively new to freebsd-update, and while I appreciate its speed 
advantange over make buildworld/buildkernel, it's confusing when it 
applies updates but does not display correct version numbers.


dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: log size handling

[David Newman]

On 7/17/08 7:10 AM, Matthew Seaman wrote:


 * Use the rotatelogs program that comes with Apache.  In this case,
   you replace the logging configuration statements in https.conf
   eg. instead of:

CustomLog "/var/log/httpd-access.log" combine

   you have:

CustomLog "|/usr/local/sbin/rotatelogs /var/log/httpd-access.log 
86400"


   which will create a new log file every 86400 seconds (= 1 day) and
   label each one with the unix time it was created appended to the
   name. eg:

   /var/log/httpd-access.log.1216252800

   That will change files at midnight UTC each day, which is fine
   if your server lives in the UK but not quite as convenient if your
   server is in Australia.


Yes. Apache's rotatelogs is a better choice than newsyslog. Under heavy 
load, the latter can corrupt Apache logs.


rotatelogs also can do changes based on log size, like this:

CustomLog "|/usr/local/sbin/rotatelogs/var/log/httpd-access.log 5M" \
combined

and if you don't like deciphering Unix epoch time, you can embed times 
in your log filenames like this:


CustomLog "|/usr/local/sbin/rotatelogs \
/var/log/httpd-access.log.%Y-%m-%d-%H_%M_%S 86400" combined

(n.b. I added the backslashes in the examples here; you want everything 
on a single line in your config file.)


dn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: upgrading a 6.3 box using portsnap and freebsd-update

[David Newman]

On 7/12/08 4:11 PM, David wrote:

So, and this worked for me, delete everything in the freebsd-update db 
directory, /var/db/freebsd-update.
It does involve re-downloading a lot of stuff. In hindsight, move the 
sub-directory "files" else where and then re-populate once it is working.


That didn't work for me. But editing /etc/freebsd-update.conf to change 
'update.FreeBSD.org' to 'update1.freebsd.org' did the trick.


Thanks for your response!

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: upgrading a 6.3 box using portsnap and freebsd-update

[David Newman]

On 7/12/08 9:55 AM, RW wrote:

On Sat, 12 Jul 2008 09:25:34 -0700
David Newman <[EMAIL PROTECTED]> wrote:

===>>> The textproc/p5-Text-ParseWords port has been deleted: Module 
included in

  core perl
===>>> Aborting update

Running "pkg_delete" reveals dependencies:

pkg_delete: package 'p5-Text-ParseWords-3.1' is required by these
other packages
and may not be deinstalled:
p5-ExtUtils-ParseXS-2.19
p5-Module-Build-0.28.08_2

How to remedy?


pkg_delete -f


Yes, that cleared the portsnap issue. Many thanks!

My remaining issue with with freebsd-update:

mail# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... none found.
Fetching public key from update.FreeBSD.org... failed.
No mirrors remaining, giving up.

Yet a FreeBSD-7.0 machine on the same subnet with an identical 
/etc/freebsd-update.conf file runs fine.


How to debug?

thanks again

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

upgrading a 6.3 box using portsnap and freebsd-update

[David Newman]

On a dual-CPU i386 box running FreeBSD 6.3, I'm having two issues with 
portsnap and freebsd-update:


1. After running "portsnap fetch" I then do "portmaster -L > 
portmaster.out" to see which ports need updating. But the output stops 
on one of the perl ports:


===>>> p5-Text-ParseWords-3.1

===>>> The textproc/p5-Text-ParseWords port has been deleted: Module 
included in

 core perl
===>>> Aborting update

Running "pkg_delete" reveals dependencies:

pkg_delete: package 'p5-Text-ParseWords-3.1' is required by these other 
packages

and may not be deinstalled:
p5-ExtUtils-ParseXS-2.19
p5-Module-Build-0.28.08_2

How to remedy?

2. freebsd-update fails to run:

mail# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... none found.
Fetching public key from update.FreeBSD.org... failed.
No mirrors remaining, giving up.

Yet a FreeBSD-7.0 machine with an identical /etc/freebsd-update.conf 
file runs fine.


How to debug?

Thanks in advances for clues on fixing either or both these issues.

dn

# uname -a

FreeBSD mail.networktest.com 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #1: 
Fri Feb 15 14:47:09 PST 2008 
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MYSMP  i386


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ntpd not starting at boot time

[David Newman]

On 4/24/08 7:47 AM, Daniel Bye wrote:


{
rc_flags="-c ${ntpd_config} ${ntpd_flags}"


You need to set ntpd_config to the path to your config file - as it is
now, you are also setting it in ntpd_flags, which the above line then
expands to something like this:

rc_flags="-c /path/in/ntpd_config -c /etc/ntp.conf"

So, remove it from your ntpd_flags definition and all should be well!



Bingo. Thanks!

dn

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ntpd not starting at boot time

[David Newman]

I've installed ntp-4.2.4p4 from ports on a FreeBSD 6.3/i386 system.

The ntpd process does not start at boot time. These lines exists in 
/etc/rc.conf:


ntpd_enable="YES"
ntpd_program="/usr/local/bin/ntpd"
ntpd_flags="-c /etc/ntp.conf -p /var/run/ntpd.pid"
ntpd_sync_on_start="YES"

Manually running '/etc/rc.d/ntpd start' produces this error:

Starting ntpd.
ERROR:  only one configfile option allowed

I've pasted the contents of ntp.conf and /etc/rc.d/ntpd files below.

Thanks in advance for clues as to what's missing.

dn



##
# BEGIN /etc/ntp.conf
##

server 127.127.26.0
fudge  127.127.26.0 time1 -0.949
server t1.timegps.net
server t2.timegps.net

restrict 207.181.8.128 mask 255.255.255.192 nomodify notrap

driftfile /var/db/ntp.drift

##
# END /etc/ntp.conf
##



##
# BEGIN /etc/rc.d/ntpd
##


# PROVIDE: ntpd
# REQUIRE: DAEMON ntpdate cleanvar devfs
# BEFORE:  LOGIN
# KEYWORD: nojail

. /etc/rc.subr

name=ntpd
rcvar=`set_rcvar`
#command="/usr/sbin/${name}"
command="/usr/local/bin/${name}"
pidfile="/var/run/${name}.pid"
start_precmd="ntpd_precmd"

load_rc_config $name

required_files="${ntpd_config}"

ntpd_precmd()
{
rc_flags="-c ${ntpd_config} ${ntpd_flags}"

if checkyesno ntpd_sync_on_start; then
rc_flags="-g $rc_flags"
fi

if [ -z "$ntpd_chrootdir" ]; then
return 0;
fi

# If running in a chroot cage, ensure that the appropriate files
# exist inside the cage, as well as helper symlinks into the cage
# from outside.
#
# As this is called after the is_running and required_dir checks
# are made in run_rc_command(), we can safely assume 
${ntpd_chrootdir}

# exists and ntpd isn't running at this point (unless forcestart
# is used).
#
if [ ! -c "${ntpd_chrootdir}/dev/clockctl" ]; then
rm -f "${ntpd_chrootdir}/dev/clockctl"
( cd /dev ; /bin/pax -rw -pe clockctl 
"${ntpd_chrootdir}/dev" )

fi
ln -fs "${ntpd_chrootdir}/var/db/ntp.drift" /var/db/ntp.drift

#   Change run_rc_commands()'s internal copy of $ntpd_flags
#
rc_flags="-u ntpd:ntpd -i ${ntpd_chrootdir} $rc_flags"
}

run_rc_command "$1"

##
# END /etc/rc.d/ntpd
##

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

error when patching cyrus-imapd-2.3.11 port

[David Newman]

Greetings. I'm building a cyrus-imapd 2.3.11 server from ports on 
FreeBSD 7.0/i386. I'm also using these two University of Athens patches:


http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.11/cyrus-imapd-2.3.11-autocreate-0.10-0.diff

http://email.uoa.gr/download/cyrus/cyrus-imapd-2.3.11/cyrus-imapd-2.3.11-autosieve-0.6.0.diff

The following steps produced the error output pasted below. Thanks in 
advance for any help in debugging and fixing this.


cd /usr/ports/mail/cyrus-imapd23/
make patch
cd work/cyrus-imapd-2.3.11/
patch -p1 < ~/cyrus-imapd-2.3.11-autocreate-0.10-0.diff
patch -p1 < ~/cyrus-imapd-2.3.11-autosieve-0.6.0.diff
cd ../..
make



cc -L/usr/lib -R/usr/lib -L/usr/local/lib -R/usr/local/lib
-rpath=/usr/lib:/usr/local/lib -o imapd  ../master/service.o pushstats.o
imapd.o proxy.o imap_proxy.o index.o version.o mutex_fake.o  libimap.a
../lib/libcyrus.a ../lib/libcyrus_min.a -L/usr/local/lib
-R/usr/local/lib -lsasl2  -lgssapi -lkrb5 -lasn1 -lroken -lcrypt
-lcom_err  -lfl   -L/usr/local/lib  -R/usr/local/lib -ldb41 -lssl
-lcrypto -lmd ../com_err/et/libcom_err.a -lwrap
libimap.a(autosieve.o)(.text+0x598): In function `autoadd_sieve':
: undefined reference to `sieve_interp_alloc'
libimap.a(autosieve.o)(.text+0x77f): In function `autoadd_sieve':
: undefined reference to `sieve_register_redirect'



*** Error code 1

Stop in /usr/ports/mail/cyrus-imapd23/work/cyrus-imapd-2.3.11/imap.

I emailed the author of the patches, and he replied:

"This is a bit of a known issue. The FreeBSD ports system changes the 
Makefiles for their own build system, and the autocreate patch has to 
change the makefiles since the sieve libraries are needed also in other 
places (because of the autocreate functionality).  If you follow the 
normal patch procedure and you add the autocreate patch in the patches 
that are in the ports build system, then the autocreate patch will not 
be applied successfully since there will be conflicts in the makefiles 
again.  (The rules apply also to autosieve if i remember correctly).


 Unfortunately i don't have a freeBSD system at hand to see the changed 
that are needed (which are not backward compatible with the vanilla 
cyrus distribution), and it is quite hard for us to produce different 
patches for different operating systems. (that's why we have all the uoa 
patches against the vanilla cyrus distribution)."


I'm reluctant to build from the cyrus-imapd sources as I don't know 
enough about possible differences in file locations (and maybe code?) 
between the two distributions. Ports would be much better for me, 
provided I can correct the missing library reference.


Again, thanks for any help in debugging this.

dn


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: source upgrade from 6.3 -> 7.0 fails SOLVED

[David Newman]

>>1. cd /usr/src
>>
>>2. cvsup -g -L 2 /usr/local/etc/security-supfile (tag points to
>> RELENG_7_0)
>>
>>3. make buildworld
>>

..

>>10. make installworld
>>
>>and get this error:
>>
>>install: crt1.o: No such file or directory
>>***Error code 71
>>
>>crt1.o does exist in /usr/lib.
>>
>>Thanks in advance for any clues on fixing this upgrade.
>>
>>dn
>>
>>
>
> I had a similar problem with one server I upgraded this way too.  I was
> running the 7.0 kernel with 6.3 world.  I rebuilt world after cleaning
> everything and the next installworld went fine.

Thanks, that was the problem. After running "make clean" before "make
buildworld" the rest of the steps completed successfully.

Many thanks!

dn




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

source upgrade from 6.3 -> 7.0 fails

[David Newman]

Having trouble upgrading 6.3 to 7.0 from source. This is on a single-CPU
amd64 machine.

These steps all work OK:

1. cd /usr/src

2. cvsup -g -L 2 /usr/local/etc/security-supfile (tag points to RELENG_7_0)

3. make buildworld

4. make buildkernel KERNCONF=GENERIC

5. make installkernel KERNCONF=GENERIC

6. reboot to single-user mode

7. mount -u /

8. mount -a

9. mergemaster -p

But then I do:

10. make installworld

and get this error:

install: crt1.o: No such file or directory
***Error code 71

crt1.o does exist in /usr/lib.

Thanks in advance for any clues on fixing this upgrade.

dn





___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

preserving device symlinks across reboots

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

To use ntpd with an HP GPS receiver on RELENG-6.2, I have a symlink from
the first serial port to the HP GPS device:

somehost# ls -l /dev/hpgps0
lrwxr-xr-x  1 root  wheel  10 Dec  1 21:06 /dev/hpgps0 -> /dev/cuad0

This works fine since the GPS receiver is attached to cuad0.

Problem is, this symlink disappears whenever a reboot is needed, for
example after patching the kernel.

How best to preserve the symlink across reboots? I created an rc.local
file making a new symlink, but maybe there's a better way.

thanks

dn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFHXiTvyPxGVjntI4IRAtEZAKDyOsiRL1ilB3yUwGGH79IeZ65l6QCgrc2V
OfqdzIvR9ua1kVtD+bdCzRc=
=pfFP
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dealing with a failing drive

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/25/07 9:08 PM, Ted Mittelstaedt wrote:

> There are two physical disks in the server.  bus 1 target 0 and
> bus 1 target 1.  Those ARE the physical disks.  If one of them
> has failed instead of:
> 
>  Sync, Ultra2, Wide - Configured in a logical volume.
> 
> you will see something like:
> 
>  Sync, Ultra2, Wide - Unconfigured
> 
> or nothing at all.

Cool, thanks. Your output and mine are virtually identical.

Now I get what you mean by running idacontrol periodically and grokking
the output to verify both disks are still in the array.

> 
> It is normal for idacontrol to generate soft write errors.  The
> developer knows about this.  There's really no easy way to make
> it not happen.  It doesen't hurt anything, however.

OK, good to know.

thanks much!

dn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFHSlXUyPxGVjntI4IRAlbxAJ0aZDSOeyrTIoEVtKOZd5UMbDMx9QCdHP8I
TAh9zWa+2cUlE5Qh2qfks2Y=
=iEK3
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dealing with a failing drive

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/24/07 12:39 PM, Ted Mittelstaedt wrote:
> The output of idacontrol show will show if one of the
> hard disks in the SmartArray has failed.  Your choice with
> a hardware array is to either run it with redundancy or not.
> (ie: raid5 or mirroring or striping)  You have to choose 
> which is more important for you.
> 
> IMHO it is very foolish to stripe an array that you have
> critical data on and assume that you can predict a failure
> of a disk using smart or other monitoring, and replace it
> in advance of a failure.  If your concern is redundancy, then
> add more disks to the array and create a raid 5 or a mirror.
> Then ignore all the predictive junk and let the array card
> concern itself with detecting if a drive has failed.  Run
> idacontrol periodically out of a script that checks for a
> failure of a disk and e-mails you if there is one.

Thanks, this is good advice, but it doesn't answer the specific
questions I had:

1. How to diagnose the health of a *physical* disk that's part of a RAID
array (RAID1, in this case) in an old Compaq Proliant server?

2. Is it normal for idacontrol to generate soft write errors?

Backstory here is that Proliant server #1 generated beaucoup hard and
soft read and write errors and eventually locked up. I thought it was
one of the disks but replacing one at a time didn't help. So I took both
disks and put them in identical Proliant server #2. Ergo, I would
conclude server #1's RAID controller flaked out.

idacontrol is useful for telling the health of the logical disk. What it
doesn't tell me (or maybe I just don't see it) is whether the physical
disks are ok, and those "soft write errors" concern me. I had a failure
situation, and need to figure out whether just the controller was bad or
whether I need to replace at least one disk too.

Thanks again!

dn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFHSf39yPxGVjntI4IRAp1yAJ4vMV9FkeaBsHRr/Z5WpCL27wJ3tACfS+pT
3UVlscnQUZhe8ulHksKDWsY=
=Om7/
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dealing with a failing drive

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/18/07 11:30 PM, Ted Mittelstaedt wrote:

> idacontrol show | grep "Status"
> 
> IF status is fully up it will say:
> 
> Status: Logical drive ok

And that's what it does say. So far so good...

...but then each time I run idacontrol I get this in /var/log/messages:

Nov 21 17:01:30 mail kernel: ida0: soft error
Nov 21 17:01:36 mail last message repeated 59 times

Does this mean the controller is OK and the disks are dying? Or is it
expected behavior with idacontrol? Or something else?

thanks

dn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFHRNeLyPxGVjntI4IRAkigAJ41KeUVpDfNab6f/F/eHcSCrJLMrwCdHLos
eYOqGGn8K3RV1l/okGwuYp4=
=U4Tx
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dealing with a failing drive

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/18/07 11:30 PM, Ted Mittelstaedt wrote:
> Hi David,  apologies to Jerry for jumping in.
> 
> Compaq uses several RAID cards most are under the so-called
> "SmartArray" using the ida driver.  If this is yours, you can
> use a utility called "idacontrol" that can monitor the array,

Hi Ted,

Thanks much for this info. I'm pleased to report that idacontrol thinks
the logical array is in good shape. (This is on an identical server; I
moved both disks from a RAID1 array there after the first server started
reporting write and read errors.)


> NOTE:
> 
> The smart utility only works on SATA or ATA/IDE drives, not SCSI.

Yes. I've heard it said that "SMART isn't."

This Proliant DL320 server uses a SmartArray controller and SCSI disks.
SMART or not, is there a way of monitoring the health of the physical
disks from within FreeBSD?

thanks again!

dn



-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFHQb1WyPxGVjntI4IRAhZwAKCzS4yKRyeJZDXm2pq+aIL8VMBKQQCfUpq3
+eThP189Kav2DSRVAgDdbDI=
=coqi
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dealing with a failing drive

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/12/07 8:14 AM, Jerry McAllister wrote:

> An update: After doing what you suggest (leaving in the "good" disk,
> adding a new disk, RAID rebuilding) I still got soft write errors --
> with *either one* of the disks I tried.
> 
> Then I tried putting both disks in an identical server and they came up
> fine, no read or write errors.
> 
> Ergo, the bad RAID controller is bad and the disks may be OK.
> 
>> Probably not.
>> Generally, if the RAID controller is bad, you will see errors
>> all over and not it just one place, tho I suppose it is possible.
>> Check and see what it reports as error locations and see if they
>> move around any.

Jerry, thanks for your response.

After 36 hours of running the same disks in a different, identical
machine there hasn't been a single read or write error. I'm hardly a
storage expert but from the evidence I have I'm inclined to believe the
root cause was a bad RAID controller and not failed disks.

I'm aware of CLI tools to monitor 3Ware SATA RAID controllers. Anyone
know if there are similar tools for HP/Compaq SCSI RAID controllers?

thanks

dn
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFHOIzOyPxGVjntI4IRAmMWAJ4grMR6mcL/j9qbcGY/fJfDEqv3KgCg8BVW
wcHVDkZPykFcQzVYnp8mx+g=
=8rws
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: dealing with a failing drive

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 11/10/07 9:09 PM, Modulok wrote:
>>> I'd welcome suggestions on how (or whether) to try to revive a SCSI
> drive that's failing.
> 
> It depends on how valuable the data on the array is, and more
> importantly, how much funding you have at your disposal to fix the
> problem. If it were me, I would set aside the bad disk, connect a new
> disk to the card and re-synchronize the array. (Assuming one of the
> members still retains a good copy of the data.) Afterwards I would
> destroy, or toss the existing disk in the trash can (depending on the
> sensitivity of the data stored on it.)

Thanks for your reply.

An update: After doing what you suggest (leaving in the "good" disk,
adding a new disk, RAID rebuilding) I still got soft write errors --
with *either one* of the disks I tried.

Then I tried putting both disks in an identical server and they came up
fine, no read or write errors.

Ergo, the bad RAID controller is bad and the disks may be OK.

>>> Is there some other way to:
>>> b)monitor the health of disks on a Compaq controller so it doesn't
> get to this point to begin with?
> 
> There are various tools out there that attempt to 'monitor' the
> condition of disk drives to try and predict when failure is eminent.
> For valuable data, it is safer to setup a mirror and simply toss out
> bad disks as they fail. For extremely valuable data use a 3 disk
> array. With a 3 disk setup you will still be covered in the event that
> an additional disk craps out during the re-sync.
> 
> To quote google's article on disk failure, regarding SMART:

Right, I've heard it said that "SMART isn't."

Nonetheless, I'd appreciate any suggestions to monitor the health of
disks -- and RAID controllers too -- on HP Proliant servers running FreeBSD.

thanks again.

dn


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFHNyZDyPxGVjntI4IRAqk1AKCUwByNOAJZwvtD9V21TZfyaMWaxgCdFSCZ
dZjf3ynK+4OffBzsDOawF9A=
=DUqc
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

dealing with a failing drive

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I'd welcome suggestions on how (or whether) to try to revive a SCSI
drive that's failing.

This is on FreeBSD 6.2-RELENG on a Compaq Proliant DL320, onboard RAID
and two SCSI drives in a RAID1 array.

Today this system rebooted and hung on Compaq's "what do you want the
RAID controller to do?" message. I told it to fix any errors.

When I brought the system back up (after running fsck in single-user
mode), the log had lots of errors like this:

Nov 10 09:00:40 mail kernel: ida0: hard write error
Nov 10 09:00:40 mail kernel: ida0: invalid request
Nov 10 09:01:48 mail last message repeated 35 times
Nov 10 09:03:49 mail last message repeated 571 times
Nov 10 09:12:27 mail last message repeated 796 times

I vaguely remember trying about a year ago to load a SMART utility from
the ports collection but it wouldn't work on drives in a RAID array.

Is there some other way to:

a) diagnose/fix the errant disk here?
b) monitor the health of disks on a Compaq controller so it doesn't get
to this point to begin with?

thanks in advance

dn





-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFHNlk+yPxGVjntI4IRAntlAJ9FWA2ez+BdnViq7mrIpkLBTLm/CgCfRyEA
czDvMn6+8KjlI3V0iBG4U3I=
=36+k
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: replicating /etc/passwd on a failover machine

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/20/06 9:06 AM, Kirk Strauser wrote:
> On Wednesday 20 December 2006 10:28 am, stas khromoy wrote:
> 
>> i doubt that just copying over /etc/passwd and master.passwd will work .
> 
> You'd also need to pick up /etc/{s,}pwd.db - the compiled versions of those 
> files.

Dunno if this works on FreeBSD, but with OpenBSD I have successfully
copied accounts between machines like this:

1. Run vipw on both machines and copy and paste the user accounts. vipw
works like vi.

Note that this step assumes the same environment exists on the source
and destination machines. If, for example, a user's shell is bash on the
source machine, then /usr/local/bin/bash must exist on the destination
box as well.

2. Copy and paste the relevant user groups from /etc/group. If users are
members of other groups (e.g., wheel), ensure that info matches as well.

3. On the source machine, run:

rsync -avz /home// destination_machine:/home

This will move username's home directory over, preserving ownership and
permissions for all directories and files. Note the trailing slash on
the source directory.

This probably needs to be run as root, which means that at least
temporarily you need to go into the destination machine's
/etc/ssh/sshd_config and add this line:

PermitRootLogin yes

and then restart sshd like this:

kill -HUP `cat /var/run/sshd.pid`

If you don't normally want ssh access for root, be sure to undo that
change in sshd_config once you're done.

dn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFiX6hyPxGVjntI4IRAs6PAKCk1YP2cKYWx70NxU5ZiOQyFtgHLACffFIH
27pgxgkQ+CYOaBJWD3n/2MQ=
=nMBm
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: small mail server

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/20/06 6:47 AM, Robin Becker wrote:
> Jeff Palmer wrote:
>> At 06:23 AM 12/20/2006, you wrote:
> 
>>
>> Robin,
>>
>> I've had much success with the following guide.
>> http://www.thekeyboardcowboys.org/help/fbsd_postfix/FreeBSD_Postfix.html
>>
>> It mentions everything you have above, with SMTP AUTH (you don't have
>> to check mail before sending)
>>
>>
>> Hope it helps,
> ...
> I've heard lots about Postfix, but have never used it. Since the box is
> currently only using sendmail for outgoing stuff I guess it shouln't be
> too much of a pain to try it out. I've actually been considering using a
> jail to do this so it should be fairly easy to do.

In my experience Postfix is simpler to administer than Sendmail, but it
really depends on what you're familiar with.

This might be overkill for your needs, but here's a useful guide to
setting up Postfix and Squirrelmail for virtual domains:

http://www.wistful.net/wiki/Ed's_FreeBSD_Virtual_Mail_How-To

There are similar howtos for exim and qmail but I haven't tried these:

http://www.tty1.net/virtual_domains_en.html
http://freebsd.qmailrocks.org/

dn


-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFiVZ1yPxGVjntI4IRAvpAAJ9tPgFYqfvreipTy4kYeqrOmvTuJwCeI7ca
x8x53/8kZ2NwFnXwJbsj78s=
=1j9T
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD as VM host OS?

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/18/06 8:32 AM, James Seward wrote:
> On 12/18/06, David Newman <[EMAIL PROTECTED]> wrote:
>> "You really need  as the host OS" is a perfectly valid
>> response too.
> 
> I run VMware Server on Ubuntu (one of the supported Linux host
> flavours, and the only one I'm prepared to put up with), hosting
> currently two Windows Server 2003 and two FreeBSD 6.x VMs on a Dell
> 1855 blade. While I haven't performed any benchmarks (benchmarks
> inside a VM are tricky to get right) I can report no noticable
> performance problems with the workload the machines have to handle.
> 
> The Windows machines are a small fileserver and a WSUS server; the
> FreeBSD machines are performing spam-assassination and NFS serving.
> 
> vmware1$ uptime
> 16:27:45 up 66 days,  5:17,  1 user,  load average: 0.27, 0.56, 0.54
> 
> I have a FreeBSD-based PXE server running in Workstation 5.5 on my
> desktop, and
> have had success running FreeBSD 4.x under ESX Server 2.5.x in a
> previous life.
> 

Thanks very much. I too have run FreeBSD as a guest OS under various
VMware flavors for years.

My question is whether FreeBSD is a suitable _host_ OS for any virtual
machine environment, preferably with support for SMP, amd64, and guest
OS speed at or close to native hardware speeds.

Thanks again!

dn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFhs3zyPxGVjntI4IRAnPAAKDxgpRIKN+s0anO6Ct8MOdf86Kh6ACeN0N+
6qknCmjZWaC0KSeRW0W2SsI=
=HIuy
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD as VM host OS?

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

This page compares various virtual machines:

http://en.wikipedia.org/wiki/Comparison_of_virtual_machines

Unfortunately it appears very few support FreeBSD as a host OS.

I would greatly appreciate advice, anecdotes, or cautionary tales of any
VMs that:

- - run on FreeBSD (amd64 or x86) as a host OS

- - run *nix guest OSs at or near native speed

"You really need  as the host OS" is a perfectly valid
response too.

many thanks

dn

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFFhq3ByPxGVjntI4IRAvENAJ93JI5Zns7A8oNc1mycw+fBxKwjcQCgsrVr
/AONY77fYle3qJcFr3/WAaA=
=4ZLr
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

accessing BIOS and RAID info on old Compaqs

[David Newman]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Greetings. For FBSD 6.1 on old Compaq DL320 and 1850R machines:

1. Is there a way to access the system BIOS, either at boot time or
(preferably) from within FBSD? I'm specifically interested in seeing
what the system's hardware clock is set to.

2. Is there a way to monitor the Compaq Smart Array RAID controllers and
disks attached to them from within FBSD?

Smartmontools is great for monitoring disk health, but no good with
RAID. I don't have Compaq RAID CDs for all the machines in question, and
in any event would prefer to monitor disks from within FBSD if possible.

thanks

dn
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)

iD8DBQFFRYXZyPxGVjntI4IRAj/rAKDIL+4dEO5boLCyyaSVRjrjiTaHlgCgxz5V
3Tdj/TWe0id1B0MLwwUEITI=
=2zec
-END PGP SIGNATURE-
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

umount/mount with HighPoint RocketRaid 1820A

[David Newman]

Greetings. I am using a HighPoint RocketRAID 1820A controller with 
FreeBSD 6.0-RELENG and the hptmv driver.


Six of the eight drives connected to the 1820A are in a RAID5 array. The
other two drives are mounted as single devices, not part of any array. I 
am using these two drives as backup volumes.


I can successfully umount one of the single drives, remove the drive, 
and insert a new drive:


# umount /backup2
#

from /var/log/messages:
Mar  1 08:38:32 lance kernel: hptmv: Device removed: controller 1 channel 7
Mar  1 08:39:00 lance kernel: RR182x [0,7]: channel started successfully

However, I  cannot remount the new drive, even though it is already
formatted:

# mount -o rw -t ufs /dev/da2s1d /backup2
mount: /dev/da2s1d: Input/output error

I then tried using fdisk and label from sysinstall, but neither let me 
write changes to the new drive.


The only sure way I've found to swap and remount single drives is with a 
reboot. Is there another method that doesn't require a reboot?


Thanks!

dn
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: windows

[David Newman]

> can i install freebsd on a compaq presario 5020 i
> have windows 2000 exec. on it now but would like to
> change if i can 

I am not familiar with the presario 5020 but I have
had great success installing FBSD on a variety of
older Compaq machines.

/wsbs




__ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

updating system version of OpenSSH

[David Newman]

What is the procedure for patching/updating system
version of OpenSSH on an FBSD 5.2.1 box?

I used the excellent Rootkit Hunter security
assessment tool:

http://www.rootkit.nl/projects/rootkit_hunter.html

and it found that I'm running OpenSSH 3.6.1p1, which
has at least one vulnerability.

I only know how to install/upgrade from ports. OpenSSH
is part of the ports collection, but the build I'm
running was included with the OS. 

What's the right way to proceed here?

thanks

/wsbs





__ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more.
http://info.mail.yahoo.com/mail_250
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: partition full, recreating a tape device

[David Newman]

On Wed, 24 Nov 2004, Dan Nelson wrote:
1. /dev/nsa1 shows up as a regular device; and
2. /dev/nsa1 doesn't fill up the filesystem
Remove /dev/nsa1, and run ./MAKEDEV sa1, which will recreate all the
device nodes for sa1, including nsa1.
Worked like a charm. Thanks for your speedy reply!
dn
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

partition full, recreating a tape device

[David Newman]

Greetings. This is regarding a FSBD 4.10-RELEASE system.
df -h shows the root file system is 109 percent utilized:
Filesystem  Size   Used  Avail Capacity  Mounted on
/dev/aacd0s1a   126M   126M  -9.9M   109%/
The culprit is a rewindable tape drive in /dev. It shows up as an ordinary 
file, not as a device (like the nonrewindable device, /dev/nsa1):

-rw-r--r--  1 root  wheel  83046400 Nov 20 01:02 /dev/nsa1
crw-r-  1 root  wheel   14,  16 Nov 24 05:50 /dev/rsa1
Question: How do I correct this so that:
1. /dev/nsa1 shows up as a regular device; and
2. /dev/nsa1 doesn't fill up the filesystem
Many thanks.
Regards,
David Newman
Network Test

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"