[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Database errors when starting up rhythm microservice

Hey Courage,

I assume you mean this?
rhythm-ms    | 22:52:39.200 [pool-9-thread-1] ERROR
o.h.e.jdbc.spi.SqlExceptionHelper - Table 'seshat.khepri_beats'
doesn't exist

What's happening there is that there's an event which triggers at
regular intervals and checks if its time to trigger events to the
other services.  In order to check, it needs to know when the events
for the other services are due.  That is saved in the database table.
So it queries that table.  But because rhythm isn't provisioned yet,
that exception flies.  As soon as rhythm is provisioned you'll stop
getting that error.

This isn't ideal.  Non-fatal errors shouldn't show up like that in the
log.  Pull requests (very) welcome.  But as long as you're not getting
that error message after provisioning is complete, the error is not
something you need to worry about.

Best Regards,

On Tue, Oct 9, 2018 at 4:52 AM Courage Angeh <courageangeh@xxxxxxxxx> wrote:
> Hi Myrle,
> Hope this message finds you well. I get this error:
> https://pastebin.com/kgCR320x when starting up the rhythm microservice.
> I have done some debugging and I think its a configuration error 'cause it
> starts-up normally and it supposed to stop at `[main] INFO
> o.a.f.c.r.service.RhythmApplication - Started RhythmApplication in 28.08
> seconds (JVM running for 29.812)`. But it goes ahead to try to provision
> before time therefore it get that error.
> Here is the configuration: https://pastebin.com/YaeFT61a that's applied on
> the microservice.
> I will really appreciate some help
> Thanks,
> Courage