cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

ctrlX Core scheduler error

alink
Long-established Member

ctrlX Core scheduler error

On startup, this error occurs in the log.

081F0042 Error in Scheduler system

0C7B4263 Timeout when restoring the configuration

I have no idea what configuration...

What does it mean, there is no further error description and how to avoid this.

It's possible to acknowledge and (I think) it doesn't block anything.

 

9 REPLIES 9
CodeShepherd
Community Moderator

Re: ctrlX Core scheduler error

On each boot the system loads it settings out of the App Data (or active configuration). And something seems to go wrong on your side.

Did you do an update of your ctrlX CORE?
Which system and app version are you using?
Is the error present in the pending diagnostics? If not it cannot be acknowledged.

alink
Long-established Member

Re: ctrlX Core scheduler error

Yes, I updated the ctrlX from 1.14 to 1.16 last week.

Currently these Apps and versions are running:

ctrlX.JPG

 Each time systems starts there is that error message in diagnostic.

error.JPG

 But it can be reseted

CodeShepherd
Community Moderator

Re: ctrlX Core scheduler error

As there where some changes in the scheduler settings from 1.14 to 1.16 this could be a problem of converting your "old" configuration to actual. Please go to the App Data and save your configuration to an archive. Reboot afterwards and see if error is still present.

save app datasave app data

You could also send us your "old" configuration so we can have a look to it.

alink
Long-established Member

Re: ctrlX Core scheduler error

Saving a new archive doesn't help, error message is still alive.

ctrlX.JPG

Attached, there are two archive files. 26082022 before updating to 1.16 (from 1.12)

and

05092022, the current one with 1.16

sebastue
Member

Re: ctrlX Core scheduler error

In the version 1.14 we used placeholder callables in the default configuration of the scheduler. In the version 1.16 per default no placeholder callables are created. You only get placeholder callables if a configured app is not installed, e.g. if the motion app is uninstalled.

The mentioned error is set if a placeholder callable is in the configuration after booting. The scheduler waits until the all required callables are available and then gets an timeout. 

To avoid the error you have to delete the placholder callables in the scheduler.

sebastue_0-1662470316662.png

 

alink
Long-established Member

Re: ctrlX Core scheduler error

Tried to delete placeholder.

The only one within in the ctrlXAutomation is '_placeholder_osciruntime'

ctrlX2.JPG

 After deleting, motion app could not go into run.

ctrlX.JPG

After restoring old configuration, motion is running.

See diagnostic as well.

But after reboot error in schedule comes again....

ctrlX3.JPG

Till now, this error doesn't block anything or I haven't noticed yet. But after booting having an error anywhere is not good.

sebastue
Member

Re: ctrlX Core scheduler error

I can reproduce this behaviour. Unfortunately we have a bug here that the error still occurs and the system doesn't boot correctly after deleting the placeholder callables.

As a workaround the the concerning callable can be removed in the configuration.

Therefor you have save and download the configuration.

sebastue_0-1662615869162.png

After that you have to open the zip archive and remove the callable from the callable pool. In your example "oscilloscope".

sebastue_1-1662616039030.png

Save the file in the archive and upload the configuration.

sebastue_2-1662616138831.png

Sorry for the inconvenience. This bug will be resolved in the next release.

alink
Long-established Member

Re: ctrlX Core scheduler error

Thanks @sebastue 

After deleting the placeholder in ctrlX Automation scheduler and the 'osciruntime' entry in scheduler/programs.json there is no error anymore.

alink
Long-established Member

Re: ctrlX Core scheduler error

One additional note:

Not only modifying "callablePool", "programs":[{ "callables"[{...()]}]} has to be modifyed as well.

Deleting the correspondent, complete entry of:

"EXAMPLE"

{
"alias": "",
"arguments": [
"distribution"
],
"id": "1",
"index": 3000,
"name": "axisprofile",
"sync": {
"after": [],
"before": []
},
"watchdog": "WDG_DEFAULT"
},

 

Then, the "sequence" has to be modifyed with the right "id"

 

Otherwise, there will be a new error, like "motion app not in run"

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist