Filebeat service not starting on reboot after OS upgrade

Elastic Stack Beats
1

Hi,
we were running filebeat 5.6.8 on an Ubuntu 14.04 machine until recently. After a release upgrade to Ubuntu 16.04 via do-release-upgrade, the filebeat service is not starting on system startup any longer.
service filebeat status only says it inactive (dead). The logs show nothing. It is possible to start the service just fine with service filebeat start. However, since that machine is being shut down and started automatically, the service start at boot is required.
Please advise.

2

your problem is [probably] not related to filebeat...

try systemctl enable --now filebeat.service and post the result

3

Indeed it was not. The problem was that Ubuntu 16 does not use the init.d Scripts any longer.