Astro Binding not working constantly

Hey Community,

I’m using openhab since a fewe weeks now and really like it.
But I’m also facing some issues with the astro binding.
Basically I’m using it for turning on or off some lights when the sun sets or rises.
The rule was working for some days and then stopped working without editing any of the rules and/or items. I write a log entry each time a rule was triggered so I can find it easier in the logfile. Therefor I can say, that the rule wasn’t triggered at all. When I was the checking the log I found the folowwing entry from which I would say, that there was an issue on updating the times for sunrise and sunset. Though I don’t know what to do about it.

Can someone with more insight help me, maybe?

2017-08-07 00:00:00.089 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:moon:home
2017-08-07 00:00:00.267 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:homenooffset
2017-08-07 00:00:00.271 [INFO ] [thome.binding.astro.internal.job.Job] - Scheduled Astro event-jobs for thing astro:sun:home
2017-08-07 00:00:00.276 [ERROR] [thome.binding.astro.internal.job.Job] - Queue full
java.lang.IllegalStateException: Queue full
	at java.util.AbstractQueue.add(AbstractQueue.java:98)[:1.8.0_121]
	at org.eclipse.smarthome.binding.astro.handler.AstroThingHandler.addJobToQueue(AstroThingHandler.java:314)[176:org.eclipse.smarthome.binding.astro:0.9.0.b5]
	at org.eclipse.smarthome.binding.astro.internal.job.Job.schedule(Job.java:58)[176:org.eclipse.smarthome.binding.astro:0.9.0.b5]
	at org.eclipse.smarthome.binding.astro.internal.job.Job.scheduleEvent(Job.java:94)[176:org.eclipse.smarthome.binding.astro:0.9.0.b5]
	at org.eclipse.smarthome.binding.astro.internal.job.Job.scheduleRange(Job.java:114)[176:org.eclipse.smarthome.binding.astro:0.9.0.b5]
	at org.eclipse.smarthome.binding.astro.internal.job.DailyJobSun.run(DailyJobSun.java:56)[176:org.eclipse.smarthome.binding.astro:0.9.0.b5]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)[:1.8.0_121]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_121]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)[:1.8.0_121]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)[:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_121]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_121]
	at java.lang.Thread.run(Thread.java:745)[:1.8.0_121]

What build number are you on? Looks like you are seeing this, which is fixed in the more recent snapshot builds.

Hi Mark,

I did not know that - somehow I even screwed up on finding that specific thread :wink:
I’ll check the version when I’m at home and will then update/close this thread.

Thanks again!

WeirdWizard