Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-14 Thread Berant Lemmenes
Argh, premature email sending! On Thu, Nov 14, 2013 at 12:28 PM, Berant Lemmenes wrote: > > On Thu, Nov 14, 2013 at 12:11 PM, Alfredo Deza > wrote: > >> This is just one of the items that caught my attention: >> >> 2013-10-29 15:56:03,982 [ceph11][ERROR ] 2013-10-29 15:56:06.303009 >> 7feaafe8e7

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-14 Thread Berant Lemmenes
On Thu, Nov 14, 2013 at 12:11 PM, Alfredo Deza wrote: > > > From your logs, it looks like you have a lot of errors from attempting > to get monitors running and I can't see how/where ceph-deploy can > be causing them. Are those errors known issues for you? Where they > fixed or those are part of th

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-14 Thread Alfredo Deza
On Wed, Nov 13, 2013 at 8:49 AM, Berant Lemmenes wrote: > > On Wed, Nov 13, 2013 at 8:05 AM, Alfredo Deza > wrote: >> >> >> Oh, and I just noticed you did say Ubuntu, so sysvinit should have >> *not* been enabled at all, this should've been >> Upstart all along. >> >> Again, logs would be super u

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-13 Thread Alfredo Deza
On Wed, Nov 13, 2013 at 8:04 AM, Alfredo Deza wrote: > On Tue, Nov 12, 2013 at 10:19 PM, Berant Lemmenes wrote: >> >> On Tue, Nov 12, 2013 at 7:28 PM, Joao Eduardo Luis >> wrote: >>> >>> >>> This looks an awful lot like you started another instance of an OSD with >>> the same ID while another wa

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-13 Thread Alfredo Deza
On Tue, Nov 12, 2013 at 10:19 PM, Berant Lemmenes wrote: > > On Tue, Nov 12, 2013 at 7:28 PM, Joao Eduardo Luis > wrote: >> >> >> This looks an awful lot like you started another instance of an OSD with >> the same ID while another was running. I'll walk you through the log lines >> that point m

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-12 Thread Berant Lemmenes
On Tue, Nov 12, 2013 at 7:28 PM, Joao Eduardo Luis wrote: > > This looks an awful lot like you started another instance of an OSD with > the same ID while another was running. I'll walk you through the log lines > that point me towards this conclusion. Would still be weird if the admin > sockets

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-12 Thread Joao Eduardo Luis
On 11/12/2013 03:07 PM, Berant Lemmenes wrote: I just restarted an OSD node and none of the admin sockets showed up on reboot (though it joined the cluster fine and all OSDs are happy. The node is a Ubuntu 12.04.3 system originally deployed via ceph-deploy on dumpling. The only thing that stands

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-12 Thread Berant Lemmenes
I just restarted an OSD node and none of the admin sockets showed up on reboot (though it joined the cluster fine and all OSDs are happy. The node is a Ubuntu 12.04.3 system originally deployed via ceph-deploy on dumpling. The only thing that stands out to me is the failure on lock_fsid and the er

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-12 Thread Joao Luis
On Nov 12, 2013 2:38 AM, "Berant Lemmenes" wrote: > > I noticed the same behavior on my dumpling cluster. They wouldn't show up after boot, but after a service restart they were there. > > I haven't tested a node reboot since I upgraded to emperor today. I'll give it a shot tomorrow. > > Thanks, >

Re: [ceph-users] No monitor sockets after upgrading to Emperor

2013-11-11 Thread Berant Lemmenes
I noticed the same behavior on my dumpling cluster. They wouldn't show up after boot, but after a service restart they were there. I haven't tested a node reboot since I upgraded to emperor today. I'll give it a shot tomorrow. Thanks, Berant On Nov 11, 2013 9:29 PM, "Peter Matulis" wrote: > Aft