Recent content by Napsty

I just want to follow-up after the Plesk support found the solution. The affected customer has several domains. One of these domains were suspended/disabled. It seems that this domain was somehow the primary domain - therefore the scheduled tasks were added with the ##!PSA!## comment. Peter...

Thank you Peter. I opened a support ticket.

Hello Peter, Appreciate you taking the time. I saw that there is a "dry run" of plesk repair where I was able to see some details. There was one warning which the command seemed to solve: # plesk repair db -y Checking the Plesk database using the native database server tools .. [OK]...

Sorry but before I do anything on a production server and suspend a paying customer (even for just a couple of seconds) please tell me where do you see inconsistencies? As you can see in the mysql output, there are no inconsistencies. Where would I check for these before blindly launching the...

Hi Peter Thanks for your suggestion. The account in question is neither suspended or disabled. So I don't know why Plesk added the ##!PSA!## comment in front of the cron job. According to your advise, I ran the command anyway to tell Plesk that the cron jobs are allowed for this user: #...

Sorry for jumping on the old train (topic) here. Fortunately it's not that old (Oct 2016). I experienced the same problem on a Plesk 12.5 server (12.5.30 Update #57). The tasks scheduled in Plesk appear commented-out in the actual crontab files on the system: # DO NOT EDIT THIS FILE - edit the...

Nevermind. Fixed it. MySQL Server missed the checkbox to be selected as default server for MySQL.

We're trying to migrate a few hundred hosting accounts from a Confixx server to Plesk 12.5 (running on Debian jessie) with the Migrator Extension. However the databases are not migrated. Migrator shows: | `- Client 'web230' | | | `- Subscription 'web230.example.com' | | |...