Re: problems after rebuild of 5.5 stable
On 10/23/06, Matthew Pope [EMAIL PROTECTED] wrote: # ifconfig sis0 add 10.1.1.99 This put me back in touch with the world on this server. Now I can cvsup to a production 'Release' version of FreeBSD, and rebuild all. Will tag=RELENG_6_1 for cvsup be the latest 'Release' then of FreeBSD, not stable, nor current, but Release? i'd rather start from scratch (back up /etc /usr/local/etc and /usr/home and anything else you need) my FreeBSD 6.1 mailserver-settings : relevant part of ports-supfile : *default host=cvsup6.nl.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=. *default delete use-rel-suffix relevant part of standard-supfile : *default host=cvsup3.nl.FreeBSD.org *default base=/var/db *default prefix=/usr *default release=cvs tag=RELENG_6_1 *default delete use-rel-suffix relevant uname -a output : FreeBSD 6.1-RELEASE-p10 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems after rebuild of 5.5 stable
Matthew Pope [EMAIL PROTECTED] writes: Lowell Gilbert wrote: Go back through mergemaster, and actually pay attention to the changes. On files you haven't modified, you will be able to (i)nstall the new versions of those files, but otherwise you will need to (m)erge them. Ok, I tried that but my system is to far gone. Close to 100 environment vars are missing and if I jam them all into rc.conf it will be a mess, especially since I would be guessing at the appropriate values for the vars. Most of those variables should be in /etc/defaults, which you should never modify on your own. Synch up that directory, and you'll be a long way towards fixed up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
problems after rebuild of 5.5 stable
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) 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 default 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 [EMAIL PROTECTED]
Re: problems after rebuild of 5.5 stable
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 default 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 [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems after rebuild of 5.5 stable
On 10/22/06, Matthew Pope [EMAIL PROTECTED] wrote: 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. -- cut -- 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 default 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. can you describe the setup, like is the domain/webserver in the LAN or connected to a separate NIC ? do you really need to use routed ? are you using firewall-software on that machine or any ping-related settings in rc.conf ? what's the output of netstat -r ? what about the ping-ability of your gateway before ? was it pingable ? or does it have ping-replies disabled ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems after rebuild of 5.5 stable
Matthew Pope [EMAIL PROTECTED] writes: [...] 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) etc [...] 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 default answer to all the prompts about conflicts. The default operation in mergemaster is to do nothing, so if you're going to choose the default the whole way, you might as well skip running mergemaster at all. Go back through mergemaster, and actually pay attention to the changes. On files you haven't modified, you will be able to (i)nstall the new versions of those files, but otherwise you will need to (m)erge them. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems after rebuild of 5.5 stable
Matthew Pope wrote: Lowell Gilbert wrote: Matthew Pope [EMAIL PROTECTED] writes: [...] 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) etc [...] 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 default answer to all the prompts about conflicts. The default operation in mergemaster is to do nothing, so if you're going to choose the default the whole way, you might as well skip running mergemaster at all. Yes, well put. That clarified I was in fact consuming resources in a less than optimal way :-) Go back through mergemaster, and actually pay attention to the changes. On files you haven't modified, you will be able to (i)nstall the new versions of those files, but otherwise you will need to (m)erge them. Ok, I tried that but my system is too far gone. Close to 100 environment vars are missing and if I jam them all into rc.conf it will be a mess, especially since I would be guessing at the appropriate values for the vars. My next step is to start from scratch (as Albi suggested.) Unfortuntely, even with ipfw set to open, I am still getting no route to host when I try and ping my gateway. It was always pingable in the past, and I've checked the cable into my new-ish switch and all seems fine, with green lights. The result of a route -n is in another virtual terminal and I can't copy and paste, but it lists the headers and then nothing for the details, i.e. no routes are in the routing table at all. OK pen and paper come to the rescue, here is the result of netstat -n on my misconfigured, 5.5 stable, upgraded system that can not seem to ping the gateway let alone do a cvsup: Active UNIX domain sockets AddressType Recv-Q Send-Q Inode Conn Refs NextRef Addr c20761a4 Stream 0 0 c207a000 0 0 0 /var/run/devd.pipe I tried trying ifup sis0 but I discovered ifup is no longer around. Thanks, Matthew Further suggestions welcome, and thanks for your help so far. Sincerely, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems after rebuild of 5.5 stable
Lowell Gilbert wrote: Matthew Pope [EMAIL PROTECTED] writes: [...] 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) etc [...] 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 default answer to all the prompts about conflicts. The default operation in mergemaster is to do nothing, so if you're going to choose the default the whole way, you might as well skip running mergemaster at all. Yes, well put. That clarified I was in fact consuming resources in a less than optimal way :-) Go back through mergemaster, and actually pay attention to the changes. On files you haven't modified, you will be able to (i)nstall the new versions of those files, but otherwise you will need to (m)erge them. Ok, I tried that but my system is to far gone. Close to 100 environment vars are missing and if I jam them all into rc.conf it will be a mess, especially since I would be guessing at the appropriate values for the vars. My next step is to start from scratch (as Albi suggested.) Unfortuntely, even with ipfw set to open, I am still getting no route to host when I try and ping my gateway. It was always pingable in the past, and I've checked the cable into my new-ish switch and all seems fine, with green lights. The result of a route -n is in another virtual terminal and I can't copy and paste, but it lists the headers and then nothing for the details, i.e. no routes are in the routing table at all. Further suggestions welcome, and thanks for your help so far. Sincerely, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problems after rebuild of 5.5 stable
Matthew Pope wrote: Matthew Pope wrote: Lowell Gilbert wrote: Matthew Pope [EMAIL PROTECTED] writes: [...] 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) etc [...] 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 default answer to all the prompts about conflicts. The default operation in mergemaster is to do nothing, so if you're going to choose the default the whole way, you might as well skip running mergemaster at all. Yes, well put. That clarified I was in fact consuming resources in a less than optimal way :-) Go back through mergemaster, and actually pay attention to the changes. On files you haven't modified, you will be able to (i)nstall the new versions of those files, but otherwise you will need to (m)erge them. Ok, I tried that but my system is too far gone. Close to 100 environment vars are missing and if I jam them all into rc.conf it will be a mess, especially since I would be guessing at the appropriate values for the vars. My next step is to start from scratch (as Albi suggested.) Unfortuntely, even with ipfw set to open, I am still getting no route to host when I try and ping my gateway. It was always pingable in the past, and I've checked the cable into my new-ish switch and all seems fine, with green lights. The result of a route -n is in another virtual terminal and I can't copy and paste, but it lists the headers and then nothing for the details, i.e. no routes are in the routing table at all. OK pen and paper come to the rescue, here is the result of netstat -n on my misconfigured, 5.5 stable, upgraded system that can not seem to ping the gateway let alone do a cvsup: Active UNIX domain sockets AddressType Recv-Q Send-Q Inode Conn Refs NextRef Addr c20761a4 Stream 0 0 c207a000 0 0 0 /var/run/devd.pipe I tried trying ifup sis0 but I discovered ifup is no longer around. Thanks, Matthew OK found the problem using ifconfig. As a result of the botched rebuild, (my bad), my netword card was given an IP_V6 address but no IP_V4 address. I used # ifconfig sis0 add 10.1.1.99 This put me back in touch with the world on this server. Now I can cvsup to a production 'Release' version of FreeBSD, and rebuild all. Will tag=RELENG_6_1 for cvsup be the latest 'Release' then of FreeBSD, not stable, nor current, but Release? Thanks in advance, Matthew Further suggestions welcome, and thanks for your help so far. Sincerely, Matthew ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
