The issue occurs because of a port conflict between the IWSVA HTTP process and the embedded Squid process. To resolve the issue, it is recommended to change the IWSVA HTTP proxy port to another port such as 8080. If this is not possible, do the following workaround:
- Using SSH, log in to the IWSVA console with the root account.
- Create a backup copy of /etc/squid/squid.conf.
- Open squid.conf using vi command.
- Change port 3128 to 3129. It should appear like this:
http_port 3129 transparent
- Back up and then open /usr/iwss/AdminUI/cache_helper.sh.
- Locate the following parameter:
SQUID_CLIENT="/usr/bin/squidclient"
- Change the value to the following:
SQUID_CLIENT="/usr/bin/squidclient -p 3129"
- If you want to ensure that the port will not revert to 3128 in case the content cache feature is disabled and re-enabled, change the HTTP port number from 3128 to 3129 in the following lines:
if [ $RETVAL -eq 0 ]; thenThe values should appear like this:
${RWCONFIG} -ct -f ${SQUID_CONF} -s "http_port" -n "3128 transparent"
else
${RWCONFIG} -at -f ${SQUID_CONF} -n "http_port 3128 transparent"
fiif [ $RETVAL -eq 0 ]; then
${RWCONFIG} -ct -f ${SQUID_CONF} -s "http_port" -n "3129 transparent"
else
${RWCONFIG} -at -f ${SQUID_CONF} -n "http_port 3129 transparent"
fi - Save the changes and then reboot IWSVA.
Note: Implement the workaround again if a future hot fix, patch or service pack replaces /usr/iwss/AdminUI/cache_helper.sh with a new version.