Connection to SOLARIS server [1]

Connection to SOLARIS server

Saturday, October 22, 2005 9:05 AM - Venkat

[18:04:37] Connecting to '192.168.35.8'...
[18:04:37] Connected.
[18:04:37] Version exchange initiated...
[18:04:37] server: SSH-2.0-OpenSSH_3.9p1
[18:04:37] client: SSH-2.0-libssh_1.3.3.0 1975 NetSarang Computer, Inc.
[18:04:37] SSH2 is selected.
[18:04:37] Algorithm negotiation initiated...
[18:04:37] key exchange: diffie-hellman-group1-sha1
[18:04:37] host key: ssh-dss
[18:04:37] outgoing encryption: aes128-cbc
[18:04:37] incoming encryption: aes128-cbc
[18:04:37] outgoing mac: hmac-sha1
[18:04:37] incoming mac: hmac-sha1
[18:04:37] outgoing compression: none
[18:04:37] incoming compression: none
[18:04:37] Host authentication initiated...
[18:04:37] Hostkey fingerprint:
[18:04:37] ssh-dsa 1024 59:cd:30:ad:3d:fb:ee:1e:90:9d:2c:44:00:21:f4:d1
[18:04:38] Accepted. Verifying host key...
[18:04:38] Verified.
[18:04:38] User authentication initiated...
[18:04:38] Sent user name 'oracle'.
[18:04:38] Sent password.
[18:04:38] Access granted.
[18:04:38] Sent X11 forwarding request...
[18:04:38] Succeeded.
[18:04:38] Sent the command line.
[18:04:38] /usr/openwin/bin/xterm -ls -display $DISPLAY
[18:04:38] Start timer (TIMER_SHUTDOWN, 180).
Could not chdir to home directory /export/home/oracle: No such file or directory
/usr/openwin/bin/xauth: error in locking authority file /export/home/oracle/.Xauthority
[18:04:39] An X11 channel (id=1) has opened.
[18:04:39] Stop timer (TIMER_SHUTDOWN).
[18:04:39] XLT: SENT CLOSE [COOKIE][1]
[18:04:39] XLT: GOT CLOSE [1]
[18:04:39] An X11 channel (id=1) has closed.
[18:04:39] All X11 channels are closed.
[18:04:39] Start timer (TIMER_SHUTDOWN, 60).
X connection to localhost:10.0 broken (explicit kill or server shutdown).
[18:04:39] XLT: GOT EOF [0]
[18:04:39] XLT: SENT CLOSE [GOT EOF][0]
[18:04:39] XLT: GOT CLOSE [0]


Re: Connection to SOLARIS server

Monday, October 24, 2005 1:58 PM - Andrew Blake

It seems like the user 'oracle' does not have $HOME directory setup. Try logging in with other accounts and see if the problem persists.

If the problem does not occur in other accounts, try recreating the user, oracle.

Hope this helps.


Previous views: 394