Can´t restart or upgrade/deploy MSR

[tamorgen]

Good morning all,
First, I just wanted to say hi and introduce myself. I've been using a Vera Plus for about 8 years now, and the luup based Reactor for two or three. Before that I used PLEG for my home logic on Vera.

I've been monitoring the evolution of Ezlo, and I'm starting to consider making the jump to it. After discussing with others over on the Vera/Ezlo community, it seems that it's not an all or nothing switch, particularly with the Patrick's MSR, so I'm joining here today to start taking a look at it.

Anyway, that's my basic post. Look forward to playing with MSR in the near future.

[toggledbits]

Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

[tamorgen]

@toggledbits said in First post:

Welcome. You'll find some differences between R4V (Reactor for Vera) and MSR, but also a lot of familiarity. Make sure to read the Concepts and Terminology section of the documentation for some background. The other parts of the docs will help you through the details.

Also, if you have problems or questions, be sure you've read the posting guidelines beforehand. The goal is to give as much information up front as possible, and do your homework first. The post explains it.

Have you decided on a platform to run MSR? Raspberry Pi? VM? Other small host? Are you familiar/comfortable with docker, or are you more likely to install Reactor directly (aka bare-metal)?

Hi Patrick,
Thanks for the warm welcome!

I've actually just installed Reactor on my home server. I have essentially a file server that I also use for various other tasks, such as Pihole, dhcp managment, PlexMediaSever, running Fedora Server 36. I installed using the bare metal method

From what I've read, MSR will give me an easier upgrade to Ezlo path than anything else. Ezlo is still missing too many things that I'm dependent on Vera to make a complete switch. I have a working Vera, so MSR should allow me to slowly transition at my own pace, until Ezlo can do it all, and eventually retire Vera.

[tamorgen]

@toggledbits
Well, like I said, I got it installed, but it would appear there is an environmental variable that isn't correct.

reactor.service: Failed at step EXEC spawning /usr/local/lib/nodejs/bin/node: No such file or directory

It worked when I ran NODE_PATH=$(pwd) node app.js, but after I installed it as a service, it did not.

Any advice on how I can find the correct path?

Note: I used the following command to install:

sudo dnf install nodejs-1:16:140.-2.fc36

[toggledbits]

The pwd command returns the path of the current directory, which in that command is the directory where app.js lives and you have Reactor installed. Just make sure your Environment line in your service file contains that fully-qualified path.

Here's the sample service file that you can modify. I'm not sure how you generated yours. You can also find this file in the tools directory in your Reactor install.

# THIS IS A SAMPLE SYSTEMD SERVICE CONFIGURATION FILE FOR REACTOR.
# Modify the WorkingDirectory, Environment, and User values below
# to suit your system configuration. Also modify ExecStart with
# the correct path to the "node" executable, if it has not been
# installed in the system binary directories.
# Then place the file in /etc/systemd/system or whatever other 
# directory is normal for your system (remove the -example) from
# the end of the name. You will need root privilegess to do this.
# Then run:
#     sudo systemctl daemon-reload
#     sudo systemctl start reactor
#
[Unit]
Description=Multi System Reactor
After=network.target

[Service]
Type=simple
User=myuser
WorkingDirectory=/home/myuser/reactor
Environment=NODE_PATH=/home/myuser/reactor
ExecStart=/usr/local/lib/nodejs/bin/node app -p
Restart=on-failure
RestartSec=5s

[Install]
WantedBy=multi-user.target

[tamorgen]

@toggledbits

Patrick,
I had already updated the reactor.service file that you are referring to, but it seems to be that the path to nodejs is incorrect. What I'm trying to figure out is where Fedora would have installed that, so I can update the correct path.

[Service]
Type=simple
User=tmorgenthaler
WorkingDirectory=/home/tmorgenthaler/reactor
Environment=NODE_PATH=/tmorgenthaler/myuser/reactor
ExecStart=/usr/local/lib/nodejs/bin/node app -p
Restart=on-failure
RestartSec=5s

[toggledbits]

Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

[tamorgen]

@toggledbits said in First post:

Haven't used Fedora in a good while (although I'm a Berkeley guy), but most *nix has the which command you can use to find the path that a command lives in: which node

That did it. I always forget that command!