Avatar
Please consider registering
guest
sp_LogInOut Log Insp_Registration Register
Register | Lost password?
Advanced Search
Forum Scope


Match



Forum Options



Minimum search word length is 3 characters - maximum search word length is 84 characters
sp_Feed Topic RSSsp_TopicIcon
ApplicationUri CentOS7 - Server does not start up - should not contain localhost
August 13, 2019
21:55, EEST
Avatar
timbo
New Member
Members
Forum Posts: 1
Member Since:
August 13, 2019
sp_UserOfflineSmall Offline

Hey everybody

I’m using prosys Simulation Server as test application for a custom OPC-UA client.
On Mac everythings works like a charm, but on Linux: CentOS7 newest updates the server could not be started up.
The error-message is, that the ApplicationURI should not contain any “localhost” – thus i found no setting where to enter the ApplicationURI by hand, it seems that the program gets it from some environmental variable – the given hostname on system (could be derived by ‘hostname’ command of shell) of the machine significantly differs from “localhost”.

I’m using SimulationServer 3.2.0-214.

Any help would be appreciated.

Thanks in advance

August 15, 2019
15:17, EEST
Avatar
Bjarne Boström
Moderator
Moderators
Forum Posts: 1045
Member Since:
April 3, 2012
sp_UserOfflineSmall Offline

Hi,

The part for the ApplicationURI is defined from hostname of the machine on it is run. This is because in OPC UA each server must have network-unique ApplicationURI and hostname fulfills this purpose.

One reason why this error could happen if for some reason the hostname could not be determined. Another is that currently the check validates that the String “localhost” does not exist in any part of the ApplicationURI, i.e. if you were to happen to have hostname literally e.g. as “localhost2”, it would cause the problem.

Due to one workaround we have in the (java) SDK which is used to make the application is if java call

InetAddress.getLocalHost();

fails, then it just uses “localhost” (so it causes this if it fails, could probably be better…). It does log a WARN level log if this happens. However in it’s current release version the software only displays logs in the “Debug Log” tab, which is not that convinient, but maybe you could check if anything is shown there.

Alternatively it is possible that something is broken in the newest CentOS. Additionally seaching e.g. https://stackoverflow.com/ques…..texception might provide some solutions.

We will try to reproduce the problem here as well.

Forum Timezone: Europe/Helsinki
Most Users Ever Online: 1919
Currently Online:
Guest(s) 40
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Heikki Tahvanainen: 402
hbrackel: 144
rocket science: 90
pramanj: 86
Francesco Zambon: 83
Ibrahim: 78
Sabari: 62
kapsl: 57
gjevremovic: 49
Xavier: 43
Member Stats:
Guest Posters: 0
Members: 732
Moderators: 8
Admins: 1
Forum Stats:
Groups: 3
Forums: 15
Topics: 1545
Posts: 6516
Newest Members:
mood edibles, LouieWreve, daniellabdx, janessan21, sammiebeak359, gena7127517, thorstenbouldin, Brett.Rollason, steven014223542, Roberthat
Moderators: Jouni Aro: 1029, Pyry: 1, Petri: 1, Bjarne Boström: 1045, Jimmy Ni: 26, Matti Siponen: 353, Lusetti: 0, Elias: 0
Administrators: admin: 1