jails

[Dirk Engling]

On 31.01.12 20:27, Bender, Chris wrote:
> zs1# ezjail-admin list
> STA JID  IP              Hostname                       Root Directory
> --- ---- --------------- ------------------------------
> ------------------------
> DR  14   172.19.4.36     wiki                           /usr/jails/wiki
> DR  9    172.19.4.41     tools2
> /usr/jails/tools2
> DR  16   172.19.4.45     rt3                            /usr/jails/rt3
> DR  17   172.19.4.42     rep                            /usr/jails/rep
> DR  11   172.19.4.190    npins                          /usr/jails/npims
> DR  13   172.19.4.39     logger
> /usr/jails/logger
> DR  12   172.19.4.44     inventory
> /usr/jails/inventory
> DR  15   172.19.4.38     dns2                           /usr/jails/dns2
> DSN N/A  172.19.4.37     dns1                           /usr/jails/dns1
> DSN N/A  172.19.4.32     db                             /usr/jails/db
> DSN N/A  172.19.4.31     coremon
> /usr/jails/coremon
> DR  10   172.19.4.43     cf                             /usr/jails/cf

This shows that all the jails that are supposed to run, are actually
running. You can console into the jail by

  ezjail-admin console tools2

and check if there are any services running. For starters you could
check if in the jail's rc.conf you have sshd enabled.

If that is the case, you can check if the host system's sshd binds on
*:22, making it impossible for the jail's sshds to bind to their port 22.

Check for:

#ListenAddress 0.0.0.0

in the host system's /etc/ssh/sshd_config and make it bind to the host
system's primary IP address.

A 'sockstat -4l | grep 22' in the host system will also tell you about
services listening on all IP addresses.

Regards,

  erdgeist