Great, that worked. I thought I had done that once before.
On Wed, May 22, 2013 at 11:15 AM, < [email protected]> wrote: > Send Clearwater mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.projectclearwater.org/listinfo/clearwater > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Clearwater digest..." > > > Today's Topics: > > 1. Re: ellis install failure (Matt Williams) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 22 May 2013 16:13:50 +0000 > From: Matt Williams <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: Re: [Clearwater] ellis install failure > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > I've looked into how ellis might have not been stopped when "apt-get > remove ellis" was run, but not found any obvious ways to hit this. > > When you hit the problem, do you know what steps you'd taken? You mention > that you'd uninstalled and re-installed, but the > /etc/clearwater/scripts/ellis file had disappeared too. Maybe a failed > uninstall or reinstall in the mean time (other than those reported below)? > > Please let me know if you have any more details on the actions you've > performed on this node. Any detail you can give would be appreciated - I'm > keen to get this install process as reliable as possible! ;) > > Thanks, > > Matt > > From: [email protected] [mailto: > [email protected]] On Behalf Of Matt Williams > Sent: 22 May 2013 15:25 > To: [email protected] > Subject: Re: [Clearwater] ellis install failure > > The issue you're now seeing is that something is already bound to > HTTP_PORT (9888). I think the most likely scenario here is that ellis is > already running - not many processes bind to that port. Please can you > check this by running "ps -eaf | grep ellis"? If you find it is running, > try running "apt-get purge ellis" again (to clear out any remaining > configuration) and then killing any ellis processes you found earlier and > checking that they stay dead. Assuming they do, you should then be OK to > run "apt-get install ellis" and not hit this problem. > > I'll look into how ellis might have continued running even after being > uninstalled. > > Please let me know how you get on. > > Thanks, > > Matt > > From: B Ray [mailto:[email protected]] > Sent: 22 May 2013 15:13 > To: Matt Williams > Subject: Re: [Clearwater] ellis install failure > > Yes, you've described the sequence of events. I did a "remove" and tried > to "install" again. I have executed the "purge" successfully. However, > the "install" is still seeing some existing issue. Also the ellis files do > show in the /var/lib/dpkg/info/ellis.list. > > In addition to a "purge" what other steps need to be done to cleanup and > re-install? > > > Finished processing dependencies for metaswitchcommon==0.1 > / > * Loading iptables rules... > * IPv4... > * IPv6... > [ > OK ] > * Stopping daemon monitor monit > [ OK ] > * Starting daemon monitor monit > [ OK ] > monit: Cannot connect to the monit daemon. Did you start it with http > support? > /usr/share/clearwater/ellis/env/local/lib/python2.7/site-packages/ellis-0.1-py2.7.egg/metaswitch/__init__.py:38: > UserWarning: Module metaswitch was already imported from > /usr/share/clearwater/ellis/env/local/lib/python2.7/site-packages/ellis-0.1-py2.7.egg/metaswitch/__init__.pyc, > but > /usr/share/clearwater/ellis/env/lib/python2.7/site-packages/metaswitchcommon-0.1-py2.7.egg > is being added to sys.path > import pkg_resources > Traceback (most recent call last): > File "/usr/lib/python2.7/runpy.py", line 162, in _run_module_as_main > "__main__", fname, loader, pkg_name) > File "/usr/lib/python2.7/runpy.py", line 72, in _run_code > exec code in run_globals > File > "/usr/share/clearwater/ellis/env/lib/python2.7/site-packages/ellis-0.1-py2.7.egg/metaswitch/ellis/main.py", > line 153, in <module> > standalone() > File > "/usr/share/clearwater/ellis/env/lib/python2.7/site-packages/ellis-0.1-py2.7.egg/metaswitch/ellis/main.py", > line 86, in standalone > http_sockets = bind_sockets(settings.HTTP_PORT) > File > "/usr/share/clearwater/ellis/env/local/lib/python2.7/site-packages/tornado-2.3-py2.7.egg/tornado/netutil.py", > line 268, in bind_sockets > sock.bind(sockaddr) > File "/usr/lib/python2.7/socket.py", line 224, in meth > return getattr(self._sock,name)(*args) > socket.error: [Errno 98] Address already in use > > > On Wed, May 22, 2013 at 8:02 AM, Matt Williams < > [email protected]<mailto:[email protected]>> wrote: > Thanks for your email. I've taken a look and think I've reproduced the > problem, but it's a slightly odd repro. > > Was this the first install attempt of ellis on this host? It's possible > that we could hit this behavior if ellis was installed, uninstalled (via > "apt-get remove") and then this file was manually deleted. "apt-get > remove" doesn't remove configuration files (which > /etc/clearwater/scripts/ellis is considered to be), but as a result > "apt-get install" won't then reinstall them. To tell apt that you want to > remove all trace of the ellis Debian package from your system, run "apt-get > purge ellis" - this will also ensure that subsequent "apt-get install > ellis" commands reinstall them. If the scenario I've described sounds > plausible, please can you try running "apt-get purge ellis" followed by > "apt-get install ellis" and see if this helps? > > I'll look at whether the /etc/clearwater/scripts/* files should really be > considered configuration - if they weren't, this might have avoided the > problems you've seen. > > If the above doesn't help, do you know which version of the ellis package > you tried to install? "apt-get install ellis" should print this as part of > the install process. The /var/lib/dpkg/info/ellis.list should list all the > files it's going to install - is /etc/clearwater/scripts/ellis present in > this list? > > Please let me know how you get on. > > Cheers, > > Matt > > From: [email protected]<mailto: > [email protected]> [mailto: > [email protected]<mailto: > [email protected]>] On Behalf Of B Ray > Sent: 21 May 2013 23:10 > To: [email protected]<mailto: > [email protected]> > Subject: [Clearwater] ellis install failure > > I'm receiving the following error on install of the ellis node. > ......... > Using > /usr/share/clearwater/ellis/env/lib/python2.7/site-packages/mock-1.0.1-py2.7.egg > Finished processing dependencies for metaswitchcommon==0.1 > / > * Loading iptables rules... > * IPv4... > * IPv6... > [ OK ] > /var/lib/dpkg/info/ellis.postinst: 84: /var/lib/dpkg/info/ellis.postinst: > /etc/clearwater/scripts/ellis: not found > dpkg: error processing ellis (--configure): > subprocess installed post-installation script returned error exit status > 127 > Errors were encountered while processing: > ellis > E: Sub-process /usr/bin/dpkg returned an error code (1) > .......... > > [ellis]ubuntu@ip-10-252-159-175:/var/lib/dpkg/info$ cd /etc/clearwater > [ellis]ubuntu@ip-10-252-159-175:/etc/clearwater$ ls > config scripts > [ellis]ubuntu@ip-10-252-159-175:/etc/clearwater$ cd scripts > [ellis]ubuntu@ip-10-252-159-175:/etc/clearwater/scripts$ ls > hostname mmonit restund > [ellis]ubuntu@ip-10-252-159-175:/etc/clearwater/scripts$ > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.projectclearwater.org/pipermail/clearwater/attachments/20130522/82aeed9d/attachment.html > > > > ------------------------------ > > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/listinfo/clearwater > > > End of Clearwater Digest, Vol 2, Issue 4 > **************************************** >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
