Welcome, Guest
Username: Password: Remember me

TOPIC: History storage in development environment

History storage in development environment 3 years 5 months ago #10831

  • silvaphoenix
  • silvaphoenix's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 97
  • Thank you received: 5
  • Karma: 4
Hi,
I am trying to set up a history storage in my project that I run at home from one computer in the development environment.
I created a new volume and identity in the global volume list.
I created RootVolumeConfig object in the project directory with the new volume name.
This volume has database mysql and server pwrp:pwrp@localhost
When I try to open the new volume I get the message 'Database 'new volume' is locked by user pwrp on 'computer name''
Removing the lock gives the following:

Failed to connect to database: Error: Access denied for user 'pwrp'@'localhost' (using password: NO)
wb_dbms::abort, rc 1
mysql_autocommit(m_con, 0) : 1
/usr/pwr57/os_linux/hw_x86_64/exp/exe/wb_open_db.sh: line 60: 28491 Segmentation fault (core dumped) wb -q "$username" "$password" $database

User pwrp exists in mysql with with password pwrp and all privileges granted.

Please help me find the problem
Thanks
Stephen
The administrator has disabled public write access.

History storage in development environment 3 years 5 months ago #10833

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3178
  • Thank you received: 502
  • Karma: 133
Hi Stephen,

The volume should have database berkeleydb as an ordinary volume. It's the sevserver object that should have database mysql.
In 5.7 you should configure the sev server as an ordinary process station with a NodeConfig object (not SevNodeConfig). The history database is configured with a SevServer object in the node hierarchy in the root volume.

/Claes
The administrator has disabled public write access.
The following user(s) said Thank You: silvaphoenix

History storage in development environment 3 years 5 months ago #10835

  • silvaphoenix
  • silvaphoenix's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 97
  • Thank you received: 5
  • Karma: 4
Thank you Claes
Stephen
The administrator has disabled public write access.

History storage in development environment 3 years 5 months ago #10845

  • silvaphoenix
  • silvaphoenix's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 97
  • Thank you received: 5
  • Karma: 4
Hi Claes,
I've set up the sev server as an ordinary process station Node with a SevServer object.
In the plant process Node I've included a SevHistMonitor object with child SevHistThread with ServerNode the new storage station node. The plant hierarchy includes an analogue value with SevHist object with ThreadObject the SevHistMonitor thread.
In runtime I get the error message for rt_sevhistmon 'Unknown server node name' referring to the SevHistMonitor thread.
Please can you let me know where I have gone wrong.
Thanks
Stephen
The administrator has disabled public write access.

History storage in development environment 3 years 5 months ago #10846

  • claes
  • claes's Avatar
  • OFFLINE
  • Platinum Boarder
  • Posts: 3178
  • Thank you received: 502
  • Karma: 133
Hi Stephen,

If the sev server is a separate project you have to configure the QCom communication between the nodes with FriendNodeConfig objects on both sides. You don't need net handler communication so you can set communication to qcomonly.

/Claes
The administrator has disabled public write access.

History storage in development environment 3 years 5 months ago #10847

  • silvaphoenix
  • silvaphoenix's Avatar
  • OFFLINE
  • Expert Boarder
  • Posts: 97
  • Thank you received: 5
  • Karma: 4
Cleas,
It's not a separate project, it's another root volume in the same project without any plant just a node with a sev sever
Stephen
The administrator has disabled public write access.
Time to create page: 9.082 seconds