Bobcares

WeSupport

Call Us! 1-800-383-5193
Call Us! 1-800-383-5193
Call Us! 1-800-383-5193

Need Help?

Emergency Response Time custom

Our experts have had an average response time of 11.06 minutes in March 2021 to fix urgent issues.

We will keep your servers stable, secure and fast at all times for one fixed price.

ERROR A worker was found in a dead state – Ansible

by | Jun 30, 2021

Stuck with ERROR A worker was found in a dead state? We can help you.

Generally, we come across this error when there is a disruption in deploying an Ansible module to a target machine.

As part of our Server Management Services, we assist our customers with several Ansible queries.

Today, let us see how we can fix this error.

 

ERROR A worker was found in a dead state

Ansible works by connecting to the target machine from the ansible controller over SSH.

It will then push small programs called “Ansible Modules” to the target machine and executes them.

Moving ahead, let us see how our Support Techs identify the cause of the problem.

Initially, we need to enable a verbose mode of ansible.

ansible-playbook -vvv playbook.yml

The -vvv flag to the ansible command will allow us to get a detailed log of what is happening on the terminal itself.

 

Possible causes and fix

  • The Target machine is Out of Memory

When the target machine is a container or VM with less memory, this error can occur.

In order to fix this, we just need to increase the memory of the target container.

  • The number of workers is over the limit

The default number of ansible forks is 5. If the ansible controller has any limitation per process, it will cause problems while executing 5 parallel processes at a time.

If we change the strategy of execution of ansible, we resolve this problem.

In the ansible command, we use the flag -f to determine the number of forks used :

ansible-playbook -vvv playbook.yml -f1

This command will reduce the forks number to 1.

  • The Ansible module timed out

If we run a process that takes a lot of time, we add a pause or wait_for ansible modules in the playbook.

Especially, if the playbook has modules like restarting the target machine or specific service.

[Still, stuck with the error? Let us take a look into it]

 

Conclusion

In short, we saw how our Support Techs fix the Ansible error for our customers.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF