panic due to 'cannot set affinity'

1,315 views
Skip to first unread message

Nick Stott

<nick.pickled@gmail.com>
unread,
Dec 14, 2015, 5:51:12 PM12/14/15
to ScyllaDB users
Hi All,
I'm trying to launch scylladb in an lxc container, and I am getting the following panic when I try to run the daemon

$/usr/bin/scylla
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 0 on socket 0
EAL: Support maximum 128 logical core(s) by configuration.
EAL: Detected 2 lcore(s)
EAL: VFIO modules not all loaded, skip VFIO support...
EAL: Setting up physically contiguous memory...
EAL: TSC frequency is ~2494055 KHz
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable clock cycles !
EAL: pthread_setaffinity_np failed
PANIC in eal_thread_init_master():
cannot set affinity
10: [/usr/bin/scylla() [0x4aebd5]]
9: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f2e35d2bec5]]
8: [/usr/bin/scylla() [0x45566e]]
7: [/usr/bin/scylla() [0x538f9c]]
6: [/usr/bin/scylla() [0x4e6a26]]
5: [/usr/bin/scylla() [0x54128b]]
4: [/usr/bin/scylla() [0x678af1]]
3: [/usr/bin/scylla() [0x67be64]]
2: [/usr/bin/scylla() [0x44e0ea]]
1: [/usr/bin/scylla() [0x67f648]]
Aborted (core dumped)

Has anyone seen this before?
Thanks!

Nick

Avi Kivity

<avi@scylladb.com>
unread,
Dec 15, 2015, 7:47:04 AM12/15/15
to scylladb-users@googlegroups.com
You are probably hitting this test in the kernel:

        /*
         * Since bandwidth control happens on root_domain basis,
         * if admission test is enabled, we only admit -deadline
         * tasks allowed to run on all the CPUs in the task's
         * root_domain.
         */
#ifdef CONFIG_SMP
        if (task_has_dl_policy(p) && dl_bandwidth_enabled()) {
                rcu_read_lock();
                if (!cpumask_subset(task_rq(p)->rd->span, new_mask)) {
                        retval = -EBUSY;
                        rcu_read_unlock();
                        goto out_free_new_mask;
                }
                rcu_read_unlock();
        }
#endif
again:

Did you limit your lxc container to run on a subset of your cpus?  Try unlimiting it (you can constrain scylla with the --smp or --cpuset parameters).


Thanks!

Nick

--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To post to this group, send email to scyllad...@googlegroups.com.
Visit this group at https://groups.google.com/group/scylladb-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/87bf75b5-0c42-43b5-8ccf-5676aba9c32d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Nick Stott

<nick.pickled@gmail.com>
unread,
Dec 15, 2015, 3:23:02 PM12/15/15
to ScyllaDB users
gotcha, yeah, that was it.. I had a limit on cpuset.cpus in the cgroups

Thanks!
Reply all
Reply to author
Forward
0 new messages