# How to run beats in linux 64 bit machine
**URL:** https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873
**Category:** Beats
**Tags:** packetbeat
**Created:** [January 22, 2016, 12:15pm UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873 "2016-01-22T12:15:19Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@rajkamalkool6](https://discuss.elastic.co/u/rajkamalkool6)
#### Post date: [January 22, 2016, 12:15pm UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873/1 "2016-01-22T12:15:19Z")
I am trying to start the packet beat in my linux machine(64bit). I am using the below command ,
`./packetbeat -e -c packetbeat.yml`. The system is waiting silently without throwing any error or any message.
Am I doing the procedure in right. Please correct me if I am wrong.
Thanks
---
### Author:  [@tudor](https://discuss.elastic.co/u/tudor)
#### Post date: [January 22, 2016, 12:23pm UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873/2 "2016-01-22T12:23:55Z")
That's about right. You can increase the verbosity with `-v` or `-d "*"` for all debug output. If it doesn't seem to pick up traffic, please post your config.
---
### Author:  [@rajkamalkool6](https://discuss.elastic.co/u/rajkamalkool6)
#### Post date: [January 22, 2016, 12:35pm UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873/3 "2016-01-22T12:35:33Z")
> [@tudor](#):
>
> -d "\*"
I didn't make changes in my yml file. I amusing the default setup only. I am getting this log information
> 2016/01/22 12:30:24.569096 beat.go:97: DBG Initializing output plugins
> 2016/01/22 12:30:24.569167 geolite.go:24: INFO GeoIP disabled: No paths were set under output.geoip.paths
> 2016/01/22 12:30:24.569239 client.go:244: DBG ES Ping(url=[http://localhost:9200](http://localhost:9200), timeout=1m30s)
> 2016/01/22 12:30:24.570128 client.go:253: DBG Ping status code: 200
> 2016/01/22 12:30:24.570147 outputs.go:111: INFO Activated elasticsearch as output plugin.
> 2016/01/22 12:30:24.570179 publish.go:198: DBG create output worker: 0x0, 0xc8210ae1a0
> 2016/01/22 12:30:24.570222 publish.go:235: DBG No output is defined to store the topology. The server fields might not be filled.
> 2016/01/22 12:30:24.570248 publish.go:249: INFO Publisher name: mysystem
> 2016/01/22 12:30:24.570385 async.go:95: DBG create bulk processing worker (interval=1s, bulk size=50)
> 2016/01/22 12:30:24.570438 beat.go:107: INFO Init Beat: packetbeat; Version: 1.0.1
> 2016/01/22 12:30:24.571105 packetbeat.go:153: DBG Initializing protocol plugins
> 2016/01/22 12:30:24.571118 memcache.go:105: DBG init memcache plugin
> 2016/01/22 12:30:24.571128 memcache.go:158: DBG maxValues = 0
> 2016/01/22 12:30:24.571134 memcache.go:159: DBG maxBytesPerValue = 2147483647
> 2016/01/22 12:30:24.571189 mongodb.go:73: DBG Init a MongoDB protocol parser
> 2016/01/22 12:30:24.571293 tcp.go:211: DBG Port map: map[8002:http 3306:mysql 5432:pgsql 27017:mongodb 8080:http 5000:http 11211:memcache 6379:redis 9090:thrift 80:http 8000:http]
> 2016/01/22 12:30:24.571312 udp.go:93: DBG Port map: map[53:dns 11211:memcache]
> 2016/01/22 12:30:24.571319 packetbeat.go:192: DBG Initializing sniffer
> 2016/01/22 12:30:24.571341 sniffer.go:247: DBG BPF filter: tcp port 80 or tcp port 8080 or tcp port 8000 or tcp port 5000 or tcp port 8002 or tcp port 3306 or tcp port 6379 or tcp port 5432 or tcp port 9090 or tcp port 27017 or udp port 53 or port 11211
> 2016/01/22 12:30:24.571354 sniffer.go:129: DBG Sniffer type: pcap device: any
> 2016/01/22 12:30:24.580296 decoder.go:37: DBG Layer type: Linux SLL
> 2016/01/22 12:30:24.580451 beat.go:133: INFO packetbeat sucessfully setup. Start running.
> 2016/01/22 12:30:24.580465 packetbeat.go:224: DBG Waiting for the sniffer to finish
> 2016/01/22 12:30:24.580513 sniffer.go:293: DBG Interrupted
> 2016/01/22 12:30:25.081082 sniffer.go:293: DBG Interrupted
> 2016/01/22 12:30:25.581741 sniffer.go:293: DBG Interrupted
> 2016/01/22 12:30:26.082349 sniffer.go:293: DBG Interrupted
> 2016/01/22 12:30:26.582942 sniffer.go:293: DBG Interrupted
> 2016/01/22 12:30:27.083626 sniffer.go:293: DBG Interrupted
> 2016/01/22 12:30:27.584300 sniffer.go:293: DBG Interrupted
> 2016/01/22 12:30:28.084911 sniffer.go:293: DBG Interrupted
---
### Author:  [@daguero](https://discuss.elastic.co/u/daguero)
#### Post date: [March 10, 2016, 3:53pm UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873/4 "2016-03-10T15:53:07Z")
I have the same problem, any idea how to solve????
---
### Author:  [@steffens](https://discuss.elastic.co/u/steffens)
#### Post date: [March 18, 2016, 1:46pm UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873/5 "2016-03-18T13:46:45Z")
Have you tried running packetbeat as root? Is promiscuous mode enabled for your NICs?
---
### Author:  [@rajkamalkool6](https://discuss.elastic.co/u/rajkamalkool6)
#### Post date: [March 21, 2016, 11:57am UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873/6 "2016-03-21T11:57:29Z")
It has been solved for me. I have commented some unused setting which is not relevant for my scenario . It has working now.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 9:54pm UTC](https://discuss.elastic.co/t/how-to-run-beats-in-linux-64-bit-machine/39873/7 "2017-07-05T21:54:25Z")