Errors while performing <hbm2ddl>

[jim_hyperic]

I searched for hbm2ddl and only saw one hit without any responses.

We're seeing an installer error using Solaris x86, mysql 5.0.53 and hyperic 3.2.3 (this time!). Anyway, there's the problem:

############
./setup.sh

Initializing Hyperic HQ 3.2.3 Installation...
Loading taskdefs...
Taskdefs loaded
Choose which software to install:
1: Hyperic HQ Server
2: Hyperic HQ Shell
3: Hyperic HQ Agent
You may enter multiple choices, separated by commas.
1,2,3
HQ server installation path [default '/home/hyperic']:
/export/home/hyperic
Choices:
1: Yes
2: No
Should we overwrite the existing HQ server installation? [default '2']:
1
Choices:
1: Oracle 8
2: Oracle 9i/10g
3: PostgreSQL
4: MySQL 5.x
What backend database should the HQ server use? [default '2']:
4
Enter the JDBC connection URL for the MySQL 5.x database [default 'jdbc:mysql://localhost:3306/HQ']:

Enter the username to use to connect to the database:
hqadmin
Enter the password to use to connect to the database:
(again):
HQ shell installation path [default '/export/home/hyperic']:

HQ agent installation path [default '/export/home/hyperic']:

Loading install configuration...
Install configuration loaded.
Preparing to install...
Validating agent install configuration...
Validating shell install configuration...
Validating server install configuration...
Checking server webapp port...
Checking server secure webapp port...
Checking server JRMP port...
Checking server JNP port...
Checking database permissions...
Verifying admin user properties
Validating server DB configuration...
Installing the agent...
Looking for previous installation
Unpacking agent to: /export/home/hyperic/agent-3.2.3...
Setting permissions on agent binaries...
Fixing line endings on text files...
--------------------------------------------------------------------------------
Installation Complete:
Agent successfully installed to: /export/home/hyperic/agent-3.2.3
--------------------------------------------------------------------------------

You can now start your HQ agent by running this command:

/export/home/hyperic/agent-3.2.3/hq-agent.sh start

Installing the shell...
Unpacking shell to: /export/home/hyperic/shell-3.2.3...
Setting permissions on shell binaries...
Fixing line endings on text files...
--------------------------------------------------------------------------------
Installation Complete:
Command shell successfully installed to: /export/home/hyperic/shell-3.2.3
--------------------------------------------------------------------------------
You can now start the HQ shell by running this command:

/export/home/hyperic/shell-3.2.3/hq-shell.sh

Installing the server...
Unpacking server to: /export/home/hyperic/server-3.2.3...
Creating server configuration files...
Copying binaries and libraries to server installation...
Copying server configuration file...
Copying server control file...
Copying server binaries...
Copying server libs...
Setting up server database...
--------------------------------------------------------------------------------
An ERROR occurred, the installation cannot continue.
FATAL EXCEPTION at /export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup.xml:442: : The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup.xml:448: The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup.xml:573: The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup-db-MySQL.xml:16: The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup-db-hibernate.xml:193: Errors while performing <hbm2ddl>
===========

The hqadmin has full permissions on HQ, hqdb and everything else. I'm not sure what the .xml files could have wrong at this point...

[scottmf]

What is the name of your database in mysql? Is it "HQ" ? Since you chose the default url of 'jdbc:mysql://localhost:3306/HQ' it assumes your created db is called 'HQ'

There is also an installer log which would be helpful to see here.

[jim_hyperic]

Indeed, the database name is HQ.

I'll see if I can check the installer log.

[jim_hyperic]

I'm not sure how the hq-install.log file could help as it seems to be the same as standard out but perhaps there are some differences here. BTW, I blew everything away and tried again only to see the same error.

=========================================================================
Installer Started
Current Date/Time: Wed Jun 25 16:59:26 PDT 2008
=========================================================================
Initializing Hyperic HQ 3.2.3 Installation...
Loading taskdefs...
Taskdefs loaded
Choose which software to install:
1: Hyperic HQ Server
2: Hyperic HQ Shell
3: Hyperic HQ Agent
You may enter multiple choices, separated by commas.
HQ server installation path [default '/home/hyperic']:
server.installdir does not exist: /export/home/hyperic
HQ server installation path [default '/home/hyperic']:
Choices:
1: Oracle 8
2: Oracle 9i/10g
3: PostgreSQL
4: MySQL 5.x
What backend database should the HQ server use? [default '2']:
Enter the JDBC connection URL for the MySQL 5.x database [default 'jdbc:mysql://localhost:3306/HQ']:
Enter the username to use to connect to the database:
HQ shell installation path [default '/export/home/hyperic']:
HQ agent installation path [default '/export/home/hyperic']:
Loading install configuration...
Install configuration loaded.
Preparing to install...
Validating agent install configuration...
Validating shell install configuration...
Validating server install configuration...
Checking server webapp port...
Checking server secure webapp port...
Checking server JRMP port...
Checking server JNP port...
Checking database permissions...
Verifying admin user properties
Validating server DB configuration...
Installing the agent...
Looking for previous installation
Unpacking agent to: /export/home/hyperic/agent-3.2.3...
Setting permissions on agent binaries...
Fixing line endings on text files...
--------------------------------------------------------------------------------
Installation Complete:
Agent successfully installed to: /export/home/hyperic/agent-3.2.3
--------------------------------------------------------------------------------

You can now start your HQ agent by running this command:

/export/home/hyperic/agent-3.2.3/hq-agent.sh start

Installing the shell...
Unpacking shell to: /export/home/hyperic/shell-3.2.3...
Setting permissions on shell binaries...
Fixing line endings on text files...
--------------------------------------------------------------------------------
Installation Complete:
Command shell successfully installed to: /export/home/hyperic/shell-3.2.3
--------------------------------------------------------------------------------
You can now start the HQ shell by running this command:

/export/home/hyperic/shell-3.2.3/hq-shell.sh

Installing the server...
Unpacking server to: /export/home/hyperic/server-3.2.3...
Creating server configuration files...
Copying binaries and libraries to server installation...
Copying server configuration file...
Copying server control file...
Copying server binaries...
Copying server libs...
Setting up server database...
--------------------------------------------------------------------------------
An ERROR occurred, the installation cannot continue.
FATAL EXCEPTION at /export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup.xml:442: : The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup.xml:448: The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup.xml:573: The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup-db-MySQL.xml:16: The following error occurred while executing this line:
/export/home/data/hyperic-hq-installer/installer-3.2.3/data/setup-db-hibernate.xml:193: Errors while performing <hbm2ddl>
--------------------------------------------------------------------------------


I can attach the hq-install.log.debug file if you want. It's 2mb in size...

[scottmf]

Just zip it up and attach. Hopefully there is something in there that can help out..

[kparikh]

Hi Jim,

Debug log will have more information, can you zip it up and attach it here.

Thanks
Kashyap

[jim_hyperic]

Okay guys, here you go. It's gzipped and attached.

[scottmf]

Jim,
Try to create a table in mysql as the HQ user in HQ db. It looks like maybe there is a permission problem with your data directory?? Perhaps a remanent from the 4.x installation?

[hibernatetool] Caused by: java.sql.SQLException: Can't create table './HQ/EAM_ACTION.frm' (errno: 121)
[hibernatetool] at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:946)

do this ->

mysql> show tables;
mysql> select * from information_schema.tables where table_name = 'EAM_ACTION' and table_schema = 'HQ';

Maybe you should try to reinstall mysql or drop and recreate the db, it could be in a bad state. Perhaps even try using hqdb as your db name to avoid a conflict from the 4.x db.

[jim_hyperic]

I'm not sure how there could be anything from the previous install as I removed the databases (HQ and hqdb), removed the hyperic home directories and completely started from scratch. Now, maybe there was something outside of the above that remained and is causing this problem... I don't know.

Here's the output from your test:

mysql> connect HQ;
Connection id: 24
Current database: HQ

mysql> show tables;
Empty set (0.00 sec)

mysql> select * from information_schema.tables where table_name = 'EAM_ACTION' and table_schema = 'HQ';
Empty set (0.00 sec)

mysql>

Does that help? BTW, I've given complete access to mysql for the hqadmin user.

[jim_hyperic]

Since this is Solaris and we had a flar backup from yesterday morning, I re-installed the OS, started completely from scratch and the problem mentioned above is gone.

Now that the install was successful, I'm seeing "HQ failed to start" so I'll look into this new issue.