Project

General

Profile

Actions

Bug #45142

open

radosgw start failed due to handle_auth_bad_method

Added by Amit Ghadge about 4 years ago. Updated 7 months ago.

Status:
Need More Info
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rgw
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Seen below issue while start fresh deploy radosgw service,

/usr/bin/radosgw -f --cluster ceph --name client.radosgw.masifgw01 --setuser ceph --setgroup ceph --debug_rgw 20
2020-04-19 09:05:05.421 7fe2eeea9700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [1] but i only support [2,1]
failed to fetch mon config (--no-mon-config to skip

set cephx authentication by,
ceph config set mon auth_cluster_required cephx
ceph config set mon auth_service_required cephx
ceph config set mon auth_client_required cephx

Actions #1

Updated by Casey Bodley almost 4 years ago

  • Status changed from New to Need More Info

Hi, are you able to reproduce this error with debug_monc=20 and share the log?

Actions #2

Updated by Amit Ghadge almost 4 years ago

After run by,
/usr/bin/radosgw -f --cluster ceph --name client.radosgw.masifgw03 --setuser ceph --setgroup ceph --debug_monc 20 --debug_ms 5

the message still showing same, nothing other error message printed, After debug the issue seen here,
https://github.com/ceph/ceph/blob/v14.2.8/src/mon/MonClient.cc#L526, return -1

Actions #3

Updated by Amit Ghadge almost 4 years ago

Please close this, not seen recent fresh deploy.

Actions #4

Updated by Rui Ma 7 months ago

Amit Ghadge wrote:

Please close this, not seen recent fresh deploy.

Hi, I meet the similary problem when using ceph-deploy create rgw. Only in physical node, vm is fine.
How did you finally solve the previous problem?

radosgw17809: 2023-09-14 16:49:30.259 7fa7fc681700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2]
radosgw17809: 2023-09-14 16:49:30.259 7fa7fbe80700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2]
radosgw17809: failed to fetch mon config (--no-mon-config to skip)
systemd1: : Main process exited, code=exited, status=1/FAILURE
systemd1: : Failed with result 'exit-code'.
audit1: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit= comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
systemd1: : Service RestartSec=100ms expired, scheduling restart.
systemd1: : Scheduled restart job, restart counter is at 4.
systemd1: Stopped Ceph rados gateway.

Actions #5

Updated by Rui Ma 7 months ago


radosgw[17809]: 2023-09-14 16:49:30.259 7fa7fc681700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2]
radosgw[17809]: 2023-09-14 16:49:30.259 7fa7fbe80700 -1 monclient(hunting): handle_auth_bad_method server allowed_methods [2] but i only support [2]
radosgw[17809]: failed to fetch mon config (--no-mon-config to skip)
systemd[1]: ceph-radosgw@rgw.xxx.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: ceph-radosgw@rgw.xxx.service: Failed with result 'exit-code'.
audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ceph-radosgw@rgw.xxx comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
systemd[1]: ceph-radosgw@rgw.xxx.service: Service RestartSec=100ms expired, scheduling restart.
systemd[1]: ceph-radosgw@rgw.xxx.service: Scheduled restart job, restart counter is at 4.
systemd[1]: Stopped Ceph rados gateway.

Actions #6

Updated by Amit Ghadge 7 months ago

Rui Ma wrote:

[...]

Hello, I'm not exactly remember how was resolved. Might be some firewall but not sure.

Actions

Also available in: Atom PDF