Have any new lines been written to daemon.log ? :)
You can increase the verbosity level of the logging with --v=2, which will spew out a lot more.
Once you get some interesting logs, you can refine it with --vmodule instead, e.g.:
--vmodule=tail=2
would increase verbosity just for tail.go's logging.
The data flow should be that the log_watcher gets notified of a file system event when daemon.log changes, which triggers a read to EOF of that file by the tailer. Each line is fed through a channel to the program loader, which fans them out into each VM. The VM handles the log lines, including mutaing the exported variables.
Potential bugs:
1. The fsnotify code doesn't work.
2. The tailer isn't getting notified of a change to the log file
3. A bug in the EOF read in tail.go
4. A bug in the loader not passing log lines to VMs
5. A bug in the exporter causing metrics to not be exported properly.
You mention this is the debian package. I don't know how it's packaged, but assuming it's barely changed from the git repo, then I presume you should be able to check out that git commit from the final part of the version string on the master branch and be able to repro this, and if you can, I'd like to know what go compiler version you have, and the output of 'make check'.
Then the loader will
The two places i'd be looking at first are the tailer, to ensure logs are being read from