[lttng-dev] lttng-sessiond stuck at "Accepting application registration"
Prashanth Raghavendra
prashanth.raghavendra at gmail.com
Fri Feb 12 08:57:50 EST 2016
Greetings,
We are trying to use lttng for tracing our application code (userspace).
Host OS: WR5.0.1.13 Linux
Lttng-tools version 2.1.0, 32-bit (lttng: ELF 32-bit LSB executable, Intel
80386)
Babeltrace version 1.0.0
Logged in as root.
When we start the lttng-sessiond, it gets stuck at "Accepting application
registration”.
Linux(debug)# /isan/lib/lttng-sessiond -vvv --no-kernel
DEBUG3: Creating LTTng run directory: /var/run/lttng [in
create_lttng_rundir() at main.c:3683]
DEBUG2: Kernel consumer err path: /var/run/lttng/kconsumerd/error [in
main() at main.c:3931]
DEBUG2: Kernel consumer cmd path: /var/run/lttng/kconsumerd/command [in
main() at main.c:3933]
DEBUG1: Client socket path /var/run/lttng/client-lttng-sessiond [in main()
at main.c:3986]
DEBUG1: Application socket path /var/run/lttng/apps-lttng-sessiond [in
main() at main.c:3987]
DEBUG1: LTTng run directory path: /var/run/lttng [in main() at main.c:3988]
DEBUG2: UST consumer 32 bits err path: /var/run/lttng/ustconsumerd32/error
[in main() at main.c:3997]
DEBUG2: UST consumer 32 bits cmd path:
/var/run/lttng/ustconsumerd32/command [in main() at main.c:3999]
DEBUG2: UST consumer 64 bits err path: /var/run/lttng/ustconsumerd64/error
[in main() at main.c:4008]
DEBUG2: UST consumer 64 bits cmd path:
/var/run/lttng/ustconsumerd64/command [in main() at main.c:4010]
DEBUG3: Created hashtable size 4 at 0x88d7080 of type 1 [in lttng_ht_new()
at hashtable.c:96]
DEBUG3: Created hashtable size 4 at 0x88d7370 of type 1 [in lttng_ht_new()
at hashtable.c:96]
DEBUG2: Creating consumer directory: /var/run/lttng/kconsumerd [in
set_consumer_sockets() at main.c:3725]
DEBUG2: Creating consumer directory: /var/run/lttng/ustconsumerd64 [in
set_consumer_sockets() at main.c:3725]
DEBUG2: Creating consumer directory: /var/run/lttng/ustconsumerd32 [in
set_consumer_sockets() at main.c:3725]
DEBUG1: Signal handler set for SIGTERM, SIGPIPE and SIGINT [in
set_signal_handler() at main.c:3817]
DEBUG3: Session daemon client socket 8 and application socket 9 created [in
init_daemon_socket() at main.c:3587]
Warning: No tracing group detected
DEBUG1: epoll set max size is 3243642 [in compat_epoll_set_max_size() at
compat-epoll.c:224]
DEBUG1: Command subsystem initialized [in cmd_init() at cmd.c:2423]
DEBUG1: [thread] Manage health check started [in thread_manage_health() at
main.c:2944]
DEBUG1: [thread] Manage client started [in thread_manage_clients() at
main.c:3138]
DEBUG1: [thread] Dispatch UST command started [in
thread_dispatch_ust_registration() at main.c:1295]
DEBUG1: Futex n to 1 prepare done [in futex_nto1_prepare() at futex.c:75]
DEBUG1: Woken up but nothing in the UST command queue [in
thread_dispatch_ust_registration() at main.c:1305]
DEBUG1: [thread] Manage application registration started [in
thread_registration_apps() at main.c:1371]
DEBUG1: [thread] Manage application started [in thread_manage_apps() at
main.c:1101]
DEBUG1: Health check ready [in thread_manage_health() at main.c:2983]
DEBUG1: Accepting client command ... [in thread_manage_clients() at
main.c:3182]
DEBUG1: Notifying applications of session daemon state: 1 [in
notify_ust_apps() at main.c:496]
DEBUG1: Apps thread polling on 2 fds [in thread_manage_apps() at
main.c:1134]
DEBUG1: Got the wait shm fd 16 [in get_wait_shm() at shm.c:117]
DEBUG1: Futex wait update active 1 [in futex_wait_update() at futex.c:63]
DEBUG1: Accepting application registration [in thread_registration_apps()
at main.c:1406] ===è Remain struck here
Because of this, we suspect that the traces from our application are not
getting generated. And we get error when we run lttng view:
(lttng enable-event, start etc went through fine)
Linux(debug)# lttng stop
Waiting for data availability
Warning: Tracing already stopped for session auto-20160211-133851
Linux(debug)# lttng view
Trace directory: /home/
[error] Cannot open any trace for reading.
[error] opening trace “/home/" for reading.
[error] none of the specified trace paths could be opened.
Please help us in fixing this issue.
Thank you.
Best Regards,
Prashanth Raghavendra
Aditya Dogra
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lttng.org/pipermail/lttng-dev/attachments/20160212/f8c9b226/attachment.html>
More information about the lttng-dev
mailing list