Re: Node - npm install fails when "node-gyp rebuild" required

Connecting to the bitbucket.org site *seems* to work, but access to the
repo does not. Do I have permission to access the repo?

ssh -v git@xxxxxxxxxxxxx
OpenSSH_6.9p1, OpenSSL 1.0.2h 3 May 2016
debug1: Reading configuration data
/QOpenSys/QIBM/ProdData/SC1/OpenSSH/openssh-4.7p1/etc/ssh_config
debug1: Connecting to bitbucket.org [104.192.143.2] port 22.
debug1: Connection established.
debug1: identity file /home/KTURNER/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/KTURNER/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/KTURNER/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/KTURNER/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/KTURNER/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/KTURNER/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/KTURNER/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/KTURNER/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_6.9
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.4
debug1: match: OpenSSH_6.4 pat OpenSSH* compat 0x04000000
debug1: Authenticating to bitbucket.org:22 as 'git'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr umac-64-etm@xxxxxxxxxxx none
debug1: kex: client->server aes128-ctr umac-64-etm@xxxxxxxxxxx none
debug1: sending SSH2_MSG_KEX_ECDH_INIT
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa
SHA256:zzXQOXSRBEiUtuE8AikJYKwbHaxvSc0ojez9YXaGp1A
debug1: Host 'bitbucket.org' is known and matches the RSA host key.
debug1: Found key in /home/KTURNER/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/KTURNER/.ssh/id_rsa
debug1: Server accepts key: pkalg ssh-rsa blen 279
debug1: read_passphrase: can't open /dev/tty: No such device or address
Enter passphrase for key '/home/KTURNER/.ssh/id_rsa': debug1:
Authentication succeeded (publickey).
Authenticated to bitbucket.org ([104.192.143.2]:22).
debug1: channel 0: new [client-session]
debug1: Requesting no-more-sessions@xxxxxxxxxxx
debug1: Entering interactive session.
tcgetattr: Invalid argument
debug1: Remote: Forced command.
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: Remote: Forced command.
debug1: Remote: Port forwarding disabled.
debug1: Remote: X11 forwarding disabled.
debug1: Remote: Agent forwarding disabled.
debug1: Remote: Pty allocation disabled.
debug1: tty_make_modes: no fd or tio
PTY allocation request failed on channel 0
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug1: client_input_channel_req: channel 0 rtype eow@xxxxxxxxxxx reply 0
logged in as kpturner.
You can use git or hg to connect to Bitbucket. Shell access is disabled.
debug1: channel 0: free: client-session, nchannels 1
Connection to bitbucket.org closed.
Transferred: sent 3384, received 3396 bytes, in 0.2 seconds
Bytes per second: sent 16434.2, received 16492.5
debug1: Exit status 0

git clone git@xxxxxxxxxxxxx:litmis/ibmichroot.git
$
cd /qopensys
$
git clone git@xxxxxxxxxxxxx:litmis/ibmichroot.git
Cloning into 'ibmichroot'...
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
$



-----Original Message-----
From: WEB400 [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Aaron
Bartell
Sent: 06 July 2016 13:46
To: Web Enabling the IBM i (AS/400 and iSeries) <web400@xxxxxxxxxxxx>
Subject: Re: [WEB400] Node - npm install fails when "node-gyp rebuild"
required

How does git running in QSH make the link to my account in bitbucket?

This might be the issue. Are you using QSH or QP2TERM? You will want to
use the latter. Concerning your question, git makes use of ssh which will
look for files /home/<youruserprofile>/.ssh/id_rsa and
/home/<youruserprofile>/.ssh/id_rsa.pub to do the handshake. The
id_rsa.pub's contents is what you should have put on Bitbucket. Then when
a connection is attempted it will compare you private key (id_rsa) to the
one on Bitbucket (id_rsa.pub) for authenticating.

Run the following and paste the contents back here. This do a verbose ssh
session to Bitbucket and convey what files are being used.

$ ssh -v git@xxxxxxxxxxxxx

Aaron Bartell
litmis.com - Services for open source on IBM i



________________________________

NOTICE: The information in this electronic mail transmission is intended
by CoralTree Systems Ltd for the use of the named individuals or entity to
which it is directed and may contain information that is privileged or
otherwise confidential. If you have received this electronic mail
transmission in error, please delete it from your system without copying or
forwarding it, and notify the sender of the error by reply email or by
telephone, so that the sender's address records can be corrected.




--------------------------------------------------------------------------------


CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT

Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.