[ICN-287] criproxy failed to start after host reboot Created: 03/Mar/20 Updated: 31/May/22 Resolved: 31/May/22 |
|
| Status: | Done |
| Project: | Integrated Cloud Native NFV |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Cheng Li | Assignee: | Kuralamudhan Ramakrishnan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
After host reboot, the criproxy failed to start. /var/log/syslog shows the following error msg.
Based on the default vars, the criproxy is installed into /tmp directory which refreshes after reboot. So I think we can fix the issue by specify a persistent directory instead of using the default /tmp |