[opencms-dev] Problems installing.

Wed Jun 21 13:14:19 CEST 2000

Hi. I'm trying to install OpenCMS on a linux redhat 6.2 installation
with apache and jserv.

I've follows the installation guide, but all I see is an internal server
error. 
In the openCMS log i see:
[21.06.2000 13:00:51] <opencms_init> [1982/374/1608][OpenCmsServlet]
logging started
[21.06.2000 13:00:51] <opencms_init> [1982/374/1608][OpenCmsServlet]
property.driver = org.gjt.mm.mysql.Driver
[21.06.2000 13:00:51] <opencms_init> [1982/372/1610][OpenCmsServlet]
property.connectString =
jdbc:mysql://linux.nebula:3306/opencms?user=root;password=
[21.06.2000 13:00:51] <opencms_init> [1982/370/1612][OpenCmsServlet]
initializing opencms with initializer:
com.opencms.file.CmsInitMySqlCache
[21.06.2000 13:00:51] <opencms_init> [1982/366/1616][OpenCmsServlet]
connecting to propertyDB via org.gjt.mm.mysql.Driver
[21.06.2000 13:00:51] <opencms_init> [1982/366/1616][OpenCms] creating
first cms-object
[21.06.2000 13:00:51] <opencms_init> [1982/366/1616][OpenCms]
initializing the cms-object and the main resource-broker
[21.06.2000 13:00:51] <opencms_init> [1982/319/1663][OpenCms]
[CmsAccessUserMySql]:Cannot load connection class
'java.sql.SQLException: General error: Access denied for user:
'@linux.nebula' to database 'opencms''.
jdbc:mysql://linux.nebula:3306/opencms?user=root;password=
[21.06.2000 13:00:51] <opencms_init> [1982/317/1665][OpenCms] initialize
launchers...
[21.06.2000 13:00:51] <opencms_init> [1982/316/1666][CmsLauncherManager]
launcher package is:com.opencms.launcher
[21.06.2000 13:00:51] <opencms_init> [1982/314/1668][CmsLauncherManager]
OpenCms launcher "CmsXmlLauncher" with launcher ID 3 loaded
successfully.
[21.06.2000 13:00:51] <opencms_init> [1982/312/1670][CmsLauncherManager]
OpenCms launcher "CmsDumpLauncher" with launcher ID 1 loaded
successfully.
[21.06.2000 13:00:51] <opencms_init> [1982/309/1673][CmsLauncherManager]
OpenCms launcher "CmsLinkLauncher" with launcher ID 4 loaded
successfully.
[21.06.2000 13:00:51] <opencms_init> [1982/307/1675][CmsLauncherManager]
OpenCms launcher "CmsPdfLauncher" with launcher ID 5 loaded
successfully.
[21.06.2000 13:01:41] <opencms_init> [1982/692/1290][OpenCmsServlet]
logging started
[21.06.2000 13:01:41] <opencms_init> [1982/691/1291][OpenCmsServlet]
property.driver = org.gjt.mm.mysql.Driver
[21.06.2000 13:01:41] <opencms_init> [1982/688/1294][OpenCmsServlet]
property.connectString = null
[21.06.2000 13:01:41] <opencms_init> [1982/688/1294][OpenCmsServlet]
initializing opencms with initializer:
com.opencms.file.CmsInitMySqlCache
[21.06.2000 13:01:41] <opencms_init> [1982/685/1297][OpenCmsServlet]
connecting to propertyDB via org.gjt.mm.mysql.Driver
[21.06.2000 13:01:41] <opencms_init> [1982/685/1297][OpenCms] creating
first cms-object
[21.06.2000 13:01:41] <opencms_init> [1982/685/1297][OpenCms]
initializing the cms-object and the main resource-broker
[21.06.2000 13:01:41] <opencms_init> [1982/683/1299][OpenCms]
[CmsAccessUserMySql]:The url cannot be null
[21.06.2000 13:01:41] <opencms_init> [1982/681/1301][OpenCms] initialize
launchers...
[21.06.2000 13:01:41] <opencms_init> [1982/680/1302][CmsLauncherManager]
launcher package is:com.opencms.launcher
[21.06.2000 13:01:41] <opencms_init> [1982/678/1304][CmsLauncherManager]
OpenCms launcher "CmsXmlLauncher" with launcher ID 3 loaded
successfully.
[21.06.2000 13:01:41] <opencms_init> [1982/676/1306][CmsLauncherManager]
OpenCms launcher "CmsDumpLauncher" with launcher ID 1 loaded
successfully.
[21.06.2000 13:01:41] <opencms_init> [1982/672/1310][CmsLauncherManager]
OpenCms launcher "CmsLinkLauncher" with launcher ID 4 loaded
successfully.
[21.06.2000 13:01:41] <opencms_init> [1982/671/1311][CmsLauncherManager]
OpenCms launcher "CmsPdfLauncher" with launcher ID 5 loaded
successfully.

I beleive that the reson is, that opencms is trying to connect to hte
mysql database useing udername @linux.nebula, and not user root.
opencms.properties attached.

Any ideas?

Thanks in advance
Anders Fugmann

-- 

Anders Fugmann
Systems Developer
E-mail: anders.fugmann at framfab.dk
Direkte: +45 39 17 48 38

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Framfab A/S

Livjægergade 17A, 2.sal.        
DK-2100 København Ø

Telefon: +45 39 17 48 48
Telefax: +45 39 17 48 49

E-mail: info at framfab.com
Web: http://www.framfab.com
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-------------- next part --------------
property.driver = org.gjt.mm.mysql.Driver
property.connectString =
jdbc:mysql://linux.nebula:3306/opencms?user=root;password=admin
#initializer.classname = com.opencms.file.CmsInitMySql
initializer.classname = com.opencms.file.CmsInitMySqlCache

#
# Logging parameters
####################

# Enable/disable OpenCms logging.
# WARNING: logging is a very expensive operation in terms of performance. You
# should reduced the generated log to a minumum or even disable it if fast 
# execution is an issue.  Note that if all log channels (see below) are
# enabled, the log may become really big since each request may
# generate many Kb of log. Some log channels are mainly for debugging
# purposes and should be disabled in a production environment.
# Syntax: log=[true,false] (boolean)
# Default: true
log=true

# Set the name of the log file.  To avoid possible confusion about
# the location of this file, an absolute pathname is recommended.
# Syntax: log.file=[log path and filename] (String)
# Default: NONE
# Note: if the file could not be opened, try using absolute paths.
log.file=/usr/local/nebula/opencms/servlets/logs/opencms.log

# Enable the timestamp before the log message
# Syntax: log.timestamp=[true,false] (boolean)
# Default: true
log.timestamp=true

# Use the given string as a data format 
# (see java.text.SimpleDateFormat for the list of options)
# Syntax: log.dateFormat=(String)
# Default: [dd/MM/yyyy HH:mm:ss:SSS zz]
log.dateFormat=[dd.MM.yyyy HH:mm:ss]

# Since all the messages logged are processed by a thread running with
# minimum priority, it's of vital importance that this thread gets a chance
# to run once in a while. If it doesn't, the log queue overflow occurs,
# usually resulting in the OutOfMemoryError.
#
# To prevent this from happening, two parameters are used: log.queue.maxage
# and log.queue.maxsize. The former defines the maximum time for the logged
# message to stay in the queue, the latter defines maximum number of
# messages in the queue.
#
# If one of those conditions becomes true (age > maxage || size > maxsize),
# the log message stating that fact is generated and the log queue is
# flushed in the separate thread.
#
# If you ever see such a message, either your system doesn't live up to its
# expectations or you have a runaway loop (probably, but not necessarily,
# generating a lot of log messages).
#
# WARNING: Default values are lousy, you probably want to tweak them and
# report the results back to the development team.

# Syntax: log.queue.maxage = [milliseconds]
# Default: 5000
log.queue.maxage = 5000

# Syntax: log.queue.maxsize = [integer]
# Default: 1000
log.queue.maxsize = 1000

# Enable logging of the channel name
log.channel=true

# Enable/disable channels, each logging different actions.
# Syntax: log.channel.[channel name]=[true,false] (boolean)
# Default: false
log.channel.opencms_init=true
log.channel.opencms_debug=true
log.channel.opencms_info=true
log.channel.opencms_critical=true
log.channel.modules_debug=true    
log.channel.modules_info=true        
log.channel.modules_critical=true     