Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Simulation scan can't be started #234

Open
RandyAndy1 opened this issue Apr 15, 2024 · 3 comments
Open

Simulation scan can't be started #234

RandyAndy1 opened this issue Apr 15, 2024 · 3 comments
Labels

Comments

@RandyAndy1
Copy link

The Simulation recording can't be started. When the recoding button is pressed no response.
To start the recording the adapter must be deactivated, the recording must be started and then the adapter must be activated.

Versions:
Adapter version: 2.3.4
Plattform: linux
RAM: 7.7 GB
Node.js: v18.18.2(18.20.2)
NPM: 9.8.1(10.5.0)

Additional context
Add any other context about the problem here.

@GermanBluefox
Copy link
Contributor

Do you see any errors in log? Because i cannot reproduce it

@RandyAndy1
Copy link
Author

RandyAndy1 commented Jun 9, 2024

In the debug mode I could not see any log. When I go to silly I get the following messages in the log:

fullcalendar.0 | 2024-06-09 17:12:57.688 | debug | Next check in 3600 seconds -- | -- | -- | -- fullcalendar.0 | 2024-06-09 17:12:57.429 | info | starting. Version 2.3.17 in /opt/iobroker/node_modules/iobroker.fullcalendar, node: v18.18.2, js-controller: 5.0.19 fullcalendar.0 | 2024-06-09 17:12:57.247 | info | Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system fullcalendar.0 | 2024-06-09 17:12:57.240 | debug | Plugin sentry Initialize Plugin (enabled=true) fullcalendar.0 | 2024-06-09 17:12:57.174 | debug | States connected to redis: 127.0.0.1:9000 fullcalendar.0 | 2024-06-09 17:12:57.113 | debug | States create User PubSub Client fullcalendar.0 | 2024-06-09 17:12:57.111 | debug | States create System PubSub Client fullcalendar.0 | 2024-06-09 17:12:57.080 | debug | Redis States: Use Redis connection: 127.0.0.1:9000 fullcalendar.0 | 2024-06-09 17:12:57.004 | debug | Objects connected to redis: 127.0.0.1:9001 fullcalendar.0 | 2024-06-09 17:12:56.996 | debug | Objects client initialize lua scripts fullcalendar.0 | 2024-06-09 17:12:56.891 | debug | Objects create User PubSub Client fullcalendar.0 | 2024-06-09 17:12:56.890 | debug | Objects create System PubSub Client fullcalendar.0 | 2024-06-09 17:12:56.887 | debug | Objects client ready ... initialize now fullcalendar.0 | 2024-06-09 17:12:56.820 | debug | Redis Objects: Use Redis connection: 127.0.0.1:9001 fullcalendar.0 | 2024-06-09 17:12:52.223 | info | terminating fullcalendar.0 | 2024-06-09 17:12:51.721 | info | Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason fullcalendar.0 | 2024-06-09 17:12:51.720 | debug | Plugin sentry destroyed fullcalendar.0 | 2024-06-09 17:12:51.717 | info | terminating fullcalendar.0 | 2024-06-09 17:12:51.712 | info | Got terminate signal TERMINATE_YOURSELF

But I assume the are triggered through the restart.
I am wondering why I get a message regarding redis, I am pretty sure I turned it of already some month ago, but seems so it is still turned on ?
I try to turn if off later today to check if this could be the origin.
Just klicking the dot "Start die Aufnahme" does not trigger any log information

@RandyAndy1
Copy link
Author

I checked now my system and redis is definetely not running.
Typing "iobroker setup custom" confirms that I am using json and not redis.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants