# No stdout and logs from Packetbeat

**URL:** <https://discuss.elastic.co/t/no-stdout-and-logs-from-packetbeat/261517>\
**Category:** Beats\
**Tags:** packetbeat\
**Created:** [January 19, 2021, 9:21am UTC](https://discuss.elastic.co/t/no-stdout-and-logs-from-packetbeat/261517 "2021-01-19T09:21:57Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![GabrielJuilien](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gabrieljuilien/32/82516_2.png) [@GabrielJuilien](https://discuss.elastic.co/u/GabrielJuilien)\
**Post date:** [January 19, 2021, 9:21am UTC](https://discuss.elastic.co/t/no-stdout-and-logs-from-packetbeat/261517/1 "2021-01-19T09:21:57Z")

</div>

Hi everyone,

I am having trouble to setup Packetbeat on my client Windows. I already have som other Beats running and working as intended.  
The thing is I am getting no sdtout output in PowerShell when trying to run packetbeat (I am using the "zip" setup option), and no log aswell. The commands I ran are the following:

```auto
.\packetbeat.exe -c packetbeat.yml -e
.\packetbeat.exe setup -e
.\packetbeat.exe devices

```

None of those are giving an answer ☹

Do you have any suggestion ?

Packetbeat yml config file:

```auto
 =============================== Network device ===============================
 
# Select the network interface to sniff the data. On Linux, you can use the
# "any" keyword to sniff on all connected interfaces.
packetbeat.interfaces.device: 0
 
# =================================== Flows ====================================
 
# Set `enabled: false` or comment out all options to disable flows reporting.
packetbeat.flows:
  # Set network flow timeout. Flow is killed if no packet is received before being
  # timed out.
  timeout: 30s
 
  # Configure reporting period. If set to -1, only killed flows will be reported
  period: 10s
 
# =========================== Transaction protocols ============================
 
packetbeat.protocols:
- type: icmp
  # Enable ICMPv4 and ICMPv6 monitoring. Default: false
  enabled: true
 
- type: dhcpv4
  # Configure the DHCP for IPv4 ports.
  ports: [67, 68]
 
- type: dns
  # Configure the ports where to listen for DNS traffic. You can disable
  # the DNS protocol by commenting out the list of ports.
  ports: [53]
 
- type: http
  # Configure the ports where to listen for HTTP traffic. You can disable
  # the HTTP protocol by commenting out the list of ports.
  ports: [80, 8080, 8000, 5000, 8002]
 
- type: tls
  # Configure the ports where to listen for TLS traffic. You can disable
  # the TLS protocol by commenting out the list of ports.
  ports:
    - 443 # HTTPS
 
# ======================= Elasticsearch template setting =======================
 
setup.template.settings:
  index.number_of_shards: 1
  #index.codec: best_compression
  #_source.enabled: false
 
# ================================== General ===================================
 
# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:
 
# A list of tags to include in every event. In the default configuration file
# the forwarded tag causes Packetbeat to not add any host fields. If you are
# monitoring a network tap or mirror port then add the forwarded tag.
#tags: [forwarded]
 
# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging
 
# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false
 
# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:
 
# =================================== Kibana ===================================
 
# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:
 
  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  host: "https://10.105.0.7:5601"
 
  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:
 
# ================================== Outputs ===================================
 
# Configure what output to use when sending the data collected by the beat.
 
# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["https://10.105.0.7:9200"]
  ssl.verification_mode: none
 
  # Protocol - either `http` (default) or `https`.
  protocol: "https"
 
  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  username: "elastic"
  password: "changeme"
 
# ------------------------------ Logstash Output -------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["https://10.105.0.7:5044"]
 
  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
 
  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"
 
  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"
 
# ================================= Processors =================================
 
processors:
  - # Add forwarded to tags when processing data from a network tap or mirror.
    if.contains.tags: forwarded
    then:
      - drop_fields:
          fields: [host]
    else:
      - add_host_metadata: ~
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
 
# ================================== Logging ===================================
 
# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug
 
# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]
 
# ================================= Migration ==================================
 
# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true

```

Thank you.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 16, 2021, 11:21am UTC](https://discuss.elastic.co/t/no-stdout-and-logs-from-packetbeat/261517/2 "2021-02-16T11:21:59Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.