You don't need to care for the process_4. is unimportant. The rest looks like start was OK.
Please check the Midtier Configuration /arsys/shared/config/config.jsp. If you have correctly configured the AR Server Setting
You write that you see AR Processes even after stopping but on the screenshot I can only see you started the AR Server. Please try to stop , in case there are still some processes try to restart the server (init 6 (?)).
The log files muss be written. arerror.log and armonitor.log muss contain some output.
these are the first thoughts
When I run top command I see the below image. However, when my client runs top she is able to see the 8 AR related java processes, which is the correct thing to see. Do you have any idea as to why I am seeing different things?
Those 8 java processes mean AR is up.
Sorry for this, but I should had mentioned last time itself. In our dev environement, we have 1 midtier and 2 AR servers.
Also, this is a silly question but where can I download User Tool? You see I have issues while logging in through browser, so I would like to login using User Tool but have no idea where can I download it. Would you please direct me there?
I went through the midtier configuration and am posting redacted screenshots below. Notice that the log file location says "error90" but when I went there, I found that it was last modified in 2017. So did not even bother to open that file. Also, please note that we have not configured the second AR server yet in MT, I found that when I logged in. Whats even more bamboozling is that I can see some logs at the very end in "Log Settings" tab, which appear to be latest - "Displaying the last 25 entries of the log". Where can I find this log file?
Thanks a ton for your timely response.
Hey Edision Sorry you’re having issues!
So the root root of this type of error is typically Apache. Basically what it is saying is it cannot understand the command order! Log4j has xml pattern or order that tags must appear in, and if it doesn’t match then it spits out these error. I typically see this when someone upgrades Apache and/or Java upgrades. Check your path and classpath on your environment, ARS and apache startup to make sure there are not old pointers, first. As it may be super simple. Second is to look at the log4j.xml and make sure it hasn’t been modified (tag order matters); do a compare with your prod server!
Thanks for your quick response.
The second part I can do easily - comparing log4j.xml from my problematic server with a working env log4j.xml file.
However, I need your help with checking path and classpath. I know how it’s done in Windows but in my case we are using Unix.
Do you have any idea on where should I go looking? Or the commands I need?
We use Redhat Enterprise Linux.
I missed putting these points forth in my previous reply.
Actually, the issues I am facing now has become two fold.
1) Not able to log in
2) None of the logs are updated (Except for the one in Log Settings tab of the Mid Tier Configuration home page, apparently - “First 25 entries from the logs”)
May I ask log4j.xml is responsible for which one of the above 2 issues? Or is it responsible for both?
Also, while my logs are not being updated, except for the “First 25 entries from the logs” Part in Log Settings tab of MT configuration home page, may I ask where this part is being updated from? I mean, where are the first 25 latest entries coming from? Just curious to know.
Thanks for extending your assistance
I suspect the problem is on the server side rather than the midtier at this point - your top output shows only one Java process which is what I would expect to see during the server startup process before it is ready to accept logins.
My suggestion would be to stop the server and make sure there are no orphaned processes running. Check with something like
$ ps -ef | grep bmc
which should show you anything running from the /opt/bmc directory tree - if there are Remedy related processes left running kill them. Now backup all of the files in the /opt/bmc/ARSystem/db and empty the directory to get a clean set of logs. Start the server and go get a coffee, it won't be ready to accept logins until you see something like this in the arerror.log and all the other processes started by armonitor are up and running
Thu Mar 21 09:13:51.630 2019 Action Request System Server Started.
Then check you can login using something like Developer Studio to confirm the server is working before making changes to the mid-tier.
>>>When I run top command I see the below image. However, when my client runs top she is able to see the 8 AR related java processes,
what do you mean by "I" and "my client" ?
Did you install ARSystem as root ? do you start ARSystem as root ? or you installed ARSystem as root but you start it as arserver?
What user are you and what user is "my client" ?
Apologies for making things so ambiguous.
my client here simply refers to my female colleague
Yup my greetings to your IT female colleague
But my question is more technical. So what a user/group are you, your colleague? and as which user was arsystem installed and which user is starting arsystem ?
I am not sure using which user the ARS was installed.
However, whenever we want to start or stop the server, we login to a different functional ID using the sudo command. Then we start or stop the AR server.
Does that clarify things?
thanks again for your quick response.
We both use the same functional ID
1 of 1 people found this helpful
ls -al /opt/bmc/ARSystem
all files/directories should have the same user:group on the left. what do you see ?
Let me check that in reply in some time. Am away from my computer right now