Search results

That's what the support replied: I have found the following errors coming to the log: # less /var/log/sw-cp-server/error_log System error 2: No such file or directory /opt/psa/admin/bin/drwebmng[8045]: Unable to get string from file: /opt/psa/handlers/info/20-drweb-zxtL7O/hook...

I escalated this issue to Parallels. Currently there's someone from Parallels logged into one of our server and running "mchk --with-spam". Maybe you try this, too. root pts/0 support.sw-soft. 01:27 4:31m 1.98s 0.00s /bin/sh /usr/local/psa/admin/sbin/mchk --with-spam I'll tell...

Sorry, I mixed up threads. The mchk command did not work for me here, either. I just helped when nobody could send/receive emails because some files were missing… The problem persists for me, too. And I tried doing it from CLI: plesk:/opt/psa/bin# ./mail --remove [email protected]...

Try running psa/admin/sbin/mchk – this worked for me. Don't worry… this script may run a long time (it tooks 3 hours on my DELL PowerEdge R200, Quad Core Xeon 3GHz, 8GB RAM). Maybe run it from a `screen` session so that you can get back to it later for checking its progress.

The same issue here. Just right after the upgrade vom 9.2.0 to 9.2.2

Hi, I would like to loose a few words, again. What I'm going to tell is proven bei reality – we administer round about 40 servers with Plesk installed. 1. Plesk has no real Postfix integration. It's a bluff package. Pure marketing. Believe it and stay with qmail. If already switched to...

On Linux traffic accounting isn't working at all after the upgrade… so good luck. I fear that we will have to wait another year for Parallels releasing an update which fixes this issue ;-)

Hi, check you logfiles to determine the entry point. This behaviour is mostly originated in hacked FTP accounts – so have a look at you xferlogs to determine the account. If you cannot find anything there this could have been caused by injection & co. – maybe some kind of script-based...

The same problem here – this was working properly before the upgrade to 9.2.1 a few days ago. I guess it's just one more bug that was introduced by the update…

Better use Spamdyke instead. It's the same with Greylisting as it was Postfix (which is still does not work reliably after more than 12 month after release): It's a bluff package from Parallels to catch some more customers. It's just a bad implementation for the sake of marketing.

Hi, I switched back to qmail and setup Spamdyke to fight spam. I'm sorry to say… but I don't think that Parallels even know what they do, sometimes (or most of the time). Just have a look at the changelog for 9.2.1 – there were bugs fixed that should never even have been introduced by...

The same issue here – but upgrading from 9.0.1 to 9.2.1 on Debian Etch AMD64 with qmail. Unpacking replacement psa-courier-imap ... Preparing to replace psa-qmail 1:1.03-debian4.0.build90090127.18 (using .../psa-qmail_1%3a1.03-debian4.0.build92090422.13_amd64.deb) ... Checking for the...

And… if you disable "Applications" or do not even have a license for this feature… it is shown up in the navigation anyway.

The most important advantage of using fcgi is in my opinion handling many requests in combination with Apache MPM Worker (Threaded). But due to the misconception it is reduced to some security benefits (which would have been also possible through some other patterns than the involved suexec one...

My previous post where I suggested informing some guys from a german IT magazine was killed by censorship. Maybe we should get it up in the blogosphere then, instead?

Maybe someone should give c't (Heise) a hint to read this thread. It would not be the first time that publicity acts as a motivation for managers to get off their seats

Full ACK – and last but not least it shows that the Parallels Platinum Support is completely worthless

Hi, we've switched to qmail by using the auto installer. This solved the problem. Maintaining the postfix course was beyond the pale after contacting the platinum reseller support (through United Internet AG) 3 times within 2 weeks without having the problem solved. It seems that...

Same here. The hotfix did not solve the problem. I tried it on 7 machines (Debian 4.0, Linux 2.6.18-6-amd64 , Plesk 9.0.1). Actually 11 of our machines are affected by this annoying issue.

It's done. Adjust configuration and run with proper rights via cron to retrieve all information for setting up a secondary dns (slave) with Bind: #!/usr/bin/env ruby require 'rubygems' require 'net/https' require 'builder' require 'rexml/document' require 'idn' require 'erb' require...