server monitor agent service doesn't start on Ubuntu 16.04

[theRAAPster]

Using the latest release (2.24.0), newrelic-sysmond does not start on Ubuntu 16.04. Chef-client thinks the service is already running, from the first run:

       * apt_package[newrelic-sysmond] action install
        - install version 2.3.0.132 of package newrelic-sysmond
      * template[/etc/newrelic/nrsysmond.cfg] action create
        - update content in file /etc/newrelic/nrsysmond.cfg from 047f66 to 958ba5
        - suppressed sensitive resource
        - change owner from 'newrelic' to 'root'
      * service[newrelic-sysmond] action enable (up to date)
      * service[newrelic-sysmond] action start
        - start service service[newrelic-sysmond]
      * service[newrelic-sysmond] action restart
        - restart service service[newrelic-sysmond]

From follow up runs:

        * file[/etc/apt/sources.list.d/newrelic.list] action create (up to date)
  (up to date)
      * apt_package[newrelic-sysmond] action install (up to date)
      * template[/etc/newrelic/nrsysmond.cfg] action create (up to date)
      * service[newrelic-sysmond] action enable (up to date)
      * service[newrelic-sysmond] action start (up to date)
       (up to date)

Service status when logged in to the VM:

vagrant@default-ubuntu-1604:~$ sudo service newrelic-sysmond status

• newrelic-sysmond.service - LSB: The New Relic Server Monitor
  Loaded: loaded (/etc/init.d/newrelic-sysmond; bad; vendor preset: enabled)
  Active: inactive (dead)
  Docs: man:systemd-sysv-generator(8)

Newrelic processes running after a kitchen converge:

vagrant@default-ubuntu-1604:~$ sudo ps aux | grep newrelic
newrelic 6137 0.0 0.0 16996 212 ? Ss 16:07 0:00 /usr/sbin/nrsysmond -c >/etc/newrelic/nrsysmond.cfg -p /var/run/newrelic/nrsysmond.pid
newrelic 6139 0.0 1.5 252016 7788 ? Sl 16:07 0:00 /usr/sbin/nrsysmond -c >/etc/newrelic/nrsysmond.cfg -p /var/run/newrelic/nrsysmond.pid
vagrant 6733 0.0 0.4 16572 2064 pts/0 S+ 16:25 0:00 grep --color=auto newrelic

Manually running "sudo service newrelic-sysmond start" works, which indicates the install process is working fine, there just appears to be an issue with starting the service via the chef-client. This plus the fact that it works with Ubuntu 14.04 led me to find these issues indicating it might be an issue with the init.d script: http://serverfault.com/questions/495969/service-doesnt-start-when-using-chef
https://stackoverflow.com/questions/39340867/chef-wont-start-my-init-d-service

My environment:

• chefdk-0.19.6-1
• virtualbox 5.1.8
• vagrant 1.8.7
• bento/ubuntu-16.04 (virtualbox, 2.3.0)

Still trying to work out a fix, but I was hoping somebody smarter than me might have an idea or be able to fix it faster.

[binkocd]

I am wondering if the issue isn't with the switch to systemd that Ubuntu between 14.04 and 16.04. My company doesn't allow, as of this moment, Ubuntu boxen on the network/in corp systems, so I can't confirm/test/etc, but that is my suspicion. I'll dig in later tonight if time allows.

[djoos]

Hi @theRAAPster,

are you still having this issue with the latest version(s) of the cookbook?

Thanks in advance!

Kind regards,
David