Hello, I recently made the jump to -stable from 6.0 on a box that I'm looking to bring into production as soon as 6.1 hits. Everything seems fine so far but for one issue that I am guessing is related to the rc changes in -stable. This host has two jails, both started via the rc.conf method, ie: # jail stuff - general jail_enable="YES" jail_list="somejail somejail2" jail_socket_unixiproute_only="YES" jail_sysvipc_allow="NO" # jail stuff - per jail settings # jail 1 - shell jail_jail1_rootdir="/jails/somejail" jail_jail1_hostname="somejail.bway.net" jail_jail1_ip="216.220.x.x" jail_jail1_exec_start="/bin/sh /etc/rc" jail_jail1_exec_stop="/bin/sh /etc/rc.shutdown" jail_jail1_devfs_enable="YES" jail_jail1_fdescfs_enable="NO" jail_jail1_procfs_enable="NO" jail_jail1_mount_enable="NO" jail_jail1_devfs_ruleset="devfsrules_jail" Since the upgrade, I've noticed that none of the ports-installed services in each jail start up. For example, both jails have apache2 and mysql40-server installed. Everything in /usr/local/etc/rc.d within each jail looks correct, and the startup flags are set in each jail's rc.conf. They start fine if I login to the jail and run the scripts, but do not start at boot. I have the main host's rc.conf set to log info and debugging info, but there does not seem to be anything relevant to /usr/local/etc/rc.d startup in there. I read the cvs commit from 12/20, scanned the rc manpage, and dug around in the archives but did not find anything that specifically addresses local startup within a jail. Any ideas? Any other info needed? My -stable is from 1/4/06. I'm including the rc.conf logs of jail startup below in case there's something I missed. Thanks, Charles /etc/rc: INFO: checkyesno: jail_enable is set to YES. /etc/rc: INFO: run_rc_command: evaluating jail_start(). /etc/rc: INFO: checkyesno: jail_set_hostname_allow is set to YES. /etc/rc: INFO: checkyesno: jail_socket_unixiproute_only is set to YES. /etc/rc: INFO: checkyesno: jail_sysvipc_allow is set to NO. /etc/rc: INFO: somejail devfs enable: YES /etc/rc: INFO: somejail fdescfs enable: NO /etc/rc: INFO: somejail procfs enable: NO /etc/rc: INFO: somejail mount enable: NO /etc/rc: INFO: somejail hostname: somejail.bway.net /etc/rc: INFO: somejail ip: 216.220.x.x /etc/rc: INFO: somejail root: /jails/somejail /etc/rc: INFO: somejail devdir: /jails/somejail/dev /etc/rc: INFO: somejail fdescdir: /jails/somejail/dev/fd /etc/rc: INFO: somejail procdir: /jails/somejail/proc /etc/rc: INFO: somejail ruleset: devfsrules_jail /etc/rc: INFO: somejail fstab: /etc/fstab.somejail /etc/rc: INFO: somejail exec start: /bin/sh /etc/rc /etc/rc: INFO: somejail exec stop: /bin/sh /etc/rc.shutdown /etc/rc: INFO: somejail flags: -l -U root /etc/rc: INFO: checkyesno: jail_mount is set to NO. /etc/rc: INFO: checkyesno: jail_devfs is set to YES. /etc/rc: INFO: Mounting devfs on /jails/somejail/dev /etc/rc: INFO: reading rulesets from file (/etc/defaults/devfs.rules) /etc/rc: INFO: found ruleset: devfsrules_hide_all=1 /etc/rc: INFO: adding rule (add hide) /etc/rc: INFO: found ruleset: devfsrules_unhide_basic=2 /etc/rc: INFO: adding rule (add path null unhide) /etc/rc: INFO: adding rule (add path zero unhide) /etc/rc: INFO: adding rule (add path crypto unhide) /etc/rc: INFO: adding rule (add path random unhide) /etc/rc: INFO: adding rule (add path urandom unhide) /etc/rc: INFO: found ruleset: devfsrules_unhide_login=3 /etc/rc: INFO: adding rule (add path 'ptyp*' unhide) /etc/rc: INFO: adding rule (add path 'ptyq*' unhide) /etc/rc: INFO: adding rule (add path 'ptyr*' unhide) /etc/rc: INFO: adding rule (add path 'ptys*' unhide) /etc/rc: INFO: adding rule (add path 'ptyP*' unhide) /etc/rc: INFO: adding rule (add path 'ptyQ*' unhide) /etc/rc: INFO: adding rule (add path 'ptyR*' unhide) /etc/rc: INFO: adding rule (add path 'ptyS*' unhide) /etc/rc: INFO: adding rule (add path 'ttyp*' unhide) /etc/rc: INFO: adding rule (add path 'ttyq*' unhide) /etc/rc: INFO: adding rule (add path 'ttyr*' unhide) /etc/rc: INFO: adding rule (add path 'ttys*' unhide) /etc/rc: INFO: adding rule (add path 'ttyP*' unhide) /etc/rc: INFO: adding rule (add path 'ttyQ*' unhide) /etc/rc: INFO: adding rule (add path 'ttyR*' unhide) /etc/rc: INFO: adding rule (add path 'ttyS*' unhide) /etc/rc: INFO: adding rule (add path fd unhide) /etc/rc: INFO: adding rule (add path 'fd/*' unhide) /etc/rc: INFO: adding rule (add path stdin unhide) /etc/rc: INFO: adding rule (add path stdout unhide) /etc/rc: INFO: adding rule (add path stderr unhide) /etc/rc: INFO: found ruleset: devfsrules_jail=4 /etc/rc: INFO: adding rule (add include $devfsrules_hide_all) /etc/rc: INFO: adding rule (add include $devfsrules_unhide_basic) /etc/rc: INFO: adding rule (add include $devfsrules_unhide_login) /etc/rc: INFO: devfs_rulesets_from_file: no such file (/etc/devfs.rules) /etc/rc: INFO: devfs_init_rulesets: devfs rulesets initialized /etc/rc: INFO: devfs_domount(): mount-point is (/jails/somejail/dev), ruleset is (devfsrules_jail) /etc/rc: INFO: devfs_init_rulesets: devfs rulesets already initialized /etc/rc: INFO: devfs_set_ruleset: setting ruleset (4) on mount-point (/jails/somejail/dev) /etc/rc: INFO: checkyesno: jail_fdescfs is set to NO. /etc/rc: INFO: checkyesno: jail_procfs is set to NO.
Charles Sprickman wrote:> Hello, > > I recently made the jump to -stable from 6.0 on a box that I'm looking to > bring into production as soon as 6.1 hits. Everything seems fine so far > but for one issue that I am guessing is related to the rc changes in > -stable. > > This host has two jails, both started via the rc.conf method, ie: > > # jail stuff - general > jail_enable="YES" > jail_list="somejail somejail2" > jail_socket_unixiproute_only="YES" > jail_sysvipc_allow="NO" > # jail stuff - per jail settings > # jail 1 - shell > jail_jail1_rootdir="/jails/somejail" > jail_jail1_hostname="somejail.bway.net" > jail_jail1_ip="216.220.x.x" > jail_jail1_exec_start="/bin/sh /etc/rc" > jail_jail1_exec_stop="/bin/sh /etc/rc.shutdown" > jail_jail1_devfs_enable="YES" > jail_jail1_fdescfs_enable="NO" > jail_jail1_procfs_enable="NO" > jail_jail1_mount_enable="NO" > jail_jail1_devfs_ruleset="devfsrules_jail" > > Since the upgrade, I've noticed that none of the ports-installed services > in each jail start up. For example, both jails have apache2 and > mysql40-server installed. Everything in /usr/local/etc/rc.d within each > jail looks correct, and the startup flags are set in each jail's rc.conf. > They start fine if I login to the jail and run the scripts, but do not > start at boot.See the thread "FreeBSD Port: sysutils/smartmontools (more RCng problems)" in -ports, particularly the posts by Doug Barton. It sounds like the same problem. I used his fix to get a couple of daemons to start at boot which had stopped doing so after u/g to 6.0. ------ quote Doug Barton -------- Ok, I installed this port and tested it myself, and the problem is the hard coded value of smartd_enable at the top of the script. For reasons I don't quite understand yet, hard coding the value in the script affects the boot-time operation of the script differently than on the command line. The good news is that the fix is simple: Index: smartd.sh ==================================================================RCS file: /home/pcvs/ports/sysutils/smartmontools/files/smartd.sh,v retrieving revision 1.5 diff -u -r1.5 smartd.sh --- smartd.sh 18 Nov 2005 11:46:38 -0000 1.5 +++ smartd.sh 6 Jan 2006 23:36:35 -0000 @@ -13,8 +13,8 @@ # # DO NOT CHANGE THESE DEFAULT VALUES HERE # -smartd_enable="NO" -smartd_pidfile="/var/run/smartd.pid" +smartd_enable=${smartd_enable:-NO} +smartd_pidfile=${smartd_pidfile:-/var/run/smartd.pid} . %%RC_SUBR%% ------ quote Doug Barton -------- HTH Regards, Mark
Charles Sprickman wrote:> Hello, > > I recently made the jump to -stable from 6.0 on a box that I'm looking > to bring into production as soon as 6.1 hits. Everything seems fine so > far but for one issue that I am guessing is related to the rc changes in > -stable.For rc.conf in the jails, try changing the value of early_late_divider to NETWORKING and let us know if that fixes it for you. Someone else has tested that solution successfully, and I'm behind on adding that hint to the rc man page. Doug -- This .signature sanitized for your protection