Date: Wed, 25 Apr 2018 15:56:10 -0400 From: Marc Branchaud <marcnarc@gmail.com> To: freebsd-stable@FreeBSD.ORG Subject: Re: Problems with ifconfig when starting all jails after 10.3 -> 10.4 upgrade Message-ID: <a6d5dc1a-ce09-c550-4f7f-beadf83054d1@gmail.com> In-Reply-To: <94c4e3f3-dac5-2958-3ad4-b4c43e4d21cf@gmail.com> References: <45483fb3-bd94-10f1-a75c-3a035ec69cfa@gmail.com> <94c4e3f3-dac5-2958-3ad4-b4c43e4d21cf@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2018-04-06 02:26 PM, Marc Branchaud wrote:
> On 2018-04-05 10:28 AM, Marc Branchaud wrote:
>> Hi all,
>>
>> I just upgraded from 10.3 to 10.4, and "/etc/rc.d/jail start" is
>> having problems starting all of my jails:
>>
>> # /etc/rc.d/jail start
>> Starting jails:xipbuild_3_3: created
>> ifconfig:: bad value
>> jail: xipbuild_3_3_8: /sbin/ifconfig lo1 inet 10.1.1.38/32 alias: failed
>> xipbuild_3_4: created
>> ifconfig:: bad value
>> jail: xipbuild_4_0: /sbin/ifconfig lo1 inet 10.1.1.5/32 alias: failed
>> xipbuild: created
>> xipbuild_4_9: created
>> ifconfig:: bad value
>> jail: xipbuild9: /sbin/ifconfig lo1 inet 10.1.1.209/32 alias: failed
>> .
>
> More info: Things work fine with jail_parallel_start="YES".
>
> In 10.4, /etc/rc.d/jail now adds "-p1" to the jail command's arguments
> when starting all jails with jail_parallel_start="NO". It's definitely
> this parameter that's causing my problems -- changing /etc/rc.d/jail to
> not add the parameter fixes the problem.
The problem stems from work for bug 209112, a patch for which (r302857)
was MFC'd to stable-10.
I've added a comment to bug 209112.
M.
> M.
>
>
>> This worked fine in 10.3. I can individually start each jail, e.g.
>> "/etc/rc.d/jail start xipbuild9".
>>
>> All the jails configure the same set of parameters. Here's my jail.conf:
>>
>> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< ---
>> xipbuild_3_3 {
>> path="/usr/build-jails/jails/3.3";
>> host.hostname="xipbuild_3_3";
>> ip4.addr="10.1.1.3/32";
>>
>> allow.chflags;
>> allow.mount;
>> mount.devfs;
>>
>> persist;
>>
>> mount="/usr/home /usr/build-jails/jails/3.3/usr/home nullfs rw 0 0";
>> interface="lo1";
>> }
>> xipbuild_3_3_8 {
>> path="/usr/build-jails/jails/3.3.8";
>> host.hostname="xipbuild_3_3_8";
>> ip4.addr="10.1.1.38/32";
>>
>> allow.chflags;
>> allow.mount;
>> mount.devfs;
>>
>> persist;
>>
>> mount="/usr/home /usr/build-jails/jails/3.3.8/usr/home nullfs rw 0
>> 0";
>> interface="lo1";
>> }
>> xipbuild_3_4 {
>> path="/usr/build-jails/jails/3.4";
>> host.hostname="xipbuild_3_4";
>> ip4.addr="10.1.1.4/32";
>>
>> allow.chflags;
>> allow.mount;
>> mount.devfs;
>>
>> persist;
>>
>> mount="/usr/home /usr/build-jails/jails/3.4/usr/home nullfs rw 0 0";
>> interface="lo1";
>> }
>> xipbuild_4_0 {
>> path="/usr/build-jails/jails/4.0";
>> host.hostname="xipbuild_4_0";
>> ip4.addr="10.1.1.5/32";
>>
>> allow.chflags;
>> allow.mount;
>> mount.devfs;
>>
>> persist;
>>
>> mount="/usr/home /usr/build-jails/jails/4.0/usr/home nullfs rw 0 0";
>> interface="lo1";
>> }
>> xipbuild {
>> path="/usr/build-jails/jails/latest";
>> host.hostname="xipbuild";
>> ip4.addr="10.1.1.200/32";
>>
>> allow.chflags;
>> allow.mount;
>> mount.devfs;
>>
>> persist;
>>
>> mount="/usr/home /usr/build-jails/jails/latest/usr/home nullfs rw
>> 0 0";
>> interface="lo1";
>> }
>> xipbuild_4_9 {
>> path="/usr/build-jails/jails/4.9";
>> host.hostname="xipbuild_4_9";
>> ip4.addr="10.1.1.90/32";
>>
>> allow.chflags;
>> allow.mount;
>> mount.devfs;
>>
>> persist;
>>
>> mount="/usr/home /usr/build-jails/jails/4.9/usr/home nullfs rw 0 0";
>> interface="lo1";
>> }
>> xipbuild9 {
>> path="/usr/build-jails/jails/latest9";
>> host.hostname="xipbuild9";
>> ip4.addr="10.1.1.209/32";
>>
>> allow.chflags;
>> allow.mount;
>> mount.devfs;
>>
>> persist;
>>
>> mount="/usr/home /usr/build-jails/jails/latest9/usr/home nullfs rw
>> 0 0";
>> interface="lo1";
>> }
>> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< ---
>>
>> I use ipnat to give the jails network access. Here's ipnat.rules:
>>
>> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< ---
>> map em0 10.1.1.0/24 -> 0/32 proxy port ftp ftp/tcp
>> map em0 10.1.1.0/24 -> 0/32
>> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< ---
>>
>> And here's my rc.conf:
>>
>> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< ---
>> # Generated by Ansible
>>
>> # hostname must be FQDN
>> hostname="devastator.xiplink.com"
>>
>> zfs_enable="False"
>>
>> # FIXME: previously auto-created?
>> ifconfig_lo1="create"
>>
>>
>> ifconfig_em0="DHCP SYNCDHCP"
>>
>> network_interfaces="em0"
>> gateway_enable="YES"
>>
>> # Prevent rpc
>> rpcbind_enable="NO"
>>
>> # Prevent sendmail to try to connect to localhost
>> sendmail_enable="NO"
>> sendmail_submit_enable="NO"
>> sendmail_outbound_enable="NO"
>> sendmail_msp_queue_enable="NO"
>>
>> # Bring up sshd, it takes some time and uses some entropy on first
>> startup
>> sshd_enable="YES"
>>
>> netwait_enable="YES"
>> netwait_ip="10.10.0.35"
>> netwait_if="em0"
>>
>> jenkins_swarm_enable="YES"
>> jenkins_swarm_opts="-executors 8"
>>
>> # --- Build jails ---
>> build_jails_enable="YES"
>> jail_enable="YES"
>>
>> # Set rules in /etc/ipnat.rules
>> ipnat_enable="YES"
>>
>> # Set interface name for ipnat
>> network_interfaces="${network_interfaces} lo1"
>>
>> # Each jail needs to specify its IP address and mask bits in
>> ipv4_addrs_lo1
>> ipv4_addrs_lo1="10.1.1.1/32"
>>
>> jail_chflags_allow="yes"
>>
>> varmfs="NO"
>> --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< --- 8< ---
>>
>> Any insight would be deeply appreciated!
>>
>> M.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a6d5dc1a-ce09-c550-4f7f-beadf83054d1>