search

Annotald / annotald

A program for annotation in the Penn Treebank format
GNU General Public License v3.0
8 stars 3 forks source link

still having trouble connecting #57

Open beatrice57 opened 10 years ago

beatrice57 commented 10 years ago

hi aaron,

as far as i can tell by checking by "ps -x" and "jobs" (see below), i don't have another annotald job running, but i'm still getting yesterday's "connection refused" problem. the chrome browser shows a "no data received" alert.

i'm getting the problem both before and after adding the ~/.ssh/config file that you suggested to ariel in connection with issue #46.

any ideas? thanks!

/home/migration/other/MIDENG/MIDDLE-FRENCH/parsed-with-pp> ps -x
Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ
  PID TTY      STAT   TIME COMMAND
 4205 ?        S      0:00 sshd: beatrice@pts/1
 4206 pts/1    Ss     0:00 -tcsh
 4249 pts/1    R+     0:00 ps -x
/home/migration/other/MIDENG/MIDDLE-FRENCH/parsed-with-pp> jobs
/home/migration/other/MIDENG/MIDDLE-FRENCH/parsed-with-pp>

/home/migration/other/MIDENG/MIDDLE-FRENCH/parsed-with-pp> fannotald test.psd
[29/May/2014:12:39:36] ENGINE Listening for SIGHUP.
[29/May/2014:12:39:36] ENGINE Listening for SIGTERM.
[29/May/2014:12:39:36] ENGINE Listening for SIGUSR1.
[29/May/2014:12:39:36] ENGINE Bus STARTING
CherryPy Checker:
The Application mounted at '' has an empty config.

[29/May/2014:12:39:36] ENGINE Started monitor thread '_TimeoutMonitor'.
[29/May/2014:12:39:36] ENGINE Started monitor thread 'Autoreloader'.
[29/May/2014:12:39:36] ENGINE Serving on 127.0.0.1:8080
[29/May/2014:12:39:36] ENGINE Bus STARTED
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
channel 3: open failed: connect failed: Connection refused
aecay commented 10 years ago

It looks like a ssh tunnel problem, which is hard for me to debug. Have you tried tearing down and recreating the tunnel?

beatrice57 commented 10 years ago

i might have, but i’m not sure exactly what you mean by tearing down (and recreating) the tunnel :-)

thanks!

On May 29, 2014, at 1:57 PM, Aaron Ecay notifications@github.com wrote:

It looks like a ssh tunnel problem, which is hard for me to debug. Have you tried tearing down and recreating the tunnel?

— Reply to this email directly or view it on GitHub.

aecay commented 10 years ago

That is, stopping and restarting the ssh command on your local computer which connects you to babel (the one that begins ssh -L etc.)

diertani commented 10 years ago

When I'm having really intractable problems with one tunnel, blowing it up and digging another usually helps.