Forum Home › Forums › Rapid SCADA on Linux Controllers and Raspberry Pi › version 5.8.1 not working on ubuntu 20.04
- This topic has 17 replies, 6 voices, and was last updated 4 years ago by Mikhail.
-
AuthorPosts
-
June 24, 2020 at 9:37 am #6926JWParticipant
after installation, error message on login page “Server is unavailable”.
no log file generated in /opt/scada/ScadaServer
the log in /opt/scada/ScadaWeb/log is attached belowI change back to 5.8.0, then everything works fine.
2020-06-24 17:29:31 <jw-ubuntu><www-data><ACT> Connect to SCADA-Server “localhost”
2020-06-24 17:29:31 <jw-ubuntu><www-data><EXC> Error connecting to SCADA-Server: Connection refused
2020-06-24 17:29:31 <jw-ubuntu><www-data><ACT> Disconnect from SCADA-Server
2020-06-24 17:29:31 <jw-ubuntu><www-data><EXC> Error refreshing the tables of the configuration database:
Scada.ScadaException: Unable to receive the configuration database modification time.
at Scada.Client.DataCache.RefreshBaseTables () [0x0007b] in <e84da16018f347e9b54944588267a3fa>:0
2020-06-24 17:29:31 <jw-ubuntu><www-data><ERR> Unable to connect to SCADA-Server. Try again.
2020-06-24 17:29:31 <jw-ubuntu><www-data><ERR> Unsuccessful login attempt: guest – Server is unavailable. IP address: 127.0.0.1June 25, 2020 at 6:36 am #6928manjey73ParticipantYou probably did something wrong, I have 5.8.1 running and running on Raspberry Pi 3
June 25, 2020 at 6:42 am #6929manjey73Participantsudo service scadaserver status
sudo service scadacomm status???
June 25, 2020 at 12:48 pm #6931MikhailModeratorThe issue is not related to the version.
You should check the log of the Server service to find the cause.June 25, 2020 at 2:18 pm #6932AnonymousInactiveThe message deleted. Respect forum participants.
- This reply was modified 4 years, 2 months ago by Mikhail.
June 26, 2020 at 2:14 am #6941JWParticipantin admin app, the status show Undefined instead of error.
there is no log files in /opt/scada/ScadaServer/Log, /opt/scada/ScadaServer/Log——————————————————————-
service status:jw@jw-ubuntu:~/Desktop$ sudo service scadaserver status
scadaserver.service – LSB: SCADA-Server daemon
Loaded: loaded (/etc/init.d/scadaserver; generated)
Active: failed (Result: exit-code) since Fri 2020-06-26 09:41:07 HKT; 2min 36s ago
Docs: man:systemd-sysv-generator(8)
Process: 883 ExecStart=/etc/init.d/scadaserver start (code=exited, status=203/EXEC)Jun 26 09:41:07 jw-ubuntu systemd[1]: Starting LSB: SCADA-Server daemon…
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadaserver.service: Control process exited, code=exited, status=203/EXEC
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadaserver.service: Failed with result ‘exit-code’.
Jun 26 09:41:07 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Server daemon.
jw@jw-ubuntu:~/Desktop$ sudo service scadacomm status
● scadacomm.service – LSB: SCADA-Communicator daemon
Loaded: loaded (/etc/init.d/scadacomm; generated)
Active: failed (Result: exit-code) since Fri 2020-06-26 09:41:07 HKT; 2min 39s ago
Docs: man:systemd-sysv-generator(8)
Process: 896 ExecStart=/etc/init.d/scadacomm start (code=exited, status=203/EXEC)Jun 26 09:41:07 jw-ubuntu systemd[1]: Starting LSB: SCADA-Communicator daemon…
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadacomm.service: Control process exited, code=exited, status=203/EXEC
Jun 26 09:41:07 jw-ubuntu systemd[1]: scadacomm.service: Failed with result ‘exit-code’.
Jun 26 09:41:07 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Communicator daemon.————————————————–
journalctl log: but the scadaserver and scadacomm file are in /etc/init.d alreadyJun 26 10:04:40 jw-ubuntu systemd[1]: Starting LSB: SCADA-Server daemon…
— Subject: A start job for unit scadaserver.service has begun execution
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— A start job for unit scadaserver.service has begun execution.
—
— The job identifier is 1786.
Jun 26 10:04:40 jw-ubuntu systemd[3498]: scadaserver.service: Failed to execute command: No such file or directory
Jun 26 10:04:40 jw-ubuntu systemd[3498]: scadaserver.service: Failed at step EXEC spawning /etc/init.d/scadaserver: No such file or directory
— Subject: Process /etc/init.d/scadaserver could not be executed
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— The process /etc/init.d/scadaserver could not be executed and failed.
—
— The error number returned by this process is ERRNO.
Jun 26 10:04:40 jw-ubuntu systemd[1]: scadaserver.service: Control process exited, code=exited, status=203/EXEC
— Subject: Unit process exited
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— An ExecStart= process belonging to unit scadaserver.service has exited.
—
— The process’ exit code is ‘exited’ and its exit status is 203.
Jun 26 10:04:40 jw-ubuntu systemd[1]: scadaserver.service: Failed with result ‘exit-code’.
— Subject: Unit failed
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— The unit scadaserver.service has entered the ‘failed’ state with result ‘exit-code’.
Jun 26 10:04:40 jw-ubuntu systemd[1]: Failed to start LSB: SCADA-Server daemon.
— Subject: A start job for unit scadaserver.service has failed
— Defined-By: systemd
— Support: http://www.ubuntu.com/support
—
— A start job for unit scadaserver.service has finished with a failure.
—
— The job identifier is 1786 and the job result is failed.June 26, 2020 at 5:09 am #6942JWParticipantAre ScadaData.Svc.dll in ScadaServer and ScadaComm folder needed for version 5.8.1?
I copied those 2 files from 5.8.0 to 5.8.1. It seems working now.
June 26, 2020 at 5:51 am #6943manjey73ParticipantHave you completely copied all the files, including the daemon files ? Do you remember to distribute the rights to the corresponding files and folders as during installation ? I just copied only the required files, but I didn’t even touch the demons, and my system started up. In your case, you either do not have the services themselves (it may be related to rights), or some files are unavailable when you start the services.
June 26, 2020 at 5:53 am #6944manjey73ParticipantJune 26, 2020 at 5:57 am #6947manjey73ParticipantJune 26, 2020 at 6:54 am #6950JWParticipantHi manjey73, thanks for your help.
it turns out it wasn’t the ScadaData.Svc.dll make it work. it was the daemons of 5.8.0 make it work.
I tried the following tests:
1. fresh install of 5.8.1, does not work;
2. fresh install of 5.8.0, work;
3. update /opt/scada to5.8.1 + keep daemons from 5.8.0, work.the file size and edit time are slightly different between 2 set of daemon files, but i can’t find the difference between the content.
5.8.0———-
-rw-rw-r– 1 jw jw 1666 2019-04-19 12:18:02.000000000 +0800 scadaagent
-rw-rw-r– 1 jw jw 1675 2018-11-22 10:02:24.000000000 +0800 scadacomm
-rw-rw-r– 1 jw jw 1735 2018-11-22 10:02:24.000000000 +0800 scadaserver
5.8.1———-
-rw-rw-r– 1 jw jw 1666 2019-04-19 12:18:00.000000000 +0800 scadaagent
-rw-rw-r– 1 jw jw 1748 2018-11-22 09:35:06.000000000 +0800 scadacomm
-rw-rw-r– 1 jw jw 1810 2018-11-22 09:35:06.000000000 +0800 scadaserverJune 26, 2020 at 7:04 am #6951JWParticipanthere maybe the root cause.
the line different from 2 version in daemon files scada
5.8.1
EXE_DIR=/etc/scada/ScadaServer/
5.8.0
EXE_DIR=/opt/scada/ScadaServer/June 26, 2020 at 9:11 am #6952manjey73ParticipantYes, I did not transfer daemons, because I have Scada installed in the user’s home directory and I fixed the paths to exe files in them, as well as added a string of rights changes to some files after restarting the server.
June 26, 2020 at 2:25 pm #6954MikhailModeratorThere was an error in scadacomm and scadaserver scripts. Now it is fixed. Thanks.
September 8, 2020 at 9:29 am #7243IsnanParticipantHi,
I’m a newbie in RS and ubuntu. and I have installed RS on ubuntu 16.4.
That I want to ask, how to use scada administrator as in the video tutorial in windows OS ?
I tried to use software “Wine” to open Scada Administrator, but when creating a project, I was stuck when adding a device with the words “Error getting device interface type from the library KpSimulator.dll: Absolute path information is required.
Parameter name: assemblyFile ”
(Google Translate)Thanks a lot,
Regards,Isnan
-
AuthorPosts
- You must be logged in to reply to this topic.