SPE will not start listen any TCP ports after re-installation


Article ID: 170640


Updated On:


Protection Engine for Cloud Services Protection Engine for NAS


After re-installation of SPE, symcscan daemon does start up, but it does not listen on any TCP port.

Typical scenario of this issue is as follows:

1. clean install SPE 7.9
2. uninstall SPE either by yum command or rpm
3. re-install SPE 7.9

There are no error messages yielded neither in uninstallation nor in re-installation.
And issue occurrs in initialazation phase of symcscan daemon, therefore no message is seen in SPE logs.



SPE uninstallation left following files undeleted under bin directory:


  # ll
-rw-rw---- 1 root avdefs 1.3K Dec  5 11:25 Certificate.pem
-rw-rw---- 1 root avdefs 2.2K Dec  5 11:25 keyStore.private
-rw-rw---- 1 root avdefs    0 Dec  5 11:42 keyStore.public

And content stored in keyStore.private retains timestamp of old instatation.
symcscan can not modify it after re-installation and evetually fails in listening.


Symantec recognizes this phenomenon and the issue is now investigated under etrack #4145181.
Resolution shall be implemented in forthcoming release.

Please remove above 3 file after uninstallation as temporary workaround.