Re: After freebsd-update - all went wrong.
On Thu, Dec 24, 2009 at 03:47:51PM +, Marwan Sultan thus spake: This is a lesson for me and everyone to never run freebsd-update on a custom kernel I run FreeBSD on a custom kernel, and do binary updates. However, I can do this because I run my own update server. So all kernels are rebuilt and distributed. It can be done. The power of FreeBSD! - Marwan Sultan System Administrator Date: Thu, 24 Dec 2009 15:35:44 +0100 From: free...@edvax.de To: dead_l...@hotmail.com CC: freebsd-questions@freebsd.org Subject: Re: After freebsd-update - all went wrong. On Thu, 24 Dec 2009 14:06:48 +, Marwan Sultan dead_l...@hotmail.com wrote: well, I have fixed problem two by installing back my custom kernel. but the system still ignores the defaultroute command in rc.conf this is why we have manuly added to the rc.local Is this possibly a spelling error? The setting in rc.conf is defaultrouter=... - routeR. But eventho it shouldnot touch rc.conf right? Correct. The rc.conf file is one of the few ones that shouldn't be in the scope of freebsd-update or mergemaster (if you update by source). my rc.local now has route add default 66.xx.x.x ifconfig em0 66.xx.x.x netmask 255.255.255.255 alias If i take it off, system will not have any defaultroute anymore although its in rc.conf defaultrouter=66.xx.x.x hostname=xx.com ifconfig_em0=inet 66.xx.x.x netmask 255.255.255.0 Your setting in rc.conf is spelled correctly (see above). Could you try what happens if you start the inet subsystem manually (/etc/rc.d/netif and /etc/rc.d/routing)? The last one reads defaultrouter=... from rc.conf. As far as I see, the settings in rc.conf are completely valid, and should work. If this is still the old rc.conf (that worked before), the services activated in there should be started, too... You could additionally check /etc/resolv.conf and /etc/hosts for any malformed entries. I think /etc/hosts could be altered / overwritten by freebsd-update? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 _ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/171222986/direct/01/___ 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
After freebsd-update - all went wrong.
Hello FreeBSD people. i'm on FreeBSD 7.2-R p4 I just applied : # freebsd-update fetch # freebsd-update install with no problems After i restarted the server i lost my ssh connection, server went down! I have contacted the hosting company, and after investigation they informed me that for some reason system is ignoring the defaulroute command in rc.conf So they had manualy add the defaultroute to rc.local !! And after this small workaround, I found out users quota is not running So i figured that its ignoring the default kernel. I have recompiled my custom kernel.. Now quotas working! and system still FreeBSD xxx.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 12:21:39 UTC 2009 it didnot even apply the patchs !! and still reading the default route from rc.local Please any help is appreciate it, this is a commercial use server you can say im eating shit now This shouldnot happen with freebsd-update tool !! what the heck! - Marwan Sultan _ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/171222986/direct/01/___ 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: After freebsd-update - all went wrong.
On Thu, 24 Dec 2009 13:31:13 +, Marwan Sultan dead_l...@hotmail.com wrote: i'm on FreeBSD 7.2-R p4 I just applied : # freebsd-update fetch # freebsd-update install with no problems Later you mentioned that you run a custom kernel, especially for inclusion of quota. When using the freebsd-update tool, you have to pay extra attention to custom kernel - it usually just works for the GENERIC kernel without any modifications, that's what this tool primarily is intended for. After i restarted the server i lost my ssh connection, server went down! Server down OR just no connection? I have contacted the hosting company, and after investigation they informed me that for some reason system is ignoring the defaulroute command in rc.conf So they had manualy add the defaultroute to rc.local !! The use of rc.local is still possible, but deprecated; it's mostly a means for backward compatibility. Furthermore, I don't see a defaulroute setting (not command per se) in /etc/rc.conf (and /etc/defaults/rc.conf for completeness); only things found are: defaultrouter=NO # Set to default gateway (or NO). ipv6_defaultrouter=NO # Set to IPv6 default gateway (or NO). #ipv6_defaultrouter=2002:c058:6301:: # Use this for 6to4 (RFC 3068) Is this what you mean? Are you sure you didn't overwrite any important configuration file, like /etc/hosts, /etc/resolv.conf or even rc.conf? And after this small workaround, I found out users quota is not running So i figured that its ignoring the default kernel. No, the GENERIC kernel just doesn't include quota functionality. I have recompiled my custom kernel.. Now quotas working! Of course, yours seems to include it. and system still FreeBSD xxx.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 12:21:39 UTC 2009 What should it be instead? It would be nice if you could tell which version you came from, and which version you updated to. Have you updated your src/ subtree, especially for the kernel sources? Seems that even if your system has been updated with freebsd-update to 8, your kernel has been compiled from the 7.2-p4 sources... it didnot even apply the patchs !! Patches go into the src/ subtree when updating it, e. g. with make update in /usr/src (using csup or cvsup). and still reading the default route from rc.local It would be helpful to see some config file examples. Maybe rc.local overrides things that should already work? This shouldnot happen with freebsd-update tool !! what the heck! Wrong use of the right tool maybe? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: After freebsd-update - all went wrong.
Hi Poly, Its very short story, my system is on FreeBSD 7.2- P4 and everything works great. Yes I have custom kernel, mainly for quotas. I have run freebsd-update fetch and install, I forgot its only for generic kernel. However, after the freebsd-update fetch/install done, i restarted my server then its down. Down means: its not connected to the internet because 1- it couldnot read the default route and couldnot recognize its ip address. 2- restored to the orginal GENERIC kernel. well, I have fixed problem two by installing back my custom kernel. but the system still ignores the defaultroute command in rc.conf this is why we have manuly added to the rc.local No, I have not overwrite any files, and everything works great, until i ran freebsd-update on my custom kernel by mistake. But eventho it shouldnot touch rc.conf right? my rc.local now has route add default 66.xx.x.x ifconfig em0 66.xx.x.x netmask 255.255.255.255 alias If i take it off, system will not have any defaultroute anymore although its in rc.conf defaultrouter=66.xx.x.x hostname=xx.com ifconfig_em0=inet 66.xx.x.x netmask 255.255.255.0 Thank you. Subject: Re: After freebsd-update - all went wrong. On Thu, 24 Dec 2009 13:31:13 +, Marwan Sultan dead_l...@hotmail.com wrote: i'm on FreeBSD 7.2-R p4 I just applied : # freebsd-update fetch # freebsd-update install with no problems Later you mentioned that you run a custom kernel, especially for inclusion of quota. When using the freebsd-update tool, you have to pay extra attention to custom kernel - it usually just works for the GENERIC kernel without any modifications, that's what this tool primarily is intended for. After i restarted the server i lost my ssh connection, server went down! Server down OR just no connection? I have contacted the hosting company, and after investigation they informed me that for some reason system is ignoring the defaulroute command in rc.conf So they had manualy add the defaultroute to rc.local !! The use of rc.local is still possible, but deprecated; it's mostly a means for backward compatibility. Furthermore, I don't see a defaulroute setting (not command per se) in /etc/rc.conf (and /etc/defaults/rc.conf for completeness); only things found are: defaultrouter=NO # Set to default gateway (or NO). ipv6_defaultrouter=NO # Set to IPv6 default gateway (or NO). #ipv6_defaultrouter=2002:c058:6301:: # Use this for 6to4 (RFC 3068) Is this what you mean? Are you sure you didn't overwrite any important configuration file, like /etc/hosts, /etc/resolv.conf or even rc.conf? And after this small workaround, I found out users quota is not running So i figured that its ignoring the default kernel. No, the GENERIC kernel just doesn't include quota functionality. I have recompiled my custom kernel.. Now quotas working! Of course, yours seems to include it. and system still FreeBSD xxx.com 7.2-RELEASE-p4 FreeBSD 7.2-RELEASE-p4 #0: Fri Oct 2 12:21:39 UTC 2009 What should it be instead? It would be nice if you could tell which version you came from, and which version you updated to. Have you updated your src/ subtree, especially for the kernel sources? Seems that even if your system has been updated with freebsd-update to 8, your kernel has been compiled from the 7.2-p4 sources... it didnot even apply the patchs !! Patches go into the src/ subtree when updating it, e. g. with make update in /usr/src (using csup or cvsup). and still reading the default route from rc.local It would be helpful to see some config file examples. Maybe rc.local overrides things that should already work? This shouldnot happen with freebsd-update tool !! what the heck! Wrong use of the right tool maybe? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... _ Hotmail: Free, trusted and rich email service. http://clk.atdmt.com/GBL/go/171222984/direct/01/___ 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: After freebsd-update - all went wrong.
On Thu, 24 Dec 2009 14:06:48 +, Marwan Sultan dead_l...@hotmail.com wrote: well, I have fixed problem two by installing back my custom kernel. but the system still ignores the defaultroute command in rc.conf this is why we have manuly added to the rc.local Is this possibly a spelling error? The setting in rc.conf is defaultrouter=... - routeR. But eventho it shouldnot touch rc.conf right? Correct. The rc.conf file is one of the few ones that shouldn't be in the scope of freebsd-update or mergemaster (if you update by source). my rc.local now has route add default 66.xx.x.x ifconfig em0 66.xx.x.x netmask 255.255.255.255 alias If i take it off, system will not have any defaultroute anymore although its in rc.conf defaultrouter=66.xx.x.x hostname=xx.com ifconfig_em0=inet 66.xx.x.x netmask 255.255.255.0 Your setting in rc.conf is spelled correctly (see above). Could you try what happens if you start the inet subsystem manually (/etc/rc.d/netif and /etc/rc.d/routing)? The last one reads defaultrouter=... from rc.conf. As far as I see, the settings in rc.conf are completely valid, and should work. If this is still the old rc.conf (that worked before), the services activated in there should be started, too... You could additionally check /etc/resolv.conf and /etc/hosts for any malformed entries. I think /etc/hosts could be altered / overwritten by freebsd-update? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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: After freebsd-update - all went wrong.
Dear Poly, /etc/resolv.conf and /etc/hosts and /etc/rc.conf are untouched. The only problem that freebsd ignores the defaultrouter line in /etc/rc.conf and just for the archives, kernel has been restored to default, but i have recompiled my kernel and its okay. I will today use the ordiary freebsd update (csup) and see if this will fix what freebsd-update broke- and will update this list. This is a lesson for me and everyone to never run freebsd-update on a custom kernel system, however It shouldnot produce such problem. (i think) Thank you - Marwan Sultan System Administrator Date: Thu, 24 Dec 2009 15:35:44 +0100 From: free...@edvax.de To: dead_l...@hotmail.com CC: freebsd-questions@freebsd.org Subject: Re: After freebsd-update - all went wrong. On Thu, 24 Dec 2009 14:06:48 +, Marwan Sultan dead_l...@hotmail.com wrote: well, I have fixed problem two by installing back my custom kernel. but the system still ignores the defaultroute command in rc.conf this is why we have manuly added to the rc.local Is this possibly a spelling error? The setting in rc.conf is defaultrouter=... - routeR. But eventho it shouldnot touch rc.conf right? Correct. The rc.conf file is one of the few ones that shouldn't be in the scope of freebsd-update or mergemaster (if you update by source). my rc.local now has route add default 66.xx.x.x ifconfig em0 66.xx.x.x netmask 255.255.255.255 alias If i take it off, system will not have any defaultroute anymore although its in rc.conf defaultrouter=66.xx.x.x hostname=xx.com ifconfig_em0=inet 66.xx.x.x netmask 255.255.255.0 Your setting in rc.conf is spelled correctly (see above). Could you try what happens if you start the inet subsystem manually (/etc/rc.d/netif and /etc/rc.d/routing)? The last one reads defaultrouter=... from rc.conf. As far as I see, the settings in rc.conf are completely valid, and should work. If this is still the old rc.conf (that worked before), the services activated in there should be started, too... You could additionally check /etc/resolv.conf and /etc/hosts for any malformed entries. I think /etc/hosts could be altered / overwritten by freebsd-update? -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ 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 _ Hotmail: Powerful Free email with security by Microsoft. http://clk.atdmt.com/GBL/go/171222986/direct/01/___ 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
