Bug #23537
closedlibceph: monX xxxxxx session lost, hunting for new mon
0%
Description
maybe connected with #17664
I use Luminous 12.2.2 on both client and cluster. Kernel at cephfs client: Linux mmwork 4.13.0-37-generic #42-Ubuntu SMP Wed Mar 7 14:13:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux.
I don't know if same bug, but symptoms are exactly the same. Many lines in dmesg like:
```
[Sun Apr 1 23:37:05 2018] libceph: mon0 10.80.20.99:6789 session established
[Sun Apr 1 23:37:36 2018] libceph: mon0 10.80.20.99:6789 session lost, hunting for new mon
[Sun Apr 1 23:37:36 2018] libceph: mon2 10.80.20.103:6789 session established
[Sun Apr 1 23:38:07 2018] libceph: mon2 10.80.20.103:6789 session lost, hunting for new mon
[Sun Apr 1 23:38:07 2018] libceph: mon1 10.80.20.100:6789 session established
[Sun Apr 1 23:38:37 2018] libceph: mon1 10.80.20.100:6789 session lost, hunting for new mon
[Sun Apr 1 23:38:37 2018] libceph: mon2 10.80.20.103:6789 session established
[Sun Apr 1 23:39:08 2018] libceph: mon2 10.80.20.103:6789 session lost, hunting for new mon
[Sun Apr 1 23:39:08 2018] libceph: mon1 10.80.20.100:6789 session established
[Sun Apr 1 23:39:39 2018] libceph: mon1 10.80.20.100:6789 session lost, hunting for new mon
[Sun Apr 1 23:39:39 2018] libceph: mon0 10.80.20.99:6789 session established
[Sun Apr 1 23:40:09 2018] libceph: mon0 10.80.20.99:6789 session lost, hunting for new mon
[Sun Apr 1 23:40:09 2018] libceph: mon1 10.80.20.100:6789 session established
[Sun Apr 1 23:40:40 2018] libceph: mon1 10.80.20.100:6789 session lost, hunting for new mon
[Sun Apr 1 23:40:40 2018] libceph: mon0 10.80.20.99:6789 session established
[Sun Apr 1 23:41:11 2018] libceph: mon0 10.80.20.99:6789 session lost, hunting for new mon
[Sun Apr 1 23:41:11 2018] libceph: mon2 10.80.20.103:6789 session established
[Sun Apr 1 23:41:42 2018] libceph: mon2 10.80.20.103:6789 session lost, hunting for new mon
```
Please note timeouts values: every 30 seconds. this timeout was mentioned in linked task.