From vinschen at redhat.com Tue Jul 2 18:18:50 2013 From: vinschen at redhat.com (Corinna Vinschen) Date: Tue, 2 Jul 2013 10:18:50 +0200 Subject: [patch/cygwin]: Fix documentation Message-ID: <20130702081850.GA4808@calimero.vinschen.de> Hi, could somebody with checkin rights please apply the below patch? It modernizes and improves readability of the Cygwin README file (which hasn't been updated for ages), drops unsupported OSes from the ssh-host-config help text, and drops an unneeded option from ssh-user-config. Thanks in advance, Corinna Index: contrib/cygwin/README =================================================================== RCS file: /cvs/openssh/contrib/cygwin/README,v retrieving revision 1.17 diff -u -p -r1.17 README --- contrib/cygwin/README 17 Jun 2010 18:11:44 -0000 1.17 +++ contrib/cygwin/README 2 Jul 2013 08:16:43 -0000 @@ -4,115 +4,18 @@ The binary package is usually built for not run on older versions. Please check http://cygwin.com/ for information about current Cygwin releases. -Build instructions are at the end of the file. - -=========================================================================== -Important change since 3.7.1p2-2: - -The ssh-host-config file doesn't create the /etc/ssh_config and -/etc/sshd_config files from builtin here-scripts anymore, but it uses -skeleton files installed in /etc/defaults/etc. - -Also it now tries hard to create appropriate permissions on files. -Same applies for ssh-user-config. - -After creating the sshd service with ssh-host-config, it's advisable to -call ssh-user-config for all affected users, also already exising user -configurations. In the latter case, file and directory permissions are -checked and changed, if requireed to match the host configuration. - -Important note for Windows 2003 Server users: ---------------------------------------------- - -2003 Server has a funny new feature. When starting services under SYSTEM -account, these services have nearly all user rights which SYSTEM holds... -except for the "Create a token object" right, which is needed to allow -public key authentication :-( - -There's no way around this, except for creating a substitute account which -has the appropriate privileges. Basically, this account should be member -of the administrators group, plus it should have the following user rights: - - Create a token object - Logon as a service - Replace a process level token - Increase Quota - -The ssh-host-config script asks you, if it should create such an account, -called "sshd_server". If you say "no" here, you're on your own. Please -follow the instruction in ssh-host-config exactly if possible. Note that -ssh-user-config sets the permissions on 2003 Server machines dependent of -whether a sshd_server account exists or not. -=========================================================================== - -=========================================================================== -Important change since 3.4p1-2: - -This version adds privilege separation as default setting, see -/usr/doc/openssh/README.privsep. According to that document the -privsep feature requires a non-privileged account called 'sshd'. - -The new ssh-host-config file which is part of this version asks -to create 'sshd' as local user if you want to use privilege -separation. If you confirm, it creates that NT user and adds -the necessary entry to /etc/passwd. - -On 9x/Me systems the script just sets UsePrivilegeSeparation to "no" -since that feature doesn't make any sense on a system which doesn't -differ between privileged and unprivileged users. - -The new ssh-host-config script also adds the /var/empty directory -needed by privilege separation. When creating the /var/empty directory -by yourself, please note that in contrast to the README.privsep document -the owner sshould not be "root" but the user which is running sshd. So, -in the standard configuration this is SYSTEM. The ssh-host-config script -chowns /var/empty accordingly. -=========================================================================== - -=========================================================================== -Important change since 3.0.1p1-2: - -This version introduces the ability to register sshd as service on -Windows 9x/Me systems. This is done only when the options -D and/or --d are not given. -=========================================================================== - -=========================================================================== -Important change since 2.9p2: - -Since Cygwin is able to switch user context without password beginning -with version 1.3.2, OpenSSH now allows to do so when it's running under -a version >= 1.3.2. Keep in mind that `ntsec' has to be activated to -allow that feature. -=========================================================================== - -=========================================================================== -Important change since 2.3.0p1: - -When using `ntea' or `ntsec' you now have to care for the ownership -and permission bits of your host key files and your private key files. -The host key files have to be owned by the NT account which starts -sshd. The user key files have to be owned by the user. The permission -bits of the private key files (host and user) have to be at least -rw------- (0600)! - -Note that this is forced under `ntsec' only if the files are on a NTFS -filesystem (which is recommended) due to the lack of any basic security -features of the FAT/FAT32 filesystems. -=========================================================================== +================== +Host configuration +================== If you are installing OpenSSH the first time, you can generate global config -files and server keys by running +files and server keys, as well as installing sshd as a service, by running /usr/bin/ssh-host-config Note that this binary archive doesn't contain default config files in /etc. That files are only created if ssh-host-config is started. -If you are updating your installation you may run the above ssh-host-config -as well to move your configuration files to the new location and to -erase the files at the old location. - To support testing and unattended installation ssh-host-config got some options: @@ -123,17 +26,26 @@ Options: --no -n Answer all questions with "no" automatically. --cygwin -c Use "options" as value for CYGWIN environment var. --port -p sshd listens on port n. - --pwd -w Use "pwd" as password for user 'sshd_server'. - -Additionally ssh-host-config now asks if it should install sshd as a -service when running under NT/W2K. This requires cygrunsrv installed. + --user -u privileged user for service, default 'cyg_server'. + --pwd -w Use "pwd" as password for privileged user. + --privileged On Windows XP, require privileged user + instead of LocalSystem for sshd service. + +Installing sshd as daemon via ssh-host-config is recommended. + +Alternatively you can start sshd via inetd, if you have the inetutils +package installed. Just run ssh-host-config, but answer "no" when asked +to install sshd as service. The ssh-host-config script also adds the +required lines to /etc/inetd.conf and /etc/services. + +================== +User configuration +================== -You can create the private and public keys for a user now by running +Any user can simplify creating the own private and public keys by running /usr/bin/ssh-user-config -under the users account. - To support testing and unattended installation ssh-user-config got some options as well: @@ -144,88 +56,30 @@ Options: --no -n Answer all questions with "no" automatically. --passphrase -p word Use "word" as passphrase automatically. -Install sshd as daemon via cygrunsrv.exe (recommended on NT/W2K), via inetd -(results in very slow deamon startup!) or from the command line (recommended -on 9X/ME). - -If you start sshd as deamon via cygrunsrv.exe you MUST give the -"-D" option to sshd. Otherwise the service can't get started at all. - -If starting via inetd, copy sshd to eg. /usr/sbin/in.sshd and add the -following line to your inetd.conf file: - -ssh stream tcp nowait root /usr/sbin/in.sshd sshd -i - -Moreover you'll have to add the following line to your -${SYSTEMROOT}/system32/drivers/etc/services file: - - ssh 22/tcp #SSH daemon - Please note that OpenSSH does never use the value of $HOME to search for the users configuration files! It always uses the value of the pw_dir field in /etc/passwd as the home directory. If no home diretory is set in /etc/passwd, the root directory is used instead! -You may use all features of the CYGWIN=ntsec setting the same -way as they are used by Cygwin's login(1) port: - - The pw_gecos field may contain an additional field, that begins - with (upper case!) "U-", followed by the domain and the username - separated by a backslash. - CAUTION: The SID _must_ remain the _last_ field in pw_gecos! - BTW: The field separator in pw_gecos is the comma. - The username in pw_name itself may be any nice name: - - domuser::1104:513:John Doe,U-domain\user,S-1-5-21-... - - Now you may use `domuser' as your login name with telnet! - This is possible additionally for local users, if you don't like - your NT login name ;-) You only have to leave out the domain: - - locuser::1104:513:John Doe,U-user,S-1-5-21-... - -Note that the CYGWIN=ntsec setting is required for public key authentication. - -SSH2 server and user keys are generated by the `ssh-*-config' scripts -as well. - -If you want to build from source, the following options to -configure are used for the Cygwin binary distribution: - - --prefix=/usr \ - --sysconfdir=/etc \ - --libexecdir='${sbindir}' \ - --localstatedir=/var \ - --datadir='${prefix}/share' \ - --mandir='${datadir}/man' \ - --infodir='${datadir}/info' - --with-tcp-wrappers - --with-libedit - -If you want to create a Cygwin package, equivalent to the one -in the Cygwin binary distribution, install like this: - - mkdir /tmp/cygwin-ssh - cd ${builddir} - make install DESTDIR=/tmp/cygwin-ssh - cd ${srcdir}/contrib/cygwin - make cygwin-postinstall DESTDIR=/tmp/cygwin-ssh - cd /tmp/cygwin-ssh - find * \! -type d | tar cvjfT my-openssh.tar.bz2 - - -You must have installed the following packages to be able to build OpenSSH: - -- zlib -- openssl-devel - -If you want to build with --with-tcp-wrappers, you also need the package - -- tcp_wrappers - -If you want to build with --with-libedit, you also need the package - -- libedit-devel +================ +Building OpenSSH +================ + +Building from source is easy. Just unpack the source archive, cd to that +directory, and call cygport: + + cygport openssh.cygport almostall + +You must have installed the following packages to be able to build OpenSSH +with the aforementioned cygport script: + + zlib + crypt + openssl-devel + libwrap-devel + libedit-devel + libkrb5-devel Please send requests, error reports etc. to cygwin at cygwin.com. Index: contrib/cygwin/ssh-host-config =================================================================== RCS file: /cvs/openssh/contrib/cygwin/ssh-host-config,v retrieving revision 1.32 diff -u -p -r1.32 ssh-host-config --- contrib/cygwin/ssh-host-config 22 Jun 2012 12:02:43 -0000 1.32 +++ contrib/cygwin/ssh-host-config 2 Jul 2013 08:16:43 -0000 @@ -606,9 +606,9 @@ do echo " --no -n Answer all questions with \"no\" automatically." echo " --cygwin -c Use \"options\" as value for CYGWIN environment var." echo " --port -p sshd listens on port n." - echo " --user -u privileged user for service." + echo " --user -u privileged user for service, default 'cyg_server'." echo " --pwd -w Use \"pwd\" as password for privileged user." - echo " --privileged On Windows NT/2k/XP, require privileged user" + echo " --privileged On Windows XP, require privileged user" echo " instead of LocalSystem for sshd service." echo exit 1 Index: contrib/cygwin/ssh-user-config =================================================================== RCS file: /cvs/openssh/contrib/cygwin/ssh-user-config,v retrieving revision 1.8 diff -u -p -r1.8 ssh-user-config --- contrib/cygwin/ssh-user-config 6 Feb 2011 02:31:25 -0000 1.8 +++ contrib/cygwin/ssh-user-config 2 Jul 2013 08:16:43 -0000 @@ -222,10 +222,6 @@ do shift ;; - --privileged ) - csih_FORCE_PRIVILEGED_USER=yes - ;; - *) echo "usage: ${PROGNAME} [OPTION]..." echo @@ -236,8 +232,6 @@ do echo " --yes -y Answer all questions with \"yes\" automatically." echo " --no -n Answer all questions with \"no\" automatically." echo " --passphrase -p word Use \"word\" as passphrase automatically." - echo " --privileged On Windows NT/2k/XP, assume privileged user" - echo " instead of LocalSystem for sshd service." echo exit 1 ;; -- Corinna Vinschen Cygwin Maintainer Red Hat From dtucker at zip.com.au Tue Jul 2 20:07:08 2013 From: dtucker at zip.com.au (Darren Tucker) Date: Tue, 2 Jul 2013 20:07:08 +1000 Subject: [patch/cygwin]: Fix documentation In-Reply-To: <20130702081850.GA4808@calimero.vinschen.de> References: <20130702081850.GA4808@calimero.vinschen.de> Message-ID: On Tue, Jul 2, 2013 at 6:18 PM, Corinna Vinschen wrote: > could somebody with checkin rights please apply the below patch? applied, thanks. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. From des at des.no Fri Jul 5 23:11:57 2013 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Fri, 05 Jul 2013 15:11:57 +0200 Subject: Trouble with -W Message-ID: <8661wp9mn6.fsf@nine.des.no> I want to ssh from a client to a machine on a closed network via a jumphost; let's call them {client,internal,jumphost}.example.com. I have authpf set up on the jumphost so that when logged in, I am allowed to open TCP connections from the jumphost to port 22 on internal nodes. This works well with port forwarding: des at client ~% ssh -L2222:internal.example.com:22 jumphost.example.com but I'd rather use ProxyCommand, so I add something like this to my ~/.ssh/config: Host * ControlMaster auto ControlPath ~/.ssh/cm-%l-%r@%h:%p Host jumphost jumphost.example.com HostName jumphost.example.com HostKeyAlias jumphost.example.com Host internal internal.example.com HostName internal.example.com HostKeyAlias internal.example.com ProxyCommand ssh -vW %h:%p jumphost.example.com I then ssh to the jumphost, which starts authpf and opens a control socket on the client: des at client ~% ssh jumphost.example.com Password: Last login: Fri Jul 5 12:44:48 2013 from client.example.com Hello des. You are authenticated from host "192.168.144.120" I should now be able to ssh to the internal node like this: des at client ~% ssh -v internal.example.com But this doesn't work: [...] debug1: Control socket "/home/des/.ssh/cm-client.example.com-des at internal.example.com:22" does not exist debug1: Executing proxy command: exec ssh -vW internal.example.com:22 jumphost.example.com debug1: permanently_drop_suid: 1001 debug1: identity file /home/des/.ssh/identity type -1 debug1: identity file /home/des/.ssh/id_rsa type 1 debug1: identity file /home/des/.ssh/id_dsa type -1 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Reading configuration data /home/des/.ssh/config debug1: Applying options for * debug1: Applying options for jumphost.example.com debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: auto-mux: Trying existing master ssh_exchange_identification: Connection closed by remote host On the jumphost, I see this: Jul 5 12:46:16 jumphost -authpf-noip: non-interactive session connection for authpf My question is: why did sshd on the jumphost try to execute authpf? Shouldn'it have just opened a TCP connection to internal.example.com:22, as it does with simple port forwarding? Is there a way to get around this? In this example, the client and server both run RHEL 6.4 with OpenSSH 5.3p1, while the jumphost runs FreeBSD 9.1 with OpenSSH 5.8p2. I can live with an answer that says "upgrade to 6.x on the jumphost", but the client and server are outside my control. DES -- Dag-Erling Sm?rgrav - des at des.no From peter at stuge.se Sat Jul 6 00:23:59 2013 From: peter at stuge.se (Peter Stuge) Date: Fri, 5 Jul 2013 16:23:59 +0200 Subject: Trouble with -W In-Reply-To: <8661wp9mn6.fsf@nine.des.no> References: <8661wp9mn6.fsf@nine.des.no> Message-ID: <20130705142359.17396.qmail@stuge.se> Dag-Erling Sm?rgrav wrote: > My question is: why did sshd on the jumphost try to execute authpf? You'll have to answer that yourself I'm afraid.. Maybe PAM is involved? > Shouldn'it have just opened a TCP connection to internal.example.com:22, > as it does with simple port forwarding? Is there a way to get around > this? Try playing with -N and -T. //Peter From des at des.no Sun Jul 7 02:39:36 2013 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Sat, 06 Jul 2013 18:39:36 +0200 Subject: Trouble with -W In-Reply-To: <20130705142359.17396.qmail@stuge.se> (Peter Stuge's message of "Fri, 5 Jul 2013 16:23:59 +0200") References: <8661wp9mn6.fsf@nine.des.no> <20130705142359.17396.qmail@stuge.se> Message-ID: <86txk7zlpz.fsf@nine.des.no> Peter Stuge writes: > Dag-Erling Sm?rgrav writes: > > My question is: why did sshd on the jumphost try to execute authpf? > You'll have to answer that yourself I'm afraid.. Maybe PAM is involved? No, authpf is the user's shell. (FWIW: I wrote FreeBSD's PAM library and most of its modules, as well as the initial version of OpenSSH's current PAM integration, so I'm pretty sure I know what's going on here.) > Try playing with -N and -T. -W implies -NT. DES -- Dag-Erling Sm?rgrav - des at des.no From peter at stuge.se Tue Jul 9 05:23:11 2013 From: peter at stuge.se (Peter Stuge) Date: Mon, 8 Jul 2013 21:23:11 +0200 Subject: Trouble with -W In-Reply-To: <86txk7zlpz.fsf@nine.des.no> References: <8661wp9mn6.fsf@nine.des.no> <20130705142359.17396.qmail@stuge.se> <86txk7zlpz.fsf@nine.des.no> Message-ID: <20130708192311.13791.qmail@stuge.se> Dag-Erling Sm?rgrav wrote: > > > My question is: why did sshd on the jumphost try to execute authpf? > > You'll have to answer that yourself I'm afraid.. Maybe PAM is involved? > > No, authpf is the user's shell. Oh! That wasn't clear to me. Sorry. :) > > Try playing with -N and -T. > > -W implies -NT. Right, it's supposed to, but maybe something is broken? //Peter From des at des.no Tue Jul 9 23:37:51 2013 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Tue, 09 Jul 2013 15:37:51 +0200 Subject: Trouble with -W In-Reply-To: <8661wp9mn6.fsf@nine.des.no> ("Dag-Erling =?utf-8?Q?Sm=C3=B8r?= =?utf-8?Q?grav=22's?= message of "Fri, 05 Jul 2013 15:11:57 +0200") References: <8661wp9mn6.fsf@nine.des.no> Message-ID: <86d2qrrh00.fsf@nine.des.no> It looks like the problem is on the client side. RedHat backported -W to 5.3p1 and clearly didn't do it right; it asks for a session channel instead of a direct-tcpip channel, so the server execs the user's shell. I don't know if that's fixable. DES -- Dag-Erling Sm?rgrav - des at des.no From davidsje at onid.orst.edu Wed Jul 10 09:53:53 2013 From: davidsje at onid.orst.edu (Jen D) Date: Tue, 9 Jul 2013 16:53:53 -0700 Subject: [off topic] [research] Interviews for contributors over 50 for Oregon State University research Message-ID: Hello, Researchers at Oregon State University are striving to conduct research to learn more about the free/open source software community landscape as it relates to older adults. We have identified you as a leader for a free/open source software community. If you?re interested, we will either do an in-person interview (if you are local to the Corvallis or Portland area), or an interview over the phone (if you are not local). The interview is expected to last no longer than an hour. You will not be compensated for participating in this study. The study title is Involving Older Adults in the Design and Development of Free/Open Source Software ? Part 2. The principal investigator is Dr. Carlos Jensen. If you would like to participate in the study, please read through the consent document [1]. Please email us at davidsje at onid.orst.edu to set up a time/location to do an interview. Thank you, Jennifer Davidson Carlos Jensen davidsje at onid.orst.edu cjensen at eecs.oregonstate.edu [1] people.oregonstate.edu/~davidsje/researchForms/groupA/ -- Jennifer Davidson Human-Computer Interaction PhD Student IGERT in Aging Sciences Program Center for Healthy Aging Research Department of Electrical Engineering and Computer Science Oregon State University From davidsje at onid.orst.edu Wed Jul 10 14:33:21 2013 From: davidsje at onid.orst.edu (Jen D) Date: Tue, 9 Jul 2013 21:33:21 -0700 Subject: [off topic] [research] Interviews for contributors over 50 for Oregon State University research In-Reply-To: References: Message-ID: Hello everyone, I apologize, but I sent out the incorrect recruitment email. Here is the correct one: Hello, Researchers at Oregon State University are striving to conduct research to learn more about the free/open source software community landscape as it relates to older adults. We?re looking for older adults who are older than 50 and are currently involved with a free/open source software project. You will be excluded from the study if you are younger than 50, have not contributed to a free/open source software project, or are not fluent in English. If you?re interested, we will either do an in-person interview (if you are local to the Corvallis or Portland area), or an interview over the phone (if you are not local). The interview is expected to last no longer than an hour. You will not be compensated for participating in this study. The study title is Involving Older Adults in the Design and Development of Free/Open Source Software ? Part 2. The principal investigator is Dr. Carlos Jensen. If you would like to participate in the study, please read through the eligibility document and consent document [1]. Please email us at davidsje at onid.orst.edu to set up a time to determine your eligibility and to set up a time/location to do an interview. Thank you, Jennifer Davidson Carlos Jensen davidsje at onid.orst.edu cjensen at eecs.oregonstate.edu [1] people.oregonstate.edu/~davidsje/researchForms/groupB/ On Tue, Jul 9, 2013 at 4:53 PM, Jen D wrote: > Hello, > > Researchers at Oregon State University are striving to conduct > research to learn more about the free/open source software community > landscape as it relates to older adults. We have identified you as a > leader for a free/open source software community. If you?re > interested, we will either do an in-person interview (if you are local > to the Corvallis or Portland area), or an interview over the phone (if > you are not local). The interview is expected to last no longer than > an hour. You will not be compensated for participating in this study. > > The study title is Involving Older Adults in the Design and > Development of Free/Open Source Software ? Part 2. The principal > investigator is Dr. Carlos Jensen. > > If you would like to participate in the study, please read through the > consent document [1]. Please email us at davidsje at onid.orst.edu to set > up a time/location to do an interview. > > Thank you, > > Jennifer Davidson Carlos Jensen > > davidsje at onid.orst.edu cjensen at eecs.oregonstate.edu > > [1] people.oregonstate.edu/~davidsje/researchForms/groupA/ > > > -- > Jennifer Davidson > Human-Computer Interaction PhD Student > IGERT in Aging Sciences Program > Center for Healthy Aging Research > Department of Electrical Engineering and Computer Science > Oregon State University > -- Jennifer Davidson Human-Computer Interaction PhD Student IGERT in Aging Sciences Program Center for Healthy Aging Research Department of Electrical Engineering and Computer Science Oregon State University From beef9999 at qq.com Wed Jul 10 18:43:54 2013 From: beef9999 at qq.com (=?ISO-8859-1?B?Qm9iIENoZW4=?=) Date: Wed, 10 Jul 2013 16:43:54 +0800 Subject: connection_in and connection_out Message-ID: Hi, I'm a newbie to openssh and was trying to read the source code recently. Could anyone tell me why in sshd the connection_in and connection_out are the same(seems to be integer 3 in my machine). connection_in is used in process_input(readset), and connection_out is used in process_output(writeset); But how does it work if it tries to read and write from the same file descriptor? /Bob From singh.ravipratap88 at gmail.com Thu Jul 11 00:27:13 2013 From: singh.ravipratap88 at gmail.com (RAVI PRATAP Singh) Date: Wed, 10 Jul 2013 19:57:13 +0530 Subject: How to set minimum size of accepted rsa key Message-ID: Hi eveyone, Is there a way to set the minimum size accepted by sshd as an RSA public key? I want to restrict users to using RSA keys that are generated with ssh-keygen -b 2048 or greater. I didn't see any option in sshd_config. There is a ServerKeyBits option, but that seems to apply only for SSHv1. Please help me and provide your response.Thanks in advance. Regards Ravi Pratap From djm at mindrot.org Thu Jul 11 10:49:08 2013 From: djm at mindrot.org (Damien Miller) Date: Thu, 11 Jul 2013 10:49:08 +1000 (EST) Subject: connection_in and connection_out In-Reply-To: References: Message-ID: On Wed, 10 Jul 2013, Bob Chen wrote: > Hi, > > > I'm a newbie to openssh and was trying to read the source code > recently. Could anyone tell me why in sshd the connection_in and > connection_out are the same(seems to be integer 3 in my machine). > connection_in is used in process_input(readset), and connection_out is > used in process_output(writeset); But how does it work if it tries to > read and write from the same file descriptor? sockets are bidirectional. If the connection was via a proxy command then they would point to different file descriptors. -d From djm at mindrot.org Thu Jul 11 10:50:30 2013 From: djm at mindrot.org (Damien Miller) Date: Thu, 11 Jul 2013 10:50:30 +1000 (EST) Subject: How to set minimum size of accepted rsa key In-Reply-To: References: Message-ID: On Wed, 10 Jul 2013, RAVI PRATAP Singh wrote: > Hi eveyone, > > Is there a way to set the minimum size accepted by sshd as an RSA public > key? > > I want to restrict users to using RSA keys that are generated with > ssh-keygen -b 2048 or greater. > > I didn't see any option in sshd_config. There is a ServerKeyBits option, > but that seems to apply only for SSHv1. You can set it at compile time only: ssh.h:#define SSH_RSA_MINIMUM_MODULUS_SIZE 768 -d From prashanth.maiya at oracle.com Wed Jul 17 17:06:18 2013 From: prashanth.maiya at oracle.com (Prashanth Maiya) Date: Wed, 17 Jul 2013 00:06:18 -0700 (PDT) Subject: Open SSH configuration query Message-ID: Hi, I have downloaded openssh(http://www.openssh.com/) on my Windows host. Just wanted to know if openssh allows executing a batch script on Windows host. Batch script contains mapping of shares which is required for my scripts. My command run from hpux: $ ssh myscript The myscript requires shares to be mapped on login via batch script. Thanks, Prashanth From m.kaushik at gmail.com Wed Jul 17 20:44:31 2013 From: m.kaushik at gmail.com (Kaushik Muthuravichandran) Date: Wed, 17 Jul 2013 18:44:31 +0800 Subject: Integrating valgrind with sftp-server Message-ID: Hi, I am trying to integrate valgrind with sftp-server. I've replaced the sftp subsystem line in /etc/ssh/sshd_config file as follows: Subsystem sftp /usr/bin/valgrind --log-file=~/abc --trace-children=yes /root/openssh-6.2p2/sftp-server But I am not able to connect to the sftp-server. These are the last messages that the client logs. debug1: Sending subsystem: sftp debug2: channel 0: request subsystem confirm 1 debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel 0: rcvd adjust 2097152 debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug2: channel 0: rcvd eof debug2: channel 0: output open -> drain debug2: channel 0: obuf empty debug2: channel 0: close_write debug2: channel 0: output drain -> closed debug2: channel 0: rcvd close debug2: channel 0: close_read debug2: channel 0: input open -> closed debug3: channel 0: will not send data after close debug2: channel 0: almost dead debug2: channel 0: gc: notify user debug2: channel 0: gc: user detached debug2: channel 0: send close debug2: channel 0: is dead debug2: channel 0: garbage collecting debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open: #0 client-session (t4 r0 i3/0 o3/0 fd -1/-1 cfd -1) debug3: channel 0: close_fds r -1 w -1 e 6 c -1 debug1: fd 0 clearing O_NONBLOCK debug3: fd 1 is not O_NONBLOCK debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 0.0 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 126 Connection closed It works fine when valgrind is not added to the sftp-server command. What is the right way to go about it ? I am using openssh 6.2p2 on Centos 5. Thanks! Kaushik From dtucker at zip.com.au Thu Jul 18 00:45:40 2013 From: dtucker at zip.com.au (Darren Tucker) Date: Thu, 18 Jul 2013 00:45:40 +1000 Subject: Open SSH configuration query In-Reply-To: References: Message-ID: On Wed, Jul 17, 2013 at 5:06 PM, Prashanth Maiya wrote: > I have downloaded openssh (http://www.openssh.com/) on my Windows host. > Just wanted to know if openssh allows executing a batch script on Windows host. > Batch script contains mapping of shares which is required for my scripts. There's no binaries available from openssh.com that run on Windows, however assuming you either have the Cygwin binaries or have compiled OpenSSH using Cygwin, any mapped drives are available under /cygdrive/$driveletter, assuming you're trying to run a script that is Cygwin aware. If it's vanilla Windows batch file then I dunno. The fact that Cygwin works as well as it does is amazing given the differences between Windows and POSIX environments, but OpenSSH targets a POSIX-like environment and I don't know how well it would be able to support a Windows batch file invoked via an ssh command. Perhaps if you provided a bit more information about what you're trying to do we might be able to provide some better advice. Alternatively, you could try it and let us know how it goes. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. From prashanth.maiya at oracle.com Thu Jul 18 01:02:53 2013 From: prashanth.maiya at oracle.com (Prashanth Maiya) Date: Wed, 17 Jul 2013 08:02:53 -0700 (PDT) Subject: Open SSH configuration query In-Reply-To: References: Message-ID: Thanks Darren. Actullay we wanted to run a Windows batch file and then execute a shell script from same SSH command. Windows batch file maps the network drives and later the shell script needs this mapped drives. Thanks, Prashanth -----Original Message----- From: Darren Tucker [mailto:dtucker at zip.com.au] Sent: Wednesday, July 17, 2013 8:16 PM To: Prashanth Maiya Cc: openssh-unix-dev at mindrot.org; Saurabh Bhatnagar Subject: Re: Open SSH configuration query On Wed, Jul 17, 2013 at 5:06 PM, Prashanth Maiya wrote: > I have downloaded openssh (http://www.openssh.com/) on my Windows host. > Just wanted to know if openssh allows executing a batch script on Windows host. > Batch script contains mapping of shares which is required for my scripts. There's no binaries available from openssh.com that run on Windows, however assuming you either have the Cygwin binaries or have compiled OpenSSH using Cygwin, any mapped drives are available under /cygdrive/$driveletter, assuming you're trying to run a script that is Cygwin aware. If it's vanilla Windows batch file then I dunno. The fact that Cygwin works as well as it does is amazing given the differences between Windows and POSIX environments, but OpenSSH targets a POSIX-like environment and I don't know how well it would be able to support a Windows batch file invoked via an ssh command. Perhaps if you provided a bit more information about what you're trying to do we might be able to provide some better advice. Alternatively, you could try it and let us know how it goes. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. From vinschen at redhat.com Thu Jul 18 01:26:45 2013 From: vinschen at redhat.com (Corinna Vinschen) Date: Wed, 17 Jul 2013 17:26:45 +0200 Subject: Open SSH configuration query In-Reply-To: References: Message-ID: <20130717152645.GH32258@calimero.vinschen.de> On Jul 18 00:45, Darren Tucker wrote: > On Wed, Jul 17, 2013 at 5:06 PM, Prashanth Maiya > wrote: > > I have downloaded openssh (http://www.openssh.com/) on my Windows host. > > Just wanted to know if openssh allows executing a batch script on Windows host. > > Batch script contains mapping of shares which is required for my scripts. > > There's no binaries available from openssh.com that run on Windows, > however assuming you either have the Cygwin binaries or have compiled > OpenSSH using Cygwin, any mapped drives are available under > /cygdrive/$driveletter, assuming you're trying to run a script that is > Cygwin aware. Install the Cygwin distro including a Cygwin OpenSSH binary starting here: http://cygwin.com/ > If it's vanilla Windows batch file then I dunno. The fact that Cygwin > works as well as it does is amazing given the differences between > Windows and POSIX environments, but OpenSSH targets a POSIX-like > environment and I don't know how well it would be able to support a > Windows batch file invoked via an ssh command. Remote shares are a bit of a problem due to Windows authentication issues. See http://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-setuid-overview for details how to get the network shares automatically attached when logging in via sshd. Corinna -- Corinna Vinschen Cygwin Maintainer Red Hat From gert at greenie.muc.de Thu Jul 18 04:35:09 2013 From: gert at greenie.muc.de (Gert Doering) Date: Wed, 17 Jul 2013 20:35:09 +0200 Subject: Open SSH configuration query In-Reply-To: References: Message-ID: <20130717183509.GM16543@greenie.muc.de> Hi On Wed, Jul 17, 2013 at 08:02:53AM -0700, Prashanth Maiya wrote: > Thanks Darren. > Actullay we wanted to run a Windows batch file and then execute a shell script from same SSH command. > Windows batch file maps the network drives and later the shell script needs this mapped drives. Then just run the batch file from the shell script? ("cmd.exe /c script.bat" if my memory isn't failing me) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de From djm at mindrot.org Thu Jul 18 10:36:04 2013 From: djm at mindrot.org (Damien Miller) Date: Thu, 18 Jul 2013 10:36:04 +1000 (EST) Subject: Integrating valgrind with sftp-server In-Reply-To: References: Message-ID: On Wed, 17 Jul 2013, Kaushik Muthuravichandran wrote: > Hi, > > I am trying to integrate valgrind with sftp-server. I've replaced the sftp > subsystem line in /etc/ssh/sshd_config file as follows: > > Subsystem sftp /usr/bin/valgrind --log-file=~/abc > --trace-children=yes /root/openssh-6.2p2/sftp-server It's probably because of the '~' in the path: valgrind: --log-file: filename begins with '~' valgrind: You probably expected the shell to expand the '~', but it valgrind: didn't. The rules for '~'-expansion vary from shell to shell. valgrind: You might have more luck using $HOME instead. valgrind: Bad option: --log-file=~/sftp-server.valgrind valgrind: Use --help for more information or consult the user manual. You don't need to run sftp-server via sshd to test it anyway: cat > ~/sftp-server-valgrind << EOF #!/bin/bash valgrind --log-file=${HOME}/sftp-server.valgrind /path/to/openssh/sftp-server EOF sftp -D $HOME/sftp-server-valgrind should do what you want. -d From saurabh.b.bhatnagar at oracle.com Thu Jul 18 12:50:15 2013 From: saurabh.b.bhatnagar at oracle.com (Saurabh Bhatnagar) Date: Wed, 17 Jul 2013 19:50:15 -0700 (PDT) Subject: Open SSH configuration query In-Reply-To: <20130717183509.GM16543@greenie.muc.de> References: <20130717183509.GM16543@greenie.muc.de> Message-ID: Hi Gert, Thanks for the inputs. Our specific requirement is that: We need cygwin to know that when a SSH session is opened onto a Windows build server, it must map the required filer shares as n/w drives in the ksh env. We can't run our shell script in dos shell but in ksh where as the .bat file needs dos shell. My command run from hpux: $ ssh myscript (mapping is implicit) -- Warm Regards, Saurabh Bhatnagar | Development Manager- Software config & Build Mgmt. Phone: +918041836080 | Fax: +918041526000 | VOIP: +918041836080 Oracle Software Engineering ORACLE India | Plot #1, NR ENCLAVE, EPIP INDUSTRIAL AREA, WHITEFIELD | 560066 BANGALORE Oracle is committed to developing practices and products that help protect the environment -----Original Message----- From: Gert Doering [mailto:gert at greenie.muc.de] Sent: Thursday, July 18, 2013 12:05 AM To: Prashanth Maiya Cc: Darren Tucker; Saurabh Bhatnagar; openssh-unix-dev at mindrot.org Subject: Re: Open SSH configuration query Hi On Wed, Jul 17, 2013 at 08:02:53AM -0700, Prashanth Maiya wrote: > Thanks Darren. > Actullay we wanted to run a Windows batch file and then execute a shell script from same SSH command. > Windows batch file maps the network drives and later the shell script needs this mapped drives. Then just run the batch file from the shell script? ("cmd.exe /c script.bat" if my memory isn't failing me) gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany HYPERLINK "mailto:gert at greenie.muc.de"gert at greenie.muc.de fax: +49-89-35655025 HYPERLINK "mailto:gert at net.informatik.tu-muenchen.de"gert at net.informatik.tu-muenchen.de From gert at greenie.muc.de Thu Jul 18 16:42:21 2013 From: gert at greenie.muc.de (Gert Doering) Date: Thu, 18 Jul 2013 08:42:21 +0200 Subject: Open SSH configuration query In-Reply-To: References: <20130717183509.GM16543@greenie.muc.de> Message-ID: <20130718064221.GN16543@greenie.muc.de> Hi, On Wed, Jul 17, 2013 at 07:50:15PM -0700, Saurabh Bhatnagar wrote: > Our specific requirement is that: > > We need cygwin to know that when a SSH session is opened onto a Windows build server, it must map the required filer shares as n/w drives in the ksh env. > > We can't run our shell script in dos shell but in ksh where as the .bat file needs dos shell. You can run cmd.exe from the ksh script, and cmd.exe will run bat files. Please *read* what I write, and spend some time thinking about it (or even testing it), before you claim "it cannot be done". gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de From saurabh.b.bhatnagar at oracle.com Thu Jul 18 18:48:14 2013 From: saurabh.b.bhatnagar at oracle.com (Saurabh Bhatnagar) Date: Thu, 18 Jul 2013 01:48:14 -0700 (PDT) Subject: Open SSH configuration query In-Reply-To: <20130718064221.GN16543@greenie.muc.de> References: <20130717183509.GM16543@greenie.muc.de> <20130718064221.GN16543@greenie.muc.de> Message-ID: <4f547335-79b3-4aa7-99d8-2b4202ae90ea@default> Hi Gert, This is true that we can run the bat file but since this command is run as an argument to passive ssh, it returns back to prompt soon after. What I need is to run the bat and then run my shell script in the *same* shell. This is what I understood: $ssh "cmd.exe /c script.bat" (This will run the bat file and return the prompt) $ What I need is that when I do $ssh mainscript.sh It should find the shares set above. This will not happen as both are different ssh sessions. Let me know now. -- Warm Regards, Saurabh Bhatnagar | Development Manager- Software config & Build Mgmt. Phone: +918041836080 | Fax: +918041526000 | VOIP: +918041836080 Oracle Software Engineering ORACLE India | Plot #1, NR ENCLAVE, EPIP INDUSTRIAL AREA, WHITEFIELD | 560066 BANGALORE Oracle is committed to developing practices and products that help protect the environment -----Original Message----- From: Gert Doering [mailto:gert at greenie.muc.de] Sent: Thursday, July 18, 2013 12:12 PM To: Saurabh Bhatnagar Cc: Gert Doering; Prashanth Maiya; Darren Tucker; openssh-unix-dev at mindrot.org Subject: Re: Open SSH configuration query Hi, On Wed, Jul 17, 2013 at 07:50:15PM -0700, Saurabh Bhatnagar wrote: > Our specific requirement is that: > > We need cygwin to know that when a SSH session is opened onto a Windows build server, it must map the required filer shares as n/w drives in the ksh env. > > We can't run our shell script in dos shell but in ksh where as the .bat file needs dos shell. You can run cmd.exe from the ksh script, and cmd.exe will run bat files. Please *read* what I write, and spend some time thinking about it (or even testing it), before you claim "it cannot be done". gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de From gert at greenie.muc.de Thu Jul 18 20:03:59 2013 From: gert at greenie.muc.de (Gert Doering) Date: Thu, 18 Jul 2013 12:03:59 +0200 Subject: Open SSH configuration query In-Reply-To: <4f547335-79b3-4aa7-99d8-2b4202ae90ea@default> References: <20130717183509.GM16543@greenie.muc.de> <20130718064221.GN16543@greenie.muc.de> <4f547335-79b3-4aa7-99d8-2b4202ae90ea@default> Message-ID: <20130718100359.GO16543@greenie.muc.de> Hi, On Thu, Jul 18, 2013 at 01:48:14AM -0700, Saurabh Bhatnagar wrote: > > $ssh "cmd.exe /c script.bat" > (This will run the bat file and return the prompt) > $ > > What I need is that when I do > $ssh mainscript.sh > It should find the shares set above. Include "cmd.exe /c setup-shares.bat" at the top of mainscript.sh if that script needs the shares. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de From saurabh.b.bhatnagar at oracle.com Thu Jul 18 20:17:19 2013 From: saurabh.b.bhatnagar at oracle.com (Saurabh Bhatnagar) Date: Thu, 18 Jul 2013 03:17:19 -0700 (PDT) Subject: Open SSH configuration query In-Reply-To: <20130718100359.GO16543@greenie.muc.de> References: <20130717183509.GM16543@greenie.muc.de> <20130718064221.GN16543@greenie.muc.de> <4f547335-79b3-4aa7-99d8-2b4202ae90ea@default> <20130718100359.GO16543@greenie.muc.de> Message-ID: <9bce6e24-655a-42e8-b7fd-2b0480a2777b@default> That script is a shell script and runs in ksh(on windows). I am not sure that it will invoke dos shell within the parent shell script. -- Warm Regards, -----Original Message----- From: Gert Doering [mailto:gert at greenie.muc.de] Sent: Thursday, July 18, 2013 3:34 PM To: Saurabh Bhatnagar Cc: Gert Doering; Prashanth Maiya; Darren Tucker; openssh-unix-dev at mindrot.org Subject: Re: Open SSH configuration query Hi, On Thu, Jul 18, 2013 at 01:48:14AM -0700, Saurabh Bhatnagar wrote: > > $ssh "cmd.exe /c script.bat" > (This will run the bat file and return the prompt) $ > > What I need is that when I do > $ssh mainscript.sh > It should find the shares set above. Include "cmd.exe /c setup-shares.bat" at the top of mainscript.sh if that script needs the shares. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de From gert at greenie.muc.de Thu Jul 18 20:24:33 2013 From: gert at greenie.muc.de (Gert Doering) Date: Thu, 18 Jul 2013 12:24:33 +0200 Subject: Open SSH configuration query In-Reply-To: <9bce6e24-655a-42e8-b7fd-2b0480a2777b@default> References: <20130717183509.GM16543@greenie.muc.de> <20130718064221.GN16543@greenie.muc.de> <4f547335-79b3-4aa7-99d8-2b4202ae90ea@default> <20130718100359.GO16543@greenie.muc.de> <9bce6e24-655a-42e8-b7fd-2b0480a2777b@default> Message-ID: <20130718102432.GP16543@greenie.muc.de> Hi, On Thu, Jul 18, 2013 at 03:17:19AM -0700, Saurabh Bhatnagar wrote: > That script is a shell script and runs in ksh(on windows). *I* can read, and have well understood that. > I am not sure that it will invoke dos shell within the parent shell script. Shell scripts call other commands to do their work. One of that command that the "ksh script" starts can be "cmd.exe /c thebatch.bat" - which will execute "thebatch.bat" from within cmd.exe . Why don't you just *try* it? gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de From m.kaushik at gmail.com Thu Jul 18 20:34:34 2013 From: m.kaushik at gmail.com (Kaushik Muthuravichandran) Date: Thu, 18 Jul 2013 18:34:34 +0800 Subject: Integrating valgrind with sftp-server In-Reply-To: References: Message-ID: Hi Damien, I tried replacing the log file with $HOME in the Subsystem line below but that still fails. The alternate way that you suggested works fine. With a limited amount of testing that I did, the valgrind report looks clean. Thanks for your help. Regards, Kaushik On Thu, Jul 18, 2013 at 8:36 AM, Damien Miller wrote: > > > On Wed, 17 Jul 2013, Kaushik Muthuravichandran wrote: > > > Hi, > > > > I am trying to integrate valgrind with sftp-server. I've replaced the > sftp > > subsystem line in /etc/ssh/sshd_config file as follows: > > > > Subsystem sftp /usr/bin/valgrind --log-file=~/abc > > --trace-children=yes /root/openssh-6.2p2/sftp-server > > It's probably because of the '~' in the path: > > valgrind: --log-file: filename begins with '~' > valgrind: You probably expected the shell to expand the '~', but it > valgrind: didn't. The rules for '~'-expansion vary from shell to shell. > valgrind: You might have more luck using $HOME instead. > valgrind: Bad option: --log-file=~/sftp-server.valgrind > valgrind: Use --help for more information or consult the user manual. > > You don't need to run sftp-server via sshd to test it anyway: > > cat > ~/sftp-server-valgrind << EOF > #!/bin/bash > > valgrind --log-file=${HOME}/sftp-server.valgrind > /path/to/openssh/sftp-server > EOF > > sftp -D $HOME/sftp-server-valgrind > > should do what you want. > > -d > > From djm at mindrot.org Thu Jul 18 21:50:03 2013 From: djm at mindrot.org (Damien Miller) Date: Thu, 18 Jul 2013 21:50:03 +1000 (EST) Subject: Integrating valgrind with sftp-server In-Reply-To: References: Message-ID: On Thu, 18 Jul 2013, Kaushik Muthuravichandran wrote: > Hi Damien, > > I tried replacing the log file with $HOME in the Subsystem line below but > that still fails. No, that won't work either as subsystem doesn't expand arguments. > The alternate way that you suggested works fine. With a limited amount of > testing that I did, the valgrind report looks clean. Yay :) -d From L-marks at northwestern.edu Thu Jul 18 23:22:52 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Thu, 18 Jul 2013 08:22:52 -0500 Subject: Any way to over-ride the "-q" option to debug a possible race condition? Message-ID: I have a slightly complicated question. I am using an mpi application (Intel impi) which uses ssh to launch applications. For about 0.1-0.2% of the ssh connections I end up with a zombie, i.e. ps will show [ssh] . Something is going wrong with the ssh when it starts, perhaps a race condition, it is not disconnecting after some time, that I have been able to verify. The most obvious thing I can think of to do is include LogLevel DEBUG in my .ssh/config to try and trace what is going on, but the ssh process is being launched with a "-q" embedded in it which is over-riding this. I am hopeful that there is something I can set to short-circuit the "-q", although I realise that the chance of their being some undocumented option is small (but finite). For reference ssh -V OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 impi 4.1 The structure is that mpirun starts mpiexec.hydra which is turn launches a series of mpi tasks via a ssh connection. N.B., if there are some known issues with that ssh version that may be relevant, information would be useful as I could push on the sys_admin. -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From flavien-ssh at lebarbe.net Fri Jul 19 00:39:28 2013 From: flavien-ssh at lebarbe.net (Flavien) Date: Thu, 18 Jul 2013 16:39:28 +0200 Subject: Any way to over-ride the "-q" option to debug a possible race condition? In-Reply-To: References: Message-ID: <20130718143928.GA5721@srv3.flavien.org> Laurence Marks ecrivait : > [...] > > The most obvious thing I can think of to do is include LogLevel DEBUG > in my .ssh/config to try and trace what is going on, but the ssh > process is being launched with a "-q" embedded in it which is > over-riding this. I am hopeful that there is something I can set to > short-circuit the "-q", although I realise that the chance of their > being some undocumented option is small (but finite). > [....] If you cannot change the command line that calls ssh with "-q", a warkaround can be to change the ssh binary itself to a wrapper that calls ssh without the "-q". Just move the binary to ssh.bin, and have a small shell script named ssh that removes the "-q" option before "exec"-ing ssh.bin. Hope this helps, Flavien. From L-marks at northwestern.edu Fri Jul 19 01:05:20 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Thu, 18 Jul 2013 10:05:20 -0500 Subject: Any way to over-ride the "-q" option to debug a possible race condition? In-Reply-To: References: Message-ID: Thanks, very nice and it even works #!/bin/bash a=`echo $@ | sed -e 's/-q//'` ssh $a On Thu, Jul 18, 2013 at 9:39 AM, Flavien wrote: > Laurence Marks ecrivait : >> [...] >> >> The most obvious thing I can think of to do is include LogLevel DEBUG >> in my .ssh/config to try and trace what is going on, but the ssh >> process is being launched with a "-q" embedded in it which is >> over-riding this. I am hopeful that there is something I can set to >> short-circuit the "-q", although I realise that the chance of their >> being some undocumented option is small (but finite). >> [....] > > If you cannot change the command line that calls ssh with "-q", a > warkaround can be to change the ssh binary itself to a wrapper that > calls ssh without the "-q". > Just move the binary to ssh.bin, and have a small shell script named > ssh that removes the "-q" option before "exec"-ing ssh.bin. > > Hope this helps, > > Flavien. -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From L-marks at northwestern.edu Fri Jul 19 01:09:05 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Thu, 18 Jul 2013 10:09:05 -0500 Subject: Any way to over-ride the "-q" option to debug a possible race condition? In-Reply-To: References: Message-ID: Even better is a=`echo $@ | sed -e 's/-q/-v/'` On Thu, Jul 18, 2013 at 10:05 AM, Laurence Marks wrote: > Thanks, very nice and it even works > > #!/bin/bash > a=`echo $@ | sed -e 's/-q//'` > ssh $a > > > On Thu, Jul 18, 2013 at 9:39 AM, Flavien wrote: >> Laurence Marks ecrivait : >>> [...] >>> >>> The most obvious thing I can think of to do is include LogLevel DEBUG >>> in my .ssh/config to try and trace what is going on, but the ssh >>> process is being launched with a "-q" embedded in it which is >>> over-riding this. I am hopeful that there is something I can set to >>> short-circuit the "-q", although I realise that the chance of their >>> being some undocumented option is small (but finite). >>> [....] >> >> If you cannot change the command line that calls ssh with "-q", a >> warkaround can be to change the ssh binary itself to a wrapper that >> calls ssh without the "-q". >> Just move the binary to ssh.bin, and have a small shell script named >> ssh that removes the "-q" option before "exec"-ing ssh.bin. >> >> Hope this helps, >> >> Flavien. > > > > -- > Professor Laurence Marks > Department of Materials Science and Engineering > Northwestern University > www.numis.northwestern.edu 1-847-491-3996 > "Research is to see what everybody else has seen, and to think what > nobody else has thought" > Albert Szent-Gyorgi -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From L-marks at northwestern.edu Fri Jul 19 03:38:52 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Thu, 18 Jul 2013 12:38:52 -0500 Subject: 001: RELIABILITY FIX: March 15, 2013 Message-ID: Can someone please provide me with a little more information about this. It could be the source of some issues I am seeing with mpirun/mpiexec.hydra/ssh (post earlier today), and information about what it leads to (and any signatures) would be helpful. Thanks. -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From djm at mindrot.org Fri Jul 19 09:36:17 2013 From: djm at mindrot.org (Damien Miller) Date: Fri, 19 Jul 2013 09:36:17 +1000 (EST) Subject: 001: RELIABILITY FIX: March 15, 2013 In-Reply-To: References: Message-ID: On Thu, 18 Jul 2013, Laurence Marks wrote: > Can someone please provide me with a little more information about > this. It could be the source of some issues I am seeing with > mpirun/mpiexec.hydra/ssh (post earlier today), and information about > what it leads to (and any signatures) would be helpful. Thanks. Not sure which patch you are talking about; http://www.openbsd.org/errata53.html has a patch matching "001: RELIABILITY FIX: March 15, 2013" but it applies to OpenBSD's bgpd and doesn't touch OpenSSH. -d From laurence.marks at gmail.com Fri Jul 19 10:48:43 2013 From: laurence.marks at gmail.com (Laurence Marks) Date: Thu, 18 Jul 2013 19:48:43 -0500 Subject: 001: RELIABILITY FIX: March 15, 2013 In-Reply-To: <1027b4517deb4d29b0c9a2af1851de9b@CHCSPCAS1.ads.northwestern.edu> References: <1027b4517deb4d29b0c9a2af1851de9b@CHCSPCAS1.ads.northwestern.edu> Message-ID: My mistake, I thought I was looking at ssh patches but I was on the wrong page. Sorry. --------------------------- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi On Jul 18, 2013 6:36 PM, "Damien Miller" wrote: > On Thu, 18 Jul 2013, Laurence Marks wrote: > > > Can someone please provide me with a little more information about > > this. It could be the source of some issues I am seeing with > > mpirun/mpiexec.hydra/ssh (post earlier today), and information about > > what it leads to (and any signatures) would be helpful. Thanks. > > Not sure which patch you are talking about; > http://www.openbsd.org/errata53.html has a patch matching > "001: RELIABILITY FIX: March 15, 2013" but it applies to OpenBSD's bgpd > and doesn't touch OpenSSH. > > -d > From L-marks at northwestern.edu Sat Jul 20 04:58:36 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Fri, 19 Jul 2013 13:58:36 -0500 Subject: Any way to over-ride the "-q" option to debug a possible race condition? In-Reply-To: References: Message-ID: As a follow up/continuation, which I have solved how to short circuit the "-q", I am stuck with trying to track this issue down. Any and all suggestions welcome. All I can see is (sometimes) in the output log information that the ssh connection was closed, nothing else. This is on Northwestern's (NU) supercomputer, so I don;t have access to the sshd logs. A couple of the NU tech support people have been looking at this, but so far they have nothing. They tell me that there is nothing odd in the sshd logs. There is nothing I can see in the Debug 1 & Debug 3 output to give any hints (I can send these to anyone who is interested as this is beyond my pay grade). Perhaps specific, can anyone give me conditions where ssh can turn into a zombie? Do multiple and near simultaneous access to config files matter? Is there anything that can be tweaked in the code to provide more information about why a connection is closed? Anything else? The main ssh on the computer is OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 ; this morning I compiled the latest tarball (OpenSSH_6.2p2, OpenSSL 1.0.0-fips 29 Mar 2010) and this changed nothing -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From djm at mindrot.org Sat Jul 20 17:32:12 2013 From: djm at mindrot.org (Damien Miller) Date: Sat, 20 Jul 2013 17:32:12 +1000 (EST) Subject: Any way to over-ride the "-q" option to debug a possible race condition? In-Reply-To: References: Message-ID: On Fri, 19 Jul 2013, Laurence Marks wrote: > As a follow up/continuation, which I have solved how to short circuit > the "-q", I am stuck with trying to track this issue down. Any and all > suggestions welcome. > > All I can see is (sometimes) in the output log information that the > ssh connection was closed, nothing else. This is on Northwestern's > (NU) supercomputer, so I don;t have access to the sshd logs. A couple > of the NU tech support people have been looking at this, but so far > they have nothing. They tell me that there is nothing odd in the sshd > logs. There is nothing I can see in the Debug 1 & Debug 3 output to > give any hints (I can send these to anyone who is interested as this > is beyond my pay grade). If we can't see the logs, we can't do much to help other than guess. Sorry. > Perhaps specific, can anyone give me conditions where ssh can turn > into a zombie? Zombie just means that ssh has exited and its parent process has not yet called wait() to collect its status. ssh may have exited for any number of reasons, so this isn't diagnostic of anything. > Do multiple and near simultaneous access to config > files matter? If by "access" you mean reading (which is all that ssh ever does) then no. > Is there anything that can be tweaked in the code to > provide more information about why a connection is closed? Anything > else? You could try to recreate the command that is being executed by whatever is running ssh manually and see what is breaking. -d From laurence.marks at gmail.com Sat Jul 20 22:07:08 2013 From: laurence.marks at gmail.com (Laurence Marks) Date: Sat, 20 Jul 2013 07:07:08 -0500 Subject: Failure to Launch (was override -q option) Message-ID: Attached is the very verbose ssh output. Just to be perverse, this time two nodes lost connectivity. The only thing I see is lines saying that the two connections are lost, although being honest I have no idea what everything else means. For reference, 8 ssh cinnections were being made at the same time for a 8x8mpi task. N.B., since the OS I am using does not have rsh, I am currently using the openmpi mpirun to replace ssh as the launcher while still using the Intel impi for communications. While a gross hack, this seems to be reliable indicating that the issue really is ssh related, but since the problem only occurs for 0.1-0.2 % of the connections I need to let 10 jobs run for a day or so more before I can be certain. -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From djm at mindrot.org Sat Jul 20 22:17:14 2013 From: djm at mindrot.org (Damien Miller) Date: Sat, 20 Jul 2013 22:17:14 +1000 (EST) Subject: Failure to Launch (was override -q option) In-Reply-To: References: Message-ID: On Sat, 20 Jul 2013, Laurence Marks wrote: > Attached is the very verbose ssh output. Sorry, it looks the mailing list software stripped the attachement. To discourage spammers, I've set the software to be rather fascist in deleting anything other than text/plain or text/diff attachments. The easiest ways to avoid it are to post with the text included in the mail itself or stash it on a website somewhere and post the URL. -d From L-marks at northwestern.edu Sun Jul 21 01:43:00 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Sat, 20 Jul 2013 10:43:00 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: References: Message-ID: I've pasted it below, hopefully it is not too long in which case I will use a web site. While it should not matter, the original output was in DOS format (i.e. ^M at the end of lines) even though it was created on a Linux system, e.g. the first Debug was debug1: Reading configuration data /etc/ssh/ssh_config^M debug1: Applying options for *^M The "^M" is getting stripped of when I use my windows computer (wordpad). *************** Contents from here ***************** /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug2: ssh_connect: needpriv 0 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Connecting to qnode0558 [172.20.116.12] port 22. OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connection established. debug1: identity file /home/lma712/.ssh/identity type -1 debug2: ssh_connect: needpriv 0 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: ssh_connect: needpriv 0 debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: identity file /home/lma712/.ssh/id_rsa type 1 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug2: ssh_connect: needpriv 0 debug1: Connecting to qnode0603 [172.20.117.15] port 22. debug1: Connection established. debug1: identity file /home/lma712/.ssh/identity type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to qnode0705 [172.20.119.33] port 22. debug1: Connecting to qnode0716 [172.20.120.2] port 22. debug1: Connection established. debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to qnode0721 [172.20.120.7] port 22. debug1: identity file /home/lma712/.ssh/identity type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug1: Connection established. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: ssh_connect: needpriv 0 debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: Connecting to qnode0743 [172.20.120.29] port 22. debug1: identity file /home/lma712/.ssh/identity type -1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: Connection established. debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/identity type -1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: Connecting to qnode0517 [172.20.115.13] port 22. debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: Connection established. debug1: Connection established. debug1: identity file /home/lma712/.ssh/identity type -1 debug1: identity file /home/lma712/.ssh/identity type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: fd 6 setting O_NONBLOCK debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug3: Wrote 24 bytes for a total of 837 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEXINIT received debug3: Wrote 24 bytes for a total of 837 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug2: dh_gen_key: priv key bits set: 141/256 debug2: bits set: 497/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug2: dh_gen_key: priv key bits set: 129/256 debug2: bits set: 521/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 119/256 debug2: bits set: 526/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 125/256 debug2: bits set: 526/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 131/256 debug2: bits set: 514/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 123/256 debug2: bits set: 522/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 133/256 debug2: bits set: 505/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 709 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 569 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 709 debug1: Host 'qnode0558' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:709 debug2: bits set: 493/1024 debug3: check_host_in_hostfile: match line 569 debug1: Host 'qnode0603' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:569 debug2: bits set: 528/1024 debug3: check_host_in_hostfile: match line 608 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 629 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 608 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: check_host_in_hostfile: match line 629 debug1: Host 'qnode0716' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:608 debug2: bits set: 518/1024 debug1: Host 'qnode0705' is known and matches the RSA host key. debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug1: ssh_rsa_verify: signature correct debug1: Found key in /home/lma712/.ssh/known_hosts:629 debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug2: bits set: 512/1024 debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug3: check_host_in_hostfile: match line 759 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 555 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug3: check_host_in_hostfile: match line 759 debug1: Host 'qnode0721' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:759 debug3: check_host_in_hostfile: match line 555 debug1: Host 'qnode0743' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:555 debug2: bits set: 509/1024 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug2: bits set: 506/1024 debug3: check_host_in_hostfile: match line 591 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug1: ssh_rsa_verify: signature correct debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug3: Wrote 48 bytes for a total of 1045 debug3: check_host_in_hostfile: match line 591 debug1: Host 'qnode0517' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:591 debug2: bits set: 506/1024 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2ad3e4f09630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b2c06d91630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2ad77e5a6630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b02a30de630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 Connection closed by 172.20.115.13 debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password Connection closed by 172.20.116.12 debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.117.15. debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b4c47973630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b90549b4630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.119.33. debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.120.29. debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.120.2. debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.120.7. debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Server accepts key: pkalg ssh-rsa blen 277 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information debug1: read PEM private key done: type RSA debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: read PEM private key done: type RSA debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: read PEM private key done: type RSA debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: read PEM private key done: type RSA debug3: Wrote 640 bytes for a total of 2117 debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug3: Wrote 640 bytes for a total of 2117 debug3: Wrote 640 bytes for a total of 2117 debug3: Wrote 640 bytes for a total of 2117 debug3: Wrote 640 bytes for a total of 2117 debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 2 debug2: channel 0: request exec confirm 1 debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug1: Requesting no-more-sessions at openssh.com debug3: Wrote 304 bytes for a total of 2549 debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 3 debug2: channel 0: request exec confirm 1 debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug2: fd 6 setting TCP_NODELAY debug2: callback done debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Wrote 304 bytes for a total of 2549 debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 4 debug2: channel 0: request exec confirm 1 debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 304 bytes for a total of 2549 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug2: channel 0: rcvd adjust 2097152 debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug3: Ignored env _ debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 6 debug2: channel 0: request exec confirm 1 debug2: channel 0: rcvd adjust 2097152 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 304 bytes for a total of 2549 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 5 debug2: channel 0: request exec confirm 1 debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 304 bytes for a total of 2549 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 On Sat, Jul 20, 2013 at 7:17 AM, Damien Miller wrote: > On Sat, 20 Jul 2013, Laurence Marks wrote: > >> Attached is the very verbose ssh output. > > Sorry, it looks the mailing list software stripped the attachement. > To discourage spammers, I've set the software to be rather fascist in > deleting anything other than text/plain or text/diff attachments. > > The easiest ways to avoid it are to post with the text included in the > mail itself or stash it on a website somewhere and post the URL. > > -d -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From djm at mindrot.org Sun Jul 21 08:10:15 2013 From: djm at mindrot.org (Damien Miller) Date: Sun, 21 Jul 2013 08:10:15 +1000 (EST) Subject: Failure to Launch (was override -q option) In-Reply-To: References: Message-ID: On Sat, 20 Jul 2013, Laurence Marks wrote: > I've pasted it below, hopefully it is not too long in which case I > will use a web site. That output was incomplete. It should lots of ssh connections connecting sucessfully to various servers, failing GSSAPI authentication but passing public key authentication, subsequently establishing a session and executing a command. Whatever was causing your ssh processes to exit early was not in that section of log. -d From L-marks at northwestern.edu Sun Jul 21 08:33:45 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Sat, 20 Jul 2013 17:33:45 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> Message-ID: You are right, not sure how that happened. I will try again, the last lines are five of "/hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13" It is looking OK before I send. If it still does not reach you I will use a web page. ****** Contents ***** /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug2: ssh_connect: needpriv 0 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Connecting to qnode0558 [172.20.116.12] port 22. OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connection established. debug1: identity file /home/lma712/.ssh/identity type -1 debug2: ssh_connect: needpriv 0 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: ssh_connect: needpriv 0 debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: identity file /home/lma712/.ssh/id_rsa type 1 OpenSSH_5.3p1, OpenSSL 1.0.0-fips 29 Mar 2010 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug2: ssh_connect: needpriv 0 debug1: Connecting to qnode0603 [172.20.117.15] port 22. debug1: Connection established. debug1: identity file /home/lma712/.ssh/identity type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to qnode0705 [172.20.119.33] port 22. debug1: Connecting to qnode0716 [172.20.120.2] port 22. debug1: Connection established. debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to qnode0721 [172.20.120.7] port 22. debug1: identity file /home/lma712/.ssh/identity type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug1: Connection established. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: ssh_connect: needpriv 0 debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: Connecting to qnode0743 [172.20.120.29] port 22. debug1: identity file /home/lma712/.ssh/identity type -1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: Connection established. debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/identity type -1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: Connecting to qnode0517 [172.20.115.13] port 22. debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: Connection established. debug1: Connection established. debug1: identity file /home/lma712/.ssh/identity type -1 debug1: identity file /home/lma712/.ssh/identity type -1 debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug3: Not a RSA1 key file /home/lma712/.ssh/id_rsa. debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----BEGIN' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug3: key_read: missing whitespace debug2: key_type_from_name: unknown key type '-----END' debug3: key_read: missing keytype debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_rsa type 1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: identity file /home/lma712/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: fd 6 setting O_NONBLOCK debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug3: Wrote 24 bytes for a total of 837 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEXINIT received debug3: Wrote 24 bytes for a total of 837 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug1: Remote protocol version 2.0, remote software version OpenSSH_5.3 debug1: match: OpenSSH_5.3 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug1: Local version string SSH-2.0-OpenSSH_5.3 debug2: fd 6 setting O_NONBLOCK debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug1: SSH2_MSG_KEXINIT sent debug3: Wrote 792 bytes for a total of 813 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug2: dh_gen_key: priv key bits set: 141/256 debug2: bits set: 497/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug1: SSH2_MSG_KEXINIT received debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: none,zlib at openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa,ssh-dss debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-cbc at lysator.liu.se debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5,hmac-sha1,umac-64 at openssh.com,hmac-ripemd160,hmac-ripemd160 at openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: none,zlib at openssh.com debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: found hmac-md5 debug1: kex: server->client aes128-ctr hmac-md5 none debug2: mac_setup: found hmac-md5 debug1: kex: client->server aes128-ctr hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug3: Wrote 24 bytes for a total of 837 debug2: dh_gen_key: priv key bits set: 129/256 debug2: bits set: 521/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 119/256 debug2: bits set: 526/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 125/256 debug2: bits set: 526/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 131/256 debug2: bits set: 514/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 123/256 debug2: bits set: 522/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug2: dh_gen_key: priv key bits set: 133/256 debug2: bits set: 505/1024 debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug3: Wrote 144 bytes for a total of 981 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 709 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 569 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 709 debug1: Host 'qnode0558' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:709 debug2: bits set: 493/1024 debug3: check_host_in_hostfile: match line 569 debug1: Host 'qnode0603' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:569 debug2: bits set: 528/1024 debug3: check_host_in_hostfile: match line 608 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 629 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 608 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: check_host_in_hostfile: match line 629 debug1: Host 'qnode0716' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:608 debug2: bits set: 518/1024 debug1: Host 'qnode0705' is known and matches the RSA host key. debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug1: ssh_rsa_verify: signature correct debug1: Found key in /home/lma712/.ssh/known_hosts:629 debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug2: bits set: 512/1024 debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug3: check_host_in_hostfile: match line 759 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug3: check_host_in_hostfile: match line 555 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug3: check_host_in_hostfile: match line 759 debug1: Host 'qnode0721' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:759 debug3: check_host_in_hostfile: match line 555 debug1: Host 'qnode0743' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:555 debug2: bits set: 509/1024 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug2: bits set: 506/1024 debug3: check_host_in_hostfile: match line 591 debug3: check_host_in_hostfile: filename /home/lma712/.ssh/known_hosts debug1: ssh_rsa_verify: signature correct debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug3: Wrote 48 bytes for a total of 1045 debug3: check_host_in_hostfile: match line 591 debug1: Host 'qnode0517' is known and matches the RSA host key. debug1: Found key in /home/lma712/.ssh/known_hosts:591 debug2: bits set: 506/1024 debug1: ssh_rsa_verify: signature correct debug2: kex_derive_keys debug2: set_newkeys: mode 1 debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug3: Wrote 16 bytes for a total of 997 debug2: set_newkeys: mode 0 debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug3: Wrote 48 bytes for a total of 1045 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2ad3e4f09630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b2c06d91630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2ad77e5a6630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b02a30de630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 Connection closed by 172.20.115.13 debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password Connection closed by 172.20.116.12 debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.117.15. debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b4c47973630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug2: service_accept: ssh-userauth debug1: SSH2_MSG_SERVICE_ACCEPT received debug2: key: /home/lma712/.ssh/identity ((nil)) debug2: key: /home/lma712/.ssh/id_rsa (0x2b90549b4630) debug2: key: /home/lma712/.ssh/id_dsa ((nil)) debug3: Wrote 64 bytes for a total of 1109 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.119.33. debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.120.29. debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.120.2. debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password debug3: start over, passed a different list publickey,gssapi-keyex,gssapi-with-mic,password debug3: preferred gssapi-keyex,gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_lookup gssapi-keyex debug3: remaining preferred: gssapi-with-mic,publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-keyex debug1: Next authentication method: gssapi-keyex debug1: No valid Key exchange context debug2: we did not send a packet, disable method debug3: authmethod_lookup gssapi-with-mic debug3: remaining preferred: publickey,keyboard-interactive,password debug3: authmethod_is_enabled gssapi-with-mic debug1: Next authentication method: gssapi-with-mic debug3: Trying to reverse map address 172.20.120.7. debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Server accepts key: pkalg ssh-rsa blen 277 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug1: Unspecified GSS failure. Minor code may provide more information debug1: read PEM private key done: type RSA debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Unspecified GSS failure. Minor code may provide more information Credentials cache file '/tmp/krb5cc_39379_K5tnHG' not found debug2: we did not send a packet, disable method debug3: authmethod_lookup publickey debug3: remaining preferred: keyboard-interactive,password debug3: authmethod_is_enabled publickey debug1: Next authentication method: publickey debug1: Trying private key: /home/lma712/.ssh/identity debug3: no such identity: /home/lma712/.ssh/identity debug1: Offering public key: /home/lma712/.ssh/id_rsa debug3: send_pubkey_test debug2: we sent a publickey packet, wait for reply debug3: Wrote 368 bytes for a total of 1477 debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: read PEM private key done: type RSA debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: read PEM private key done: type RSA debug1: Server accepts key: pkalg ssh-rsa blen 277 debug2: input_userauth_pk_ok: SHA1 fp 44:90:7a:6a:b6:17:9f:48:07:6e:5b:20:b3:a2:b7:57:a8:87:5d:4a debug3: sign_and_send_pubkey debug1: read PEM private key done: type RSA debug3: Wrote 640 bytes for a total of 2117 debug1: read PEM private key done: type RSA debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug3: Wrote 640 bytes for a total of 2117 debug3: Wrote 640 bytes for a total of 2117 debug3: Wrote 640 bytes for a total of 2117 debug3: Wrote 640 bytes for a total of 2117 debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 2 debug2: channel 0: request exec confirm 1 debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug1: Requesting no-more-sessions at openssh.com debug3: Wrote 304 bytes for a total of 2549 debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug1: Authentication succeeded (publickey). debug2: fd 8 setting O_NONBLOCK debug2: fd 9 setting O_NONBLOCK debug2: fd 13 setting O_NONBLOCK debug1: channel 0: new [client-session] debug3: ssh_session2_open: channel_new: 0 debug2: channel 0: send open debug1: Requesting no-more-sessions at openssh.com debug1: Entering interactive session. debug3: Wrote 128 bytes for a total of 2245 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 3 debug2: channel 0: request exec confirm 1 debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug2: fd 6 setting TCP_NODELAY debug2: callback done debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Wrote 304 bytes for a total of 2549 debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 4 debug2: channel 0: request exec confirm 1 debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 304 bytes for a total of 2549 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug2: channel 0: rcvd adjust 2097152 debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug3: Ignored env _ debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 6 debug2: channel 0: request exec confirm 1 debug2: channel 0: rcvd adjust 2097152 debug2: callback start debug2: client_session2_setup: id 0 debug1: Sending environment. debug3: Ignored env MPILIBS debug3: Ignored env MODULE_VERSION_STACK debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 304 bytes for a total of 2549 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug3: Ignored env MANPATH debug3: Ignored env HOSTNAME debug3: Ignored env MKLINC debug3: Ignored env PBS_VERSION debug3: Ignored env I_MPI_F77 debug3: Ignored env INTEL_LICENSE_FILE debug3: Ignored env INTELLIB debug3: Ignored env MKLPATH debug3: Ignored env MPICC debug3: Ignored env TERM debug3: Ignored env SHELL debug3: Ignored env HOST debug3: Ignored env USE_REMOTE debug3: Ignored env HISTSIZE debug3: Ignored env SSH_CLIENT debug3: Ignored env PBS_JOBNAME debug3: Ignored env TMPDIR debug3: Ignored env LIBRARY_PATH debug3: Ignored env CVSROOT debug3: Ignored env PDFREADER debug3: Ignored env PBS_ENVIRONMENT debug3: Ignored env QTDIR debug3: Ignored env QTINC debug3: Ignored env I_MPI_PLATFORM debug3: Ignored env PBS_O_WORKDIR debug3: Ignored env MIC_LD_LIBRARY_PATH debug3: Ignored env SSH_TTY debug3: Ignored env FFTW debug3: Ignored env USER debug3: Ignored env PBS_TASKNUM debug3: Ignored env GROUP debug3: Ignored env LD_LIBRARY_PATH debug3: Ignored env LS_COLORS debug3: Ignored env PBS_O_HOME debug3: Ignored env CPATH debug3: Ignored env HOSTTYPE debug3: Ignored env PBS_WALLTIME debug3: Ignored env PBS_MOMPORT debug3: Ignored env PBS_GPUFILE debug3: Ignored env PBS_O_QUEUE debug3: Ignored env NLSPATH debug3: Ignored env MPIROOT debug3: Ignored env PATH debug3: Ignored env PBS_O_LOGNAME debug3: Ignored env MODULE_VERSION debug3: Ignored env MAIL debug3: Ignored env I_MPI_FABRICS_LIST debug3: Ignored env PBS_O_LANG debug3: Ignored env MKL_NUM_THREADS debug3: Ignored env PBS_JOBCOOKIE debug3: Ignored env TBBROOT debug3: Ignored env I_MPI_FALLBACK debug3: Ignored env F90 debug3: Ignored env PWD debug3: Ignored env _LMFILES_ debug3: Ignored env EDITOR debug3: Ignored env MKL_DOMAIN_NUM_THREADS debug3: Ignored env KDE_IS_PRELINKED debug3: Ignored env PBS_NODENUM debug3: Ignored env MODULEPATH debug3: Ignored env MOABHOMEDIR debug3: Ignored env LOADEDMODULES debug3: Ignored env KDEDIRS debug3: Ignored env PBS_NUM_NODES debug3: Ignored env I_MPI_HYDRA_RMK debug3: Ignored env P4_GLOBMEMSIZE debug3: Ignored env I_MPI_JOB_CONTEXT debug3: Ignored env I_MPI_F90 debug3: Ignored env PBS_O_SHELL debug3: Ignored env F77 debug3: Ignored env I_MPI_CC debug3: Ignored env MKL_DYNAMIC debug3: Ignored env PBS_JOBID debug3: Ignored env CXX debug3: Ignored env SSH_ASKPASS debug3: Ignored env HISTCONTROL debug3: Ignored env KRB5CCNAME debug3: Ignored env ENVIRONMENT debug3: Ignored env DAPL_DBG_TYPE debug3: Ignored env SHLVL debug3: Ignored env HOME debug3: Ignored env MPI_REMOTE debug3: Ignored env I_MPI_CXX debug3: Ignored env FFTW3 debug3: Ignored env OSTYPE debug3: Ignored env PBS_DEFAULT debug3: Ignored env PBS_O_HOST debug3: Ignored env CFLAGS debug3: Ignored env I_MPI_FC debug3: Ignored env WIENCODE debug3: Ignored env PBS_VNODENUM debug3: Ignored env VENDOR debug3: Ignored env LOGNAME debug3: Ignored env MACHTYPE debug3: Ignored env WIEN_MPIRUN debug3: Ignored env MPIF77 debug3: Ignored env QTLIB debug3: Ignored env CVS_RSH debug3: Ignored env WIEN_GRANULARITY debug3: Ignored env MPIBLACS debug3: Ignored env SSH_CONNECTION debug3: Ignored env PBS_QUEUE debug3: Ignored env MODULESHOME debug3: Ignored env PBS_O_MAIL debug3: Ignored env OMP_NUM_THREADS debug3: Ignored env LESSOPEN debug3: Ignored env PBS_MICFILE debug3: Ignored env INTELROOT debug3: Ignored env WIENROOT debug3: Ignored env CC debug3: Ignored env PBS_NP debug3: Ignored env I_MPI_MPD_TMPDIR debug3: Ignored env PBS_O_SERVER debug3: Ignored env PBS_NUM_PPN debug3: Ignored env INCLUDE debug3: Ignored env SCRATCH debug3: Ignored env G_BROKEN_FILENAMES debug3: Ignored env PBS_NODEFILE debug3: Ignored env PBS_O_PATH debug3: Ignored env MPICXX debug3: Ignored env FFLAGS debug3: Ignored env I_MPI_ROOT debug3: Ignored env module debug3: Ignored env _ debug1: Sending command: /opt/intel/impi/4.1.0/intel64/bin/pmi_proxy --control-port qnode0595:44629 --pmi-connect lazy-cache --pmi-aggregate -s 0 --rmk pbs --launcher ssh --launcher-exec /home/lma712/bin/hssh --demux poll --pgid 0 --enable-stdin 1 --retries 10 --proxy-id 5 debug2: channel 0: request exec confirm 1 debug2: fd 6 setting TCP_NODELAY debug2: callback done debug2: channel 0: open confirm rwindow 0 rmax 32768 debug3: Wrote 304 bytes for a total of 2549 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug2: channel 0: rcvd adjust 2097152 debug2: channel_input_status_confirm: type 99 id 0 debug2: exec request accepted on channel 0 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 debug2: channel 0: rcvd ext data 88 /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: command not found debug2: channel 0: written 88 to efd 13 -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From djm at mindrot.org Sun Jul 21 08:43:21 2013 From: djm at mindrot.org (Damien Miller) Date: Sun, 21 Jul 2013 08:43:21 +1000 (EST) Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> Message-ID: On Sat, 20 Jul 2013, Laurence Marks wrote: > You are right, not sure how that happened. I will try again, the last > lines are five of > "/hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: > command not found > debug2: channel 0: written 88 to efd 13" I see those lines in the log file, but there is nothing to indicate ssh has exited at this point. As far as can be ascertained from the logs, it is either still running happily, has crashed with a SEGV (which seems unlikely given you've tried two different versions) or has been killed with an untrappable signal by its parent process. If there is no more log output and the ssh processes are ending up dead or zombied, then I'd suggest running strace on one of the ssh processes to watch which syscalls it is making and any signals it is receiving. -d From L-marks at northwestern.edu Sun Jul 21 08:39:16 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Sat, 20 Jul 2013 17:39:16 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> Message-ID: Actually, double checking the first email I sent was "right". Can you confirm the lines at the end reach you, the same as below. If you do get everything and there is nothing useful then suggestions about what to look for in syslog etc would be useful as I can then encourage the sys_admin's to look. > > ****** Contents ***** > ..... > /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: > command not found > debug2: channel 0: written 88 to efd 13 > debug2: channel 0: rcvd ext data 88 > /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: > command not found > debug2: channel 0: written 88 to efd 13 > debug2: channel 0: rcvd ext data 88 > /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: > command not found > debug2: channel 0: written 88 to efd 13 > debug2: channel 0: rcvd ext data 88 > /hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: > command not found > debug2: channel 0: written 88 to efd 13 > > -- > Professor Laurence Marks > Department of Materials Science and Engineering > Northwestern University > www.numis.northwestern.edu 1-847-491-3996 > "Research is to see what everybody else has seen, and to think what > nobody else has thought" > Albert Szent-Gyorgi -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From L-marks at northwestern.edu Sun Jul 21 09:02:14 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Sat, 20 Jul 2013 18:02:14 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: Hmmmm. I guess I can create a script to run "strace ssh @". I will have to do a bit of tweaking of a few scripts since I don't want to disturb jobs which are currently running happily using openmpi/mpirun to replace ssh. Can you suggest what flags etc to use with strace? I would prefer to get this right (tomorrow), since what I will have to do is start some (2-4) not so useful jobs then wait 10-36 hrs so they can work through the job queue and one will hopefully hit the 0.1-0.2% failure rate. (I assume it won't be useful to attach strace to an existing zombie.) On Sat, Jul 20, 2013 at 5:43 PM, Damien Miller wrote: > On Sat, 20 Jul 2013, Laurence Marks wrote: > >> You are right, not sure how that happened. I will try again, the last >> lines are five of >> "/hpc/opt/intel/composer_xe_2013/mkl/bin/mklvars.sh: line 93: manpath: >> command not found >> debug2: channel 0: written 88 to efd 13" > > I see those lines in the log file, but there is nothing to indicate > ssh has exited at this point. As far as can be ascertained from the > logs, it is either still running happily, has crashed with a SEGV > (which seems unlikely given you've tried two different versions) or > has been killed with an untrappable signal by its parent process. > > If there is no more log output and the ssh processes are ending up dead > or zombied, then I'd suggest running strace on one of the ssh processes > to watch which syscalls it is making and any signals it is receiving. > > -d > -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From djm at mindrot.org Sun Jul 21 09:24:00 2013 From: djm at mindrot.org (Damien Miller) Date: Sun, 21 Jul 2013 09:24:00 +1000 (EST) Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: On Sat, 20 Jul 2013, Laurence Marks wrote: > Hmmmm. I guess I can create a script to run "strace ssh @". I will > have to do a bit of tweaking of a few scripts since I don't want to > disturb jobs which are currently running happily using openmpi/mpirun > to replace ssh. Maybe something like #!/bin/sh exec strace -ffro ssh.strace ssh "$@" This should make ssh.strace.$PID logs that will be easier to read than everything mushed together. strace output may well contain sensitive information like the contents of private keys. You should either use a test key or send only logs from after the point where authentication has completed (we're only interested in that anyway). -d From dtucker at zip.com.au Sun Jul 21 17:52:40 2013 From: dtucker at zip.com.au (Darren Tucker) Date: Sun, 21 Jul 2013 17:52:40 +1000 Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: On Sun, Jul 21, 2013 at 5:48 PM, Darren Tucker wrote: [...] > The other thing that I'd suggest is using 6.2p2 and the newly-added -E > option to write the debug logs to separate files, ie "ssh -E > ssh.$$.log" ... oh hang on, -E was added after 6.2p2. You could still redirect stderr to separate log files (ie 2> ssh.$$.log) although that will contain both debug logs and stderr from the program being run. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. From dtucker at zip.com.au Sun Jul 21 17:48:49 2013 From: dtucker at zip.com.au (Darren Tucker) Date: Sun, 21 Jul 2013 17:48:49 +1000 Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: On Sun, Jul 21, 2013 at 9:24 AM, Damien Miller wrote: > On Sat, 20 Jul 2013, Laurence Marks wrote: > >> Hmmmm. I guess I can create a script to run "strace ssh @". I will >> have to do a bit of tweaking of a few scripts since I don't want to >> disturb jobs which are currently running happily using openmpi/mpirun >> to replace ssh. > > Maybe something like > > #!/bin/sh > exec strace -ffro ssh.strace ssh "$@" The other thing that I'd suggest is using 6.2p2 and the newly-added -E option to write the debug logs to separate files, ie "ssh -E ssh.$$.log" ... -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. From L-marks at northwestern.edu Sun Jul 21 23:45:36 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Sun, 21 Jul 2013 08:45:36 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: Thanks. After a bit of tweaking (including finding where strace was hidden on the compute nodes) I am running 2000 repeats of the shortest of the three mpi tasks. Hopefully it will hang.... On Sun, Jul 21, 2013 at 2:52 AM, Darren Tucker wrote: > On Sun, Jul 21, 2013 at 5:48 PM, Darren Tucker wrote: > [...] >> The other thing that I'd suggest is using 6.2p2 and the newly-added -E >> option to write the debug logs to separate files, ie "ssh -E >> ssh.$$.log" ... > > oh hang on, -E was added after 6.2p2. You could still redirect stderr > to separate log files (ie 2> ssh.$$.log) although that will contain > both debug logs and stderr from the program being run. > > -- > Darren Tucker (dtucker at zip.com.au) > GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 > Good judgement comes with experience. Unfortunately, the experience > usually comes from bad judgement. -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From L-marks at northwestern.edu Mon Jul 22 23:11:40 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Mon, 22 Jul 2013 08:11:40 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: Murphy's law. I ran 345 repeats of a shorter mpi code and did not find any issue. I am trying a loop of two different mpi codes, and to date nothing. It may be that I will need to run a number of similar jobs in parallel which is tricky to setup reliably with a queueing system. One question: is there any conceivable way if 10-20 tasks are all trying to connect via ssh at the same time that there can be an issue? They would all be accessing the same $HOME/.ssh directory, but different syslog files. (In case it matters, the compute nodes are diskless.) On Sun, Jul 21, 2013 at 8:45 AM, Laurence Marks wrote: > Thanks. After a bit of tweaking (including finding where strace was > hidden on the compute nodes) I am running 2000 repeats of the shortest > of the three mpi tasks. Hopefully it will hang.... > > On Sun, Jul 21, 2013 at 2:52 AM, Darren Tucker wrote: >> On Sun, Jul 21, 2013 at 5:48 PM, Darren Tucker wrote: >> [...] >>> The other thing that I'd suggest is using 6.2p2 and the newly-added -E >>> option to write the debug logs to separate files, ie "ssh -E >>> ssh.$$.log" ... >> >> oh hang on, -E was added after 6.2p2. You could still redirect stderr >> to separate log files (ie 2> ssh.$$.log) although that will contain >> both debug logs and stderr from the program being run. >> >> -- >> Darren Tucker (dtucker at zip.com.au) >> GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 >> Good judgement comes with experience. Unfortunately, the experience >> usually comes from bad judgement. > > > > -- > Professor Laurence Marks > Department of Materials Science and Engineering > Northwestern University > www.numis.northwestern.edu 1-847-491-3996 > "Research is to see what everybody else has seen, and to think what > nobody else has thought" > Albert Szent-Gyorgi -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From L-marks at northwestern.edu Mon Jul 22 23:21:12 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Mon, 22 Jul 2013 08:21:12 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: N.B., I can confirm that this is certainly ssh related somehow. My hack of replacing the ssh connection with openmpi/mpirun is stable, and ~15 jobs have now run for 24-36 hrs without any problems. Of course this does not mean that it is a openssh problem, but links it clearly in my mind to something associated with it that openmpi/mpirun avoids. On Mon, Jul 22, 2013 at 8:11 AM, Laurence Marks wrote: > Murphy's law. I ran 345 repeats of a shorter mpi code and did not find > any issue. I am trying a loop of two different mpi codes, and to date > nothing. > > It may be that I will need to run a number of similar jobs in parallel > which is tricky to setup reliably with a queueing system. One > question: is there any conceivable way if 10-20 tasks are all trying > to connect via ssh at the same time that there can be an issue? They > would all be accessing the same $HOME/.ssh directory, but different > syslog files. (In case it matters, the compute nodes are diskless.) > > On Sun, Jul 21, 2013 at 8:45 AM, Laurence Marks > wrote: >> Thanks. After a bit of tweaking (including finding where strace was >> hidden on the compute nodes) I am running 2000 repeats of the shortest >> of the three mpi tasks. Hopefully it will hang.... >> >> On Sun, Jul 21, 2013 at 2:52 AM, Darren Tucker wrote: >>> On Sun, Jul 21, 2013 at 5:48 PM, Darren Tucker wrote: >>> [...] >>>> The other thing that I'd suggest is using 6.2p2 and the newly-added -E >>>> option to write the debug logs to separate files, ie "ssh -E >>>> ssh.$$.log" ... >>> >>> oh hang on, -E was added after 6.2p2. You could still redirect stderr >>> to separate log files (ie 2> ssh.$$.log) although that will contain >>> both debug logs and stderr from the program being run. >>> >>> -- >>> Darren Tucker (dtucker at zip.com.au) >>> GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 >>> Good judgement comes with experience. Unfortunately, the experience >>> usually comes from bad judgement. >> >> >> >> -- >> Professor Laurence Marks >> Department of Materials Science and Engineering >> Northwestern University >> www.numis.northwestern.edu 1-847-491-3996 >> "Research is to see what everybody else has seen, and to think what >> nobody else has thought" >> Albert Szent-Gyorgi > > > > -- > Professor Laurence Marks > Department of Materials Science and Engineering > Northwestern University > www.numis.northwestern.edu 1-847-491-3996 > "Research is to see what everybody else has seen, and to think what > nobody else has thought" > Albert Szent-Gyorgi -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From gert at greenie.muc.de Mon Jul 22 23:41:50 2013 From: gert at greenie.muc.de (Gert Doering) Date: Mon, 22 Jul 2013 15:41:50 +0200 Subject: Failure to Launch (was override -q option) In-Reply-To: References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> Message-ID: <20130722134150.GK16543@greenie.muc.de> Hi, On Mon, Jul 22, 2013 at 08:11:40AM -0500, Laurence Marks wrote: > It may be that I will need to run a number of similar jobs in parallel > which is tricky to setup reliably with a queueing system. One > question: is there any conceivable way if 10-20 tasks are all trying > to connect via ssh at the same time that there can be an issue? They There is a limit on the number of yet-unauthenticated ssh sessions that the server permits. sshd_config MaxStartups Specifies the maximum number of concurrent unauthenticated con- nections to the SSH daemon. Additional connections will be dropped until authentication succeeds or the LoginGraceTime expires for a connection. The default is 10. this *might* be hitting you... gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de From L-marks at northwestern.edu Mon Jul 22 23:51:53 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Mon, 22 Jul 2013 08:51:53 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: <91b0995a9aee495596c5d3ce06548348@CHCSPCAS2.ads.northwestern.edu> References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> <91b0995a9aee495596c5d3ce06548348@CHCSPCAS2.ads.northwestern.edu> Message-ID: Thanks, a good suggestion. Which sshd daemon would this be? The jobs are running with the local head node a diskless one which has between 8 and 12 cores, and the job is only starting 8 ssh connections. However, it might be that other nodes are also starting ssh connections at the same time. N.B., I do not have read access to sshd_config so I have to ask for that information (just did). On Mon, Jul 22, 2013 at 8:41 AM, Gert Doering wrote: > Hi, > > On Mon, Jul 22, 2013 at 08:11:40AM -0500, Laurence Marks wrote: >> It may be that I will need to run a number of similar jobs in parallel >> which is tricky to setup reliably with a queueing system. One >> question: is there any conceivable way if 10-20 tasks are all trying >> to connect via ssh at the same time that there can be an issue? They > > There is a limit on the number of yet-unauthenticated ssh sessions that > the server permits. > > sshd_config > > MaxStartups > Specifies the maximum number of concurrent unauthenticated con- > nections to the SSH daemon. Additional connections will be > dropped until authentication succeeds or the LoginGraceTime > expires for a connection. The default is 10. > > this *might* be hitting you... > > gert > -- > USENET is *not* the non-clickable part of WWW! > //www.muc.de/~gert/ > Gert Doering - Munich, Germany gert at greenie.muc.de > fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From beef9999 at qq.com Tue Jul 23 12:54:30 2013 From: beef9999 at qq.com (=?ISO-8859-1?B?Qm9iIENoZW4=?=) Date: Tue, 23 Jul 2013 10:54:30 +0800 Subject: openssh dev materials Message-ID: Hi folks, Could you tell me where I can find some documents or introductions about how openssh is implemented? Or, is there any debugging method that can help me understand the source code better? I found openssh consists of so many modules, such as server/client loop, channel, packet, buffer, crypto/authentication, etc. Too complicated to understand... /Bob From imorgan at nas.nasa.gov Wed Jul 24 02:33:05 2013 From: imorgan at nas.nasa.gov (Iain Morgan) Date: Tue, 23 Jul 2013 09:33:05 -0700 Subject: ECDSA key on anoncvs.mindrot.org Message-ID: <20130723163305.GA18047@linux124.nas.nasa.gov> Hello, While running 'cvs up' against the CVS repository for the portable branch of OpenSSH, I received the following warning: % cvs up @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is d0:46:24:c1:63:cf:6b:f2:e3:33:3d:15:62:08:53:72. Please contact your system administrator. Add correct host key in /u/wk/imorgan/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /u/wk/imorgan/.ssh/known_hosts:32 ECDSA host key for anoncvs.mindrot.org has changed and you have requested strict checking. Host key verification failed. cvs [update aborted]: end of file from server (consult above messages if any) So, I'd just like to confirm that the ECDSA key (and possibly the RSA and DSA keys) were legitimately changed. Thanks, -- Iain Morgan From djm at mindrot.org Wed Jul 24 08:18:07 2013 From: djm at mindrot.org (Damien Miller) Date: Wed, 24 Jul 2013 08:18:07 +1000 (EST) Subject: ECDSA key on anoncvs.mindrot.org In-Reply-To: <20130723163305.GA18047@linux124.nas.nasa.gov> References: <20130723163305.GA18047@linux124.nas.nasa.gov> Message-ID: On Tue, 23 Jul 2013, Iain Morgan wrote: > Hello, > > While running 'cvs up' against the CVS repository for the portable > branch of OpenSSH, I received the following warning: > > % cvs up > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > Someone could be eavesdropping on you right now (man-in-the-middle > attack)! Thanks for reporting this. Could you give it a try now? -d From imorgan at nas.nasa.gov Wed Jul 24 11:08:45 2013 From: imorgan at nas.nasa.gov (Iain Morgan) Date: Tue, 23 Jul 2013 18:08:45 -0700 Subject: ECDSA key on anoncvs.mindrot.org In-Reply-To: References: <20130723163305.GA18047@linux124.nas.nasa.gov> Message-ID: <20130724010845.GL21085@linux124.nas.nasa.gov> On Tue, Jul 23, 2013 at 17:18:07 -0500, Damien Miller wrote: > On Tue, 23 Jul 2013, Iain Morgan wrote: > > > Hello, > > > > While running 'cvs up' against the CVS repository for the portable > > branch of OpenSSH, I received the following warning: > > > > % cvs up > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > > IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! > > Someone could be eavesdropping on you right now (man-in-the-middle > > attack)! > > Thanks for reporting this. Could you give it a try now? > > -d Much better now. The original key is working. -- Iain Morgan From djm at mindrot.org Wed Jul 24 11:31:25 2013 From: djm at mindrot.org (Damien Miller) Date: Wed, 24 Jul 2013 11:31:25 +1000 (EST) Subject: ECDSA key on anoncvs.mindrot.org In-Reply-To: <20130724010845.GL21085@linux124.nas.nasa.gov> References: <20130723163305.GA18047@linux124.nas.nasa.gov> <20130724010845.GL21085@linux124.nas.nasa.gov> Message-ID: On Tue, 23 Jul 2013, Iain Morgan wrote: > Much better now. The original key is working. By way of explanation: I run a separate sshd for the anoncvs service and I forgot to restart it, so connections were falling through to the wildcard- bound main sshd. -d From ag4ve.us at gmail.com Wed Jul 24 22:54:17 2013 From: ag4ve.us at gmail.com (shawn wilson) Date: Wed, 24 Jul 2013 08:54:17 -0400 Subject: Universal variables Message-ID: Variables such as %u, %r, etc are only interpreted sometimes. Is there any reason they shouldn't always be expanded? Ie, if I want a config that I could send to many users, I might want to do: User %u123 Thinking that I can derrive a the username from what they are using to login with. However, this doesn't work. So, I started wondering, It's probably harder to limit where these variables are used vs just allowing them universally, so why is this done? From djm at mindrot.org Thu Jul 25 08:51:24 2013 From: djm at mindrot.org (Damien Miller) Date: Thu, 25 Jul 2013 08:51:24 +1000 (EST) Subject: Universal variables In-Reply-To: References: Message-ID: On Wed, 24 Jul 2013, shawn wilson wrote: > Variables such as %u, %r, etc are only interpreted sometimes. Is there > any reason they shouldn't always be expanded? Ie, if I want a config > that I could send to many users, I might want to do: > User %u123 > Thinking that I can derrive a the username from what they are using to > login with. However, this doesn't work. So, I started wondering, It's > probably harder to limit where these variables are used vs just > allowing them universally This isn't true. Every place where we want to expand a variable requires at least three lines of code. -d From djm at mindrot.org Thu Jul 25 13:35:25 2013 From: djm at mindrot.org (Damien Miller) Date: Thu, 25 Jul 2013 13:35:25 +1000 (EST) Subject: Call for testing: OpenSSH-6.3 Message-ID: Hi, OpenSSH 6.3 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This release contains some substantial new features and a number of bugfixes. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH is also available via anonymous CVS using the instructions at http://www.openssh.com/portable.html#cvs or via Mercurial at http://hg.mindrot.org/openssh Running the regression tests supplied with Portable OpenSSH does not require installation and is a simply: $ ./configure && make tests Live testing on suitable non-production systems is also appreciated. Please send reports of success or failure to openssh-unix-dev at mindrot.org. Below is a summary of changes. More detail may be found in the ChangeLog in the portable OpenSSH tarballs. Thanks to the many people who contributed to this release. Changes since OpenSSH 6.2 ========================= This release is predominantly a bugfix release: Features: * sshd(8): add ssh-agent(1) support to sshd(8); allows encrypted hostkeys, or hostkeys on smartcards. * ssh(1)/sshd(8): allow optional time-based rekeying via a second argument to the existing RekeyLimit option. RekeyLimit is now supported in sshd_config as well as on the client. * sshd(8): standardise logging of information during user authentication. The presented key/cert and the remote username (if available) is now logged in the authentication success/failure message on the same log line as the local username, remote host/port and protocol in use. Certificates contents and the key fingerprint of the signing CA are logged too. Including all relevant information on a single line simplifies log analysis as it is no longer necessary to relate information scattered across multiple log entries. * ssh(1): add the ability to query supported ciphers, MAC algorithms, key types and key exchange methods. * ssh(1): support ProxyCommand=- to allow support cases where stdin and stdout already point to the proxy. * ssh(1): allow IdenityFile=none * ssh(1)/sshd(8): add -E option to ssh and sshd to append debugging logs to a specified file instead of stderr or syslog. * sftp(1): add support for resuming partial downloads using the "reget" command and on the sftp commandline or on the "get" commandline using the "-a" (append) option. * ssh(1): add an "IgnoreUnknown" configuration option to selectively suppress errors arising from unknown configuration directives. * sshd(8): add support for submethods to be appended to required authentication methods listed via AuthenticationMethods. Bugfixes: * sshd(8): fix refusal to accept certificate if a key of a different type to the CA key appeared in authorized_keys before the CA key. * ssh(1)/ssh-agent(1)/sshd(8): Use a monotonic time source for timers so that things like keepalives and rekeying will work properly over clock steps. * sftp(1): update progressmeter when data is acknowledged, not when it's sent. bz#2108 * ssh(1)/ssh-keygen(1): improve error messages when the current user does not exist in /etc/passwd; bz#2125 * ssh(1): reset the order in which public keys are tried after partial authentication success. * ssh-agent(1): clean up socket files after SIGINT when in debug mode; bz#2120 * ssh(1) and others: avoid confusing error messages in the case of broken system resolver configurations; bz#2122 * ssh(1): set TCP nodelay for connections started with -N; bz#2124 * ssh(1): correct manual for permission requirements on ~/.ssh/config; bz#2078 * ssh(1): fix ControlPersist timeout not triggering in cases where TCP connections have hung. bz#1917 * ssh(1): properly deatch a ControlPersist master from its controlling terminal. * sftp(1): avoid crashes in libedit when it has been compiled with multi- byte character support. bz#1990 * sshd(8): when running sshd -D, close stderr unless we have explicitly requested logging to stderr. bz#1976, * ssh(1): fix incomplete bzero; bz#2100 * sshd(8): log and error and exit if ChrootDirectory is specified and running without root privileges. * Many improvements to the regression test suite. In particular log files are now saved from ssh and sshd after failures. * Fix a number of memory leaks. bz#1967 bz#2096 and others * sshd(8): fix public key authentication when a :style is appended to the requested username. * ssh(1): do not fatally exit when attempting to cleanup multiplexing- created channels that are incompletely opened. bz#2079 Portable OpenSSH: * Major overhaul of contrib/cygwin/README * Fix unaligned accesses in umac.c for strict-alignment architectures. bz#2101 * Enable -Wsizeof-pointer-memaccess if the compiler supports it. bz#2100 * Fix broken incorrect commandline reporting errors. bz#1448 * Only include SHA256 and ECC-based key exchange methods if libcrypto has the required support. * A number of portability fixes for Android: * Don't try to use lastlog on Android; bz#2111 * Fall back to using openssl's DES_crypt function on platorms that don't have a native crypt() function; bz#2112 * Test for fd_mask, howmany and NFDBITS rather than trying to enumerate the plaforms that don't have them. bz#2085 * Replace S_IWRITE, which isn't standardized, with S_IWUSR, which is. bz#2085 * Add a null implementation of endgrent for platforms that don't have it (eg Android) bz#2087 * Support platforms, such as Android, that lack struct passwd.pw_gecos. bz#2086 Reporting Bugs: =============== - Please read http://www.openssh.com/report.html Security bugs should be reported directly to openssh at openssh.com OpenSSH is brought to you by Markus Friedl, Niels Provos, Theo de Raadt, Kevin Steves, Damien Miller, Darren Tucker, Jason McIntyre, Tim Rice and Ben Lindstrom. From vinschen at redhat.com Fri Jul 26 01:38:23 2013 From: vinschen at redhat.com (Corinna Vinschen) Date: Thu, 25 Jul 2013 17:38:23 +0200 Subject: Call for testing: OpenSSH-6.3 In-Reply-To: References: Message-ID: <20130725153823.GA30021@calimero.vinschen.de> On Jul 25 13:35, Damien Miller wrote: > Hi, > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > on as many platforms and systems as possible. This release contains > some substantial new features and a number of bugfixes. I'm testing from current CVS, and I ran into a problem on Cygwin. The new forwarding.sh regression test testing LocalForward/RemoteForward doesn't work. I'm getting "connection refused" errors. Does this functionality use AF_LOCAL descriptor passing by any chance? If so, it can't work on Cygwin and the test should be disabled. Other than that, 6.3p1 builds fine on Cygwin x86 and x86_64 and all other tests pass. Thanks, Corinna -- Corinna Vinschen Cygwin Maintainer Red Hat From tim at multitalents.net Fri Jul 26 09:07:00 2013 From: tim at multitalents.net (Tim Rice) Date: Thu, 25 Jul 2013 16:07:00 -0700 (PDT) Subject: Call for testing: OpenSSH-6.3 In-Reply-To: <20130725153823.GA30021@calimero.vinschen.de> References: <20130725153823.GA30021@calimero.vinschen.de> Message-ID: On Thu, 25 Jul 2013, Corinna Vinschen wrote: > On Jul 25 13:35, Damien Miller wrote: > > Hi, > > > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > > on as many platforms and systems as possible. This release contains > > some substantial new features and a number of bugfixes. > > I'm testing from current CVS, and I ran into a problem on Cygwin. The > new forwarding.sh regression test testing LocalForward/RemoteForward > doesn't work. I'm getting "connection refused" errors. In case you're building from a read only tree, I've just commited a fix to forwarding.sh for that. -- Tim Rice Multitalents tim at multitalents.net From andyb1 at andy-t.org Fri Jul 26 10:52:09 2013 From: andyb1 at andy-t.org (Andy Tsouladze) Date: Thu, 25 Jul 2013 19:52:09 -0500 (CDT) Subject: Call for testing: OpenSSH-6.3 In-Reply-To: References: Message-ID: openssh-SNAP-20130726.tar.gz compiles and passes all tests on slackware64-14.0. I found it strange that configure script does not try to determine whether md5 passwords are supported by the system, and it defaults to no support. It only checks if --with-md5-passwords was supplied. Is this intended? What are the consequences of running sshd with no md5 password support on a system that does support them? Is there a way to programmatically determine this? Or maybe default should be to support md5 passwords? Regards, Andy On Thu, 25 Jul 2013, Damien Miller wrote: > Hi, > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > on as many platforms and systems as possible. This release contains > some substantial new features and a number of bugfixes. > > Snapshot releases for portable OpenSSH are available from > http://www.mindrot.org/openssh_snap/ > > The OpenBSD version is available in CVS HEAD: > http://www.openbsd.org/anoncvs.html > > Portable OpenSSH is also available via anonymous CVS using the > instructions at http://www.openssh.com/portable.html#cvs or > via Mercurial at http://hg.mindrot.org/openssh > > Running the regression tests supplied with Portable OpenSSH does not > require installation and is a simply: > > $ ./configure && make tests > > Live testing on suitable non-production systems is also > appreciated. Please send reports of success or failure to > openssh-unix-dev at mindrot.org. > > Below is a summary of changes. More detail may be found in the ChangeLog > in the portable OpenSSH tarballs. > > Thanks to the many people who contributed to this release. > > Changes since OpenSSH 6.2 > ========================= > > This release is predominantly a bugfix release: > > Features: > > * sshd(8): add ssh-agent(1) support to sshd(8); allows encrypted hostkeys, > or hostkeys on smartcards. > > * ssh(1)/sshd(8): allow optional time-based rekeying via a second argument > to the existing RekeyLimit option. RekeyLimit is now supported in > sshd_config as well as on the client. > > * sshd(8): standardise logging of information during user authentication. > > The presented key/cert and the remote username (if available) is now > logged in the authentication success/failure message on the same log > line as the local username, remote host/port and protocol in use. > Certificates contents and the key fingerprint of the signing CA are > logged too. > > Including all relevant information on a single line simplifies log > analysis as it is no longer necessary to relate information scattered > across multiple log entries. > > * ssh(1): add the ability to query supported ciphers, MAC algorithms, key > types and key exchange methods. > > * ssh(1): support ProxyCommand=- to allow support cases where stdin and > stdout already point to the proxy. > > * ssh(1): allow IdenityFile=none > > * ssh(1)/sshd(8): add -E option to ssh and sshd to append debugging logs > to a specified file instead of stderr or syslog. > > * sftp(1): add support for resuming partial downloads using the "reget" > command and on the sftp commandline or on the "get" commandline using > the "-a" (append) option. > > * ssh(1): add an "IgnoreUnknown" configuration option to selectively > suppress errors arising from unknown configuration directives. > > * sshd(8): add support for submethods to be appended to required > authentication methods listed via AuthenticationMethods. > > Bugfixes: > > * sshd(8): fix refusal to accept certificate if a key of a different type > to the CA key appeared in authorized_keys before the CA key. > > * ssh(1)/ssh-agent(1)/sshd(8): Use a monotonic time source for timers so > that things like keepalives and rekeying will work properly over clock > steps. > > * sftp(1): update progressmeter when data is acknowledged, not when it's > sent. bz#2108 > > * ssh(1)/ssh-keygen(1): improve error messages when the current user does > not exist in /etc/passwd; bz#2125 > > * ssh(1): reset the order in which public keys are tried after partial > authentication success. > > * ssh-agent(1): clean up socket files after SIGINT when in debug mode; > bz#2120 > > * ssh(1) and others: avoid confusing error messages in the case of broken > system resolver configurations; bz#2122 > > * ssh(1): set TCP nodelay for connections started with -N; bz#2124 > > * ssh(1): correct manual for permission requirements on ~/.ssh/config; > bz#2078 > > * ssh(1): fix ControlPersist timeout not triggering in cases where TCP > connections have hung. bz#1917 > > * ssh(1): properly deatch a ControlPersist master from its controlling > terminal. > > * sftp(1): avoid crashes in libedit when it has been compiled with multi- > byte character support. bz#1990 > > * sshd(8): when running sshd -D, close stderr unless we have explicitly > requested logging to stderr. bz#1976, > > * ssh(1): fix incomplete bzero; bz#2100 > > * sshd(8): log and error and exit if ChrootDirectory is specified and > running without root privileges. > > * Many improvements to the regression test suite. In particular log files > are now saved from ssh and sshd after failures. > > * Fix a number of memory leaks. bz#1967 bz#2096 and others > > * sshd(8): fix public key authentication when a :style is appended to > the requested username. > > * ssh(1): do not fatally exit when attempting to cleanup multiplexing- > created channels that are incompletely opened. bz#2079 > > Portable OpenSSH: > > * Major overhaul of contrib/cygwin/README > > * Fix unaligned accesses in umac.c for strict-alignment architectures. > bz#2101 > > * Enable -Wsizeof-pointer-memaccess if the compiler supports it. bz#2100 > > * Fix broken incorrect commandline reporting errors. bz#1448 > > * Only include SHA256 and ECC-based key exchange methods if libcrypto has > the required support. > > * A number of portability fixes for Android: > * Don't try to use lastlog on Android; bz#2111 > * Fall back to using openssl's DES_crypt function on platorms that don't > have a native crypt() function; bz#2112 > * Test for fd_mask, howmany and NFDBITS rather than trying to enumerate > the plaforms that don't have them. bz#2085 > * Replace S_IWRITE, which isn't standardized, with S_IWUSR, which is. > bz#2085 > * Add a null implementation of endgrent for platforms that don't have > it (eg Android) bz#2087 > * Support platforms, such as Android, that lack struct passwd.pw_gecos. > bz#2086 > > Reporting Bugs: > =============== > > - Please read http://www.openssh.com/report.html > Security bugs should be reported directly to openssh at openssh.com > > OpenSSH is brought to you by Markus Friedl, Niels Provos, Theo de Raadt, > Kevin Steves, Damien Miller, Darren Tucker, Jason McIntyre, Tim Rice and > Ben Lindstrom. > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev > Dr Andy Tsouladze Sr Unix/Storage SysAdmin From djm at mindrot.org Fri Jul 26 11:22:14 2013 From: djm at mindrot.org (Damien Miller) Date: Fri, 26 Jul 2013 11:22:14 +1000 (EST) Subject: Call for testing: OpenSSH-6.3 In-Reply-To: References: Message-ID: On Thu, 25 Jul 2013, Andy Tsouladze wrote: > openssh-SNAP-20130726.tar.gz compiles and passes all tests on > slackware64-14.0. Thanks for testing. > I found it strange that configure script does not try to determine > whether md5 passwords are supported by the system, and it defaults to > no support. It only checks if --with-md5-passwords was supplied. Is > this intended? What are the consequences of running sshd with no md5 > password support on a system that does support them? Is there a way to > programmatically determine this? Or maybe default should be to support > md5 passwords? These days, libc's crypt(3) is expected to handle any style of password hashing in use on the system. Looking at the crypt manpage the Ubuntu box I have at hand, it currently supports olde DES, md5crypt and their own SHA-256 and SHA-512 styles. OpenSSH's --with-md5-passwords dates from a time before wide libc support for anything but DES crypt and where authenticating applications were expected to either supply their own crypt-variants or delegate it to a PAM module that did. OpenSSH could be compiled without PAM support, but still needed to be able to authenticate users, so we needed to supply our own. If you are unable to authenticate without --with-md5-passwords with your usual system passwords, then I'd argue that your system is broken: your password database should be intelligible to your libc's crypt(3) on its own. -d From tim at multitalents.net Fri Jul 26 11:38:46 2013 From: tim at multitalents.net (Tim Rice) Date: Thu, 25 Jul 2013 18:38:46 -0700 (PDT) Subject: forwarding.sh [was: Call for testing: OpenSSH-6.3] In-Reply-To: References: <20130725153823.GA30021@calimero.vinschen.de> Message-ID: On Thu, 25 Jul 2013, Tim Rice wrote: > On Thu, 25 Jul 2013, Corinna Vinschen wrote: > > > On Jul 25 13:35, Damien Miller wrote: > > > Hi, > > > > > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > > > on as many platforms and systems as possible. This release contains > > > some substantial new features and a number of bugfixes. > > > > I'm testing from current CVS, and I ran into a problem on Cygwin. The > > new forwarding.sh regression test testing LocalForward/RemoteForward > > doesn't work. I'm getting "connection refused" errors. > > In case you're building from a read only tree, I've just committed > a fix to forwarding.sh for that. Actually the fix is for building outside the source tree. The fact that it was spotted while building from a read only tree is not relevant. -- Tim Rice Multitalents tim at multitalents.net From vinschen at redhat.com Fri Jul 26 18:43:29 2013 From: vinschen at redhat.com (Corinna Vinschen) Date: Fri, 26 Jul 2013 10:43:29 +0200 Subject: forwarding.sh [was: Call for testing: OpenSSH-6.3] In-Reply-To: References: <20130725153823.GA30021@calimero.vinschen.de> Message-ID: <20130726084329.GP5086@calimero.vinschen.de> On Jul 25 18:38, Tim Rice wrote: > On Thu, 25 Jul 2013, Tim Rice wrote: > > > On Thu, 25 Jul 2013, Corinna Vinschen wrote: > > > > > On Jul 25 13:35, Damien Miller wrote: > > > > Hi, > > > > > > > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > > > > on as many platforms and systems as possible. This release contains > > > > some substantial new features and a number of bugfixes. > > > > > > I'm testing from current CVS, and I ran into a problem on Cygwin. The > > > new forwarding.sh regression test testing LocalForward/RemoteForward > > > doesn't work. I'm getting "connection refused" errors. > > > > In case you're building from a read only tree, I've just committed > > a fix to forwarding.sh for that. > > Actually the fix is for building outside the source tree. The fact > that it was spotted while building from a read only tree is not relevant. Oh, *that* was the problem. Thanks for spotting. Yes, I'm always building outside the source tree, unless the project's build system doesn't allow that. Problem is fixed, all tests pass. However, I have another tiny testsuite problem. The sftp.sh test tests with a buffersize of 5. While this test works fine, it's an excessive performance hit under Cygwin. I tested this in a Windows 8 VM, and the buffersize 5 test alone takes hours. With all other buffersizes, it's a case of seconds. Is there a chance we can disable the buffersize 5 test? Thanks, Corinna -- Corinna Vinschen Cygwin Maintainer Red Hat From des at des.no Sat Jul 27 01:40:30 2013 From: des at des.no (=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?=) Date: Fri, 26 Jul 2013 17:40:30 +0200 Subject: Call for testing: OpenSSH-6.3 In-Reply-To: (Damien Miller's message of "Thu, 25 Jul 2013 13:35:25 +1000 (EST)") References: Message-ID: <86mwp9ba8h.fsf@nine.des.no> Damien Miller writes: > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > on as many platforms and systems as possible. This release contains > some substantial new features and a number of bugfixes. Could you please look into the sftp symlink issue before 6.3? Basically, the sftp hardlink patch included a hunk which converts the symlink target to an absolute path, mirroring the logic used for hardlinks. This is correct for hardlinks but not for symlinks. DES -- Dag-Erling Sm?rgrav - des at des.no From scott_n at xypro.com Sat Jul 27 07:35:37 2013 From: scott_n at xypro.com (Scott Neugroschl) Date: Fri, 26 Jul 2013 21:35:37 +0000 Subject: Call for testing: OpenSSH-6.3 In-Reply-To: References: Message-ID: Mageia 3, 64 bit. All tests passed. 2013-07-27 Snapshot. From djm at mindrot.org Sat Jul 27 14:48:05 2013 From: djm at mindrot.org (Damien Miller) Date: Sat, 27 Jul 2013 14:48:05 +1000 (EST) Subject: Call for testing: OpenSSH-6.3 In-Reply-To: <86mwp9ba8h.fsf@nine.des.no> References: <86mwp9ba8h.fsf@nine.des.no> Message-ID: On Fri, 26 Jul 2013, Dag-Erling Sm?rgrav wrote: > Damien Miller writes: > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > > on as many platforms and systems as possible. This release contains > > some substantial new features and a number of bugfixes. > > Could you please look into the sftp symlink issue before 6.3? > Basically, the sftp hardlink patch included a hunk which converts the > symlink target to an absolute path, mirroring the logic used for > hardlinks. This is correct for hardlinks but not for symlinks. Too late sorry - I'll commit it right after we unlock. This doesn't seem like a recent regression though - AFAIK hardlink support was added over two years ago. -d From beef9999 at qq.com Mon Jul 29 18:01:51 2013 From: beef9999 at qq.com (=?ISO-8859-1?B?Qm9iIENoZW4=?=) Date: Mon, 29 Jul 2013 16:01:51 +0800 Subject: user input in clientloop.c Message-ID: Hi folks, Could you tell me which function in clientloop.c is responsible for reading user keyboard input? What I found are client_make_packets_from_stdin_data() and client_process_input(), but they not for 'compat20' mode. My app runs in 'compat20'. Thanks, Bob From djm at mindrot.org Mon Jul 29 18:28:24 2013 From: djm at mindrot.org (Damien Miller) Date: Mon, 29 Jul 2013 18:28:24 +1000 (EST) Subject: user input in clientloop.c In-Reply-To: References: Message-ID: On Mon, 29 Jul 2013, Bob Chen wrote: > Hi folks, > > > Could you tell me which function in clientloop.c is > responsible for reading user keyboard input? None of them :) For protocol 2, most of the file descriptor interaction is handled by the channels code, so see channels.c. Specifically channel_pre_open() to arm the fd_sets, channel_post_open() => channel_handle_rfd() channel_handle_wfd() and channel_handle_efd() to read or write data. -d From L-marks at northwestern.edu Mon Jul 29 21:57:51 2013 From: L-marks at northwestern.edu (Laurence Marks) Date: Mon, 29 Jul 2013 06:57:51 -0500 Subject: Failure to Launch (was override -q option) In-Reply-To: <91b0995a9aee495596c5d3ce06548348@CHCSPCAS2.ads.northwestern.edu> References: <92cc1a0c7d2344309b80472e77973198@CHCSPCAS1.ads.northwestern.edu> <4f5c2f2377724e0192fcde4fde9754e1@CHCSPCAS2.ads.northwestern.edu> <91b0995a9aee495596c5d3ce06548348@CHCSPCAS2.ads.northwestern.edu> Message-ID: A brief update. It was not MaxStartups which was set to 1000. As a minor clue (perhaps), I tried hard to reproduce the problem by repeatedly running a single 64 core mpi task, but could not. Since when I had this problem I was running ~10 jobs at the same time (all using 64 cores and launching 8 mpi tasks every 5-15 minutes by ssh) this strongly suggests that it is "somehow" congestion related, Wild guesses would include not being able to read or access a ssh related file because it is currently open or something else. Since it is not my cluster (and my personal one is too small to test this on) and I cannot get access to log file information (or much else) I've given up. I am using openmpi/mpirun instead of ssh to create the remote connections and this seems to be 100% reliable (on the cluster I am using). Thanks for your (collective) help, which gave me the clues to the patch I have ended up with. On Mon, Jul 22, 2013 at 8:41 AM, Gert Doering wrote: > Hi, > > On Mon, Jul 22, 2013 at 08:11:40AM -0500, Laurence Marks wrote: >> It may be that I will need to run a number of similar jobs in parallel >> which is tricky to setup reliably with a queueing system. One >> question: is there any conceivable way if 10-20 tasks are all trying >> to connect via ssh at the same time that there can be an issue? They > > There is a limit on the number of yet-unauthenticated ssh sessions that > the server permits. > > sshd_config > > MaxStartups > Specifies the maximum number of concurrent unauthenticated con- > nections to the SSH daemon. Additional connections will be > dropped until authentication succeeds or the LoginGraceTime > expires for a connection. The default is 10. > > this *might* be hitting you... > > gert > -- > USENET is *not* the non-clickable part of WWW! > //www.muc.de/~gert/ > Gert Doering - Munich, Germany gert at greenie.muc.de > fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de -- Professor Laurence Marks Department of Materials Science and Engineering Northwestern University www.numis.northwestern.edu 1-847-491-3996 "Research is to see what everybody else has seen, and to think what nobody else has thought" Albert Szent-Gyorgi From imorgan at nas.nasa.gov Tue Jul 30 08:25:56 2013 From: imorgan at nas.nasa.gov (Iain Morgan) Date: Mon, 29 Jul 2013 15:25:56 -0700 Subject: Call for testing: OpenSSH-6.3 In-Reply-To: References: Message-ID: <20130729222556.GB18047@linux124.nas.nasa.gov> On Wed, Jul 24, 2013 at 22:35:25 -0500, Damien Miller wrote: > Hi, > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > on as many platforms and systems as possible. This release contains > some substantial new features and a number of bugfixes. > All tests passed with the 20130730 snapshot on the following platforms: RHEL 6.4/x86_64 OpenSSL 1.0.0-fips RHEL 6.4/x86_64 OpenSSL 1.0.1e SLES 11 SP1/x86_64 OpenSSL 1.0.1c OS X 10.8.4 OpenSSL 0.9.8x For completeness, I should note that I encountered a hang in try-ciphers on OS X when attempting to build against OpenSSL 1.0.1e. I'm assuming that this is an issue with my build environment, but haven't looked at it closely yet. The support for additional build hardening options which Darren suggested earlier this year seems to be missing. Is this an oversight or simply that there wan't enough testing and feedback in the meantime? I expect it is too late to include the build modifications into this release, but it would be nice to see them in the next one. -- Iain Morgan From dtucker at zip.com.au Tue Jul 30 11:40:42 2013 From: dtucker at zip.com.au (Darren Tucker) Date: Tue, 30 Jul 2013 11:40:42 +1000 Subject: Call for testing: OpenSSH-6.3 In-Reply-To: <20130729222556.GB18047@linux124.nas.nasa.gov> References: <20130729222556.GB18047@linux124.nas.nasa.gov> Message-ID: On Tue, Jul 30, 2013 at 8:25 AM, Iain Morgan wrote: > The support for additional build hardening options which Darren > suggested earlier this year seems to be missing. Is this an oversight or > simply that there wan't enough testing and feedback in the meantime? My experience was that it was a really good way to break compilers in interesting and unusual ways. I ICEd several versions of gcc on a couple of platforms (no current versions, though) and made clang 2.9 to produce a binaries that would spin burning a whole cpu while doing nothing (I reduced that one to a small testcase, however it's not present in current versions). Also, different compilers have different takes on what -Werror means, which didn't help. I'll probably put it in early in the next cycle so there's more time to deal with fallout. -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement. From imorgan at nas.nasa.gov Wed Jul 31 05:46:50 2013 From: imorgan at nas.nasa.gov (Iain Morgan) Date: Tue, 30 Jul 2013 12:46:50 -0700 Subject: Call for testing: OpenSSH-6.3 In-Reply-To: References: Message-ID: <20130730194649.GC18047@linux124.nas.nasa.gov> On Wed, Jul 24, 2013 at 22:35:25 -0500, Damien Miller wrote: > Hi, > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > on as many platforms and systems as possible. This release contains > some substantial new features and a number of bugfixes. > [snip] > > * sftp(1): add support for resuming partial downloads using the "reget" > command and on the sftp commandline or on the "get" commandline using > the "-a" (append) option. > Some initial testing of the reget functionality shows that its interaction with the progress meter code is a bit buggy. In one test, it reported an inordinately high initial rate. In another test, it reported a negative rate. A simple test is to reget a file which was already transferred successfully: sftp> reget testfile.10gb Resuming /nobackupp1/imorgan/testfile.10gb to testfile.10gb /nobackupp1/imorgan/testfile.10gb 100% 10GB -2097151.-9KB/s 00: sftp> -- Iain Morgan From nico at cryptonector.com Wed Jul 31 06:37:14 2013 From: nico at cryptonector.com (Nico Williams) Date: Tue, 30 Jul 2013 15:37:14 -0500 Subject: Bug #866 Message-ID: It's great to see this fixed. It's too bad that: a) I didn't have the sense of humor in 2004 to propose KnownUnknowns, and even UnknownUnknowns (a boolean, natch); b) you used a different parameter name than SunSSH (which uses IgnoreIfUnknown). It may not be too late to do something about either of those... I think the Oracle folks will have no problem adding IgnoreUnknown as an alias of IgnoreIfUnknown, so (b) is not a problem. And humor or lack thereof is not a problem either. So there may be nothing to do here, though if I were at Oracle I'd probably ask you if you could match the SunSSH parameter just to avoid unnecessary divergence. I'm actually more interested in knowing why this got fixed now. I searched the list archives for discussion of the need for this, but found nothing in the past two years (I gave up searching then). Has NFS (or similar) become more widely used by the dev team? Were there off-list requests for this feature? Nico PS: I'm Nicolas.Williams at sun.com, or was anyways. From djm at mindrot.org Wed Jul 31 10:54:52 2013 From: djm at mindrot.org (Damien Miller) Date: Wed, 31 Jul 2013 10:54:52 +1000 (EST) Subject: Bug #866 In-Reply-To: References: Message-ID: On Tue, 30 Jul 2013, Nico Williams wrote: > I'm actually more interested in knowing why this got fixed now. I > searched the list archives for discussion of the need for this, but > found nothing in the past two years (I gave up searching then). Has > NFS (or similar) become more widely used by the dev team? Were there > off-list requests for this feature? Why now? The proliferation of vendor packages that patch in things like GSSAPI-KEX and have default configurations that enable them explicitly. It makes it quite difficult to use custom-compiled packages of OpenSSH on these systems. For the record, I think turning on the attack surface of GSSAPI by default is a Very Bad Decision all by itself. -d From loganaden at gmail.com Wed Jul 31 15:04:36 2013 From: loganaden at gmail.com (Loganaden Velvindron) Date: Wed, 31 Jul 2013 09:04:36 +0400 Subject: openssh-unix-dev Digest, Vol 123, Issue 13 In-Reply-To: References: Message-ID: > > Message: 8 > Date: Tue, 30 Jul 2013 12:46:50 -0700 > From: Iain Morgan > To: Damien Miller > Cc: "openssh-unix-dev at mindrot.org" > Subject: Re: Call for testing: OpenSSH-6.3 > Message-ID: <20130730194649.GC18047 at linux124.nas.nasa.gov> > Content-Type: text/plain; charset=us-ascii > > On Wed, Jul 24, 2013 at 22:35:25 -0500, Damien Miller wrote: > > Hi, > > > > OpenSSH 6.3 is almost ready for release, so we would appreciate testing > > on as many platforms and systems as possible. This release contains > > some substantial new features and a number of bugfixes. > > > [snip] > > > > * sftp(1): add support for resuming partial downloads using the "reget" > > command and on the sftp commandline or on the "get" commandline using > > the "-a" (append) option. > > > > Some initial testing of the reget functionality shows that its > interaction with the progress meter code is a bit buggy. In one test, it > reported an inordinately high initial rate. In another test, it reported > a negative rate. > > A simple test is to reget a file which was already transferred > successfully: > > sftp> reget testfile.10gb > Resuming /nobackupp1/imorgan/testfile.10gb to testfile.10gb > /nobackupp1/imorgan/testfile.10gb 100% 10GB > -2097151.-9KB/s 00: > sftp> > > -- > Iain Morgan > > > I didn't encounter such problems during my testing. I'll try again @ work with huge files and see if I can reproduce this. > ------------------------------ > > _______________________________________________ > openssh-unix-dev mailing list > openssh-unix-dev at mindrot.org > https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev > > > End of openssh-unix-dev Digest, Vol 123, Issue 13 > ************************************************* > -- This message is strictly personal and the opinions expressed do not represent those of my employers, either past or present. From loganaden at gmail.com Wed Jul 31 16:31:24 2013 From: loganaden at gmail.com (Loganaden Velvindron) Date: Wed, 31 Jul 2013 10:31:24 +0400 Subject: openssh-unix-dev Digest, Vol 123, Issue 13 In-Reply-To: References: Message-ID: On Wed, Jul 31, 2013 at 9:04 AM, Loganaden Velvindron wrote: > > >> Message: 8 >> Date: Tue, 30 Jul 2013 12:46:50 -0700 >> From: Iain Morgan >> To: Damien Miller >> Cc: "openssh-unix-dev at mindrot.org" >> Subject: Re: Call for testing: OpenSSH-6.3 >> Message-ID: <20130730194649.GC18047 at linux124.nas.nasa.gov> >> Content-Type: text/plain; charset=us-ascii >> >> On Wed, Jul 24, 2013 at 22:35:25 -0500, Damien Miller wrote: >> > Hi, >> > >> > OpenSSH 6.3 is almost ready for release, so we would appreciate testing >> > on as many platforms and systems as possible. This release contains >> > some substantial new features and a number of bugfixes. >> > >> [snip] >> > >> > * sftp(1): add support for resuming partial downloads using the "reget" >> > command and on the sftp commandline or on the "get" commandline using >> > the "-a" (append) option. >> > >> >> Some initial testing of the reget functionality shows that its >> interaction with the progress meter code is a bit buggy. In one test, it >> reported an inordinately high initial rate. In another test, it reported >> a negative rate. >> >> A simple test is to reget a file which was already transferred >> successfully: >> >> sftp> reget testfile.10gb >> Resuming /nobackupp1/imorgan/testfile.10gb to testfile.10gb >> /nobackupp1/imorgan/testfile.10gb 100% 10GB >> -2097151.-9KB/s 00: >> sftp> >> >> I think I hit a similar case: sftp> reget foo2 Resuming /home/loganaden/foo2 to foo2 /home/loganaden/foo2 100% 2048KB 48.8KB/s 00:42 sftp> reget foo2 Resuming /home/loganaden/foo2 to foo2 /home/loganaden/foo2 100% 2048KB 2.0MB/s 00:00 I'm currently looking into this. > -- >> Iain Morgan >> >> >> I didn't encounter such problems during my testing. I'll try again @ work > with huge files > and see if I can reproduce this. > > > >> ------------------------------ >> >> _______________________________________________ >> openssh-unix-dev mailing list >> openssh-unix-dev at mindrot.org >> https://lists.mindrot.org/mailman/listinfo/openssh-unix-dev >> >> >> End of openssh-unix-dev Digest, Vol 123, Issue 13 >> ************************************************* >> > > > > -- > This message is strictly personal and the opinions expressed do not > represent those of my employers, either past or present. > > > > > -- This message is strictly personal and the opinions expressed do not represent those of my employers, either past or present.