On Wed, 14 Jan 2009, Sage Weil wrote: > Can you include './ceph -w' output during the startup procedure? That > will tell you what the system is (not) doing. You just need to make sure > ./ceph -w starts up after the .ceph_monmap file has been generated.
# ./ceph -w [opened monmap at .ceph_monmap fsid 892067c5-5d61-7b19-1580-1919e8f088d6] 09.01.15 13:59:36.988138 pg v2: 0 pgs: ; 0 KB data, 0 KB used, 0 KB / 0 KB avail 09.01.15 13:59:36.988555 mds e1: 0/0/1 up 09.01.15 13:59:36.988758 osd e1: 0 osds: 0 up, 0 in 09.01.15 13:59:36.988931 client v1: 0 clients, next is client0 09.01.15 13:59:36.989116 log 09.01.15 13:59:02.495662 unknown0 0.0.0.0:0/0/0 0 : [ERR] mkfs 09.01.15 13:59:40.329350 mds e2: 0/0/1 up, 1 up:standby 09.01.15 13:59:42.690252 mds e3: 1/1/1 up, 1 up:creating ... At first I got the following message in /var/log/messages , but when I changed the monitor port to match the default monitor port it did not appear again. # tail -1 /var/log/messages Jan 15 13:59:40 xp2 kernel: /root/ceph/src/kernel/messenge: mon0 130.238.138.242:6789 connection failed # --jerker ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Ceph-devel mailing list Ceph-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ceph-devel
