Hi Attila,
Can you copy the full exception trace to pastebin?
Thanks
Le 11/11/2013 13:08, Attila Heidrich a écrit :
Thanks for the comments!
My problem with the new build is different. All apps are running, but
server interface shows the active agent, but the autodiscovery queue is
empty.
There are exceptions in server.log and agent.log, like:
agent.log:
2013-11-11 12:48:56,383 INFO
[ResourceDiscoveryComponent.invoker.daemon-147]
(org.rhq.plugins.apache.ApacheServerDiscoveryComponent)- SNMPConf
directive not found. Skipping SNMP configuration.
2013-11-11 12:48:56,384 INFO [InventoryManager.discovery-1]
(rhq.core.pc.inventory.AutoDiscoveryExecutor)- Discovered new platform
with 8 child server(s).
2013-11-11 12:48:56,384 INFO [InventoryManager.discovery-1]
(rhq.core.pc.inventory.InventoryManager)- Sending [server] inventory
report to Server...
2013-11-11 12:48:56,849 WARN [InventoryManager.discovery-1]
(rhq.core.pc.inventory.AutoDiscoveryExecutor)- Exception caught while
executing server discovery scan.
[Warning] javax.ejb.EJBTransactionRolledbackException:
org.hibernate.exception.ConstraintViolationException: could not perform
addBatch
...
...
Caused by: java.sql.BatchUpdateException: Batch entry 0 insert into
RHQ_STORAGE_NODE (ADDRESS, CQL_PORT, CTIME, ERROR_MSG,
RESOURCE_OP_HIST_ID, MAINTENANCE_PENDING, MTIME, OPERATION_MODE,
RESOURCE_ID, ID) values ('rhq-test.xxxxxxx.hu
<
http://rhq-test.xxxxxxx.hu>';, 9142, 1384170536686, NULL, NULL, '0',
1384170536686, 'INSTALLED', 10332, 10176) was aborted. Call
getNextException to see the cause.
at
org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2746)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1887)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:405)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2893)
at sun.reflect.GeneratedMethodAccessor123.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.postgresql.ds.jdbc23.AbstractJdbc23PooledConnection$StatementHandler.invoke(AbstractJdbc23PooledConnection.java:453)
at com.sun.proxy.$Proxy106.executeBatch(Unknown Source)
at
org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeBatch(CachedPreparedStatement.java:708)
at
org.jboss.jca.adapters.jdbc.WrappedStatement.executeBatch(WrappedStatement.java:1077)
at
org.hibernate.engine.jdbc.batch.internal.BatchingBatch.performExecution(BatchingBatch.java:110)
rhq=# select * from rhq_storage_node;
id | address | cql_port | operation_mode | ctime
| mtime | error_msg | maintenance_pending | resource_id |
resource_op_hist_id
------+--------------------+----------+----------------+---------------+---------------+-----------+---------------------+-------------+---------------------
1001 | rhq-test.xxxxxx.hu <
http://rhq-test.xxxxxx.hu> | 9142 |
INSTALLED | 1384039582998 | 1384039582998 | | f
| |
(1 row)
Attila
2013/11/10 John Mazzitelli <mazz(a)redhat.com <mailto:mazz@redhat.com>>
> Installation seems OK, but the followings:
> 00:26:26,113 INFO
[org.rhq.enterprise.server.installer.InstallerServiceImpl]
> App server has been successfully asked to reload its configuration
> 00:26:26,155 ERROR [org.jboss.remoting.remote.connection]
JBREM000200: Remote
> connection failed: java.io.IOException: JBREM000202: Abrupt close on
> Remoting connection 38dcf88e to localhost/ 127.0.0.1:6999
<
http://127.0.0.1:6999>
> 00:26:27,253 INFO
[org.rhq.enterprise.server.installer.InstallerServiceImpl]
> Installing RHQ EAR subsystem
That error is not really an error :) Its to be expected. What is
happening is after the installer successfully sends all the remote
commands to the app server to configure it to run RHQ, it asks the
app server to reload its internal components (that is, the app
server internals will do something like a shutdown, reload its
config, and start back up again - thus picking up all changes the
installer did.) Since some of the config changes the installer asked
to make are not hot-loaded at runtime, we have to ask the app server
to essentially recycle its internals so the changes are picked up.
When this happens, the remote connection is disconnected and
sometimes you get that error message (though I can't say I remember
seeing that in my latest builds, but maybe I just haven't looked for
it).
> "rhqctl install" stops everything at the end. It doesn't really
seems to be
> an error, so I have restarted it again
Yes, this "feature" of stopping after the install was something that
people explicitly asked for. We were asked to ensure "install"
doesn't also do a "start" - as apparently, some customers don't
expect an install to leave the software running once the install is
done. So, now, when you install, the components are shutdown at the
end.
If you want to keep the components started after the install, just
pass in "--start" on the command line when doing the install - e.g.
"rhqctl install --start".
_______________________________________________
rhq-users mailing list
rhq-users(a)lists.fedorahosted.org
<mailto:rhq-users@lists.fedorahosted.org>
https://lists.fedorahosted.org/mailman/listinfo/rhq-users
_______________________________________________
rhq-users mailing list
rhq-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-users