Didn't get chance to try it out from home but I'm sure it's probably a
firewall not letting me out. If I try it on an external connection and
still have issues I'll log it on the off chance ;)
Just did a "heroku stack" and it's saying cedar.
>From all the variations I've tried so far it feels like the following
happens:
- git commands fire off fine (git init, git add, git commit)
- git push to github starts
- It spots the GIT_SSH environmental variable.
- Reads it correctly.
- Can't find the file /app/git_ssh.sh error (unable to fork)
It's really weird, because that file definitely exists. It's almost seems
like the git process spawns "sh" to run the script but it can't see the
/app mount? I'm grabbing at straws if that sounds daft ;)
On Wednesday, April 3, 2013 8:18:49 PM UTC+1, Daniel Farina wrote:
>
> On Wed, Apr 3, 2013 at 8:14 AM, David Boyer
> <[email protected]<javascript:>>
> wrote:
> > Does ssh.sh has execute permissions set correctly?
> > Is ssh.sh sitting in a mount point with `noexec` set? (mount | grep
> noexec)
> >
> > I'll double check these when I get chance (can't seem to access bash
> from
> > work), but in the meantime I tried setting GIT_SSH to just "ssh". It
> ran it
> > without an error, although github refused the push since it wasn't
> > authenticated (as expected).
>
> Interesting. In my recollection, "heroku run" (as in "heroku run
> bash") does not rely on HTTP to do the heavy lifting, unlike most of
> the toolchain. Sounds like it can't navigate a firewall. The
> relevant implementation is here:
>
>
> https://github.com/heroku/heroku/blob/master/lib/heroku/client/rendezvous.rb#L27-L45
>
>
> Although I might guess this problem may have come up before, it's a
> new one to me...it's probably worth a filed issue on Github, although
> I think the odds of this changing Real Soon are not vast :(
>
> And just to double-check: are you using the Cedar stack?
>
> > I read up and GIT_SSH isn't capable of taking command arguments, so most
> > people use a .sh script. I've managed to get rid of the permissions
> error
> > but it now complains about not being able to find the file
> (/app/git_ssh.sh)
> > even though I test for it's existence in the app and it's definitely
> there
> > (also set 0755 permissions to be sure).
> >
> > "error: cannot run /app/git_ssh.sh: No such file or directory\nfatal:
> unable
> > to fork\n"
>
> Something is wrong: if executable bits didn't work in /app, then a ton
> of stuff would be broken.
>
> Here is a dump of the mount table from a fresh app for all involved, I
> think eliminating the noexec suspicion:
>
> ~ $ mount
> rootfs on / type rootfs (rw)
> /dev/loop1 on / type ext3
> (ro,nosuid,nodev,noatime,nodiratime,errors=continue,data=writeback)
> /dev/sda2 on /app type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> /dev/sda2 on /tmp type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> /dev/sda2 on /var/tmp type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> none on /proc type proc (rw,relatime)
> none on /dev type devtmpfs
> (rw,relatime,size=17364800k,nr_inodes=4341200,mode=755)
> none on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
> none on /dev/shm type tmpfs
> (rw,nosuid,nodev,relatime,size=5120k,nr_inodes=1024,mode=700,uid=55751,gid=55751)
>
>
> none on /dev/console type devpts
> (rw,nosuid,noexec,relatime,gid=5,mode=620)
> /dev/sda2 on /etc/passwd type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> /dev/sda2 on /etc/hostname type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> /dev/sda2 on /etc/hosts type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> /dev/sda2 on /etc/profile type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> /dev/sda2 on /etc/bash.bashrc type ext3
> (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
> /dev/sda1 on /etc/resolv.conf type ext3
> (rw,relatime,errors=continue,data=writeback)
>
> --
> fdr
>
--
--
You received this message because you are subscribed to the Google
Groups "Heroku" group.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en_US?hl=en
---
You received this message because you are subscribed to the Google Groups
"Heroku Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
