Re: Problem with freebsd-update on 7.3-RELEASE

[Brian DeFreitas]

Konstantin Vasilyev wrote:
 Hi all!
 
 I have installed
 %uname -a
 FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4 #3:
 Tue Jan 25 19:19:34 MSK 2011
 kvasi...@ota2.cellnetrix.com:/usr/obj/usr/src/sys/GENERIC  i386
 
 I have
 @dailyfreebsd-update cron
 in root's crontab.
 
 Why does freebsd-update mail me the following?
[...]
 Who can give me ideas what's happening?

Have you checked the man page for freebsd-update(8) ?

cron Sleep a random amount of time between 1 and 3600 seconds,
 then download updates as if the fetch command was used.  If
 updates are downloaded, an email will be sent (to root or a
 different address if specified via the -t option or in the
 configuration file).

Sounds exactly like the expected behavior to me.

So, the cron subcommand only does the 'fetch' part of freebsd-update.
You'll still need to run 'freebsd-update install' to actually install
the updates.

___
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: Problem with freebsd-update on 7.3-RELEASE

[Brian DeFreitas]

Konstantin Vasilyev wrote:
 I know about how freedsd-update work.
 I use for a long time.
 But I don't understand why is freebsd-update going to update
  FreeBSD ota2.cellnetrix.com 7.3-RELEASE-p4 FreeBSD 7.3-RELEASE-p4
 to
  The following files will be updated as part of updating to 
  7.3-RELEASE-p4:...

Ah, I see the problem now. 

The only thing I can think of is that your kernel and world might be out
of sync, but if you're used to freebsd-update that seems unlikely.

What's the output of 'freebsd-update IDS' ? I've had luck running that
to see what freebsd-update thinks is going on with the system.

___
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

Stability issues after upgrading to 7.1 - NFS related?

[Brian DeFreitas]

Hello all,

We recently upgraded an NFS server from 7.0-p6 to 7.1-p6.  The following
Monday morning, we found the server's networking to be wedged, and
console error messages that strongly resemble this post [1].

In an effort to try the mentioned fixes, we upgraded to 7-STABLE. This
did not seem to help matters; the NFS server keeps wedging 1-2x a
day, requiring soft reboots (via console) at times and hard reboots at
others. Heavy NFS load seems to trigger everything.

Initially, we thought there might be a problem with rpc.statd because
we started seeing RPC: Port mapper failure - RPC : Timed out messages.
All the hosts that timed out were previously-working Linux (CentOS) NFS
clients.

We have IPsec configured in transport mode between all FreeBSD and Linux
NFS clients, but only see the RPC error for CentOS (not RHEL) hosts,
(and no errors from FreeBSD clients). Before the system wedges
completely, `top` reports that most nfsd processes are in the *ipsec
state.

These are all the troubleshooting steps we have taken:

- disabled NFS locking on the Linux NFS clients
- RPC timed out messages still appear

- set up RPC to use static ports for NFS on our CentOS clients
  (to work better with our firewalls, which needed no such
  rules before)
- RPC timed out messages still appear

- added 'rpc_lockd_enable=NO' to /etc/rc.conf
- after rebooting, `rpcinfo -p` showed no lock manager running,
  but the crashes persisted

- added nooptions NFSLOCKD to the kernel configuration
- this only caused things to crash faster (few minutes after
  boot, with very little NFS load)

Unfortunately, one of the issues we've run into in debugging this
problem is the lack of useful logs and debugging information. Some info
we have managed to gather:

- before one reboot, we noticed console messages about mbuf's
  filling up.  Running `netstat -m` right before crashes seems to
  confirm this.

If anyone could provide some insight into what's happening, or help
us get more debugging information, it would be very helpful.

[1] http://lists.freebsd.org/pipermail/freebsd-current/2009-May/006434.html

-- 
Brian DeFreitas
Lead Unix Systems Administrator
Network Infrastructure, RSSP-IT
UC Berkeley


pgpW3JBwvnLhZ.pgp
Description: PGP signature