Penny,
When the test server is available again, try the following:
verify that there is and 'las' user entry for the fully qualified
domain name where LAS is running and that you can login using this
command line on the host where LAS is running.
mysql -u las -p lasrules -h hostname.subdomain.nasa.gov lasN
and then in your webapps/las/WEB-INF/classes/las.properties file (using
whatever name you gave this installation in place of 'las') for the
tomcat servlet container where the test server is running: use the
following
las.db.host=hostname.subdomain.nasa.gov <-- where this is the fully
qualified domain name of the mysqld host you want to connect to.
las.db.user=las <-- This should work instead of root provide the
correct entry exists.
las.db.password=lasrules <-- This should work unless it's been
changed.
las.db.dbase=lasN <-- This should not change.
From what I can tell you have not tried this combination before (you
tried the fully qualified domain name with the root user, but not this).
You have to restart the servlet contain for these changes to take
effect. If you make any change to the mysql grant tables (adding
users, etc) then you should tell the mysqld to re-read the grant tables
with the "mysqladmin reload" command.
Let me know.
Roland
Penny Oots wrote:
Roland,
The servers are on two different hosts and do not share the same
mysqld.
I believe the output from the las.properties file is as follows:
las.db.host=localhost
las.db.user=root
las.db.password=xxxxxx
las.db.dbase=las0
At the moment, the system administrator is not allowing logins. The
information above is from the working server. I'll let you know if
there is any difference when I can get in again. We did try
entering the full host name when doing a make but that did not correct
the problem. In the mysql database, the user las has an entry for
localhost, the full host name and just the shortened host name.
Root has an entry for local host and the shortened host name (no third
entry).
Penny
At 03:15 PM 3/22/2005, Roland Schweitzer wrote:
Penny,
Can you please send us the following additional information? This
will help me get a better picture of how your site is arranged.
In the webapps/las/WEB-INF/classes directory there is a las.properties
file. This controls how the User Interface servlet connects to the
LAS database. It also contains the mySQL password for the account
being used to connect to the database. Do not send us the
password, but please send us the other entries in the file for both
systems.
E.g.
las.db.host=stout.pmel.noaa.gov
las.db.user=las
las.db.password=xxxxxx
las.db.dbase=las3
Also, how many msyqld processes are you running. In other words, do
the test server and the production server share the same mysqld? If
so, are they on the same host. If not are they on different
hosts.
Roland
Penny Oots wrote:
Greetings,
We currently have 2 servers configured in an identical format. One is a
production machine running
LAS and can be found here:
http://mynasadata.larc.nasa.gov/data.html
While all is fine with this system, our development system has flaked
out...why? I don't know why?
As of yesterday morning 03-15-05 our system development system was
running without error. That
afternoon while trying to connect to the LAS server the error below is
displayed.
To the best of my knowledge and those working with the system, no
changes
had been made. Apache
displays fine up to the point that you click the Live Access Server
section on the page. Choosing
port 8080 will display the default Tomcat page. MySQL is up and
running.
I have compared
various files and folders to the working mynasadata server, but cannot
seem to find any differences.
I have stopped the server, ran a make on the system, and have restarted
the server....but still same
problem. Is this a MySQL, LAS, Tomcat problem? Any help would be
greatly
appreciated
Thanks again
David Dove
Systems Engineer
Note from Penny Oots: We are still experiencing this issue even
though we can login to mysql using root or las database users.
Since last week (among other things), we added --log to the mysqld
startup script, but no entries are written to it when we try to bring
up
the LAS gui. In additon to LAS 6.4, we are using jakarta
-tomcat-connectors jk-1.2. Again this is also on the working system
on the production system.
Any ideas anyone??
Penny
LAS server error
You have encountered an unexpected User Interface error!
Please click
here to return to the Datasets page. If this error persists please
contact the LAS administrator for this
site.
The following error occurred:
javax.servlet.ServletException: Server configuration denies access
to data source
at
gov.noaa.pmel.tmap.SessionFilter.initDefaultContexts(SessionFilter.java:190)
at
gov.noaa.pmel.tmap.SessionFilter.checkSession(SessionFilter.java:318)
at
gov.noaa.pmel.tmap.SessionFilter.doFilter(SessionFilter.java:347)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:204)
at
gov.noaa.pmel.tmap.ExceptionFilter.doFilter(ExceptionFilter.java:24)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:233)
....
More java errors and then this error:
Root cause of servlet exception was:
java.sql.SQLException: Server configuration denies access to data
source
at
org.gjt.mm.mysql.MysqlIO.init(MysqlIO.java:203)
at
org.gjt.mm.mysql.Connection.connectionInit(Connection.java:276)
at
org.gjt.mm.mysql.jdbc2.Connection.connectionInit(Connection.java:89)
at
org.gjt.mm.mysql.Driver.connect(Driver.java:167)
at
java.sql.DriverManager.getConnection(DriverManager.java:512)
at
java.sql.DriverManager.getConnection(DriverManager.java:193)
.....more java errors.
|