SQL Server support in future releases
by Steve Bicker
Hello,
I would like to use RHQ with SQL Server as a database backend. I understand
that this is not currently supported. I have also come across this error
since I am trying to use SQL Server 2008 R2:
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=758362 . This
completely prevents me from installing using 2008 R2.
My question is whether there is a timeline for adding official SQL Server
support, or for a fix of the bug referenced above. Specifically I am
wondering if any of this may make it into one of the next releases?
Thanks,
Steve
12 years, 1 month
LDAP broken? Any user allowed in.
by Matt Warren
I'm new to RHQ so please be gentle…
I setup RHQ 4.2 to auth against AD.
Logged in as me, got prompt to enter new info and did.
Now on subsequent login attempts, I can enter ANY password and get access.
This has to be broken, correct? Log snip below. Clearly something is broken in my config but I'd think that any LDAP failure should prevent an access, no?
As well, if I enter ANY username (nonexistent user) it prompts me to create an account.
Is this expected behavior?
-----------------------
2012-02-28 14:22:09,351 WARN [gwt-log] Sending exception to client: [1330456929349]
javax.ejb.EJBException: java.lang.RuntimeException: javax.naming.AuthenticationException: [LDAP: err
or code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece]
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:63)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:83)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:191)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:95)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor
.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101)
12 years, 1 month
Fwd: [ANNOUNCE] Security Update 2012-02-27 released
by Heiko W.Rupp
FYI ..
Anfang der weitergeleiteten E-Mail:
> Von: Selena Deckelmann <selena(a)postgresql.org>
> Datum: 27. Februar 2012 16:51:45 MEZ
> An: pgsql-announce(a)postgresql.org
> Betreff: [ANNOUNCE] Security Update 2012-02-27 released
>
> The PostgreSQL Global Development Group today released security updates for all active branches of the PostgreSQL object-relational database system, including versions 9.1.3, 9.0.7, 8.4.11 and 8.3.18.
>
> Users of pg_dump, users of SSL certificates for validation or users of triggers using SECURITY DEFINER should upgrade their installations immediately. All other database administrators are urged to upgrade your version of PostgreSQL at the next scheduled downtime. More details on the security fixes are included below.
>
> Features affected by bug fixes in this update include: binary replication and hot standby, GIN, WITH, foreign data wrappers, PL/pgsql, PL/python, inet datatype, intarray, pgcrypto, pg_upgrade, pg_restore and pg_dump. Users of these features should apply the updates as soon as possible.
>
> This release contains 45 fixes to version 9.1, and a smaller number of fixes to older versions, including:
>
> * Fix btree index corruption from insertions concurrent with vacuuming
> * Recover from errors occurring during WAL replay of DROP TABLESPACE
> * Fix transient zeroing of shared buffers during WAL replay
> * Fix postmaster to attempt restart after a hot-standby crash
> * Fix corner case in SSI transaction cleanup
> * Update per-column permissions, not only per-table permissions, when changing table owner
> * Fix handling of data-modifying WITH subplans in READ COMMITTED rechecking
> * Fix for "could not find plan for CTE" failures
> * Fix unsupported node type error caused by COLLATE in an INSERT expression
> * Avoid crashing when we have problems deleting table files post-commit
> * Fix recently-introduced memory leak in processing of inet/cidr
> * Fix GIN cost estimation to handle column IN (...) index conditions
> * Fix I/O-conversion-related memory leaks in plpgsql
> * Teach pg_upgrade to handle renaming of plpython's shared library (affecting upgrades to 9.1)
>
> As with other minor releases, users are not required to dump and reload their database or use pg_upgrade in order to apply this update release; you may simply shut down PostgreSQL and update its binaries. Perform post-update steps after the database is restarted.
>
> This update includes three security fixes for the following issues:
>
> * CVE-2012-0866: Permissions on a function called by a trigger are not checked.
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0866
>
> This fix prevents users from defining triggers which execute functions on which the user does not have EXECUTE permission.
>
> CREATE TRIGGER failed to make any permissions check on the trigger function to be called. An unprivileged database user could attach a trigger function to a table they owned and cause it to be called on data of their choosing. Normally, this would execute with the permissions of a table owner, and thus not give additional capability. However, if a trigger function is marked SECURITY DEFINER, privilege escalation is possible.
>
> * CVE-2012-0867: SSL certificate name checks are truncated to 32 characters, allowing connection spoofing under some circumstances.
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0867
>
> This fixes SSL common name truncation, which could allow hijacking of an SSL connection under exceptional circumstances.
>
> When using SSL certificates, both clients and servers can be configured to verify the other's host name against the common name in the certificate it presents. However, the name extracted from the certificate was incorrectly truncated to 32 characters. Normally that just results in a verification failure, but if the actual host name of a machine is exactly 32 characters long, it could, in principle, be spoofed. The risk of this actually happening appears unlikely, and an attacker would still need to take additional steps outside of PostgreSQL to succeed with an exploit.
>
> * CVE-2012-0868: Line breaks in object names can be exploited to execute code when loading a pg_dump file.
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-0868
>
> This fix removes '\n' and '\r' from dumpfile comments.
>
> pg_dump copied object names into comments in a SQL script without sanitizing them. An object name that includes a newline followed by an SQL command would result in a dump script in which the SQL command is exposed for execution. When and if the dump script is reloaded, the command would be executed with the privileges of whoever is running the script - often a superuser.
>
> All supported versions of PostgreSQL are affected.
>
> Download new versions now:
>
> Main download page: http://www.postgresql.org/download/
> Source code: http://www.postgresql.org/ftp/source/
> Binary packages: http://www.postgresql.org/ftp/binary/
> One-click installer, including Windows packages: http://www.enterprisedb.com/products/pgdownload.do
>
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham, Charles Cachera
12 years, 1 month
Avoiding User's Session Timeout
by Herbert de Borba
I've sent this message erroneously to another thread... so I'm creating a
new and sending again.
Hey all,
I'm trying to figure out how to effectively use RHQ's dashboard as a main
view to a wall fixed monitor. I'm interested on showing the "Alerted or
Unavailable Resources" and "Platform Utilization" portlets side by side.
I've configured it like that and have been using a specific read only user
to keep the session (FIGURA1.png).
All works fine, but the issue is that the user session keeps expiring. I
referred to "https://bugzilla.redhat.com/show_bug.cgi?id=RHQ-2082" but the
"refresh interval" is already setted to "1 minute" and this do not prevent
the session expiration, so the annoying user/pass modal window appears
after a while.
Meanwhile, to try to resolve that I built a simple HTML page that
periodically refreshes an iframe which refers to the dashboard's address,
but then I faced other issue: on the majority of refreshes instead of
showing the dashboard content it shows the "Globally Uncaught Exception"
error (FIGURA2.png).
Does someone knows how could one fix this expire session issue? Maybe some
setting on the RHQ server's configuration?
RHQ version: 4.1 on Ubuntu 10.04 LTS
Browser being tested: Firefox 10.0.1 (Windows and Linux, the error after
refresh issue happens on both).
HTML code for iframe:
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="pt-br" lang="pt-br">
<head>
<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-Equiv="Cache-Control" Content="no-cache" />
<meta http-Equiv="Pragma" Content="no-cache" />
<meta http-Equiv="Expires" Content="0" />
<meta http-equiv="refresh" content="30" />
</head>
<body style="margin: 0px;">
<iframe name="myInnerFrame" id="innerframe" src="
http://rhq:7080/coregui/#Dashboards" style="width: 100%; height: 100%">O
Seo Browser da Dona Internet não suporta frames?</iframe>
</body>
</html>
Best regards.
Herbert
--
Herbert Mattei de Borba
herbertdeborba(a)gmail.com
12 years, 2 months
random question on CLI commands
by Deon Lackey
Hey, guys.
The commands that the CLI uses in interactive mode -- exec, quit,
version -- where do those come from? I see the rhq class which has login
and logout, but it doesn't seem to have the others.
Thanks!
Deon
12 years, 2 months
OC Systems RTI v3.3 - JBoss Performance Diagnostics for RHQ
by Steve Sturtevant
Hi Everyone,
I wanted to share the news that OC Systems has announced the release of RTI
v3.3 - http://www.rtiperformance.com/landing-rti-version-33 - which
integrates as an add-on to both RHQ and JBoss Operations Network. RTI
provides deep method-level performance monitoring, and diagnostics for
JBoss, Tomcat and more. A few of the new features we offer as an add-on to
RHQ:
- *Lightweight Business Transaction Profiling* - production performance
monitoring at about 2% overhead
- *Comprehensive performance metrics and charting* - server, JVM, JMX,
and transaction performance metrics
- *Dynamically deep-dive* into problem transactions, trace distributed
transactions across JVMs and platforms
- *Performance Alerting* and snapshots integrated with RHQ's alerting
system.
We put together a short video to highlight the new features, and the
integration points - http://www.rtiperformance.com/landing-rti-version-33.
In order to best move RTI forward to meet the needs of our users, we are
interested in thoughts and enhancement requests from the RHQ community. If
anyone thinks that RTI might be a good fit for use within an existing RHQ
deployment please contact me directly, I would be happy to discuss
exchanging licenses for your feedback and review.
Thanks,
Steve
--
Steve Sturtevant (v) (703) 577-6633
Product Manager, RTI *
Lightweight Performance Monitoring and Diagnostics*
http://www.rtiperformance.com/ <http://www.rtiperformance.com/download/>
12 years, 2 months
Help install rhq on 2 servers ( rhq / db server)
by Ferioli Mirko
Hi,
I've a problem when I try to install RHQ on my servers
I've a server ( 10.0.0.71) where I would install RHQ and a second sever (10.0.0.66 ) where is install the postgresql server db.
During installation, in the start.jsp page, on Database Connection URL I've typed jdbc:postgresql://10.0.0.66:5432/rhq ( The db was created on the server and the server works ) but when I test the connection I've this error:
Org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "10.0.0.71", user "rhqadmin", database "rhq", SSL off
How I can do ?
Thanks
Mirko
La presente comunicazione e ogni suo allegato è destinata esclusivamente al soggetto indicato quale destinatario o ad eventuali altri soggetti autorizzati a riceverla.
Essa contiene informazioni strettamente confidenziali e riservate, la cui comunicazione o diffusione a terzi è proibita, salvo che non sia stata espressamente autorizzata.
Se avete ricevuto questa comunicazione per errore, Vi preghiamo di darne immediata comunicazione al mittente e di cancellarne ogni evidenza dai Vostri supporti.
This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed or his/her authorized representative.
If you are not the original recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error, and that any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited.
If you received this email in error, please immediately notify the sender and delete any evidence on your database.
12 years, 2 months
Using RHQ as base platform for commercial project
by Prashant Shewale
Hi All,
I would like to ask if we can use RHQ framework as base for
commercial project. I would like to design management software for our
enterprise software using RHQ as a base. I know RHQ is licensed as GPL and
so its difficult to sell closed source product. Can you please provide me
some guidelines?
Thanks,
Prashant
12 years, 2 months
Wrong alerts
by Milan Tomic
I wanted to set an alert if tomcat heap memory usage exceeds 75% of
meximum, but I got an alert even for lower values (this is copy/paste from
alert e-mail):
Conditions:
- Condition 1: Heap Usage > 75,0% of Baseline Maximum Value
- Date/Time: 2012/02/01 10:55:11 CET
- Details: 92,9MB
This tomcat has 1GB+ memory assigned. Did I used wrong condition?
Thank you in advance,
Milan
12 years, 2 months