Hello Jonathan. I have tried every other thing on your last message. Attached is the output of the lttng-sessiond -vvv
Thanks. root@ebele-desktop:~# lttng-sessiond -vvv DEBUG1 - 20:29:17.718632 [8086/8086]: run_as signal handler set for SIGTERM and SIGINT (in set_worker_sighandlers() at runas.c:600) DEBUG1 - 20:29:17.719781 [8085/8085]: Health check time delta in seconds set to 20 (in health_init() at health.c:74) DEBUG1 - 20:29:17.720333 [8085/8085]: epoll set max size is 334459 (in compat_epoll_set_max_size() at compat-epoll.c:290) DEBUG3 - 20:29:17.720888 [8085/8085]: Creating LTTng run directory: /var/run/lttng (in create_lttng_rundir() at main.c:5156) DEBUG2 - 20:29:17.721063 [8085/8085]: Kernel consumer err path: /var/run/lttng/kconsumerd/error (in main() at main.c:5601) DEBUG2 - 20:29:17.721101 [8085/8085]: Kernel consumer cmd path: /var/run/lttng/kconsumerd/command (in main() at main.c:5603) Error: Could not get lock file /var/run/lttng/lttng-sessiond.lck, another instance is running. DEBUG1 - 20:29:17.721231 [8085/8085]: Cleanup sessiond (in sessiond_cleanup() at main.c:622) DEBUG1 - 20:29:17.721322 [8085/8085]: Removing sessiond and consumerd content of directory /var/run/lttng (in sessiond_cleanup() at main.c:641) DEBUG1 - 20:29:17.721360 [8085/8085]: Removing /var/run/lttng/lttng-sessiond.pid (in sessiond_cleanup() at main.c:647) DEBUG1 - 20:29:17.721417 [8085/8085]: Removing /var/run/lttng/agent.port (in sessiond_cleanup() at main.c:652) DEBUG1 - 20:29:17.721462 [8085/8085]: Removing /var/run/lttng/kconsumerd/error (in sessiond_cleanup() at main.c:659) DEBUG1 - 20:29:17.721510 [8085/8085]: Removing directory /var/run/lttng/kconsumerd (in sessiond_cleanup() at main.c:665) DEBUG1 - 20:29:17.721558 [8085/8085]: Removing /var/run/lttng/ustconsumerd32/error (in sessiond_cleanup() at main.c:672) DEBUG1 - 20:29:17.721602 [8085/8085]: Removing directory /var/run/lttng/ustconsumerd32 (in sessiond_cleanup() at main.c:678) DEBUG1 - 20:29:17.721647 [8085/8085]: Removing /var/run/lttng/ustconsumerd64/error (in sessiond_cleanup() at main.c:685) DEBUG1 - 20:29:17.721693 [8085/8085]: Removing directory /var/run/lttng/ustconsumerd64 (in sessiond_cleanup() at main.c:691) DEBUG1 - 20:29:17.721734 [8085/8085]: Cleaning up all sessions (in sessiond_cleanup() at main.c:694) DEBUG1 - 20:29:17.721765 [8085/8085]: Cleaning up all agent apps (in sessiond_cleanup() at main.c:711) DEBUG1 - 20:29:17.721796 [8085/8085]: Closing all UST sockets (in sessiond_cleanup() at main.c:714) DEBUG2 - 20:29:17.721825 [8085/8085]: UST app cleaning registered apps hash table (in ust_app_clean_list() at ust-app.c:3702) DEBUG3 - 20:29:17.721856 [8085/8085]: Buffer registry destroy all registry (in buffer_reg_destroy_registries() at buffer-registry.c:716) DEBUG2 - 20:29:17.721886 [8085/8085]: Closing kernel fd (in sessiond_cleanup() at main.c:719) DEBUG1 - 20:29:17.721914 [8085/8085]: Unloading kernel modules (in sessiond_cleanup() at main.c:726) DEBUG1 - 20:29:17.722118 [8085/8087]: [ht-thread] startup. (in thread_ht_cleanup() at ht-cleanup.c:37) DEBUG3 - 20:29:17.723951 [8085/8087]: [ht-thread] Polling. (in thread_ht_cleanup() at ht-cleanup.c:67) DEBUG1 - 20:29:17.736599 [8085/8085]: Modprobe removal successful lttng-kretprobes (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.750243 [8085/8085]: Modprobe removal successful lttng-kprobes (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.763239 [8085/8085]: Modprobe removal successful lttng-ftrace (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.778109 [8085/8085]: Modprobe removal successful lttng-types (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.793153 [8085/8085]: Modprobe removal successful lttng-ring-buffer-metadata-mmap-client (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.810951 [8085/8085]: Modprobe removal successful lttng-ring-buffer-client-mmap-overwrite (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.823876 [8085/8085]: Modprobe removal successful lttng-ring-buffer-client-mmap-discard (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.836698 [8085/8085]: Modprobe removal successful lttng-ring-buffer-metadata-client (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.849417 [8085/8085]: Modprobe removal successful lttng-ring-buffer-client-overwrite (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.864495 [8085/8085]: Modprobe removal successful lttng-ring-buffer-client-discard (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.879363 [8085/8085]: Modprobe removal successful lttng-lib-ring-buffer (in modprobe_remove_lttng() at modprobe.c:126) DEBUG1 - 20:29:17.896710 [8085/8085]: Modprobe removal successful lttng-tracer (in modprobe_remove_lttng() at modprobe.c:126) DEBUG3 - 20:29:17.897048 [8085/8087]: [ht-thread] Returning from poll on 2 fds. (in thread_ht_cleanup() at ht-cleanup.c:74) DEBUG1 - 20:29:17.897154 [8085/8087]: [ht-cleanup] quit. (in thread_ht_cleanup() at ht-cleanup.c:153) DEBUG1 - 20:29:17.897262 [8085/8087]: [ht-cleanup] Thread terminates. (in thread_ht_cleanup() at ht-cleanup.c:164) DEBUG1 - 20:29:17.897743 [8085/8085]: Cleaning up options (in sessiond_cleanup_options() at main.c:773) DEBUG1 - 20:29:17.901442 [8085/8085]: lttng-runas terminated with status code 0 (in run_as_destroy_worker() at runas.c:737) DEBUG1 - 20:29:17.901548 [8085/8085]: *** assert failed :-) *** ==> Matthew, BEET driven development works! (in sessiond_cleanup_options() at main.c:805) root@ebele-desktop:~# On Thu, Nov 17, 2016 at 7:38 PM, Jonathan Rajotte Julien < [email protected]> wrote: > Hi, > > On 2016-11-17 07:24 PM, Nwafor, Ebelechukwu wrote: > >> Thanks Jonathan for you helpful response. I was able to install the >> specific linux-headers and it seems to install all of the modules. Now i've >> hit another roadblock. whenever i try to list all of the kernel events >> using lttng list -k, it throws an error: unable to list kernel events: >> Kernel tracer is not available. I have two lttng-sessiond running. >> > > Terminate both of them. Since you installed it from apt-get the > lttng-tools package provide a service for lttng-sessiond implying that the > lttng-sessiond process should get restarted automatically if killed. > > Again, make sure that the user issuing the "lttng list -k" is part of the > "tracing" group or simply root. > > If this still does not work refer to the last email and stop the service > then, as root, launch "lttng-sessiond -vvv" and check the output to make > sure that the modules gets loaded. > > Open another terminal and test the kernel tracepoint listing. > > If this does not work make sure to include the output from "lttng-sessiond > -vvv" in your next email. > > Cheers > >> >> On Thu, Nov 17, 2016 at 4:45 PM, Jonathan Rajotte Julien < >> [email protected] <mailto:Jonathan.rajotte-julie >> [email protected]>> wrote: >> >> Hi, >> >> >> On 2016-11-17 04:24 PM, Nwafor, Ebelechukwu wrote: >> >> Hi Jonathan. Thank you for your response. >> >> On the beaglebone black, i tried building lttng-tools, >> lttng-modules-dkms and lttng-ust-dev from source v2.8.1 by >> following the documentation. lttng-modules-dkms runs fine but >> the module does not show up on the list of running modules >> when i issue an lsmod command. Also, i run into errors while >> trying to build and compile lttng-tools. Beaglebone black runs >> on debian. Linux beaglebone 3.8.13-bone70 #1 SMP Fri Jan 23 >> 02:15:42 UTC 2015 armv7l GNU/Linux >> >> >> What errors do you see when building lttng-tools? >> >> >> >> On the raspberry pi, I use the commands, apt-get install >> lttng-modules-dkms lttng-tools lttng-ust-dev. Everything seems >> to work fine with the exception of lttng-modules-dkms which >> does not show up on the list on running modules. Also, every >> time i try to view available kernel events, it comes up with >> an error saying unable to list kernel events: kernel tracer >> not available. The LTTNG version installed using apt-get is >> 2.7.1. I am running ubuntu mate OS. Below are the output while >> installing lttng-modules-dkms >> >> >> Well as the error points out do you have the kernel tracer started? >> >> ps -aux | grep lttng-sessiond >> >> Does the user trying to use lttng is part of the tracing group or >> is root ? >> >> You can start lttng-sessiond with the -vvv options make sure to be >> root when doing so lttng-sessiond load the tracing modules. >> >> Since you installed it from apt-get the lttng-tools package >> provide a daemon for lttng-sessiond so before testing manually: >> >> service lttng-sessiond stop >> >> >> >> root@ebele-desktop:~# apt-get install lttng-modules-dkms >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> lttng-modules-dkms is already the newest version (2.7.1-1). >> 0 upgraded, 0 newly installed, 0 to remove and 14 not upgraded. >> 2 not fully installed or removed. >> After this operation, 0 B of additional disk space will be used. >> Do you want to continue? [Y/n] Y >> Setting up linux-headers-4.4.0-22 (4.4.0-22.40) ... >> Setting up lttng-modules-dkms (2.7.1-1) ... >> Loading new lttng-modules-2.7.1 DKMS files... >> First Installation: checking all kernels... >> dpkg: warning: version '*-*' has bad syntax: version number >> does not start with digit >> It is likely that 4.4.30-v7+ belongs to a chroot's host >> Module build for the currently running kernel was skipped >> since the >> kernel source for this kernel does not seem to be installed. >> >> >> >> Could you make sure that your linux header for the running kernel >> are installed. >> >> 4.4.30-v7+ seems like a custom kernel install. >> >> root@ebele-desktop:~# >> >> >> >> On Thu, Nov 17, 2016 at 3:00 PM, Jonathan Rajotte >> <[email protected] >> <mailto:[email protected]> >> <mailto:[email protected] >> <mailto:[email protected]>>> wrote: >> >> Hi, >> >> Could you be a bit more precise regarding which part of the >> documentation does not work ? >> >> How did you install it ? Distribution packages ? From >> sources ? >> Cross compiled ? >> >> What is your setup ? Raspian for the Pi ? Custom kernel >> image ? >> >> Cheers >> >> On Thu, Nov 17, 2016 at 2:54 PM, Nwafor, Ebelechukwu >> <[email protected] >> <mailto:[email protected]> >> <mailto:[email protected] >> <mailto:[email protected]>>> wrote: >> >> Hello. >> >> I am trying to install LTTNG tracing tool on raspberry >> pi and >> beaglebone black board.The official LTTNG >> documentation does >> not work on these devices. Does anyone know of any >> tutorial >> that can help me accomplish this? Thanks. >> >> -- Ebelechukwu Nwafor, >> Graduate Student, >> Howard University. >> >> _______________________________________________ >> lttng-dev mailing list >> [email protected] <mailto:[email protected]> >> <mailto:[email protected] >> <mailto:[email protected]>> >> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev >> <https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev> >> <https://lists.lttng.org/cgi- >> bin/mailman/listinfo/lttng-dev >> <https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev>> >> >> >> >> >> -- Jonathan Rajotte Julien >> >> >> >> >> -- Ebelechukwu Nwafor, >> Graduate Student, >> Howard University. >> >> >> _______________________________________________ >> lttng-dev mailing list >> [email protected] <mailto:[email protected]> >> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev >> <https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev> >> >> >> -- Jonathan R. Julien >> Efficios >> >> >> _______________________________________________ >> lttng-dev mailing list >> [email protected] <mailto:[email protected]> >> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev >> <https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev> >> >> >> >> >> -- >> Ebelechukwu Nwafor, >> Graduate Student, >> Howard University. >> > > -- > Jonathan R. Julien > Efficios > > -- Ebelechukwu Nwafor, Graduate Student, Howard University.
_______________________________________________ lttng-dev mailing list [email protected] https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
