Still having issue… 

Connection test works fine but not able to map the image… 

# ceph -n client.infra-dev --keyring /etc/ceph/client.infra-dev.keyring -s
  cluster:
    id:     3b850efe-5dec-11f0-af3c-c1a764f7824e
    health: HEALTH_OK

# rbd -n client.infra-dev map rbd_k8s_infra_dev/test  --key 
AQCX+6VoA9dFMRAA4cARD/U9CLcouwoW6d9YMw==
rbd: sysfs write failed
In some cases useful info is found in syslog - try "dmesg | tail".
rbd: map failed: (110) Connection timed out

# dmesg |tail
[2317050.540190] libceph: mon0 (1)10.101.1.248:6789 feature set mismatch, my 
2f018fb87aa4aafe < server's 2f018fb8faa4aafe, missing 80000000
[2317050.540357] libceph: mon0 (1)10.101.1.248:6789 missing required protocol 
features
[2317051.497679] libceph: mon1 (1)10.101.1.247:6789 feature set mismatch, my 
2f018fb87aa4aafe < server's 2f018fb8faa4aafe, missing 80000000
[2317051.497848] libceph: mon1 (1)10.101.1.247:6789 missing required protocol 
features
[2317051.755665] libceph: mon1 (1)10.101.1.247:6789 feature set mismatch, my 
2f018fb87aa4aafe < server's 2f018fb8faa4aafe, missing 80000000
[2317051.755820] libceph: mon1 (1)10.101.1.247:6789 missing required protocol 
features
[2317052.258640] libceph: mon1 (1)10.101.1.247:6789 feature set mismatch, my 
2f018fb87aa4aafe < server's 2f018fb8faa4aafe, missing 80000000
[2317052.258796] libceph: mon1 (1)10.101.1.247:6789 missing required protocol 
features
[2317053.481804] libceph: mon1 (1)10.101.1.247:6789 feature set mismatch, my 
2f018fb87aa4aafe < server's 2f018fb8faa4aafe, missing 80000000


CLient pversion
# ceph -v
ceph version 19.2.1 (9efac4a81335940925dd17dbf407bfd6d3860d28) squid (stable)


# ceph features
{
    "mon": [
        {
            "features": "0x3f03cffffffdffff",
            "release": "squid",
            "num": 3
        }
    ],
    "mds": [
        {
            "features": "0x3f03cffffffdffff",
            "release": "squid",
            "num": 3
        }
    ],
    "osd": [
        {
            "features": "0x3f03cffffffdffff",
            "release": "squid",
            "num": 12
        }
    ],
    "client": [
        {
            "features": "0x3f03cffffffdffff",
            "release": "squid",
            "num": 25
        }
    ],
    "mgr": [
        {
            "features": "0x3f03cffffffdffff",
            "release": "squid",
            "num": 2
        }
    ]
}

Regards
Dev


> On Aug 19, 2025, at 2:31 PM, Devender Singh <deven...@netskrt.io> wrote:
> 
> Dear all 
> 
> Getting below error, any fix for this?
> 
> # apt update
> Hit:1 https://repo.zabbix.com/zabbix/6.4/ubuntu noble InRelease
> Hit:2 http://security.ubuntu.com/ubuntu noble-security InRelease
> Ign:3 https://download.ceph.com/debian-squid noble InRelease
> Err:4 https://download.ceph.com/debian-squid noble Release
>   404  Not Found [IP: 158.69.68.124 443]
> Hit:5 http://archive.ubuntu.com/ubuntu noble InRelease
> Hit:6 http://archive.ubuntu.com/ubuntu noble-updates InRelease
> Hit:7 http://archive.ubuntu.com/ubuntu noble-backports InRelease
> Reading package lists... Done
> E: The repository 'https://download.ceph.com/debian-squid noble Release' does 
> not have a Release file.
> N: Updating from such a repository can't be done securely, and is therefore 
> disabled by default.
> N: See apt-secure(8) manpage for repository creation and user configuration 
> details.
> 
> # cat /etc/os-release
> PRETTY_NAME="Ubuntu 24.04.3 LTS"
> NAME="Ubuntu"
> VERSION_ID="24.04"
> VERSION="24.04.3 LTS (Noble Numbat)"
> VERSION_CODENAME=noble
> ID=ubuntu
> ID_LIKE=debian
> HOME_URL="https://www.ubuntu.com/";
> SUPPORT_URL="https://help.ubuntu.com/";
> BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
> PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
> UBUNTU_CODENAME=noble
> LOGO=ubuntu-logo
> 
> # cat /etc/apt/sources.list.d/ceph.list
> deb https://download.ceph.com/debian-squid/ noble main
> 
> Regards
> Dev
> 

_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Reply via email to