Hyrax - Frequently Asked Questions - Revision history

PatrickWest: /* BES Fatal; cannot open log file ./bes.log. */

2011-02-03T01:12:12Z

BES Fatal; cannot open log file ./bes.log.

← Older revision		Revision as of 01:12, 3 February 2011
Line 95:		Line 95:
	==BES Fatal; cannot open log file ./bes.log.==		==BES Fatal; cannot open log file ./bes.log.==

	Although the BES is started as root, is will be running as the user you set in the BES configuration file. So be sure that that user has permission to write to the current directory where you are starting the BES.		Although the BES is started as root, it will be running as the user you set in the BES configuration file. So be sure that that user has permission to write to the current directory where you are starting the BES.

	Alternatively, edit the BES configuration file bes.conf and change the location of the bes.log file.		Alternatively, edit the BES configuration file bes.conf and change the location of the bes.log file.

			==How do I add configuration parameters to my .conf file==

			Every module has its own configuration file, x.conf. For example, the netcdf data handler module has a configuration file called nc.conf. These files are located in the intall_dir/etc/bes/modules directory. So if you install in /usr/local, it will be in /usr/local/etc/bes/modules. If you are writing a module, you can add your own parameters to your configuration file.

			Please go to the [http://docs.opendap.org/index.php/Hyrax_-_Extending_BES_Module#Configuring_your_Module BES module page] for more information on how to do this.

PatrickWest at 21:25, 28 April 2010

2010-04-28T21:25:15Z

← Older revision		Revision as of 21:25, 28 April 2010
Line 92:		Line 92:

	If building from source or from SVN, just running 'make install' isn't enough. You must also either run 'make bes-conf' or run the bes-x-data.sh script for that data handler. For example, bes-nc-data.sh. Building that target using make, or running those scripts, adds information to the BES configuration file, bes.conf. This step is important to installing the different modules and handlers.		If building from source or from SVN, just running 'make install' isn't enough. You must also either run 'make bes-conf' or run the bes-x-data.sh script for that data handler. For example, bes-nc-data.sh. Building that target using make, or running those scripts, adds information to the BES configuration file, bes.conf. This step is important to installing the different modules and handlers.

			==BES Fatal; cannot open log file ./bes.log.==

			Although the BES is started as root, is will be running as the user you set in the BES configuration file. So be sure that that user has permission to write to the current directory where you are starting the BES.

			Alternatively, edit the BES configuration file bes.conf and change the location of the bes.log file.

PatrickWest at 16:08, 27 April 2010

2010-04-27T16:08:29Z

← Older revision		Revision as of 16:08, 27 April 2010
Line 2:		Line 2:
	The OPeNDAP Lightweight Front-end Service		The OPeNDAP Lightweight Front-end Service

	== Status 503 "application not currently available"		== Status 503 "application not currently available" ==
	After starting up the tomcat server with the opendap.war file placed in the webapps directory, I can see the tomcat splash page if I go to <pre>http://localhost:8080/</pre>. But when I go to <pre>http://localhost:8080/opendap/</pre> I get this error.		After starting up the tomcat server with the opendap.war file placed in the webapps directory, I can see the tomcat splash page if I go to <pre>http://localhost:8080/</pre>. But when I go to <pre>http://localhost:8080/opendap/</pre> I get this error.

PatrickWest at 16:08, 27 April 2010

2010-04-27T16:08:14Z

← Older revision		Revision as of 16:08, 27 April 2010
Line 1:		Line 1:
			=OLFS=
			The OPeNDAP Lightweight Front-end Service

			== Status 503 "application not currently available"
			After starting up the tomcat server with the opendap.war file placed in the webapps directory, I can see the tomcat splash page if I go to <pre>http://localhost:8080/</pre>. But when I go to <pre>http://localhost:8080/opendap/</pre> I get this error.

	=BES=		=BES=
			The OPeNDAP Hyrax Back-End Server

	==Regular expression matches in BES==		==Regular expression matches in BES==

PatrickWest: /* The service dap has already been registered */

2010-04-19T17:43:27Z

The service dap has already been registered

← Older revision		Revision as of 17:43, 19 April 2010
Line 50:		Line 50:
	To correct this, please change the parameter BES.Memory.GlobalArea.Maximu'''n'''HeapSize to BES.Memory.GlobalArea.Maximu'''m'''HeapSize.		To correct this, please change the parameter BES.Memory.GlobalArea.Maximu'''n'''HeapSize to BES.Memory.GlobalArea.Maximu'''m'''HeapSize.

	=The service dap has already been registered=		==The service dap has already been registered==

	Starting with Hyrax 1.6.0, the BES configuration has changed. It used to be that each handler/module would modify the bes.conf file, or the user would have to modify the bes.conf file, in order to enable that module. Now, the handler/module installs a .conf file in the directory modules under <prefix>/etc/bes/modules. The bes.conf file exists in <prefix>/etc/bes, and includes any .conf files located in the modules directory.		Starting with Hyrax 1.6.0, the BES configuration has changed. It used to be that each handler/module would modify the bes.conf file, or the user would have to modify the bes.conf file, in order to enable that module. Now, the handler/module installs a .conf file in the directory modules under <prefix>/etc/bes/modules. The bes.conf file exists in <prefix>/etc/bes, and includes any .conf files located in the modules directory.

PatrickWest at 17:43, 19 April 2010

2010-04-19T17:43:08Z

← Older revision		Revision as of 17:43, 19 April 2010
Line 1:		Line 1:
	=Regular expression matches in BES=		=BES=
			==Regular expression matches in BES==

	There are two regular expression matches in the BES, both configured in the BES configuration file bes.conf.		There are two regular expression matches in the BES, both configured in the BES configuration file bes.conf.
Line 41:		Line 42:
	followed by an underscore and anything else.		followed by an underscore and anything else.

	=BES: unable to start properly because can not determine memory keys.=		==BES: unable to start properly because can not determine memory keys.==

	In release 1.4.1 of Hyrax, which includes release 3.6.0 of the BES, we fixed a typo in the BES configuration file. Unfortunately, this produces an error when you start up the BES if the configuration still contains the typo. The error message is:		In release 1.4.1 of Hyrax, which includes release 3.6.0 of the BES, we fixed a typo in the BES configuration file. Unfortunately, this produces an error when you start up the BES if the configuration still contains the typo. The error message is:
Line 72:		Line 73:
	BES.CacheDir=<path_to_bes_cache_directory>		BES.CacheDir=<path_to_bes_cache_directory>

	=I've installed the BES, but I'm not able to access any data=		==I've installed the BES, but I'm not able to access any data==

	The BES is a software framework that allows data providers to serve specific kinds of data in specific ways. Off the shelf the BES doesn't provide any data access or any kinds of responses, not even DAP responses like DAS, DDS, ASCII, etc...		The BES is a software framework that allows data providers to serve specific kinds of data in specific ways. Off the shelf the BES doesn't provide any data access or any kinds of responses, not even DAP responses like DAS, DDS, ASCII, etc...
Line 83:		Line 84:

	If building from source or from SVN, just running 'make install' isn't enough. You must also either run 'make bes-conf' or run the bes-x-data.sh script for that data handler. For example, bes-nc-data.sh. Building that target using make, or running those scripts, adds information to the BES configuration file, bes.conf. This step is important to installing the different modules and handlers.		If building from source or from SVN, just running 'make install' isn't enough. You must also either run 'make bes-conf' or run the bes-x-data.sh script for that data handler. For example, bes-nc-data.sh. Building that target using make, or running those scripts, adds information to the BES configuration file, bes.conf. This step is important to installing the different modules and handlers.

	~~=Question 5=~~
	~~=Question 6=~~
	~~=Question 7=~~
	~~=Question 8=~~
	~~=Question 9=~~

PatrickWest: /* Question 4 */

2010-04-19T17:39:04Z

Question 4

← Older revision		Revision as of 17:39, 19 April 2010
Line 72:		Line 72:
	BES.CacheDir=<path_to_bes_cache_directory>		BES.CacheDir=<path_to_bes_cache_directory>

	=~~Question 4~~=		=I've installed the BES, but I'm not able to access any data=

			The BES is a software framework that allows data providers to serve specific kinds of data in specific ways. Off the shelf the BES doesn't provide any data access or any kinds of responses, not even DAP responses like DAS, DDS, ASCII, etc...

			In order to return DAP responses like DAS, DDS, DDX, DataDDS you have to have a BES installed that is built against libdap. When building from source you should first install, or build and install, libdap. When installing from RPM you will not be able to install without first installing the libdap RPM.

			In order to have an ascii response for your data, or have the html form presented, you must install the General Purpose Handlers, which can be found on the Hyrax Download Page, as can any of the data handlers, libdap, and the fileout module. Here is the official list of BES modules.

			In order to serve a particular type of data you must install one of the data handlers. The current officially supported data handlers are netcdf, hdf4, hdf5 and freeform. Again, these can be downloaded from Hyrax Download Page.

			If building from source or from SVN, just running 'make install' isn't enough. You must also either run 'make bes-conf' or run the bes-x-data.sh script for that data handler. For example, bes-nc-data.sh. Building that target using make, or running those scripts, adds information to the BES configuration file, bes.conf. This step is important to installing the different modules and handlers.

	=Question 5=		=Question 5=
	=Question 6=		=Question 6=

PatrickWest: /* The service dap has already been registered */

2010-04-19T17:37:58Z

The service dap has already been registered

← Older revision		Revision as of 17:37, 19 April 2010
Line 50:		Line 50:

	=The service dap has already been registered=		=The service dap has already been registered=

			Starting with Hyrax 1.6.0, the BES configuration has changed. It used to be that each handler/module would modify the bes.conf file, or the user would have to modify the bes.conf file, in order to enable that module. Now, the handler/module installs a .conf file in the directory modules under <prefix>/etc/bes/modules. The bes.conf file exists in <prefix>/etc/bes, and includes any .conf files located in the modules directory.

			If you've installed the new BES for Hyrax 1.6, and then modify your bes.conf file like you've done in the past, this could cause problems like duplicate modules registered, duplicate services registered, etc...

			So, in the new bes.conf file, there is a line:

			BES.modules=

			which is empty. Leave it empty. The .conf files in the modules directory, such as nc.conf, will contain a line that looks like this:

			BES.modules+=nc
			BES.module.nc=<prefix>/lib/bes/libnc_module.so

			The only items that you will need to change in the bes.conf file is:

			BES.ServerAdministrator=
			BES.User=
			BES.Group=
			BES.LogName=<path_to>/bes.log
			BES.CacheDir=<path_to_bes_cache_directory>

	=Question 4=		=Question 4=

PatrickWest: /* Question 3 */

2010-04-19T17:30:49Z

Question 3

← Older revision		Revision as of 17:30, 19 April 2010
Line 49:		Line 49:
	To correct this, please change the parameter BES.Memory.GlobalArea.Maximu'''n'''HeapSize to BES.Memory.GlobalArea.Maximu'''m'''HeapSize.		To correct this, please change the parameter BES.Memory.GlobalArea.Maximu'''n'''HeapSize to BES.Memory.GlobalArea.Maximu'''m'''HeapSize.

	=~~Question 3~~=		=The service dap has already been registered=

	=Question 4=		=Question 4=
	=Question 5=		=Question 5=

PatrickWest: /* Regular expression matches in BES */

2010-01-09T19:13:33Z

Regular expression matches in BES

← Older revision		Revision as of 19:13, 9 January 2010
Line 38:		Line 38:
	expression ".\.nc(\.bz2\|\.gz\|\.Z)?$\|.JA2_[OIG]P[NRS]_.*$" matches exactly, type = nc		expression ".\.nc(\.bz2\|\.gz\|\.Z)?$\|.JA2_[OIG]P[NRS]_.*$" matches exactly, type = nc

	Matches anything that ends with .nc OR anything that ends with a file that begins with JA2_; then one of O, I, G; then P; then one of N, R, S; followed by an underscore and anything else.		Matches anything that ends with .nc OR anything that ends with a file that begins with JA2_; then one of O, I, G; then P; then one of N, R, S;
			followed by an underscore and anything else.

	=BES: unable to start properly because can not determine memory keys.=		=BES: unable to start properly because can not determine memory keys.=