[sheepdog-users] Crash of a node

[Valerio Pachera]

I got this message in sheep.log when starting a guest.

Jun 17 22:19:20 [gway 28617] gateway_forward_request(308) fail to
write local 2e51900006c86, No object found
Jun 17 22:19:20 [oc_push 28465] push_cache_object(471) failed to push
object No object found
Jun 17 22:19:20 [oc_push 28465] do_push_object(841) PANIC: push failed
but should never fail
Jun 17 22:19:20 [oc_push 28465] crash_handler(180) sheep exits
unexpectedly (Aborted).
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(833) sheep.c:182: crash_handler
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(847)
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf02f) [0x7fa7f103e02f]
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(847)
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x34) [0x7fa7f064a474]
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(847)
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17f) [0x7fa7f064d6ef]
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(833) object_cache.c:841:
do_push_object
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(833) work.c:243: worker_routine
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(847)
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b4f) [0x7fa7f1035b4f]
Jun 17 22:19:21 [oc_push 28465] sd_backtrace(847)
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6c) [0x7fa7f06f2a7c]
Jun 17 22:19:21 [oc_push 28465] __dump_stack_frames(743) cannot find gdb
Jun 17 22:19:21 [oc_push 28465] __sd_dump_variable(693) cannot find gdb
Jun 17 22:19:21 [main] crash_handler(487) sheep pid 11158 exited unexpectedly.
Jun 17 22:29:18 [main] md_add_disk(161) /mnt/wd_WCAYUEP99298/obj, nr 1
Jun 17 22:29:18 [main] md_add_disk(161) /mnt/wd_WCAWZ1588874, nr 2
Jun 17 22:29:18 [main] send_join_request(1101) IPv4 ip:192.168.6.44 port:7000
Jun 17 22:29:18 [main] for_each_object_in_stale(403)
/mnt/wd_WCAYUEP99298/obj/.stale
Jun 17 22:29:18 [main] for_each_object_in_stale(403) /mnt/wd_WCAWZ1588874/.stale
Jun 17 22:29:18 [main] init_vdi_state(194) failed to read inode header
80c8d12d00000000 0
Jun 17 22:29:18 [main] init_vdi_state(194) failed to read inode header
80c8be4d00000000 0
Jun 17 22:29:18 [main] init_vdi_state(194) failed to read inode header
80c8d12c00000000 0
Jun 17 22:29:18 [main] check_host_env(404) Allowed core file size 0,
suggested unlimited
Jun 17 22:29:18 [main] main(774) sheepdog daemon (version
0.6.0_26_g9663187) started
Jun 17 22:29:18 [main] update_cluster_info(877) status = 1, epoch =
20, finished: 0
Jun 17 22:29:48 [main] check_request_epoch(163) old node version 21,
20 (READ_PEER)
Jun 17 22:29:48 [main] check_request_epoch(163) old node version 21,
20 (READ_PEER)
Jun 17 22:29:49 [rw] get_object_sha1(489) fail to get sha1,
/mnt/wd_WCAYUEP99298/obj/.stale/00c8d128000274cb.19
Jun 17 22:29:49 [main] recover_object_main(626) done:1 count:270470,
oid:c8d128000274cb
Jun 17 22:29:49 [rw] get_object_sha1(489) fail to get sha1,
/mnt/wd_WCAYUEP99298/obj/.stale/00c8d128000382cc.19
Jun 17 22:29:50 [main] recover_object_main(626) done:2 count:270470,
oid:c8d128000382cc
Jun 17 22:29:50 [rw] get_object_sha1(489) fail to get sha1,
/mnt/wd_WCAYUEP99298/obj/.stale/00c8d12c000370df.19
Jun 17 22:29:50 [main] recover_object_main(626) done:3 count:270470,
oid:c8d12c000370df
Jun 17 22:29:50 [main] recover_object_main(626) done:4 count:270470,
oid:c8d12e0001eb7a

This may be consequent of some wrong thing I've done with cache today.
Anyway, ti should not crash.