Re: Switch to using rc.d for local packages is premature for RELENG_6
On Mar 21, 2006, at 11:23 PM, Maxim Sobolev wrote: As part of testing how well some of our products work with latest RELENG_6, I have make a new build and found that lot of important services (for example PostgreSQL, Apache) doesn't start up (despite having respective xxx_enable entries in /etc/rc.conf) when installed from the freshly updated ports tree onto a I upgraded a server from 5.4-stable to 6.1-PRERELEASE on march 2, and postgres started up just fine as did apache 2.0. i even did a full reinstall of all ports and it continued to work. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Switch to using rc.d for local packages is premature for RELENG_6
On Tue, Mar 21, 2006 at 08:23:40PM -0800, Maxim Sobolev wrote: Hi guys, As part of testing how well some of our products work with latest RELENG_6, I have make a new build and found that lot of important services (for example PostgreSQL, Apache) doesn't start up (despite having respective xxx_enable entries in /etc/rc.conf) when installed from the freshly updated ports tree onto a clean, freshly updated RELENG_6 system. This is very bad, considering how close to release are we and how much FreeBSD users rely on those services to work OOB. Did you e.g. neglect to mergemaster? This really does work for others. Kris pgp8GoqGZhvnu.pgp Description: PGP signature
Re: Switch to using rc.d for local packages is premature for RELENG_6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, Mar 22, 2006 at 01:35:24PM -0500, Kris Kennaway wrote: On Tue, Mar 21, 2006 at 08:23:40PM -0800, Maxim Sobolev wrote: Hi guys, As part of testing how well some of our products work with latest RELENG_6, I have make a new build and found that lot of important services (for example PostgreSQL, Apache) doesn't start up (despite having respective xxx_enable entries in /etc/rc.conf) when installed from the freshly updated ports tree onto a clean, freshly updated RELENG_6 system. This is very bad, considering how close to release are we and how much FreeBSD users rely on those services to work OOB. Did you e.g. neglect to mergemaster? This really does work for others. The really stupid question (only because it happened to me, but I'm stupid). You're not running them in a jail, are you? In that case, one has to add early_late_divider=NETWORKING to the jail's rc.conf. (At least that fixed it for me, thanks to Doug B. who was nice enough to not point out that had I looked at the rc.conf man page, I could have found the solution myself.) - -- Scott Robbins GPG KeyID EB3467D6 ( 1B848 077D 66F6 9DB0 FDC2 A409 FA54 D575 EB34 67D6) gpg --keyserver pgp.mit.edu --recv-keys EB3467D6 Xander: You were looking at my neck. Angel: What? Xander: You were checking out my neck, I saw that. Angel: No, I wasn't. Xander: Just keep your distance, pal. Angel: I wasn't looking at your neck. Xander: I told you to eat before we left. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEIZ0x+lTVdes0Z9YRAua4AKCRyNgi+wxEXPGVwesMrf5wC7NSxwCgjFlV /zfsxtWgFBm3yLjUupPda7k= =LW+O -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Switch to using rc.d for local packages is premature for RELENG_6
Maxim Sobolev wrote: Hi guys, As part of testing how well some of our products work with latest RELENG_6, I have make a new build and found that lot of important services (for example PostgreSQL, Apache) doesn't start up (despite having respective xxx_enable entries in /etc/rc.conf) when installed from the freshly updated ports tree onto a clean, freshly updated RELENG_6 system. This is very bad, considering how close to release are we and how much FreeBSD users rely on those services to work OOB. While I can certainly appreciate your frustration, it doesn't work isn't much of a bug report. You mentioned latest RELENG_6, and if you got the new local_startup code then I assume that you've mergemaster'ed, that leaves your ports. Are you using the latest versions of everything? The two specific examples you gave have both been updated since the first of the year to address problems that surfaced after the local_startup change was mfc'ed. I would expect them to be really pissed off when lot of important services just don't work after upgrading their server from 6.0 to 6.1 or after installing it from install cd. This is apparently caused by the fact that lot of rc.d scripts in /usr/local/etc/rc.d are newstyle one now (sufficiently newstyle to pass find_local_scripts_new check), but few of them were actually tested to work correctly in fully rc.d environment. On the contrary, as I said above, the two you mentioned specifically have both been upgraded for the new environment. If you can provide more information (perhaps as a followup to the -ports list) I'm sure we can help you debug it more thoroughly. Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Switch to using rc.d for local packages is premature for RELENG_6
Hi guys, As part of testing how well some of our products work with latest RELENG_6, I have make a new build and found that lot of important services (for example PostgreSQL, Apache) doesn't start up (despite having respective xxx_enable entries in /etc/rc.conf) when installed from the freshly updated ports tree onto a clean, freshly updated RELENG_6 system. This is very bad, considering how close to release are we and how much FreeBSD users rely on those services to work OOB. I would expect them to be really pissed off when lot of important services just don't work after upgrading their server from 6.0 to 6.1 or after installing it from install cd. This is apparently caused by the fact that lot of rc.d scripts in /usr/local/etc/rc.d are newstyle one now (sufficiently newstyle to pass find_local_scripts_new check), but few of them were actually tested to work correctly in fully rc.d environment. Therefore, I think that the RELENG_6 should be reverted to using old stuff and it should be left for 7.x tree. Regards, Maxim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Switch to using rc.d for local packages is premature for RELENG_6
I have just realized that maybe the best approach to address this problem would be not reverting the change in question, but making find_local_scripts_new() more strict, so that only those local rc.d scripts that have been explicitly marked by maintainer as fully rc.d-safe are handled in a new way. Checking for '^# PROVIDE:' doesn't really work reliably. -Maxim Maxim Sobolev wrote: Hi guys, As part of testing how well some of our products work with latest RELENG_6, I have make a new build and found that lot of important services (for example PostgreSQL, Apache) doesn't start up (despite having respective xxx_enable entries in /etc/rc.conf) when installed from the freshly updated ports tree onto a clean, freshly updated RELENG_6 system. This is very bad, considering how close to release are we and how much FreeBSD users rely on those services to work OOB. I would expect them to be really pissed off when lot of important services just don't work after upgrading their server from 6.0 to 6.1 or after installing it from install cd. This is apparently caused by the fact that lot of rc.d scripts in /usr/local/etc/rc.d are newstyle one now (sufficiently newstyle to pass find_local_scripts_new check), but few of them were actually tested to work correctly in fully rc.d environment. Therefore, I think that the RELENG_6 should be reverted to using old stuff and it should be left for 7.x tree. Regards, Maxim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
