Closed GoogleCodeExporter closed 8 years ago
Haven't seen this before. This may happen due to a conflicting port
configuration in
TYPHOONAE_ROOT/etc/supervisord.conf. The default configuration starts the
supervisor as a daemon.
Change the supervisor configuration to run in the foreground. To achieve this
edit
TYPHOONAE_ROOT/etc/supervisord.conf as described here:
1) Delete the [inet_http_server] and [supervisorctl] sections
2) In the [supervisord] section set the nodaemon flag to true
3) Run bin/supervisord
Please let me know if this works for you.
- Tobias
Original comment by tobias.r...@gmail.com
on 22 Feb 2010 at 12:32
It seems removing [inet_http_server] and [supervisorctl] sections permits it to
start
successfully.
Original comment by Noah.Mci...@gmail.com
on 22 Feb 2010 at 3:32
Could you provide the error message with full traceback (if any), please?
Thanks!
- Tobias
Original comment by tobias.r...@gmail.com
on 22 Feb 2010 at 8:21
AFAIK that is the only relevant line. I am wondering what is the error message
for error code -5?
I have tried many different port numbers, there is no difference to the result.
root@nwm:~/typhoonae# bin/supervisord
2010-02-22 12:24:56,193 CRIT Supervisor running as root (no user in config file)
2010-02-22 12:24:56,193 WARN Included extra file
"/root/typhoonae/etc/demo-supervisor.conf" during parsing
Error: Cannot open an HTTP server: socket.error reported -5
For help, use bin/supervisord -h
Original comment by Noah.Mci...@gmail.com
on 22 Feb 2010 at 12:28
This is really strange. I've tried to reproduce the problem on Debian Lenny.
Except that memcached needed the -
u switch (can't run as root without the -u switch) everything worked quite
flawlessly. Have you tried to run
TyphoonAE with a user other than root?
Original comment by tobias.r...@gmail.com
on 22 Feb 2010 at 9:22
Running as a different user results in the exact same error.
It is strange, because the HTTP server used to serve pages from the GAE app
works fine,
so I don't think it is an issue of network configuration.
Original comment by Noah.Mci...@gmail.com
on 22 Feb 2010 at 9:54
The socket.error code -5 indicates that an I/O error occurred. I'm not sure why
an when this happens. Can you
reproduce the issue on another machine? You have successfully run TyphoonAE
before, haven't you?
Original comment by tobias.r...@gmail.com
on 22 Feb 2010 at 11:11
I have previously set up TyphoonAE successfully on two other machines.
The machine this error occurs on is actually a VPS hosted at http://vpslink.com/
I tried reformatting, same problem occurs, I am going to give a different
distro a try
now.
Original comment by Noah.Mci...@gmail.com
on 23 Feb 2010 at 3:18
A very similar problem occurs under Debian 5.0, the only difference is that the
error
code is now -2.
Original comment by Noah.Mci...@gmail.com
on 23 Feb 2010 at 4:21
Not reproducible.
Original comment by tobias.r...@gmail.com
on 5 Mar 2010 at 10:05
Hello,
I've faced this issue too and I have solved this configuring the
'inet_http_server' section as following:
[inet_http_server]
port = 127.0.0.1:9001
username = test
password = test
Notice that in the 'port' parameter I have specificied the localhost address.
I hope this would be useful for you ;-)
Best regards,
Manuel Viera <manuel.viera.tirado@gmail.com> <mviera@yaco.es>
Alejandro Blanco <alejandro.be@gmail.com> <ablanco@yaco.es>
Original comment by korosu.i...@gmail.com
on 30 Nov 2010 at 10:05
Hi,
Thanks a lot for providing this solution. I'm going to add this to the next
release.
- Tobias
Original comment by tobias.r...@gmail.com
on 2 Dec 2010 at 11:16
Original comment by tobias.r...@gmail.com
on 2 Dec 2010 at 11:16
Fixed in the 0.2.0 release.
Original comment by tobias.r...@gmail.com
on 12 Dec 2010 at 11:26
Original issue reported on code.google.com by
Noah.Mci...@gmail.com
on 21 Feb 2010 at 11:17