Receiving "service name conflict" errors after upgrade from 0.4.38 to 1.7

barrydick · 26. Dezember 2014

Hi I have just completed a rather rocky upgrade from 0.4.38 to 1.7. Everything seems to be working ok but i am seeing these 'service name conflict' logs when restarting the system. Is this a problem and if so how do I resolve? Thanks

Code

Dec 26 11:03:46 MediaServer monit: /etc/monit/conf.d/openmediavault-system.conf:1: Error: service name conflict, localhost already defined 'localhost'
Dec 26 11:03:46 MediaServer monit: /etc/monit/conf.d/openmediavault:6: Error: service name conflict, rootfs already defined '/'
Dec 26 11:03:46 MediaServer monit: /etc/monit/conf.d/collectd:1: Error: service name conflict, collectd already defined '/var/run/collectd.pid'

datadigger · 26. Dezember 2014

Probably something that happened during the upgrade, to me it looks like some definitions are now contained twice in the mentioned config files.
Are you familiar with using an editor at the CLI? Open the file /etc/monit/conf.d/openmediavault-system.conf and and check if the localhost definition appears twice.

barrydick · 26. Dezember 2014

I think I've fixed this. There was a few duplicate files in '/etc/monit/conf.d/' with the same contents, eg a 'system' file and a 'openmediavault-system.conf' file with the same contents. I've got rid of the duplicates and the error messages have gone away.

Thanks for your help!

Jetzt mitmachen!