Opened 9 years ago

Closed 9 years ago

#1057 closed defect (fixed)

RNP protocol work not correctly in Centos 7

Reported by: Bang Pham Huu Owned by: gmerticariu,
Priority: major Milestone:
Component: rasnet Version: development
Keywords: Cc: George Merticariu
Complexity: Medium

Description

Hi George,

Thanks for your willingness, this is a case that I've faced 2 days ago when clone Rasdaman and install in my new installation Centos 7. Please note that this is not my desktop in my office that I've installed a lot with grpc without success. So you can see it is very new installation (no install Rasdaman before, the first time and the error is below). My installation when configure is just

./configure —prefix=$RMANHOME —with-java-server=embedded.

I think RNP still support in Rasdaman so please check that some where there are mixing between Rasnet and RNP.

it looks like RNP not work correctly (Centos 7 - not install grpc (rasnet)).
onfiguration dir: /home/rasdaman/install/etc/
rasj[0] RasRNPImplementation.executeGetFreeServer: 805
rasj[0] RasRNPImplementation.getFreeServer: RasManager Error: No suitable servers started, call administrator.
rasj[0] RasRNPImplementation.executeGetFreeServer: 805
rasj[0] RasRNPImplementation.getFreeServer: RasManager Error: No suitable servers started, call administrator.
rasj[0] RasRNPImplementation.executeGetFreeServer: 805
rasj[0] RasRNPImplementation.getFreeServer: RasManager Error: No suitable servers started, call administrator.
rasj[0] RasRNPImplementation.executeGetFreeServer: 805
rasj[0] RasRNPImplementation.getFreeServer: RasManager Error: No suitable servers started, call administrator.
rasj[0] RasRNPImplementation.executeGetFreeServer: 805
rasj[0] RasRNPImplementation.getFreeServer: RasManager Error: No suitable servers started, call administrator.
  WARN [22:54:31] RasUtil@401: Failed retrieving rasdaman version
rasj.RasConnectionFailedException: RasManager Error: No suitable servers started, call administrator.
	at rasj.rnp.RasRNPImplementation.executeGetFreeServer(RasRNPImplementation.java:791)
	at rasj.rnp.RasRNPImplementation.getFreeServer(RasRNPImplementation.java:704)
	at rasj.rnp.RasRNPImplementation.openDB(RasRNPImplementation.java:262)
	at rasj.odmg.RasDatabase.open(RasDatabase.java:72)
	at petascope.util.ras.RasUtil.executeRasqlQuery(RasUtil.java:140)
	at petascope.util.ras.RasUtil.executeRasqlQuery(RasUtil.java:234)
	at petascope.util.ras.RasUtil.executeRasqlQuery(RasUtil.java:88)
	at petascope.util.ras.RasUtil.getRasdamanVersion(RasUtil.java:399)
	at petascope.ConfigManager.initSettings(ConfigManager.java:328)
	at petascope.ConfigManager.<init>(ConfigManager.java:253)
	at petascope.ConfigManager.getInstance(ConfigManager.java:270)
	at petascope.PetascopeInterface.init(PetascopeInterface.java:119)
	at javax.servlet.GenericServlet.init(GenericServlet.java:256)
	at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:477)
	at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:293)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
	at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:730)
	at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:254)
	at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1238)
	at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:689)
	at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:480)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
	at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:229)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
	at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:95)
	at org.eclipse.jetty.server.Server.doStart(Server.java:279)
	at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:64)
	at start_petascope.main(start_petascope.java:281)
[rasdaman@linux test_wcs]$ ./test.sh 
Old logfile found, copying it to /home/rasdaman/rasdaman/systemtest/testcases_services/test_wcs/log.save
test.sh: starting test at Thu Nov  5 22:57:56 EET 2015
test.sh: 
test.sh: Testing service: wcs
rasdaman error 805: RasManager Error: No suitable servers started, call administrator.
rasdaman error 805: RasManager Error: No suitable servers started, call administrator.
test.sh: deleting coverage rgb from petascope... no such coverage found.

Attachments (2)

log_rasdaman.tar.gz (18.2 KB ) - added by Bang Pham Huu 9 years ago.
log_error.tar.gz (15.3 KB ) - added by Bang Pham Huu 9 years ago.

Download all attachments as: .zip

Change History (7)

comment:1 by Dimitar Misev, 9 years ago

So is rasdaman started? Can you upload the rasdaman logs?

by Bang Pham Huu, 9 years ago

Attachment: log_rasdaman.tar.gz added

comment:2 by Bang Pham Huu, 9 years ago

I've added my log (looks like rasgmr could not load due to configuration).

comment:3 by Dimitar Misev, 9 years ago

It looks like your rasmgr.conf is broken, or something else is wrong. It's not an issue with RNP, I'm sure the protocol works as we have been using it for a looong time now ;)

by Bang Pham Huu, 9 years ago

Attachment: log_error.tar.gz added

comment:4 by Bang Pham Huu, 9 years ago

@Dimitar: yes, it seems like this (I've make clean to uninstall Rasdaman and reinstall it again with ./configure —prefix=/home/rasdaman/install —with-java-server=embedded —enable-netcdf). It seems rasmgr now can start but it has a problem when I tried to import with ./test.sh in test_wcs. It is not related to this ticket but I think you maybe have experience before so please view the log files (you can do it next week :) ).

Rasserver

07/11/2015 11:31:37.792 [FATAL] SQL query failed: BEGIN IMMEDIATE TRANSACTION
07/11/2015 11:31:37.792 [FATAL] Database error, code: 5, message: database is locked
07/11/2015 11:31:37.792 [ERROR] Error: base DBMS reports: Error in base DBMS, error number: 5
database is locked
07/11/2015 11:35:38.025 [ERROR] Client has timed out, connection being freed.

Rasmgr

[ERROR] Error: write transaction in progress, conflicts with request.


comment:5 by Dimitar Misev, 9 years ago

Resolution: fixed
Status: newclosed

Ok let's close this ticket then. Please get the latest rasdaman, what you have is not latest.

Note: See TracTickets for help on using tickets.