[lttng-dev] lttng trace kernel on arm64

Lichuanbao lichuanbao at hisilicon.com
Fri Apr 8 06:28:08 UTC 2016


Hi,
   I want to use lttng trace kernel event,I installed lttng-tools 2.7.1 lttng-ust 2.7.2 lttng-modules 2.7.2 on my arm64 board,
And then I create my session like sub command as root,but there is nothing result to view.

    # lttng create
    # lttng enable-event --kernel --all
    # lttng start
    # sleep 10               # let the system generate some activity
    # lttng stop
    # lttng view
# lttng destroy

-bash-4.3# lttng view
Trace directory: /root/lttng-traces/auto-20160407-211248

[error] Cannot open any trace for reading.

[error] opening trace "/root/lttng-traces/auto-20160407-211248" for reading.

[error] none of the specified trace paths could be opened.

Get thes session daemon log as follow:

bash-4.3# lttng-sessiond -vvv
DEBUG1 - 21:52:15.396991 [5621/5621]: run_as signal handler set for SIGTERM and SIGINT (in set_worker_sighandlers() at runas.c:600)
DEBUG1 - 21:52:15.397410 [5620/5620]: Health check time delta in seconds set to 20 (in health_init() at health.c:74)
DEBUG1 - 21:52:15.397661 [5620/5620]: epoll set max size is 27037798 (in compat_epoll_set_max_size() at compat-epoll.c:290)
DEBUG3 - 21:52:15.397838 [5620/5620]: Creating LTTng run directory: /var/run/lttng (in create_lttng_rundir() at main.c:5156)
DEBUG1 - 21:52:15.397852 [5620/5622]: [ht-thread] startup. (in thread_ht_cleanup() at ht-cleanup.c:37)
DEBUG2 - 21:52:15.397986 [5620/5620]: Kernel consumer err path: /var/run/lttng/kconsumerd/error (in main() at main.c:5601)
DEBUG2 - 21:52:15.398070 [5620/5620]: Kernel consumer cmd path: /var/run/lttng/kconsumerd/command (in main() at main.c:5603)
DEBUG3 - 21:52:15.398034 [5620/5622]: [ht-thread] Polling. (in thread_ht_cleanup() at ht-cleanup.c:67)
Error: Could not get lock file /var/run/lttng/lttng-sessiond.lck, another instance is running.
DEBUG1 - 21:52:15.398240 [5620/5620]: Cleanup sessiond (in sessiond_cleanup() at main.c:622)
DEBUG1 - 21:52:15.398294 [5620/5620]: Removing sessiond and consumerd content of directory /var/run/lttng (in sessiond_cleanup() at main.c:641)
DEBUG1 - 21:52:15.398321 [5620/5620]: Removing /var/run/lttng/lttng-sessiond.pid (in sessiond_cleanup() at main.c:647)
DEBUG1 - 21:52:15.398372 [5620/5620]: Removing /var/run/lttng/agent.port (in sessiond_cleanup() at main.c:652)
DEBUG1 - 21:52:15.398420 [5620/5620]: Removing /var/run/lttng/kconsumerd/error (in sessiond_cleanup() at main.c:659)
DEBUG1 - 21:52:15.398472 [5620/5620]: Removing directory /var/run/lttng/kconsumerd (in sessiond_cleanup() at main.c:665)
DEBUG1 - 21:52:15.398526 [5620/5620]: Removing /var/run/lttng/ustconsumerd32/error (in sessiond_cleanup() at main.c:672)
DEBUG1 - 21:52:15.398579 [5620/5620]: Removing directory /var/run/lttng/ustconsumerd32 (in sessiond_cleanup() at main.c:678)
DEBUG1 - 21:52:15.398620 [5620/5620]: Removing /var/run/lttng/ustconsumerd64/error (in sessiond_cleanup() at main.c:685)
DEBUG1 - 21:52:15.398673 [5620/5620]: Removing directory /var/run/lttng/ustconsumerd64 (in sessiond_cleanup() at main.c:691)
DEBUG1 - 21:52:15.398734 [5620/5620]: Cleaning up all sessions (in sessiond_cleanup() at main.c:694)
DEBUG1 - 21:52:15.398765 [5620/5620]: Cleaning up all agent apps (in sessiond_cleanup() at main.c:711)
DEBUG1 - 21:52:15.398789 [5620/5620]: Closing all UST sockets (in sessiond_cleanup() at main.c:714)
DEBUG2 - 21:52:15.398813 [5620/5620]: UST app cleaning registered apps hash table (in ust_app_clean_list() at ust-app.c:3702)
DEBUG3 - 21:52:15.398837 [5620/5620]: Buffer registry destroy all registry (in buffer_reg_destroy_registries() at buffer-registry.c:716)
DEBUG2 - 21:52:15.398861 [5620/5620]: Closing kernel fd (in sessiond_cleanup() at main.c:719)
DEBUG1 - 21:52:15.398884 [5620/5620]: Unloading kernel modules (in sessiond_cleanup() at main.c:726)
DEBUG1 - 21:52:15.403580 [5620/5620]: Modprobe removal successful lttng-kretprobes (in modprobe_remove_lttng() at modprobe.c:126)
DEBUG1 - 21:52:15.407855 [5620/5620]: Modprobe removal successful lttng-kprobes (in modprobe_remove_lttng() at modprobe.c:126)
DEBUG1 - 21:52:15.412073 [5620/5620]: Modprobe removal successful lttng-ftrace (in modprobe_remove_lttng() at modprobe.c:126)
DEBUG1 - 21:52:15.416256 [5620/5620]: Modprobe removal successful lttng-types (in modprobe_remove_lttng() at modprobe.c:126)
DEBUG1 - 21:52:15.420593 [5620/5620]: Modprobe removal successful lttng-ring-buffer-metadata-mmap-client (in modprobe_remove_lttng() at modprobe.c:126)
DEBUG1 - 21:52:15.425108 [5620/5620]: Modprobe removal successful lttng-ring-buffer-client-mmap-overwrite (in modprobe_remove_lttng() at modprobe.c:126)
DEBUG1 - 21:52:15.429745 [5620/5620]: Modprobe removal successful lttng-ring-buffer-client-mmap-discard (in modprobe_remove_lttng() at modprobe.c:126)
Error: Unable to remove module lttng-ring-buffer-metadata-client
DEBUG1 - 21:52:15.438779 [5620/5620]: Modprobe removal successful lttng-ring-buffer-client-overwrite (in modprobe_remove_lttng() at modprobe.c:126)
Error: Unable to remove module lttng-ring-buffer-client-discard
Error: Unable to remove module lttng-lib-ring-buffer
Error: Unable to remove module lttng-tracer
DEBUG3 - 21:52:15.452135 [5620/5622]: [ht-thread] Returning from poll on 2 fds. (in thread_ht_cleanup() at ht-cleanup.c:74)
DEBUG1 - 21:52:15.452186 [5620/5622]: [ht-cleanup] quit. (in thread_ht_cleanup() at ht-cleanup.c:153)
DEBUG1 - 21:52:15.452225 [5620/5622]: [ht-cleanup] Thread terminates. (in thread_ht_cleanup() at ht-cleanup.c:164)
DEBUG1 - 21:52:15.452333 [5620/5620]: Cleaning up options (in sessiond_cleanup_options() at main.c:773)
DEBUG1 - 21:52:15.453308 [5620/5620]: lttng-runas terminated with status code 0 (in run_as_destroy_worker() at runas.c:737)
DEBUG1 - 21:52:15.453349 [5620/5620]: *** assert failed :-) *** ==> Matthew, BEET driven development works! (in sessiond_cleanup_options() at main.c:805)


can anybody help me ?

thanks very much.

lichuanbao

ShenZhen in China


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20160408/9e9a3fd1/attachment.html>


More information about the lttng-dev mailing list