|
It actually doesn't exist in the DB right now that we can tell, further confusing us on whether or not it would hurt the working glu instance to have these tables created.
The full stack from the glu startup log is:
2014/03/19 10:29:03.014 ERROR [SchemaUpdate] Unsuccessful: create table db_command_execution (id bigint not null auto_increment, version bigint not null, agent varchar(255) not null, command varchar(255) not null, command_id varchar(255) not null unique, command_type varchar(255) not null, completion_time bigint, exit_error varchar(255), exit_value varchar(255), fabric varchar(255) not null, is_executing bit not null, redirect_stderr bit not null, start_time bigint not null, stderr_first_bytes tinyblob, stderr_total_bytes_count bigint, stdin_first_bytes tinyblob, stdin_total_bytes_count bigint, stdout_first_bytes tinyblob, stdout_total_bytes_count bigint, username varchar(255) not null, primary key (id)) ENGINE=InnoDB
2014/03/19 10:29:03.014 ERROR [SchemaUpdate] CREATE command denied to user 'glu'@'ourhost.someip.com' for table 'db_command_execution'
2014/03/19 10:29:03.017 WARN [AbstractEhcacheRegionFactory] Couldn't find a specific ehcache configuration for cache named [org.hibernate.cache.UpdateTimestampsCache]; using defaults.
2014/03/19 10:29:03.036 WARN [AbstractEhcacheRegionFactory] Couldn't find a specific ehcache configuration for cache named [org.hibernate.cache.StandardQueryCache]; using defaults.
Edit: I have not used the commands feature before.
|