Failed to start tailwatchd - Unit tailwatchd service entered failed state

Failed to start tailwatchd.

Unit tailwatchd.service entered failed state. 

tailwatchd.service failed.

tailwatchd has failed. Contact your system administrator if the service does not automagically recover.


This can often occur when multiple instances of tailwatchd are running. Perform the following via SSH:

ps aux | grep tailwatchd
kill -9 #


Where # will be all the processes listed. Once the processes are all killed perform:

/bin/systemctl restart  tailwatchd.service
or
service tailwatchd restart

 

  • 108 Users Found This Useful

Was this answer helpful?

Related Articles

Error: Multilib version problems found

Finished Dependency Resolution Error:  Multilib version problems found. This often means that...

error: db3 error(-) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery

error: db3 error(-) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery...

VPS Time not Correct with Time Server

If you have a problem with your VPS time not staying sync in a Xen VPS you will want to enable...

ModSecurity: collection_store: Failed to access DBM file /var/cpanel/secdatadir/ip: Permission denied

The error Failed to access DBM file /var/cpanel/secdatadir/ip: Permission denied can occur on...

Account's error_log produces flood of missing modules

 Account's error_log produces flood of missing modules. Ex:   From error_log:     [23-Apr-2018...