Gateway failes to start due to read only issue with tmp directory
Article ID: 109929
Updated On:
Products
STARTER PACK-7
CA Rapid App Security
CA API Gateway
Issue/Introduction
The below error is seen in sspc_0_0.log:
Error while starting ssg service on appliance. Starting Gateway Services: mktemp: failed to create file via template `/tmp/sspcd.pid.XXXX': Read-only file system chown: cannot access `': No such file or directory /opt/SecureSpan/Controller/bin/processcontroller.sh: line 92: : No such file or directory Error starting Process Controller.
Permissions are correct for /tmp folder.
[[email protected] /]# ls -alrt | grep tmp
drwxrwxrwt 16 root root 4096 May 26 04:46 tmp
Error while starting ssg service on appliance. Starting Gateway Services: mktemp: failed to create file via template `/tmp/sspcd.pid.XXXX': Read-only file system chown: cannot access `': No such file or directory /opt/SecureSpan/Controller/bin/processcontroller.sh: line 92: : No such file or directory Error starting Process Controller.
Permissions are correct for /tmp folder.
[[email protected] /]# ls -alrt | grep tmp
drwxrwxrwt 16 root root 4096 May 26 04:46 tmp
Cause
This can be caused by a potential inconsistency in the file system
Environment
Found in API Gateway 9.2 CR06 but can exist in any build as this is an OS issue.
Resolution
Execute fsck and reboot the server.
[[email protected] ~]# fsck /dev/mapper/vg00-lv_tmp -y
The output should reveal that this volume contains errors. If not then this is not the root cause.
[[email protected] ~]# fsck /dev/mapper/vg00-lv_tmp -y
The output should reveal that this volume contains errors. If not then this is not the root cause.
Feedback
Yes
No
Powered by
