You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I turn off my wi-fi connection and run elasticsearch, tried with 1.7, 2.3 and 5.0 and it is always the same, the process prints out the following to start with:
log4j:WARN No appenders could be found for logger (common).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
The logging.yml is the default one. After that everything looks ok, usual logging etc.. I guess this is due to the order of initialization of our logging, we may be ok with this initial warning but maybe there is something that we want to do about it.
The text was updated successfully, but these errors were encountered:
Now the coup de grâce. The method MacAddressProvider#getSecureMungedAddress tries to get a secure MAC address for use in generating the time-based UUIDs. If all the network interfaces are disabled, then there is no MAC address to use so the check on line 73 passes:
73: if (!isValidAddress(address)) {
which leads to the fatal logging statement on line 74:
74: logger.warn("Unable to get a valid mac address, will use a dummy address");
This line being fatal because it's invoked before logging has been initialized.
Two lessons:
static is evil, don't do static
logging in static methods using a statically-initialized static logger (instead of an instance of logger from an AbstractComponent) is prone to this problem
If I turn off my wi-fi connection and run elasticsearch, tried with 1.7, 2.3 and 5.0 and it is always the same, the process prints out the following to start with:
The
logging.yml
is the default one. After that everything looks ok, usual logging etc.. I guess this is due to the order of initialization of our logging, we may be ok with this initial warning but maybe there is something that we want to do about it.The text was updated successfully, but these errors were encountered: