On 2014-12-24 04:38, Venu Murthy wrote:
Hello Ken,
Try switch to the screen
for eg.
screen -x stack
Oh, wow. Thanks! That sure showed what happened... though I don't know
why. Looks like I'm timing out trying to fetch a .PNG:
------------------------------------------
2014-12-24 01:19:53.404 DEBUG eventlet.wsgi.server [-] 125.64.35.67 - -
[24/Dec/2014 01:19:53] "GET
http://s1.bdstatic.com/r/www/cache/static/home/img/logos/nuomi_ade5465d.png
HTTP/1.1" 404 278 0.003209 from (pid=10629) write
/opt/stack/heat/heat/common/wsgi.py:183
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenpool.py",
line 82, in _spawn_n_impl
func(*args, **kwargs)
File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line
661, in process_request
proto.__init__(sock, address, self)
File "/usr/lib/python2.7/SocketServer.py", line 649, in __init__
self.handle()
File "/usr/lib/python2.7/BaseHTTPServer.py", line 342, in handle
self.handle_one_request()
File "/usr/local/lib/python2.7/dist-packages/eventlet/wsgi.py", line
267, in handle_one_request
self.raw_requestline =
self.rfile.readline(self.server.url_length_limit)
File "/usr/lib/python2.7/socket.py", line 476, in readline
data = self._sock.recv(self._rbufsize)
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenio.py",
line 296, in recv
return fd.recv(buflen, flags)
error: [Errno 110] Connection timed out
------------------------------------------
Upon reflection, I noticed what was probably the same behavior when I
tried to download an Ubuntu cloud image via URL -- it just sat there,
saying it was "queued", but there was zero network I/O. In both cases,
I was able to use the system to successfully download both files using
wget, so it's not a connectivity issue. Why would Python GETs work any
differently than "wget"?
Thanks,
-Ken
Best regards,
Venu
[2]
---
_“Excellence is never an accident. It is always the result of high
intention, sincere effort, and intelligent execution.... ―
Aristotle_
On Wed, Dec 24, 2014 at 11:29 AM, Ken D'Ambrosio <[email protected]> wrote:
Hi, all. Trying to get a feel for OpenStack, so I installed
DevStack. And it works great... until I have the audacity to
restart it. Apache doesn't go fully live unless I do a restart --
and if I do that, I don't get past the login screen (just tells me
that admin had trouble authenticating). Likewise, the few things
I'm even mildly familiar with -- e.g., nova commands -- never seem
to execute, or even return to the CLI. I'm guessing it's getting
hung up on something during rejoin-stack.sh. The log files aren't
showing me anything that leaps to my eye. I've done a full
DevStack re-install from scratch -- same problem.
1) Which log files should I be digging into for more info?
2) Is there a way to get a status on the various components?
3) Should I wipe my Ubuntu 14.04 install entirely, and start from
scratch?
Thanks much -- and Happy Holidays to thems that celebrate 'em!
-Ken
_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]
Post to : [email protected]
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack [1]
Links:
------
[1] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
[2] http://www.thoughtworks.com/
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : [email protected]
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
