# Packetbeat installation issues **URL:** \ **Category:** Beats\ **Tags:** packetbeat\ **Created:** [January 8, 2018, 1:24pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528 "2018-01-08T13:24:20Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![purpleturtle99](https://avatars.discourse-cdn.com/v4/letter/p/a9adbd/32.png) [@purpleturtle99](https://discuss.elastic.co/u/purpleturtle99)\ **Post date:** [January 8, 2018, 1:24pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/1 "2018-01-08T13:24:20Z")
I have installed Elastic search and Kibana on Fedora 27 and got them to work. But I would like to do network monitoring with packetbeat. When I follow the rpm install instructions as per : [https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-installation.html](https://www.elastic.co/guide/en/beats/packetbeat/current/packetbeat-installation.html) The bin file gets installed under /etc/packetbeat but the packetbeat.yml file under /home/user/packetbeat. then I was unable to run ./packetbeat to import index or set up dashboards. as they weren't in the same dir. So I downloaded the linux tar file extracted that to a dir in the /home/usr and hey presto the .yml and bin files were in the same dir so I could run a few commands. But now I can't import index nor the dashboard. Yes I have x-pack installed and yes I have set the usernames and password in the yml accordingly? All help appreciated. ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [January 9, 2018, 12:34pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/2 "2018-01-09T12:34:50Z")
Which packetbeat version have you installed? You changed packetbeat version when using the tarball? How exactly do you run packetbeat by now? Can you try to run packetbeat in foreground with `-e -v -d '*'` to print debug logs? Please share debug logs ---
**Author:** ![purpleturtle99](https://avatars.discourse-cdn.com/v4/letter/p/a9adbd/32.png) [@purpleturtle99](https://discuss.elastic.co/u/purpleturtle99)\ **Post date:** [January 9, 2018, 1:07pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/3 "2018-01-09T13:07:38Z")
That was done on a clean install on Fedora 27 so no upgrade just the version as per install instructions from: curl -L -O [https://artifacts.elastic.co/downloads/beats/packetbeat/packetbeat-6.1.1-amd64.deb](https://artifacts.elastic.co/downloads/beats/packetbeat/packetbeat-6.1.1-amd64.deb) so it would be version 6.1.1. I have now formatted the hard drive that it was installed on but later today I will be installing Ubuntu desktop and then try again and see if the .yml file is in the same dir as bin. Can you please explain a bit more as to how to get the debug log files? ./packetbeat -e -v -d '\*'. Would this then print the log to the terminal? ---
**Author:** ![purpleturtle99](https://avatars.discourse-cdn.com/v4/letter/p/a9adbd/32.png) [@purpleturtle99](https://discuss.elastic.co/u/purpleturtle99)\ **Post date:** [January 9, 2018, 2:45pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/4 "2018-01-09T14:45:45Z")
Right, A fresh install of Ubuntu 16.04.3 only sudo apt-get updates and upgrade run. NO other install e.g kibana or x-pack. then run sudo apt-get install libpcap0.8 sudo yum install curl curl -L -O [https://artifacts.elastic.co/downloads/beats/packetbeat/packetbeat-6.1.1-amd64.deb](https://artifacts.elastic.co/downloads/beats/packetbeat/packetbeat-6.1.1-amd64.deb) sudo dpkg -i packetbeat-6.1.1-amd64.deb ![etc_packetbeat](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1f2e7b03f0e1bbe4f661303e301bb15d5074f5a2.png) ![user share](https://us1.discourse-cdn.com/elastic/original/3X/b/9/b93169cf520a22ab7e342120683f053f7457955b.png) ![etc_packetbeat](https://us1.discourse-cdn.com/elastic/original/3X/1/f/1f2e7b03f0e1bbe4f661303e301bb15d5074f5a2.png) ![user share](https://us1.discourse-cdn.com/elastic/original/3X/b/9/b93169cf520a22ab7e342120683f053f7457955b.png) and as per screenshot the .yml file and bin files are in different dir .yml in /etc/packetbeat bin in /usr/share/packetbeat ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [January 9, 2018, 3:07pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/5 "2018-01-09T15:07:25Z")
That's correct. The binary and other files are stored in `/usr/share/packetbeat`, while the config files are stored in `/etc/packetbeat`. For linux installs using rpm/deb we also install a packetbeat wrapper script into /usr/bin, configuring the correct paths. Don't run packetbeat from `/usr/share/packetbeat/bin`. You can set the config file to use via `-c `. ---
**Author:** ![purpleturtle99](https://avatars.discourse-cdn.com/v4/letter/p/a9adbd/32.png) [@purpleturtle99](https://discuss.elastic.co/u/purpleturtle99)\ **Post date:** [January 10, 2018, 9:02am UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/6 "2018-01-10T09:02:21Z")
Hi Steffen Really appreciate your help on this, but I am as confused as ever regarding this apology I am a newbie to packetbeat I must admit. What is this wrapper script called in /usr/bin? And how would I set the path? and what to set it too? via -c \ Reagrds Harry ---
**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\ **Post date:** [January 10, 2018, 12:20pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/7 "2018-01-10T12:20:04Z")
With 6.1 the wrapper script is called `packetbeat` (given you installed via rpm/deb packet). That is, do not switch to `/usr/share/packetbeat/bin` and don't run `./packetbeat` from this directory. The script provided in `/usr/bin/packetbeat` sets up the path and will run `/usr/share/packetbeat/bin/packetbeat -c /etc/packetbeat/packetbeat.yml` for you. Just switch to your home directory and test packetbeat by running: ```auto $ packetbeat -e -v -d '*' ``` This will start packetbeat in debug mode. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 7, 2018, 12:20pm UTC](https://discuss.elastic.co/t/packetbeat-installation-issues/114528/8 "2018-02-07T12:20:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.