When we are trying to access the Security Director UI, you will find the error "The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later." if the Slipstream and Redis services are not running. This article explains the scenario where the Security Director's UI services were not running due to the permission issuee
You will find the below error while checking the service logs using the command "journalctl -u slipstream"
Nov 24 10:31:45 space-0050569a4bb8 runuser[2546]: pam_unix(runuser:session): session opened for user slipstream by (uid=0)
Nov 24 10:31:45 space-0050569a4bb8 slipstream[2270]: Starting slipstream-server: bash: /var/log/slipstream/slipstream-server.log: Permission denied
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: info: Forever processing file: /usr/local/slipstream/app.js
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: fs.js:652
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: ^
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: Error: EACCES: permission denied, open '/var/log/slipstream/slipstream-server.log'
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: at Object.fs.openSync (fs.js:652:18)
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: at Object.forever.startDaemon (/usr/local/slipstream/node_modules/forever/lib/forever.js:460:14)
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: at /usr/local/slipstream/node_modules/forever/lib/forever/cli.js:269:13
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: at /usr/local/slipstream/node_modules/forever/lib/forever/cli.js:156:5
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: at /usr/local/slipstream/node_modules/forever/lib/forever.js:409:24
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: at FSReqWrap.oncomplete (fs.js:153:5)
Nov 24 10:31:46 space-0050569a4bb8 runuser[2546]: pam_unix(runuser:session): session closed for user slipstream
Nov 24 10:31:46 space-0050569a4bb8 slipstream[2270]: [FAILED]
Nov 24 10:31:46 space-0050569a4bb8 systemd[1]: slipstream.service: control process exited, code=exited status=1
Nov 24 10:31:46 space-0050569a4bb8 systemd[1]: Failed to start SYSV: Starts and stops the slipstream daemon..
Nov 24 10:31:46 space-0050569a4bb8 systemd[1]: Unit slipstream.service entered failed state.
Nov 24 10:31:46 space-0050569a4bb8 systemd[1]: slipstream.service failed.
As per the error, there is no permission to open the file "/var/log/slipstream/slipstream-server.log". However the file has required ownership and permission.
To fix the issue, please change the SS_USER in the /etc/init.d/slipstream file from slipstream to root.
Before : SS_USER=slipstream
Change to: SS_USER=root
After that restart the slipstream service using the below command:
systemctl restart slipstream