From owner-freebsd-questions@FreeBSD.ORG Sun Oct 22 11:44:42 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 633F716A407 for ; Sun, 22 Oct 2006 11:44:42 +0000 (UTC) (envelope-from mpope@teksavvy.com) Received: from ironport-out.pppoe.ca (ironport-out.pppoe.ca [206.248.154.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC30043D46 for ; Sun, 22 Oct 2006 11:44:41 +0000 (GMT) (envelope-from mpope@teksavvy.com) Received: from smtp.pppoe.ca ([65.39.192.132]) by ironport-out.pppoe.ca with ESMTP; 22 Oct 2006 07:44:41 -0400 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.09,339,1157342400"; d="scan'208"; a="49162871:sNHT21461774" Received: from [10.1.1.173] ([69.28.228.189]) by smtp.pppoe.ca (Internet Mail Server v1.0) with ESMTP id AVO62740 for ; Sun, 22 Oct 2006 07:44:40 -0400 Message-ID: <453B5A1A.8000804@teksavvy.com> Date: Sun, 22 Oct 2006 07:46:34 -0400 From: Matthew Pope User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <453B4ACD.1070802@teksavvy.com> In-Reply-To: <453B4ACD.1070802@teksavvy.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: problems after rebuild of 5.5 stable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Oct 2006 11:44:42 -0000 Added to my original problem description the full list of WARNING messages from boot: BTW, my FreeBSD 5.5 is running on a Pentium 4/2.4 GHz, 512 M RAM, Asus mother board, oodles of disk Matthew Pope wrote: > Hello, > I have a bit of grey hair, but I've been blessed with working with > FreeBSD gurus so much that I am struggling to run my own domain and > webserver. That is I have have been co-dependant upon FreeBSD gurus in > the past, so I was lazy. I'm now on my own and finding that > administering a UNIX system based domain and webserver is rewarding, > but requires a lot of technical knowledge. > > The root of my problem was my 5.4 based system was running out of > sockets due to a close early problem, and a problem description I read > in the mailing lists did describe something very close, for which the > discoverer of the problem provided a patch. Rather than patch, I > thought it that since it's been a year, it was time to rebuild the > kernel with the latest STABLE release. So I did the rebuild as > instructed in the FreeBSD Handbook. Now I'm up to 5-5 STABLE using a > default kernel Generic i386 version. > > The mergemaster step following the rebuild and reboot took me for a > ride. Rather I rode free and easy not quite sure what I was doing. I > was not sure exactly which file to go with, and I tended to choose t > for temp file for many of the prompts. Now my 5.5 kernel boots, but > there are a number of messages of the form: > source_rc_confs: not found > $ipnat_enable is not set properly - see rc.conf(5) > $ipfs_enable is not set properly - see rc.conf(5) same message as above but with these additional var names: $harvest_ethernet $harvest_p_to_p $start_vinum $background_fsck $ip6addrctl_enable $atm_enable $ipv6_firewall_enable $ipv6_enable $svr4_enable $sysvipc_enable $mroutedbd_enable $ipv6_router_enable $mrouted_enable $router_enable $syslogd_enable $nfs_server_enable $rpc_statd_enable $rpc_lockd_enable $pflog_enable $pf_enable $pppoed_enable $virecover_enable $rpcbind_enable $nis_ypxfrd_enable $nis_server_enable $rpc_ypupdated_enable $nis_client_enable $nis_ypset_enable $nis_yppasswdd_enable $accounting_enable $pflog_enable $cron_enable $jail_enable $inetd_enable $cron_dst $kadmind5_server_enable $keyserv_enable $kpasswdd_server_enable $ldconfig_insecure $enable_quotas $mountd_enable $watchdogd_enable $ugidfw_enable $timed_enable $bootparamd_enable $hcsecd_enable $lpd_enable # > etc.... > > My rc.conf includes: > routed_enable="YES" > router="/sbin/routed" > defaultrouter="10.1.1.1" > > I later read in the mailing list that someone had a simliar problem > and solved it by re-running the mergemaster step. I tried that too, > and this time I selected answer to all the prompts about > conflicts. I rebooted, but I still cannot even ping my gateway, as > I'm getting "no route to host". > > I tried starting routed manually, but still no routes were > discovered. I also tried inserting a subroutine into rc.subr that > called source_rc_confs that did source the rc.confs, and it is called > during boot I see from /var/messages. But alas this is a desperate > measure, there must be something I can do to fix this problem without > meddling in rc.subr. So my routing is down, which means my dns is > down, and most definetely my httpd is down. > > Any help in debugging, resolving this poorly executed upgrade would be > very welcome. > Thanks, > Matthew > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" >