Open haf opened 9 years ago
Hmmmm... not sure what is going on in here.
I've just tried to reproduce and could not.
System is a vanilla CentOS.
# /usr/bin/hekad
2015/09/20 21:08:27 Error reading config: Error opening config file: open /etc/hekad.toml: no such file or directory
# touch heka.toml
# /usr/bin/hekad -config=heka.toml
2015/09/20 21:09:24 Pre-loading: [ProtobufDecoder]
2015/09/20 21:09:24 Loading: [ProtobufDecoder]
2015/09/20 21:09:24 Pre-loading: [ProtobufEncoder]
2015/09/20 21:09:24 Loading: [ProtobufEncoder]
2015/09/20 21:09:24 Pre-loading: [TokenSplitter]
2015/09/20 21:09:24 Loading: [TokenSplitter]
2015/09/20 21:09:24 Pre-loading: [HekaFramingSplitter]
2015/09/20 21:09:24 Loading: [HekaFramingSplitter]
2015/09/20 21:09:24 Pre-loading: [NullSplitter]
2015/09/20 21:09:24 Loading: [NullSplitter]
2015/09/20 21:09:24 Starting hekad...
2015/09/20 21:09:24 MessageRouter started.
^C2015/09/20 21:09:25 Shutdown initiated.
2015/09/20 21:09:25 Waiting for decoders shutdown
2015/09/20 21:09:25 Decoders shutdown complete
2015/09/20 21:09:25 Shutdown complete.
The issue happens if you explicitly use an empty directory as the config setting, or if you point it at an empty TOML file. I've opened #1740 which should resolve.
@rafrombrc
Cool. I could not reproduce the issue, even with an empty file (note the touch heka.toml
step taken above) but happy to assume it happens.
Cheers
Yeah I think it was only happening when the empty TOML file was in a directory and Heka was pointed at the folder for its config.
Maybe it's because there are no config folder. But the software should not panic like this; it should specify the error of the config.