# Rule engine not running although bundle active?

**URL:** <https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517>\
**Category:** Installation\
**Tags:** rules-dsl\
**Created:** [January 8, 2025, 10:18am UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517 "2025-01-08T10:18:10Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![bjscheue](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/5e9695/32.png) [@bjscheue](https://community.openhab.org/u/bjscheue)\
**Post date:** [January 10, 2025, 5:14pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/21 "2025-01-10T17:14:28Z")

</div>

Thanks for pointing this out. This was not at all clear for me from the information that I could find online before upgrading. Actually, quite in contrast, there were quite a few posts in this forum which talked about doing exactly what I did: install OH 4, restore a backup from OH 3.x, run the upgradetool. I think it was even you, @rlkoshak, who recommended doing it like this here: [Upgrade 3.4 to 4, but how? - #2 by rlkoshak](https://community.openhab.org/t/upgrade-3-4-to-4-but-how/151031/2) 😉

Of course I ran the upgradetool after restoring the backup and before starting OH 4 for the first time.

If restoring a 3.x backup (+ running the upgradetool) to migrate a backed-up OH 3.x configuration into OH4 does indeed not (or no longer) work, this might deserve some clear(er) advice in the documentation? If it _does_ work (as several earlier threads indicate), it might be worth pointing out that this is not the case for full backups.

---

<div class="post-metadata">

**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\
**Post date:** [January 10, 2025, 5:20pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/22 "2025-01-10T17:20:25Z")

</div>

> [@bjscheue](#):
>
> If restoring a 3.x backup (+ running the upgradetool) to migrate a backed-up OH 3.x configuration into OH4 does indeed not (or no longer) work,

OH 3.4 to 4.0 _can_ work that way but only for non-full backups.

Or you can clear the cache immediately after restoring the full backup but before running anything else (which essentially converts your full backup to a regular backup since the inclusion of cache and tmp is the only difference between a full and a regular backup.

But that was an exception and not guaranteed to work between any arbitrary OH versions down to the first point level (e.g. 4.2 to 4.3 may not work but 4.3.1 to 4.3.2 should work, though you won’t get any of the updates to your installed add-ons if you use a full backup).

---

<div class="post-metadata">

**Author:** ![bjscheue](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/5e9695/32.png) [@bjscheue](https://community.openhab.org/u/bjscheue)\
**Post date:** [January 10, 2025, 5:23pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/23 "2025-01-10T17:23:14Z")

</div>

Yep, now we seem to have reached consensus. 😉 That’s what I figured out the very hard way.

Therefore, again: a hint in the docs that full backups shouldn’t be used across versions would be very helpful. Or a warning message of the upgradetool, if the cache is not empty. Or a warning message when restoring a full backup into a newer OH version.

---

<div class="post-metadata">

**Author:** ![kstuken](https://community.openhab.org/letter_avatar_proxy/v4/letter/k/a9adbd/32.png) [@kstuken](https://community.openhab.org/u/kstuken)\
**Post date:** [January 10, 2025, 5:34pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/24 "2025-01-10T17:34:21Z")

</div>

Have just added my description to the Github issue.  
Have started experiencing this since upgrading to 4.3 from 4.2.  
64bit Openhabian, fairly large system, 1100 items, 135 things, \>70 JS rules, all files-based.

In my case the issue occurs occasionally (total of six times since upgrade to 4.3, approx every 4th of 5th system restart), but not reproducably. `sysctl restart openhab`has so far reliably fixed the issue when it occured. Nothing in the logs that would suggest an error, just that system only gets to runlevel 40 and not beyond, and then rules engine is not loaded. Which leaves the system functioning, but without any automation.

Key difference in my case compared to many of the other reports: virtually no DSL rules. (There was still one (active but unused) one, which I have now deactivated).

---

<div class="post-metadata">

**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\
**Post date:** [January 10, 2025, 5:46pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/25 "2025-01-10T17:46:15Z")

</div>

> [@bjscheue](#):
>
> Therefore, again: a hint in the docs that full backups shouldn’t be used across versions would be very helpful.

I’m not sure where backups and restores are documented in the first place. Not that people read the docs in the first place. But if you know where, there’s a link at the bottom of every documentation page where an edit can be submitted. It’s a great way to contribute to the project.

> [@bjscheue](#):
>
> Or a warning message of the upgradetool, if the cache is not empty.

On a normal upgrade, when upgradetool runs the cache wouldn’t be empty. I think teh cache is cleared as the last step. And you can run upgradetool at any time.

---

<div class="post-metadata">

**Author:** ![mstormi](https://community.openhab.org/user_avatar/community.openhab.org/mstormi/32/55857_2.png) [@mstormi](https://community.openhab.org/u/mstormi)\
**Post date:** [January 10, 2025, 5:43pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/26 "2025-01-10T17:43:35Z")

</div>

Off topic and sorry to be frank but no!  
Upgrade instructions are given where applicable such as in release notes and if users decide to do stuff beyond or ignoring that they must not expect that to work or docs/developers/maintainers to warn them of.

ALL software in general and their docs just don’t work that way.  
It’s impossible to list everything one must not do so it remains to be any user’s duty to read and follow the instructions.

---

<div class="post-metadata">

**Author:** ![bjscheue](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/5e9695/32.png) [@bjscheue](https://community.openhab.org/u/bjscheue)\
**Post date:** [January 10, 2025, 5:54pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/27 "2025-01-10T17:54:02Z")

</div>

Well… I read up as much as I could before going that step. And all I found indicated not only that this is possible, but even that it’s the recommended way of doing it when you are going to a new machine and a new OH version at the same time. I linked an example above.

Saying that it’s the user’s fault is… well… okay. But not if you want this to work for someone who doesn’t spend all their time in the intestines of this particular software.

---

<div class="post-metadata">

**Author:** ![mstormi](https://community.openhab.org/user_avatar/community.openhab.org/mstormi/32/55857_2.png) [@mstormi](https://community.openhab.org/u/mstormi)\
**Post date:** [January 10, 2025, 7:07pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/28 "2025-01-10T19:07:16Z")

</div>

> [@bjscheue](#):
>
> Saying that it’s the user’s fault is… well… okay. But not if you want this to work for someone who doesn’t spend all their time in the intestines of this particular software.

Oh yes, even and especially in that case. If some user does not want to go the extra mile of understanding the internals and proper context, that’s fine of course.  
But then they must be reading the official docs and stick to the documented procedures exclusively and not attempt stuff that’s not officially documented.  
So hands off if you don’t find mentioned what you’re about to try.  
Note Rich’ post you refer to was a _forum post_, and forum posts are not part of the official docs.  
And on the docs part, I’ll renew my statement that you must not expect _any_ software creator to document any No-Go.  
Again, that’s not how _any_ software docs work. It’s on the user to understand that upfront.

Now please get back on the thread topic. What I understood so far is you had a similar symptom after performing some unsupported form of upgrade (which probably caused that in the first place).  
Correct? So I don’t think analyzing that contributes to a solution here? or is there anything I missed?

---

<div class="post-metadata">

**Author:** ![bjscheue](https://community.openhab.org/letter_avatar_proxy/v4/letter/b/5e9695/32.png) [@bjscheue](https://community.openhab.org/u/bjscheue)\
**Post date:** [January 10, 2025, 7:26pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/29 "2025-01-10T19:26:18Z")

</div>

I used the upgrade tool which comes with OH 4.3 and states has the purpose of converting an OH 3.4 configuration to the new version. You are telling me that this despite this tool coming with 4.3 it must under no circumstances be used.

I tried to help. But never mind, I am off.

---

<div class="post-metadata">

**Author:** ![Will](https://community.openhab.org/user_avatar/community.openhab.org/will/32/71123_2.png) [@Will](https://community.openhab.org/u/Will)\
**Post date:** [January 14, 2025, 2:29pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/30 "2025-01-14T14:29:52Z")

</div>

I have/had many invalid cron… more than I thought 🙂  
I improved the script provided above. More in this post: [Script to check Quartz CRON format](https://community.openhab.org/t/script-to-check-quartz-cron-format/161714)

---

<div class="post-metadata">

**Author:** ![Will](https://community.openhab.org/user_avatar/community.openhab.org/will/32/71123_2.png) [@Will](https://community.openhab.org/u/Will)\
**Post date:** [January 16, 2025, 3:51pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/31 "2025-01-16T15:51:04Z")

</div>

Just doing some testing to validate cron expressions.

WARNING: Installing this rule will likely force you to restart the OH service. Do keep an eye on Load and Temperature if you copy this on your system.

I made a little test file that instantly chocked my install:

```auto
rule "junk"
when
    Time cron "0 0 8 * * ? *" or
    Time cron "0 0 20 * * ? *" or
    Time cron "0 0 19 ? * *" or
    Time cron "0 0 6 * * ?" or
    Time cron "0 0 21 * * ?" or
    Time cron "0 0 1 * * ?" or
    Time cron "0 0 5 * * ?" or
    Time cron "0 0 9 * * ?" or
    Time cron "0 0 10 * * ?" or
    Time cron "0 0 * * * ?" or
    Time cron "0 0 8 * * ?" or
    Time cron "0 0 5 * * ?" or
    Time cron "0 0 19 * * ?" or
    Time cron "0 0 20 * * ?" or
    Time cron "0 0 22 * * ?" or
    Time cron " 0 0 8 2 1 ?" or
    Time cron " 0 0 5 31 2 *" or
    Time cron "0 0 12 * * ?" or
    Time cron "0 0 9 * * ?" or
    Time cron "0 0 19 ? * *" or
    Time cron "0 0 17 * * ?" or
    Time cron "0 0 22 * * ?" or
    Time cron "0 0 22 * * *" or
    Time cron "0 * * * * ?" or
    Time cron "0 0 * * * ?" or
    Time cron "0 0 8 * * *" or
    Time cron "0 0 4 * * *" or
    Time cron "0 30 20 * * *" or
    Time cron "0 0 5 * * ?" or
    Time cron "0 0 7 * * ?" or
    Time cron "0 0 7 * * 2-6" or
    Time cron "0 30 19 * * *" or
    Time cron "0 30 20 * * * *" or
    Time cron "0 0 8 * * 2-6 *" or
    Time cron "0 0 13 * * 2-6" or
    Time cron "0 0 18 * * *" or
    Time cron "0 0 20 * * *" or
    Time cron "0 0 19 * * 2-6 *" or
    Time cron "0 25 19 * * * *" or
    Time cron "0 45 7 * * * *" or
    Time cron "0 30 19 * * ? *" or
    Time cron "0 15 6 * * ? *" or
    Time cron "0 0 6 * * * *" or
    Time cron "0 0 5 * * ? *"
then
end

```

---

<div class="post-metadata">

**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\
**Post date:** [January 16, 2025, 3:52pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/32 "2025-01-16T15:52:40Z")

</div>

> [@Will](#):
>
> I made a little test file that instantly chocked my install:

With the recently released 4.3.2? The cron expression problems should be fixed in that release. Two separate PRs related to cron expression parsing are included.

---

<div class="post-metadata">

**Author:** ![Will](https://community.openhab.org/user_avatar/community.openhab.org/will/32/71123_2.png) [@Will](https://community.openhab.org/u/Will)\
**Post date:** [January 16, 2025, 4:02pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/33 "2025-01-16T16:02:38Z")

</div>

Oh I did not see that one yet.  
Let me upgrade right away !

---

<div class="post-metadata">

**Author:** ![Will](https://community.openhab.org/user_avatar/community.openhab.org/will/32/71123_2.png) [@Will](https://community.openhab.org/u/Will)\
**Post date:** [January 16, 2025, 4:23pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/34 "2025-01-16T16:23:01Z")

</div>

I upgraded and rebooted.

I reintroduced my `junk.rules` above. The rule has been loaded, load increased slightly and went then right down to nothing.

Checking the logs, I see a WARN:

```auto
Failed to schedule job for trigger '16'. Invalid cron expression '0 0 5 31 2 *': Conditions not satisfied.

```

noice !

---

<div class="post-metadata">

**Author:** ![rlkoshak](https://community.openhab.org/user_avatar/community.openhab.org/rlkoshak/32/75251_2.png) [@rlkoshak](https://community.openhab.org/u/rlkoshak)\
**Post date:** [January 16, 2025, 4:31pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/35 "2025-01-16T16:31:33Z")

</div>

Great! That means the cron expression cause for this problem appears to be fixed. For everyone else on this thread who are seeing this problem without cron expressions, please test on 4.3.2 and report if the problem still persists. There is strong evidence that there’s more than one problem .

---

<div class="post-metadata">

**Author:** ![Tim\_R](https://community.openhab.org/user_avatar/community.openhab.org/tim_r/32/85402_2.png) [@Tim\_R](https://community.openhab.org/u/Tim_R)\
**Post date:** [January 17, 2025, 8:15pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/36 "2025-01-17T20:15:32Z")

</div>

I just upgraded to 4.3.2 and openhab started smoothly without any (unnormal) warning message.  
But I just tried to restart once…  
And I doubt that my issue was caused by an invalid cron expression.

---

<div class="post-metadata">

**Author:** ![jangerhart](https://community.openhab.org/user_avatar/community.openhab.org/jangerhart/32/106683_2.png) [@jangerhart](https://community.openhab.org/u/jangerhart)\
**Post date:** [January 25, 2025, 11:00am UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/37 "2025-01-25T11:00:45Z")

</div>

Hello,

there are my log entries which I think can help to investigate:

```yaml
2025-01-25 11:32:26.672 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Dependency not satisfied: $000
2025-01-25 11:32:26.672 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Dependency not satisfied: $001
2025-01-25 11:32:26.672 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Dependency not satisfied: $002
2025-01-25 11:32:26.673 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Not all dependencies satisfied, cannot activate

```

Some entries about the dependencies:

```yaml
2025-01-25 11:32:26.639 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Updating target filters
2025-01-25 11:32:26.640 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No change in target property for dependency $000: currently registered: false
2025-01-25 11:32:26.640 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No existing service listener to unregister for dependency $000
2025-01-25 11:32:26.641 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Setting target property for dependency $000 to null
2025-01-25 11:32:26.642 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : New service tracker for $000, initial active: false, previous references: {}, classFilter: (objectClass=org.openhab.core.automation.type.ModuleTypeRegistry), initialReferenceFilter (objectClass=org.openhab.core.automation.type.ModuleTypeRegistry)
2025-01-25 11:32:26.642 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : dm $000 tracker reset (closed)
2025-01-25 11:32:26.643 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : dm $000 tracker opened
2025-01-25 11:32:26.643 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : registering service listener for dependency $000
2025-01-25 11:32:26.644 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No change in target property for dependency $001: currently registered: false
2025-01-25 11:32:26.644 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No existing service listener to unregister for dependency $001
2025-01-25 11:32:26.645 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Setting target property for dependency $001 to null
2025-01-25 11:32:26.645 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : New service tracker for $001, initial active: false, previous references: {}, classFilter: (objectClass=org.openhab.core.automation.RuleRegistry), initialReferenceFilter (objectClass=org.openhab.core.automation.RuleRegistry)
2025-01-25 11:32:26.645 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : dm $001 tracker reset (closed)
2025-01-25 11:32:26.646 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : dm $001 tracker opened
2025-01-25 11:32:26.646 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : registering service listener for dependency $001
2025-01-25 11:32:26.647 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No change in target property for dependency $002: currently registered: false
2025-01-25 11:32:26.647 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No existing service listener to unregister for dependency $002
2025-01-25 11:32:26.647 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Setting target property for dependency $002 to null
2025-01-25 11:32:26.648 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : New service tracker for $002, initial active: false, previous references: {}, classFilter: (objectClass=org.openhab.core.storage.StorageService), initialReferenceFilter (objectClass=org.openhab.core.storage.StorageService)
2025-01-25 11:32:26.648 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : dm $002 tracker reset (closed)
2025-01-25 11:32:26.649 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : dm $002 tracker opened
2025-01-25 11:32:26.649 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : registering service listener for dependency $002
2025-01-25 11:32:26.649 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No change in target property for dependency $003: currently registered: false
2025-01-25 11:32:26.649 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : No existing service listener to unregister for dependency $003
2025-01-25 11:32:26.650 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : Setting target property for dependency $003 to null
2025-01-25 11:32:26.650 [DEBUG] [e.automation.internal.RuleEngineImpl] - bundle org.openhab.core.automation:4.3.2 (163)[org.openhab.core.automation.internal.RuleEngineImpl(70)] : New service tracker for $003, initial active: false, previous references: {}, classFilter: (objectClass=org.openhab.core.service.ReadyService), initialReferenceFilter (objectClass=org.openhab.core.service.ReadyService)

```

My behavior is like that. Once I manualy restart bundle org.openhab.core.automation, the RuelEngine srarts and everything is working.

If you want to send whole opehnab.log, just let me know and I will share it.

Jan

---

<div class="post-metadata">

**Author:** ![mstormi](https://community.openhab.org/user_avatar/community.openhab.org/mstormi/32/55857_2.png) [@mstormi](https://community.openhab.org/u/mstormi)\
**Post date:** [January 25, 2025, 11:24am UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/38 "2025-01-25T11:24:09Z")

</div>

Thanks. Could you please file that observation as a GitHub issue with `openhab-core`?

---

<div class="post-metadata">

**Author:** ![jangerhart](https://community.openhab.org/user_avatar/community.openhab.org/jangerhart/32/106683_2.png) [@jangerhart](https://community.openhab.org/u/jangerhart)\
**Post date:** [January 25, 2025, 1:40pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/39 "2025-01-25T13:40:42Z")

</div>

Issue created:

[Rule engine not yet started #4576](https://github.com/openhab/openhab-core/issues/4576)

---

<div class="post-metadata">

**Author:** ![demon](https://community.openhab.org/letter_avatar_proxy/v4/letter/d/7ba0ec/32.png) [@demon](https://community.openhab.org/u/demon)\
**Post date:** [January 26, 2025, 2:59pm UTC](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517/40 "2025-01-26T14:59:39Z")

</div>

Thanks! I think, I have the same behaviour.  
Updated from 4.2.1 to 4.3.2 (on openhabian) and all rules seemed to stop working.

“bundle:restart org.openhab.core.automation” fixed it.

If I can help to further track it down, please tell me.

[Previous page](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517.md?page=1)

[Next page](https://community.openhab.org/t/rule-engine-not-running-although-bundle-active/161517.md?page=3)