Bug #355
closed
PERROR: sendmsg: Socket operation on non-socket
Added by Mathieu Desnoyers over 11 years ago.
Updated over 11 years ago.
Description
lttng-sessiond running as user.
lttng create
lttng enable-event -u -a
lttng start
and then run:
for a in $(seq 1 1000); do ./demo-trace; done
gets us many:
PERROR: sendmsg: Socket operation on non-socket [in lttcomm_send_unix_sock() at unix.c:204]
PERROR: send consumer channel: Socket operation on non-socket [in consumer_send_channel() at consumer.c:473]
from possibly sessiond or consumerd.
- Status changed from New to Invalid
Was caused by my local dev branch of userspace RCU installed on my machine. Sorry for the noise.
- Status changed from Invalid to New
Actually, I've just reproduced the issue with the userspace RCU master branch installed in my system. So it does not happen every time, but say every 2 times the 1000 for loop is executed.
On the first loop, we see some messages:
Unable to find channel key: No such file or directory
- Status changed from New to Confirmed
- Assignee set to David Goulet
- Priority changed from Critical to High
- Target version set to 2.1 stable
I'm going to take this one and flag it for 2.1-stable.
I've changed the status to High since it does not break any features but fails for a certain very specific use case.
I can reproduced that each time and even with the debug enabled so should be "easily" fixable.
- Status changed from Confirmed to Resolved
- % Done changed from 0 to 100
Also available in: Atom
PDF