Hi, > please try the SSH connection when you are your Apache user (e.g. > www-data/www-run). I've tried this and I had to accept the host-key, but it worked. > Please also check your logs (/var/log/syslog) if the > SSH daemon reports anything if and why the connection is not accepted. Here are the messages (first ssh from apache-user (www-data), second LAM test):
1) syslog: Mar 3 21:22:14 ARGLOS nslcd[863]: [2dba31] connected to LDAP server ldap://127.0.0.1/ auth.log: Mar 3 21:22:14 ARGLOS sshd[2153]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=localhost user=manager Mar 3 21:22:14 ARGLOS sshd[2153]: Accepted password for manager from ::1 port 48108 ssh2 Mar 3 21:22:14 ARGLOS sshd[2153]: pam_unix(sshd:session): session opened for user manager by (uid=0) 2) syslog: Mar 3 21:24:55 ARGLOS nslcd[863]: [7130a3] failed to bind to LDAP server ldap://127.0.0.1/: Invalid credentials: Success auth.log: Mar 3 21:24:55 ARGLOS sshd[2248]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=localhost user=manager Mar 3 21:24:56 ARGLOS sshd[2248]: Failed password for manager from ::1 port 59774 ssh2 It looks like LAM uses a wrong password (see auth.log). > If this does not help please check with wireshark/tcpdump if there is > really a connection attempt to SSH. There is really an attempt to connect, wireshark logs ssh-protol packets. Best regards Simon ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Lam-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lam-public
