We decided to comment-out the configuration item "#server-name = ....." in stead, because is near the top of the config.file and it will register clearly as faulty in the msg__webseald-INSTANCE.log. (after deploy and restart)
"36 2024-06-26-08:43:30.646+02:00I----- 0x1354A09C webseald ERROR ivc general cfgfile.cpp 120 0x7fa8f7821e80 -- HPDCO0156E Configuration item missing (server, server-name). "
------------------------------
Frank Koster
------------------------------
Original Message:
Sent: Tue June 25, 2024 06:45 PM
From: Scott Exton
Subject: Prevent a stopped instance to automatic restart after reboot
Frank,
Unfortunately there is no 'nice' way to do this. As you already mentioned, the only way to do this is to temporarily modify the configuration so that WebSEAL fails to start. There are many configuration items which will stop WebSEAL from starting. One such example would be set to '[server] https = no' (you would also need to set '[server] http = no'.
I hope that this helps.
Scott A. Exton
Senior Software Engineer
Chief Programmer - IBM Security Verify Access
IBM Master Inventor
Original Message:
Sent: 6/25/2024 12:47:00 PM
From: Frank Koster
Subject: Prevent a stopped instance to automatic restart after reboot
Sometime we need to have only 1 instance active in our cluster for development purposes and troubleshooting logs.
We are looking for a way to disable the reverse proxy instance in a way it stays disabled (state = stopped) after a restart.
The issue is that upon a scheduled or instant reboot often it is unclear which instances were intentionally stopped prior to the restart.
I thought I once saw a workaround mentioning to temporary alter a config item so it will not restart properly.
------------------------------
Frank Koster
------------------------------