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

TOPIC: Help with upgrade. 5.5 to 5.6

Help with upgrade. 5.5 to 5.6 5 years 2 months ago #10163

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

I'm upgrading the system I built, to proview last version and I have problems to start the runtime process in a raspberry.

After a hard work I could make it work with the previous version, but this one is starting to get on my nerves.

Although I have included a new sev server in the project, and here is where the problem is, I'm not able to make it work.

pwrp@mephisto:~$ 
   Proview/R Version V5.6.1 for Linux on ARM
   Copyright (C) 2005-2018 SSAB EMEA AB

   Proview/R is free software; you can redistribute it and/or
   modify it under the terms of the GNU General Public License.

   This program is distributed in the hope that it will be useful
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
   GNU General Public License for more details.

   ProviewR Runtime Environment

rt_bck_load: No such file or directory
sched_setscheduler: Operation not permitted
failed to set pid 1250's policy
sched_setscheduler: Operation not permitted
failed to set pid 1251's policy
sched_setscheduler: Operation not permitted
failed to set pid 1252's policy
sched_setscheduler: Operation not permitted
failed to set pid 1253's policy
sched_setscheduler: Operation not permitted
failed to set pid 1254's policy
sched_setscheduler: Operation not permitted
failed to set pid 1255's policy
sched_setscheduler: Operation not permitted
failed to set pid 1256's policy
sched_setscheduler: Operation not permitted
failed to set pid 1257's policy
sched_setscheduler: Operation not permitted
failed to set pid 1258's policy
sched_setscheduler: Operation not permitted
failed to set pid 1259's policy
sched_setscheduler: Operation not permitted
failed to set pid 1260's policy
sched_setscheduler: Operation not permitted
failed to set pid 1261's policy
sched_setscheduler: Operation not permitted
failed to set pid 1262's policy
sched_setscheduler: Operation not permitted
failed to set pid 1263's policy
sev_dbms_env::create: /pwrp/common/db/pwrp__horno.db
In ../../sev_dbms.cpp row 290:
Failed to connect to database: Error: Access denied for user 'pwrp'@'localhost' (using password: NO)
HistServer startingjava.library.path = /usr/pwrrt/exe:/usr/java/packages/lib/arm:/lib:/usr/lib

JHist: Before waiting for client


Any hint?

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

Help with upgrade. 5.5 to 5.6 5 years 2 months ago #10164

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

Have you created user pwrp in mysql?

/Claes
The administrator has disabled public write access.

Help with upgrade. 5.5 to 5.6 5 years 2 months ago #10173

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

Thanks for answering my question.

Yes, I have created the user, but I can't access to mysql with this 'pwrp' user without using a password.

I think that is where the error resides.

The log on the upper side of this post was captured the first time i started the server after installation.

This one is the "usual" log upon start.

pwrp@mephisto:~$ pwr start
Start Proview Runtime Environment.
Done.
pwrp@mephisto:~$ 
   Proview/R Version V5.6.1 for Linux on ARM
   Copyright (C) 2005-2018 SSAB EMEA AB

   Proview/R is free software; you can redistribute it and/or
   modify it under the terms of the GNU General Public License.

   This program is distributed in the hope that it will be useful
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
   GNU General Public License for more details.

   ProviewR Runtime Environment

sched_setscheduler: Operation not permitted
failed to set pid 1236's policy
sched_setscheduler: Operation not permitted
failed to set pid 1237's policy
sched_setscheduler: Operation not permitted
failed to set pid 1238's policy
sched_setscheduler: Operation not permitted
failed to set pid 1239's policy
sched_setscheduler: Operation not permitted
failed to set pid 1240's policy
sched_setscheduler: Operation not permitted
failed to set pid 1241's policy
sched_setscheduler: Operation not permitted
failed to set pid 1242's policy
sched_setscheduler: Operation not permitted
failed to set pid 1243's policy
sched_setscheduler: Operation not permitted
failed to set pid 1244's policy
sched_setscheduler: Operation not permitted
failed to set pid 1245's policy
sched_setscheduler: Operation not permitted
failed to set pid 1246's policy
sched_setscheduler: Operation not permitted
failed to set pid 1247's policy
sched_setscheduler: Operation not permitted
failed to set pid 1248's policy
sched_setscheduler: Operation not permitted
failed to set pid 1249's policy
No such database
java.library.path = /usr/pwrrt/exe:/usr/java/packages/lib/arm:/lib:/usr/lib
HistServer starting
JHist: Before waiting for client

Should I reinstall rt on the raspi? (Notice the "no such database" statement)

What's the scheduler error?

Thanks in advance
The administrator has disabled public write access.

Help with upgrade. 5.5 to 5.6 5 years 2 months ago #10174

  • Avispao
  • Avispao's Avatar
  • OFFLINE
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
I have just answered my question.

The user in mysql was indeed created, but with password set.

I deleted the user, and recreated it without pass, and then:

pwrp@mephisto:/etc/init.d$ pwr start
Start Proview Runtime Environment.
Done.
pwrp@mephisto:/etc/init.d$ 
   Proview/R Version V5.6.1 for Linux on ARM
   Copyright (C) 2005-2018 SSAB EMEA AB

   Proview/R is free software; you can redistribute it and/or
   modify it under the terms of the GNU General Public License.

   This program is distributed in the hope that it will be useful
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
   GNU General Public License for more details.

   ProviewR Runtime Environment

mq_send: Resource temporarily unavailable
sched_setscheduler: Operation not permitted
failed to set pid 3513's policy
sched_setscheduler: Operation not permitted
failed to set pid 3514's policy
sched_setscheduler: Operation not permitted
failed to set pid 3515's policy
sched_setscheduler: Operation not permitted
failed to set pid 3516's policy
sched_setscheduler: Operation not permitted
failed to set pid 3517's policy
sched_setscheduler: Operation not permitted
failed to set pid 3518's policy
sched_setscheduler: Operation not permitted
failed to set pid 3519's policy
sched_setscheduler: Operation not permitted
failed to set pid 3520's policy
sched_setscheduler: Operation not permitted
failed to set pid 3521's policy
sched_setscheduler: Operation not permitted
failed to set pid 3522's policy
sched_setscheduler: Operation not permitted
failed to set pid 3523's policy
sched_setscheduler: Operation not permitted
failed to set pid 3524's policy
sched_setscheduler: Operation not permitted
failed to set pid 3525's policy
sched_setscheduler: Operation not permitted
failed to set pid 3526's policy
In ../../sev_dbms.cpp row 518:
Create objectitemattributes table: Specified key was too long; max key length is 767 bytes
old sev_version: 4, new sev_version: 4
HistServer starting
java.library.path = /usr/pwrrt/exe:/usr/java/packages/lib/arm:/lib:/usr/lib
JHist: Before waiting for client

Still some errors but it's a start.

PS.: I still don't know what happens with the scheduler.
Last Edit: 5 years 2 months ago by Avispao. Reason: Wrong tag
The administrator has disabled public write access.
  • Page:
  • 1
Time to create page: 7.987 seconds