I'm coming from bug #590862 which was marked as a duplicate of this bug. And I had been asked to outline my network configuration.
No, there is no error message in nmbd.log at all. The reason for not starting is not a failure in configuration. It always starts properly when I launch it manually with service nmbd start.
On that machine I am using just a static ethernet network configuration.
I'll attach my /etc/network/interfaces file.
As far as I can see the problem is that nmbd is simply not always started at boottime. Interestingly I found it to be running in rare cases.
My guess is that there is a timing problem with the net-device-up signal.
The major problem might be the lack of proper documentation for the upstart code (and an increasing ignorance of the upstart maintainers).
I'm coming from bug #590862 which was marked as a duplicate of this bug. And I had been asked to outline my network configuration.
No, there is no error message in nmbd.log at all. The reason for not starting is not a failure in configuration. It always starts properly when I launch it manually with service nmbd start.
On that machine I am using just a static ethernet network configuration.
I'll attach my /etc/network/ interfaces file.
As far as I can see the problem is that nmbd is simply not always started at boottime. Interestingly I found it to be running in rare cases.
My guess is that there is a timing problem with the net-device-up signal.
The major problem might be the lack of proper documentation for the upstart code (and an increasing ignorance of the upstart maintainers).