- Plesk 12.0 for Linux
- Plesk 12.5 for Windows
- Plesk Onyx for Windows
Plesk upgrade from 12.0 to 12.5 is stuck on "upgrading Spamassassin..." step. The following records are found in
MSI (04): Plesk custom action start 11:16:05: Importing bayes database...
MSI (04): Execute C:\\webservices\\plesk\\admin\\bin\\spammng.exe --import-bayes-db
MSI (04): Output:
MSI (04): Use of uninitialized value $file in concatenation (.) or string at D:/Program Files (x86)/Parallels/Plesk/perl/lib/File/Spec/Win32.pm line 310.
MSI (04): Subroutine Mail::SpamAssassin::Util::WTERMSIG redefined at D:\\Program Files (x86)\\Parallels\\Plesk\\Additional\\SpamAssassin\\\\lib/Mail/SpamAssassin/Util.pm line 93.
The following is shown in Process Monitor if it is filtered to
"C:\\webservices\\plesk\\perl\\bin\\perl.exe" C:\\webservices\\plesk\\Additional\\SpamAssassin\\bin\\psa-spam-filter "--virtual-config-dir=C:\\webservices\\plesk\\Additional\\SpamAssassin\\SpamFilterUserConfigsPath\\%user%@%domain%" "--config-file=C:\\webservices\\plesk\\Additional\\SpamAssassin\\etc\\mail\\spamassassin" "--port=8783"
There are too many mails to be processed by SpamAssassin.
Connect to the server via RDP and make sure that the process is not stuck in Process Monitor:
Find PID of
perl.exeprocess in Task Manager > Details
Filter Process Monitor to track
Make sure that there are new entries written and that process consumes server resources
Alternatively, check the process status in Process Explorer:
perl.exeprocess under a
perl.exeprocess consumes server resources
Hover the mouse pointer to
perl.exeprocess to get more details about what is currently being processed by SpamAssassin.
If process is not stuck, wait until it is completed. If process is stuck, contact Plesk technical support .