Due to the way all daemons are wired, it is very likely that the first daemon loading its spring application context while starting OpenNMS will fail, if something is fishy over all daemons (e.g. datacollection file is missing). In some cases the result may vary, but in probably almost all cases if anything is not configured correctly in OpenNMS and while loading the Spring Application Context Eventd will most likely always complain, as it is the first daemon to start/load.
This is nothing which is worth fixing in my opinion.
In this case a XML datacollection file was missing. But the interesting part is, why eventd is complaining about.
I found this issue because ONMS did not start anymore. But this issue is handled in an other issue. See links.