Weblogic em console shows "status pending" for the admin servers and managed servers, even though when they are up. It is not showing other metrics as well.
Below are the head error messages.
oracle.sysman.emas.sdk.model.metric.MetricsUnavailableException
at oracle.sysman.emas.sdk.model.metric.WLMetricProvider.getMetricServiceMBean(WLMetricProvider.java:313)
at oracle.sysman.emas.sdk.model.metric.WLMetricProvider.queryMetricTable(WLMetricProvider.java:364)
at oracle.sysman.emas.sdk.model.metric.WLMetricProvider.getMetrics(WLMetricProvider.java:155)
at oracle.sysman.emas.sdk.model.metric.MetricUtil.getMetrics(MetricUtil.java:271)
I would suggest opening a ticket with Oracle. You could try enabling Platform MBean Server which is in Domain home -> Advanced and restarting the domain. Usually this would fix it but without logs, its very hard to tell. Please try to provide us the sysman logs for the em.
I found the solution for this issue. This is a bug and oracle has released a patch for this BUG_13826887/Patch p13826887_111160_Generic.
1.Set ORACLE_HOME, java
2.check which opatch, opatch apply
3.restart complete weblogic
Related
I am behind an enterprise firewall, have checked "Auto-detect proxy settings" in System Settings -> HTTP Proxy. I entered the correct credentials and checked "Remember". I know the credentials are correct, as I am able, for example, to download and install plugins.
However, IntelliJ keeps asking me periodically to re-enter the proxy credentials. Why?
For me the solution was changing proxy setting to "No Proxy" from "Auto-detect".
Idea retrieves proxy settings anyway from Windows.
Version:2019.3
Raising a case they said the SSL certificate gets replaced via the proxy.
I was baffled as it works for some people and not others. People sitting next to each other!
Essentially the proxy gets in the way (from all non-JDK reports) and this is why you can't see the Last Seen dates in the site for all licensees.
The KB: https://intellij-support.jetbrains.com/hc/en-us/articles/206544889-SignatureException-Signature-doesn-t-match-or-Signature-length-not-correct-got-256-but-was-expecting-512
Solution:
The only alternative is to use the Offline Activation codes for each user who will need to login to https://JetBrains.com and get their individual Offline Activation code. Then activate the software offline. Help Menu > Register.
SQ 5.6, LDAP plugin 2.0.
I've successfully installed the LDAP plugin and restarted the SQ server. In the log (/opt/sonar/logs/sonar.log) the plugin is apparently deployed, but seemingly no attempt is made to initialize/enable it or connect to the LDAP server.
INFO web[o.s.s.p.ServerPluginRepository] Deploy plugin LDAP / 2.0 / 2910f3981167a70a201ccfae01471dfd26c794b7
.
.
INFO web[o.s.s.p.RailsAppsDeployer] Deploying app: ldap
These are the only mentions of ldap/LDAP in the log.
Relevant part of the conf/sonar.properties file:
sonar.security.realm=LDAP
ldap.url=ldap://myldap:389
ldap.user.baseDn=ou=mycompany,ou=People,dc=myurl,dc=com
I believe I've verified ldap.url and ldap.user.baseDn via JXplorer (an LDAP browser).
What really puzzles me is that I don't see anything like the following in the logs, which is what I'd expect from the SQ docs:
INFO org.sonar.INFO Security realm: LDAP ...
INFO o.s.p.l.LdapContextFactory Test LDAP connection: OK
No errors of any kind are noted in the log.
Any idea why SQ is not even apparently trying to kick off LDAP authentication on a restart?
I had the same problem. I'm running Sonarqube using docker. It did not pick up on changes when I restart the server from the Sonarqube UI. Only after restarting the docker image it could pick up the changed file.
Well, now it just started working. I don't have an answer as to why though. Maybe something changed with my LDAP server, or there was some latency that needed to be overcome. I didn't change anything on my end that I'm aware of. In any case, thanks to those that responded.
After countless hours of trial end error I finally figured out how to get cassandra 1.2 and usergrid 1.x up and running and talking to each other. "cassandraAvailable" : true, the keyspace has been created (by calling /system/database/setup and /system/superuser/setup). Then I installed Portal end see the login screen, but neither my sysadmin nor my test account, which I configured in usergrid-default.properties are accepted. Also I can not register a new user. It says "Error registering:" and nothing else.
Where can I look for error logging? What do I have to set to get Usergrid Portal working?
Thanks for your help!
First, make sure you are using the correct URL to log into the portal, you will need to repeat the host twice so the portal knows what Usergrid instance you want to interact with.
http://[host]:8080/usergrid-portal/?api_url=http://[host]:8080
If you are running on Tomcat (make sure you are using Tomcat 7 for Usergrid 1.x) then you can look at the Tomcat logs for Usergrid issues.
I'm using ActiveMQ 5.10 and would like to create a user that has read-only access through the web console.
Red Hat published this article, mentioning that it's not really read only due to a bug in ActiveMQ.
According to the bug report AMQ-4567, the bug is fixed as of ActiveMQ 5.9. However, I'm not seeing it work appropriately.
I have tried a number of different configurations, with the most recent being two separate JAAS implementations, one for Jetty and one for ActiveMQ. The relevant property files are excerpted below.
I can mostly log in to the web console using the "system" user. But the guest user doesn't work at all. The application user (appuser) doesn't need access to the web console at all.
My authN/authZ needs are pretty trivial: one admin user, one application account, and one read-only monitoring account.
Is there any good way to get this working with a recent version of ActiveMQ (>= 5.9.0)?
groups.properties
admins=system
users=appuser,admin
guests=guest
users.properties
system={password redacted}
appuser=appuser
guest=guest
jetty-realm.properties
system: MD5:46cf1b5451345f5176cd70713e0c9e07,user,admin
guest: guest,guest
As an aside, I used the Jetty tutorial and the Rundeck instructions to figure out the jetty-realm.properties file and chapter 6 of ActiveMQ in Action to work out the ActiveMQ JAAS.
I was finally able to get to what I wanted by deploying the web console to an external Tomcat instance. I assume that when it runs out of process, it can't bypass security and so has to use whatever credentials you provide. In this case, I gave the Tomcat instance the read-only JMX user credentials.
It's not great, as there is no security trimmed UI. You can still attempt to create new destinations, delete destinations, etc. When you try with a read-only user, you get an error. That gets a "D" for UX, but a "B" for security.
so on the left hand side of weblogic console panel...there are 5 different health status of the servers. I see weblogic change them status to warning whenever there is a stuck thread. However, when one does in wlst script.
connection(name,pass,url)
serverRuntime()
get('HealthState') the server health returns Health_Ok even though on the panel on the left hand side the health status is warning.
Any tips are appreciated
I tried serverLifeCycleRuntimes() by the way. I googled every website regarding Weblogic and not being able to figure out. Thanks
Well I kinda figure it out. It has subsystems. What I do is I cd into JDBC, check the health, then cd into ThreadPool check the health. When the server changes to overload? I do not know