On Mon, 4 Jan 2016, Dan McDonald wrote:
On Dec 31, 2015, at 10:45 AM, Bob Friesenhahn <bfrie...@simple.dallas.tx.us>
wrote:
I am accessing the system via ssh which uses '~.' to terminate the ssh session. This is
also the default shutdown sequence for 'zlogin -C'. The idea is that after doing some
initial administration using 'zlogin -C', the "~." sequence was used to quit
it. This terminates the ssh session rather than the zone console login. While
subsequent 'zlogin -C' works, it may be that the unclean/violent termination of the zone
console login has left behind residue which prevents the zone from shutting down.
Dumb questions: which ssh client, and which ssh server?
It's highly possible the process you have simply backgrounds once ssh quits.
Knowing which server + client combo may help... especially given that you now
have OpenSSH doing a lot more in recent OmniOS updates.
I no longer believe that the problem is due to hung state associated
with a ssh session since I have since seen it several times using
'zlogin' without -C and using 'exit' to quit the session.
Regardless, this is the answer to your question:
On Solaris 10 client system:
Sun_SSH_1.1.5, SSH protocols 1.5/2.0, OpenSSL 0x0090704f
On OmniOS system
Sun_SSH_1.5, SSH protocols 1.5/2.0, OpenSSL 0x1000205f
As far as I am aware, the problem has not happened without first
having done a 'zlogin' to the zone. Also, as far as I am aware, the
problem afflicts the most recently created zone (until at least system
reboot) but it is also not consistent in that sometimes the shutdown
succeeds and sometimes it fails.
Bob
--
Bob Friesenhahn
bfrie...@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
_______________________________________________
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss
