Advice reqeusted to migrate MSR from Bare Metal to Container

[rafale77]

@LibraSun

I would encourage you to open a new thread? I will fork it if you don't mind.

[LibraSun]

Concur, and let's get @toggledbits ' earlier Docker-related notes copied into this thread as well. Dunno if they were higher up in the "MSR Available" thread?

[LibraSun]

Hopefully not about to ask the world's dumbest question, but here goes...

I'm stumped at Step 1 of the "Getting Started" docs (https://reactor.toggledbits.com/docs/Getting-Started/), since I'm unable to locate the referenced reactor.yaml file.

The only files I see under my <reactor-data>/config folder are:
all-json.out (2 bytes)
all-yaml.out (3 bytes)

IMPORTANT NOTE: I'm running MSR under Docker on my Synology NAS, but I believe it behaves identically in all respects to bare metal (Linux) installs. I'm wondering if it's possible that the desired YAML file exists within the distributed image, but is not being exposed yet by the container running MSR.

Will not proceed until advised by someone more knowledgeable. Until then, I have no "Hub/HA" defined, so cannot do anything, really, with MSR. (Makes me kinda wish these settings lived within MSR's panels and not a YAML file, LOL!)

Thanks - Libra

[toggledbits]

The docker container is slightly different in that the data folder does not live within the container, it lives on a volume that the container mounts separately. This is so that the container can read and write data as needed and it is not destroyed when the image or container is replaced (e.g. you would otherwise lose your config and all your rules and reactions), and so you can edit your config without having to breach the walls of the container.

The install steps for the docker container has a step for you to create a directory that would become this volume. To confirm you are looking in the right place, open Docker via the package manager. Go to Container, then click the Reactor container. Hit the Details button, and then the Volume tab. The line that shows the mount path "/var/reactor" is the place where your config and data are stored (not /var/reactor, the path to the left of that under File/Folder. So check that to make sure you are looking in the right place. You should see config, logs and storage at a minimum, and possibly also local and sys.

[LibraSun]

@toggledbits said in Multi-System Reactor Developer Preview AVAILABLE:

You should see config, logs and storage at a minimum, and possibly also local and sys

In that folder (which in my case happens to be Reactor/Data, I only see the following subfolders:
config
storage

[LibraSun]

(Dang it, I should have posted this latest question under the "Synology Docker" thread... @rafale77 can you please bump us over??)

[toggledbits]

OK, then somehow the initial data didn't get copied. If you haven't already, open a PR for that on Mantis, and I'll post the two files so you can put them into the folder yourself, and I'll hunt down why it didn't copy them in the first place.

[rafale77]

@LibraSun
sitôt dit, sitôt fait. (sorry I don't know the equivalent in english)

[Elcid]

"no sooner said than done" I believe.

[LibraSun]

I like, "Your wish is my command."

[toggledbits]

FYI, I can move them also.

[LibraSun]

Beneath your pay grade sir.

[toggledbits]

No job too big or too small. If it needs to get done, I'm happy to do it.

[LibraSun]

Strictly FYI, I've gone ahead and installed NODE.JS v12 on my Synology NAS in anticipation of attempting the Reactor backup conversion to MSR Rulesets. In my Linux-challenged mind, that's a step in the right direction. Next, I'll need to (re-)learn how to SSH into the NAS for executing Terminal commands. Will let you know if this gets me further along that trajectory.

EDIT: Nope, I was clearly jumping the gun. Will have to take another tack.

[toggledbits]

I've also rolled 21062 (today's daily build) into a docker container for Synology. Link is in PR #58 on the bug tracker.

[LibraSun]

Installed. Works like a charm. Your instructions were spot on, as per usual.

[toggledbits]

We can both thank @kfxo for those instructions!

[noelab]

Hi! this is for asking an help to correct time zone.
MSR is now installed (1.0.0-21200-16a604f) on my Synology NAS (DS 720+ with DSM 7) and Docker running on it. With my previous DS119j impossible to do anything with it.

All entities from Vera Lite are imported ok .

Trying to import also entities from Ezlo Plus without success.

So looking in the "reactor.log" I notice TZ offset with something like this:

2021-08-03T20:46:16.212Z wsapi:NOTICE wsapi: starting version 21196
2021-08-03T20:46:16.286Z Engine:INFO Engine#1 master timer tick, local time "8/3/2021, 10:46:16 PM" (TZ offset 120 mins from UTC)
2021-08-03T20:46:16.560Z wsapi:INFO wsapi: connection from ::ffff:172.17.0.1

In reactor container, going on LOG tab, I have something like this:

time = 23.00.05
and log
2021-08-03T23:00:05.001Z Engine:INFO Engine#1 master timer tick, local time "8/4/2021, 1:00:05 AM" (TZ offset 120 mins from UTC)

TZ variable for reactor container is: Europe/Rome
On nas control Panel, server NTP is on time.google.com
in Docker LOG tab, time is correct
Browser time and host Time in MSR GUI are correct

does anyone have any advice?

[toggledbits]

Seems like everything is correct. The log timestamps are always UTC. The master timer tick log entry looks correct for about the time of your posting and the time zone you show set below.

[noelab]

I was not able to import entities from Ezlo Plus and I was thinking about a problem between time zone and access token.
Now I have also ezlo entities imported ok but only after putting both “offlineAnonymousAccess” and “offlineInsecureAccess” set to true with API call.

In all this ways nothing:
config:

username: "somebody"  # put your username here betw quotes
   password: "????????"  # and password

then config

set_anonymous_access: true   <--- add this line, same indent as previous

then with

“offlineInsecureAccess” enabled:true

the log was:

2021-08-04T00:08:25.648Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000/" }
2021-08-04T00:08:25.648Z <EzloController:null> EzloController#ezlo instance log level (null) (4)
2021-08-04T00:08:25.667Z <Controller:INFO> EzloController#ezlo device data loaded; checking structure
2021-08-04T00:08:25.669Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication; hub.offline.insecure_access must be enabled!
2021-08-04T00:08:25.696Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
2021-08-04T00:08:25.743Z <Controller:INFO> EzloController#ezlo opening local hub connection to (undefined) at wss://10.0.4.119:17000/
2021-08-04T00:08:25.743Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ((undefined)) certificate
2021-08-04T00:08:25.744Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000/
2021-08-04T00:08:25.750Z <app:INFO> Structure running; pausing for controllers' initial ready
2021-08-04T00:08:25.856Z <Controller:INFO> EzloController#ezlo hub websocket connected; inventory hub...
2021-08-04T00:08:25.905Z <Controller:ERR> EzloController#ezlo stopping; hub's offline insecure access is disabled, and cloud auth info is not configured
2021-08-04T00:08:25.906Z <Controller:ERR> EzloController#ezlo failed to complete inventory: Error: hub offline anonymous access is disabled, and cloud auth info is not configured
2021-08-04T00:08:25.907Z <Controller:CRIT> Error: hub offline anonymous access is disabled, and cloud auth info is not configured
Error: hub offline anonymous access is disabled, and cloud auth info is not configured
    at /opt/reactor/server/lib/EzloController.js:895:27
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
2021-08-04T00:08:25.915Z <Controller:NOTICE> EzloController#ezlo websocket closing, 1002

After putting both “offlineAnonymousAccess” and “offlineInsecureAccess” set to true with API call, all entities are imported OK. The problem was hub.offline.insecure_access . This is now the log:

2021-08-04T01:01:18.564Z <EzloController:null> EzloController#ezlo created, config { "source": "wss://10.0.4.119:17000/" }
2021-08-04T01:01:18.564Z <EzloController:null> EzloController#ezlo instance log level (null) (4)
2021-08-04T01:01:18.593Z <Controller:INFO> EzloController#ezlo device data loaded; checking structure
2021-08-04T01:01:18.596Z <Controller:INFO> EzloController#ezlo performing hub login without cloud authentication; hub.offline.insecure_access must be enabled!
2021-08-04T01:01:18.626Z <Controller:NOTICE> Controller SystemController#reactor_system is now online.
2021-08-04T01:01:18.675Z <Controller:INFO> EzloController#ezlo opening local hub connection to (undefined) at wss://10.0.4.119:17000/
2021-08-04T01:01:18.675Z <Controller:NOTICE> EzloController#ezlo configured to ignore host ((undefined)) certificate
2021-08-04T01:01:18.677Z <Controller:NOTICE> EzloController#ezlo connecting via WS to wss://10.0.4.119:17000/
2021-08-04T01:01:18.682Z <app:INFO> Structure running; pausing for controllers' initial ready
2021-08-04T01:01:18.790Z <Controller:INFO> EzloController#ezlo hub websocket connected; inventory hub...
2021-08-04T01:01:18.896Z <Controller:INFO> EzloController#ezlo data load complete; 2 devices received, 7 entities registered; 12 items.
2021-08-04T01:01:18.897Z <Controller:INFO> EzloController#ezlo hub inventory complete/successful; 105ms
2021-08-04T01:01:18.897Z <Controller:NOTICE> Controller EzloController#ezlo is now online.
2021-08-04T01:01:19.152Z <VeraController:WARN> VeraController#vera ignoring geotag ({ "iduser": 1520131, "geotags": [ { "PK_User": 0, "id": 1, "accuracy": 0, "ishome": 1, "notify": 1, "radius": 100, "address": "Via , fi", "color": "006e45", "latitude": "437930", "longitude": "11210", "name": "testi, fi", "status": --null-- } ] }) for user 1520131, user not in user list
2021-08-04T01:01:20.388Z <OWMWeatherController:NOTICE> Controller OWMWeatherController#weather is now online.
2021-08-04T01:01:22.993Z <VeraController:NOTICE> Controller VeraController#vera is now online.