Sometimes during the course of troubleshooting a support case, one of our support engineers might ask you to obtain system information. This post explains how.
The output of the script should look something like this:
Any errors that occurred will be displayed after this, and if this happens you should contact support to overcome these errors.
This script collects outsystems platform logs, application server logs, some system information (Java version being used, memory, etc), application server configuration and other useful data for troubleshooting problems in a java installation.
* alternatively, run the following commands (if you have internet access):
When we are running collect_stats.sh file, it throwing error "This account is currently not available." and no dump is generated. what could be the reason for this?
Collect_stats.sh execution log..
Gathering JBoss (Process 29787) info...
* CPU statistics
* Thread Stacks
This account is currently not available.
Gathering OutSystems Services info ...
Include JBoss Memory Dump? [n] y
Gathering JBoss (Process 29787) memory dump...
It looks like that your JBoss user is not allowed to login and run the required commands ( a shell is required).
Could you check in your /etc/passwd file if jboss user is being denied to login? e.g.jboss:x:501:501:JBoss user account, created by OutSystems:/home/jboss:/bin/nologin
Granting a shell to jboss user should fix your issue. e.g.
jboss:x:501:501:JBoss user account, created by OutSystems:/home/jboss:/bin/bash
passwd file is showing these two entries, could you please let me know should be done to fix the issue?
jboss:x:185:185:JBoss:/var/lib/jbossas:/sbin/nologinoutsystems:x:500:500:OutSystems Platform account:/home/outsystems:/bin/bash
Ivo Gonçalves wrote:
Updating jboss:x:185:185:JBoss:/var/lib/jbossas:/sbin/nologin to jboss:x:185:185:JBoss:/var/lib/jbossas:/bin/bash should fix your error.
Hello to everyone.
I suggest to update the script, so it works with JBoss EAP, and possibly other scenarios. With the JBoss EAP default installations, the jboss user is set with the /sbin/nologin shell, which makes the su command fail. This is the same issue that was described by Chetan Shettigar.
I simply changed the su commands to ignore the predefined shell, and always use /bin/bash. That is accomplished with the -s flag, as documented on the su man page.
The script is attached. Please review it, and if possible, merge with the official version.