Jail not starting

[Jon Passki]

On 10/22/07, freebsd at vfemail.net <freebsd at vfemail.net> wrote:
>
> Sorry folks
>
> even though I sent this reply long back, didn't realize that it didn't
> go to the mailing list until today.
>
> I am still having the same problem, and would appreciate suggestions
> for further testing.

[snip]

> well, I'm trying to run BIND in one jail and Apache on the other.
> first, I tried doing the BIND/named. As you have suggested, I hit the
> ^T, couple of times, and this is what came up
>
>    /etc/rc.d/jail start
> Configuring jails:.
> Starting jails:load: 0.60  cmd: sh 76309 [runnable] 0.00u 0.00s 0% 1716k
> load: 0.72  cmd: sh 77454 [runnable] 0.00u 0.00s 0% 2656k
> load: 0.74  cmd: dirname 77929 [runnable] 0.00u 0.00s 0% 340k
> load: 0.74  cmd: sh 75636 [runnable] 0.28u 2.31s 9% 3204k
> load: 0.74  cmd: dirname 78312 [runnable] 0.00u 0.00s 0% 532k
> load: 0.76  cmd: dirname 78415 [runnable] 0.00u 0.00s 0% 344k
> load: 0.76  cmd: sh 78506 [runnable] 0.00u 0.00s 0% 3528k
> load: 0.76  cmd: dirname 78631 [runnable] 0.00u 0.00s 0% 148k
> load: 0.76  cmd: sh 75636 [runnable] 0.32u 3.14s 11% 3696k
> load: 0.76  cmd: sh 75636 [runnable] 0.32u 3.26s 11% 3764k
> load: 0.76  cmd: dirname 78850 [runnable] 0.00u 0.00s 0% 216k
> load: 0.76  cmd: dirname 78898 [runnable] 0.00u 0.00s 0% 148k
> load: 0.76  cmd: dirname 78968 [runnable] 0.00u 0.00s 0% 452k
> load: 0.78  cmd: sh 79018 [runnable] 0.00u 0.00s 0% 3952k
> load: 0.78  cmd: sh 75636 [runnable] 0.37u 3.65s 12% 4000k
> load: 0.78  cmd: sh 79165 [runnable] 0.00u 0.00s 0% 4072k
> load: 0.78  cmd: sh 75636 [runnable] 0.40u 3.86s 12% 4124k
> load: 0.78  cmd: sh 75636 [runnable] 0.44u 4.39s 14% 4408k
> load: 0.80  cmd: sh 75636 [runnable] 0.44u 4.53s 14% 4480k
> load: 0.80  cmd: dirname 79720 [runnable] 0.00u 0.00s 0% 472k
> load: 0.92  cmd: sh 82655 [runnable] 0.00u 0.00s 0% 6952k

When troubleshooting rc.d issues, I find it best to set rc.debug="yes"
in rc.conf and watch its output on a restart.  Try setting it and do
an `/etc/rc.d/jail restart`, recording the output.  Outside of typos,
not having mounted a devfs can cause some failures that are difficult
to notice.

Jon