Re: Problem with Ceph daemons

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Adam:

 

Not really….

 

-- Unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has begun starting up.

Feb 16 15:01:03 c01 podman[426007]:

Feb 16 15:01:04 c01 bash[426007]: 915d1e19fa0f213902c666371c8e825480e103f85172f3b15d1d5bf2427a87c9

Feb 16 15:01:04 c01 conmon[426038]: debug 2022-02-16T20:01:04.303+0000 7f4f72ff6440  0 deferred set uid:gid to 167:167 (ceph:ceph)

Feb 16 15:01:04 c01 conmon[426038]: debug 2022-02-16T20:01:04.303+0000 7f4f72ff6440  0 ceph version 16.2.7 (dd0603118f56ab514f133c8d2e3adfc983942503) pacific (st>

Feb 16 15:01:04 c01 conmon[426038]: debug 2022-02-16T20:01:04.303+0000 7f4f72ff6440  0 framework: beast

Feb 16 15:01:04 c01 conmon[426038]: debug 2022-02-16T20:01:04.303+0000 7f4f72ff6440  0 framework conf key: port, val: 80

Feb 16 15:01:04 c01 conmon[426038]: debug 2022-02-16T20:01:04.303+0000 7f4f72ff6440  1 radosgw_Main not setting numa affinity

Feb 16 15:01:04 c01 systemd[1]: Started Ceph rgw.obj0.c01.gpqshk for 35194656-893e-11ec-85c8-005056870dae.

-- Subject: Unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has finished start-up

-- Defined-By: systemd

-- Support: https://access.redhat.com/support

--

-- Unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has finished starting up.

--

-- The start-up result is done.

Feb 16 15:01:04 c01 systemd[1]: ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service: Main process exited, code=exited, status=98/n/a

Feb 16 15:01:05 c01 systemd[1]: ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: https://access.redhat.com/support

--

-- The unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has entered the 'failed' state with result 'exit-code'.

Feb 16 15:01:15 c01 systemd[1]: ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service: Service RestartSec=10s expired, scheduling restart.

Feb 16 15:01:15 c01 systemd[1]: ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service: Scheduled restart job, restart counter is at 5.

-- Subject: Automatic restarting of a unit has been scheduled

-- Defined-By: systemd

-- Support: https://access.redhat.com/support

--

-- Automatic restarting of the unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has been scheduled, as the result for

-- the configured Restart= setting for the unit.

Feb 16 15:01:15 c01 systemd[1]: Stopped Ceph rgw.obj0.c01.gpqshk for 35194656-893e-11ec-85c8-005056870dae.

-- Subject: Unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has finished shutting down

-- Defined-By: systemd

-- Support: https://access.redhat.com/support

--

-- Unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has finished shutting down.

Feb 16 15:01:15 c01 systemd[1]: ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service: Start request repeated too quickly.

Feb 16 15:01:15 c01 systemd[1]: ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service: Failed with result 'exit-code'.

-- Subject: Unit failed

-- Defined-By: systemd

-- Support: https://access.redhat.com/support

--

-- The unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has entered the 'failed' state with result 'exit-code'.

Feb 16 15:01:15 c01 systemd[1]: Failed to start Ceph rgw.obj0.c01.gpqshk for 35194656-893e-11ec-85c8-005056870dae.

-- Subject: Unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has failed

-- Defined-By: systemd

-- Support: https://access.redhat.com/support

--

-- Unit ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk.service has failed.

--

-- The result is failed.

 

Ron Gage

Westland, MI

 

From: Adam King <adking@xxxxxxxxxx> 
Sent: Wednesday, February 16, 2022 4:18 PM
To: Ron Gage <ron@xxxxxxxxxxx>
Cc: ceph-users <ceph-users@xxxxxxx>
Subject: Re:  Problem with Ceph daemons

 

Is there anything useful in the rgw daemon's logs? (e.g. journalctl -xeu ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk <mailto:ceph-35194656-893e-11ec-85c8-005056870dae@rgw.obj0.c01.gpqshk> )

 

 - Adam King

 

On Wed, Feb 16, 2022 at 3:58 PM Ron Gage <ron@xxxxxxxxxxx <mailto:ron@xxxxxxxxxxx> > wrote:

Hi everyone!



Looks like I am having some problems with some of my ceph RGW daemons - they
won't stay running.




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux