Entries Not Flushing Through

19 views
Skip to first unread message

Richard Herbert

unread,
Apr 22, 2014, 9:35:31 AM4/22/14
to bugl...@googlegroups.com
Hi,

I'm starting to play with BugLogHQ and don't seem to be seeing entries in the db or dashboard until I do a stop/start at which point records seem to be flushed through.

Known issue or configuration problem?

Ciao for now,

Richard

Oscar Arevalo

unread,
Apr 22, 2014, 9:43:53 AM4/22/14
to bugl...@googlegroups.com

No Richard,
It might be that the scheduled task is not running or that it is generating an error on each run.
Please click on the icon next to the start/stop link. That will show the current messages on the queue, along with the internal error log. See if there are any clues there.

Also check your config for the server url setting to make sure that it's the correct one.

Let us know what you find.

Oscar

--

---
You received this message because you are subscribed to the Google Groups "BugLogHQ" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bugloghq+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Richard Herbert

unread,
Apr 22, 2014, 10:20:56 AM4/22/14
to bugl...@googlegroups.com
Hi Oscar,

Thanks for the prompt reply.

Yes, my error is being shown in the queue.

There are no scheduled task errors shown.
The task is being run on schedule according to the ColdFusion logs.

If I run the scheduled task from the ColdFusion Admin interface then the queue is not flushed.

If I run the scheduled task URL manually in a new browser tab the queue is flushed.

Not sure what you mean by "config for the server url setting"?

Does this help?

Ciao for now,

Richard

Richard Herbert

unread,
Apr 22, 2014, 10:31:40 AM4/22/14
to bugl...@googlegroups.com
Hold on!

As soon as I posted my reply I had a light bulb moment.

My local dev environment has a self-signed certificate to mimic production. The URL of the scheduled task created by BugLogHQ was https rather than http.

I changed the protocol to http and all seems to be working. I'm guessing the scheduled task was failing silently due to the certificate credentials not being recognised.

Sorry to worry you :-)

Ciao for now,

Richard
Reply all
Reply to author
Forward
0 new messages