GeezerVison

The World Wide Web, restored to 800 pixels of glory.

GeezerVison is showing docs.openstack.org — System-wide debugging — DevStack documentation

System-wide debugging

System-wide debugging¶

A lot can go wrong during a devstack run, and there are a few inbuilt tools to help you.

dstat¶

Enable the dstat service to produce performance logs during the devstack run. These will be logged to the journal and also as a CSV file.

memory_tracker¶

The memory_tracker service periodically monitors RAM usage and provides consumption output when available memory is seen to be falling (i.e. processes are consuming memory). It also provides output showing locked (unswappable) memory.

file_tracker¶

The file_tracker service periodically monitors the number of open files in the system.

tcpdump¶

Enable the tcpdump service to run a background tcpdump. You must set the TCPDUMP_ARGS variable to something suitable (there is no default). For example, to trace iSCSI communication during a job in the OpenStack gate and copy the result into the log output, you might use:

job:
  name: devstack-job
  parent: devstack
  vars:
    devstack_services:
      tcpdump: true
    devstack_localrc:
      TCPDUMP_ARGS: "-i any tcp port 3260"
    zuul_copy_output:
      '{{ devstack_log_dir }}/tcpdump.pcap': logs

this page last updated: 2022-11-02 16:43:41

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.

found an error? report a bug

DevStack

Page Contents

System-wide debugging

You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.