Share all details related to your problem, including any error messages you may have received.
Q1.I want to restart one of my server as the c drive is full. what measures do i need to take to ensure smooth process. Also what i can do so that tasks won’t be running on the server for sometime?
Q2. All the server using in sailpoint prod are using obsolete java and they need to be updated. what action needs to be taken on that as well?
Please help me on the above 2 questions. waiting for your reply.
We categorize the servers to UI and Task servers and we maintain 2 each.
Do not restart all servers in a single go, Do one by one.
If it is UI server, not a problem. But if it is Task Server, make sure that no Task is running while you go for restart. We do have scheduled Tasks rite, don’t restart at that time.
When you go for one Task server restart, the other one will take care of the requests.
Same goes for UI as well, one will go for restart and the other one will be available for user requests.
Go for restart after office hours if this is not a urgent need.
Same goes for Java update as well, do it in one server in Non-PROD first, do a sanity test. Post that, you can do the for PROD servers one by one.
As Krishna already mentioned: Make sure there is no running task (you can ignore Perform Maintenance, this task recovers without issue when being stopped/killed/cancelled). All remaining internal processes demonstrate resilience.
Amit,
I don’t understand your concerns. When you talk about restarts, you should distinguish between restarting the entire server (VM, iron) vs restarting Tomcat. If you have a full drive, you have more important problems to deal with than what tasks might restart. You need to fix the source of the issue.
Let’s start with your deployment. Best practice is to install tomcat using a process that just unzips the tomcat zip file (you have already disclosed you are running on Windows) into a folder on a drive OTHER than the C drive. This would be a D or E drive. I prefer to just unzip the 4th file in the downloads area - the 64 bit windows Zip - into the D drive so it creates a folder D:\apache-tomcat-9.0.xx (whatever version is current). I never recommend using the msi installer as it creates everything in the C:\Program Files folder and that’s not the best way to install Tomcat.
Once you have your tomcat installed properly you need to make sure you manage your log files and temp files properly. In reasonable intervals, after stopping tomcat, I like to delete the contents of tomcat’s temp folder and delete files in the logs folder that are older than 10 days or so. That’s just for tomcat logging. For SailPoint logging you should be using a RollingFile appender and sending the logs to a separate folder like D:\Logs so that the SailPoint logs don’t pollute the tomcat logs folder. Using rolling logs is best and never use a date field or the gz options for that. Just use something like D:\Logs\sailpoint.log and D:\Logs\sailpoint-%i.log
Hope this helps. The only concern with stopping tomcat or restarting a server is that any active tasks will die, which is not a concern most of the time. They will restart on their own. The only time I do anything to prevent tasks from starting (by just advancing the next start time in TaskSchedule) is when I am doing an upgrade and I don’t want tasks to all of a sudden start when I am pulling up a freshly upgraded system.
As far as Java goes, install JDK 11 or 17 and change JAVA_HOME. There’s a special setting for JDK 17 in the install guide that really is only for the LDAP connector, and you’ll need to upgrade the SSB if you go to 17. I like the Adopt OpenJDK 11 myself.