Closed AlessioCasco closed 8 years ago
the time between your capture box and capture server are not synced. please use ntpdate for this.
They are bot synced with same date, and were synced back on the 22nd and 24th:
web server~# date Tue Jan 26 11:09:13 UTC 2016
DB machine~# date Tue Jan 26 11:09:13 UTC 2016
same on the capture machine
Hi Alessio, I'd suggest you take a trace of the DB queries performed by Homer, then try them manually on the DB. It's been useful in some cases to check the data consistency.
Messages are looked up not just with the ID but also with a reference to the timestamp, so there may be an issue in that area even though the host clocks are well sync'd.
If it's not a time issue, again those queries will show you what Homer is trying to look up and you can compare with the actual data stored.
Giacomo
On 26 January 2016 at 12:13, Alessio Casco notifications@github.com wrote:
They are bot synced with same date, and were synced back on the 22nd and 24th:
web server~# date Tue Jan 26 11:09:13 UTC 2016
DB machine~# date Tue Jan 26 11:09:13 UTC 2016
— Reply to this email directly or view it on GitHub https://github.com/sipcapture/homer-api/issues/69#issuecomment-174960083 .
Thanks guys!
Will have a look and let you know!
Alessio
any progress ?
Not yet sorry, will try to have a look into it tomorrow
Sorry for the late
Hello Guys,
I'm unable to reproduce this issue, so will close it for now, and update with the findings as soon as it happens again.
Thanks for your help, will keep you posted
Alessio
Hello.
I just noticed, that for a very small amount of calls, HOMER returns me blank results on the details page, even when looks like the DB has all the info on it (at least the data db):
This is what I see:
Call was made on the 22nd, query on homer on the 24th, we keep the data for more than 2 days in the db
Any idea why is this happening?
Thanks Alessio