Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't restart splunk docker after ubuntu upgrade #45

Closed
SirTerrific opened this issue Oct 19, 2018 · 4 comments
Closed

Can't restart splunk docker after ubuntu upgrade #45

SirTerrific opened this issue Oct 19, 2018 · 4 comments
Assignees

Comments

@SirTerrific
Copy link

SirTerrific commented Oct 19, 2018

VM Ubuntu 16.04

I use a splunk docker on en VM ubuntu. After the upgrade, I restarted the VM but splunk docker can't start.

splunk | Friday 19 October 2018 03:09:30 +0000 (0:00:41.411) 0:00:41.565 ********
splunk | ===============================================================================
splunk | Gathering Facts -------------------------------------------------------- 41.41s
splunk | [WARNING]: provided hosts list is empty, only localhost is available. Note
splunk | that the implicit localhost does not match 'all'
splunk |
splunk |
splunk | PLAY [localhost] ***************************************************************
splunk |
splunk | TASK [Gathering Facts] *********************************************************
splunk | Friday 19 October 2018 03:09:40 +0000 (0:00:00.197) 0:00:00.198 ********
splunk | An exception occurred during task execution. To see the full traceback, use -vvv. The error was: TimeoutError: Timer expired after 10 seconds
splunk | fatal: [localhost]: FAILED! => {"changed": false, "cmd": "/bin/lsblk --list --noheadings --paths --output NAME,UUID --exclude 2", "msg": "Timer expired after 10 seconds", "rc": 257}
splunk | to retry, use: --limit @/opt/ansible/ansible-retry/site.retry
splunk |
splunk | PLAY RECAP *********************************************************************
splunk | localhost : ok=0 changed=0 unreachable=0 failed=1
splunk |
splunk | Friday 19 October 2018 03:09:59 +0000 (0:00:19.578) 0:00:19.777 ********
splunk | ===============================================================================
splunk | Gathering Facts -------------------------------------------------------- 19.58s
splunk exited with code 2

All worked well before.
Do you have any ideas?

@bb03 bb03 self-assigned this Oct 22, 2018
@bb03
Copy link
Contributor

bb03 commented Oct 22, 2018

@SirTerrific Taking a look at this now. Can you give me more information about the workflow used. The title says you were restarting the container and the contents say you were starting it. I want to make sure that I get the exact workflow down.

@bb03
Copy link
Contributor

bb03 commented Oct 22, 2018

Here's the environment that I tested on.

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.5 LTS"

I did not have any issues in this environment. More details about your error would be nice, thank you!

@bb03
Copy link
Contributor

bb03 commented Oct 25, 2018

Under the environment listed, could not reproduce the issue. Seemed to run fine.

@SirTerrific
Copy link
Author

SirTerrific commented Oct 27, 2018

I was using a VM on HyperV v1 and it's seem that the hypervisor is the problem. I tried with a debian, ubuntu and alpine and I had the same issue with the splunk 7.2 docker. I installed on a non Virtualize system with the same OS' and all works. So with the VM, I'm able to use the 7.1.2 docker with alpine OS as host and all work great.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants