Welcome, Guest
Username: Password: Remember me
Forgot your password? Forgot your username? Create an account
  • Page:
  • 1

TOPIC: Proviewr v5.8 Runtime Operator Station

Proviewr v5.8 Runtime Operator Station 2 years 10 months ago #11078

  • Pomplun
  • Pomplun's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 17
  • Karma: 0
Hello Everybody,

3 weeks ago I had converted an RPI project from 5.7 to v5.8. With a patch from Claes I was able to compile the project.
Now I've finally found the time to set up the new RPi 4 B for this project.
It was noticed that the command "systemctl enable pwr" and then "systemctl start pwr" are acknowledged with an error.
pwrp@rpihzg58:~ $ sudo systemctl status pwr
? pwr.service - ProviewR Runtime Environment
Loaded: loaded (/etc/systemd/system/pwr.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2021-06-10 20:36:00 CEST; 13s ago
Docs: man:pwr(1)
Process: 1668 ExecStart=/etc/init.d/pwr start (code=exited, status=2)

Jun 10 20:36:00 rpihzg58 systemd[1]: Starting ProviewR Runtime Environment...
Jun 10 20:36:00 rpihzg58 ProviewR[1668]: /etc/init.d/pwr: 37: /etc/init.d/pwr: Syntax error: word unexpected (expecting ";;")
Jun 10 20:36:00 rpihzg58 systemd[1]: pwr.service: Control process exited, code=exited, status=2/INVALIDARGUMENT
Jun 10 20:36:00 rpihzg58 systemd[1]: pwr.service: Failed with result 'exit-code'.
Jun 10 20:36:00 rpihzg58 systemd[1]: Failed to start ProviewR Runtime Environment.

Has anything changed in the instructions for starting Runtime?
Why does the pwr service not start on the runtime station?

I had exactly the same problem today with an Ubuntu 20.04 with pwrrt v5.8.
The packed file pwrp_pkg_project_00xx.tgz is still transferred to the runtime station with distribute.
Then I get the message /pwr_pkg.sh No such file or ??? in the terminal.
I think it has to do with the service pwr on the runtime station. But I can't find a point where I have to change something or what I've done wrong.

If I unpack the project with pwr_pkg.sh -i project_name_0001.tgz on the runtime station and start it with rt_ini -i and rt_xtt -q Nodes-project_name-OpPlaces-Op, it even seems to run

Thanks for help

/Wolfgang
The administrator has disabled public write access.

Proviewr v5.8 Runtime Operator Station 2 years 8 months ago #11112

  • Avispao
  • Avispao's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
Hi,

I'm suffering the same problem in one of my projects, on the other hand, the only one which involves a raspberry pi.

I can't start the pwr service at startup under raspios, with 5.10.17 kernel.


A start job for unit pwr.service has begun execution.
-- 
-- The job identifier is 981.
jul 30 17:33:23 mephisto systemd[1425]: pwr.service: Failed to execute command: Exec format error
jul 30 17:33:23 mephisto systemd[1425]: pwr.service: Failed at step EXEC spawning /etc/init.d/pwr: Exec format error
-- Subject: Process /etc/init.d/pwr could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The process /etc/init.d/pwr could not be executed and failed.
-- 
-- The error number returned by this process is ERRNO.
jul 30 17:33:23 mephisto systemd[1]: pwr.service: Control process exited, code=exited, status=203/EXEC
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- An ExecStart= process belonging to unit pwr.service has exited.
-- 
-- The process' exit code is 'exited' and its exit status is 203.
jul 30 17:33:23 mephisto systemd[1]: pwr.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit pwr.service has entered the 'failed' state with result 'exit-code'.
jul 30 17:33:23 mephisto systemd[1]: Failed to start ProviewR Runtime Environment.
-- Subject: A start job for unit pwr.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit pwr.service has finished with a failure.
-- 
-- The job identifier is 981 and the job result is failed.


If I start de runtime using the monitor (pwr_rtmon), everything works, but it implies the user has to do it.

Claes, do you have any clue on what's happening?

Thanks in advance.
The administrator has disabled public write access.

Proviewr v5.8 Runtime Operator Station 2 years 8 months ago #11125

  • Avispao
  • Avispao's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
Fresh news...

I've been tinkering on the problem with the raspberry and systemd, and I've managed to make it work.

I changed the service script, replacing the original file descriptor (coded by Claes?) "10" used at flock invocation with a single digit; "9".
I modified the locking mechanism of "flock" changing the "(", and ")" with "{" and "}" and adding "-x" because I don't want to fork to another subshell, because of environment variables. Link

I also changed the service itself, adding "mysql.service" in the requirements of the unit ("Wants=" and "After=" ) because I'm running sevserver.


I created another service to autostart my project on system startup (Again requiring pwr.service and after graphical.target)

...And it works!!!
The administrator has disabled public write access.

Proviewr v5.8 Runtime Operator Station 2 years 8 months ago #11126

  • Pomplun
  • Pomplun's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 17
  • Karma: 0
Hello Avispa,

congratulations for the success.
I would like to share my happiness with you, but unfortunately I cannot quite follow your description.

I in the file
/etc/init.d/pwr

I found a line with
flock -w 180 10
.
There you changed the 10 to 9 OK?

Is it possible that you describe the files and the changes in more detail?
So I can't understand your changes.

I would also like to get ahead at this point.
Many thanks in advance.

Greeting
wolfgang
The administrator has disabled public write access.

Proviewr v5.8 Runtime Operator Station 2 years 8 months ago #11127

  • Pomplun
  • Pomplun's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 17
  • Karma: 0
Hello Avispoa,

here are my messages from "sudo journalctl -xe" after running "sudo systemctl start pwr.service"
-- A start job for unit pwr.service has begun execution.
-- 
-- The job identifier is 1034.
Aug 07 13:43:57 rpihzg58 ProviewR[1074]: Starting ProviewR Runtime: rt_ini
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    Proview/R Version V5.8.0 for Linux on ARM
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    Copyright (C) 2005-2021 SSAB EMEA AB
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    Proview/R is free software; you can redistribute it and/or
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    modify it under the terms of the GNU General Public License.
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    This program is distributed in the hope that it will be useful
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    but WITHOUT ANY WARRANTY; without even the implied warranty of
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    GNU General Public License for more details.
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    ProviewR Runtime Environment
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    Proview/R Version V5.8.0 for Linux on ARM
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    Copyright (C) 2005-2021 SSAB EMEA AB
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    Proview/R is free software; you can redistribute it and/or
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    modify it under the terms of the GNU General Public License.
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    This program is distributed in the hope that it will be useful
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    but WITHOUT ANY WARRANTY; without even the implied warranty of
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    GNU General Public License for more details.
Aug 07 13:43:57 rpihzg58 ProviewR[1074]:    ProviewR Runtime Environment
Aug 07 13:44:02 rpihzg58 ProviewR[1074]: .
Aug 07 13:44:02 rpihzg58 systemd[1]: pwr.service: Can't open PID file /run/pwr/pwr.pid (yet?) after start: No such file or directory
Aug 07 13:44:02 rpihzg58 systemd[1]: pwr.service: Failed with result 'protocol'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit pwr.service has entered the 'failed' state with result 'protocol'.
Aug 07 13:44:02 rpihzg58 systemd[1]: Failed to start ProviewR Runtime Environment.
-- Subject: A start job for unit pwr.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit pwr.service has finished with a failure.
-- 
-- The job identifier is 1034 and the job result is failed.
Aug 07 13:44:03 rpihzg58 sudo[1071]: pam_unix(sudo:session): session closed for user root
Aug 07 13:44:25 rpihzg58 sudo[1111]:     pwrp : TTY=pts/0 ; PWD=/home/pwrp ; USER=root ; COMMAND=/usr/bin/journalctl -xe
Aug 07 13:44:25 rpihzg58 sudo[1111]: pam_unix(sudo:session): session opened for user root by (uid=0)

my modification in "etc/init.d/pwr" looks like:
               {
                        flock -x -w 180 9
                        start-stop-daemon --start --oknodo --pidfile $PIDFILE --startas $DAEMON -- -D
                        sleep 5
                } 9>$LOCKFILE

Now i will restart from zero with my raspberry pi 4.

I have no idea :S

greetings
Wolfgang
The administrator has disabled public write access.

Proviewr v5.8 Runtime Operator Station 2 years 8 months ago #11128

  • Pomplun
  • Pomplun's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 17
  • Karma: 0
Hello everyone,

now it works for me too.
The change in
/etc/init.d/pwr
brought the success. (@Avispoa)

For whatever reason.
The first installation of the project is very confusing.
The service pwr actually has to be running so that the project can be properly unpacked, but the service pwr probably expects an installed project so that it can be started.
Then the dog bites its tail.

It was very important that the line
source /etc/pwrp_profile
was entered in
/home/pwrp/.bashrc
Otherwise no paths are right and nothing works.
This was worked out much better up to V5.7. It seems that big changes have been made to ProviewR that still take a little bit of suffering.
Still a great system. :kiss:

Thanks Avispoa
Thanks to the Proview team
The administrator has disabled public write access.
  • Page:
  • 1
Time to create page: 8.172 seconds