[Oisf-users] Profiling on Suricata 2.04 NOT working

[Charles DeVoe]

I for some reason am unable to get profiling to work on my sensors.   Is there an issue in 2.04?


the build info
/usr/local/bin/suricata --build-infoThis is Suricata version 2.0.4 RELEASEFeatures: PCAP_SET_BUFF LIBPCAP_VERSION_MAJOR=1 PF_RING AF_PACKET HAVE_PACKET_FANOUT LIBCAP_NG LIBNET1.1 HAVE_HTP_URI_NORMALIZE_HOOK HAVE_NSS PROFILING SIMD support: SSE_4_2 SSE_4_1 SSE_3 Atomic intrisics: 1 2 4 8 16 byte(s)64-bits, Little-endian architectureGCC version 4.4.7 20120313 (Red Hat 4.4.7-4), C version 199901compiled with -fstack-protectorcompiled with _FORTIFY_SOURCE=2L1 cache line size (CLS)=64compiled with LibHTP v0.5.15, linked against LibHTP v0.5.15Suricata Configuration:  AF_PACKET support:                       yes  PF_RING support:                         yes  NFQueue support:                         no  NFLOG support:                           no  IPFW support:                            no  DAG enabled:                             no  Napatech enabled:                        no  Unix socket enabled:                     no  Detection enabled:                       yes
  libnss support:                          yes  libnspr support:                         yes  libjansson support:                      no  Prelude support:                         no  PCRE jit:                                no  LUA support:                             no  libluajit:                               no  libgeoip:                                no  Non-bundled htp:                         no  Old barnyard2 support:                   no  CUDA enabled:                            no
  Suricatasc install:                      yes
  Unit tests enabled:                      no  Debug output enabled:                    no  Debug validation enabled:                no  Profiling enabled:                       yes  Profiling locks enabled:                 no  Coccinelle / spatch:                     no
Generic build parameters:  Installation prefix (--prefix):          /usr/local  Configuration directory (--sysconfdir):  /usr/local/etc/suricata/  Log directory (--localstatedir) :        /usr/local/var/log/suricata/
  Host:                                    x86_64-unknown-linux-gnu  GCC binary:                              gcc  GCC Protect enabled:                     yes  GCC march native enabled:                yes  GCC Profile enabled:                     no

System info

Linux sensor-name 3.8.13-16.2.1.el6uek.x86_64 #1 SMP Thu Nov 7 17:01:44 PST 2013 x86_64 x86_64 x86_64 GNU/Linux

 Suricata.yaml appropriate section
  # rule profiling  rules:
    # Profiling can be disabled here, but it will still have a    # performance impact if compiled in.    enabled: yes    filename: rule_perf.log    append: yes
    # Sort options: ticks, avgticks, checks, matches, maxticks    sort: avgticks
    # Limit the number of items printed at exit.    limit: 100
  # per keyword profiling  keywords:    enabled: yes    filename: keyword_perf.log    append: yes
  # packet profiling  packets:
    # Profiling can be disabled here, but it will still have a    # performance impact if compiled in.    enabled: yes    filename: packet_stats.log    append: yes
    # per packet csv output    csv:
      # Output can be disabled here, but it will still have a      # performance impact if compiled in.      enabled: no      filename: packet_stats.csv
  # profiling of locking. Only available when Suricata was built with  # --enable-profiling-locks.  locks:    enabled: no    filename: lock_stats.log    append: yes 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openinfosecfoundation.org/pipermail/oisf-users/attachments/20150617/555e3257/attachment.html>