run parts sh not found

[Wikibear]

Today i get an email with this:


/bin/sh: 1: /usr/local/psa/bin/run-parts.sh: not found

Yes, its missing via terminal check. How can i get it back?

Using Ubuntu 14.04 TLS with newews Plesk 12 18 and fresh installation from yesterday.

 

[IgorG]

Hmm... As far as I remember this file /usr/local/psa/bin/run-parts.sh used for a long time ago in very old 7.5 and 8.x Plesk versions.

 

[Wikibear]

There was never installed any old version on this server.

 

[IgorG]

You can try to grep this run-parts.sh in files from /etc and remove mention in found files.

 

[Wikibear]

I dont find this file. I have two server with same config. I don't find this on both.

/etc/psa/plesk-cron.daily

Send this mail with this error.

 

[IgorG]

Are you sure that you have Ubuntu but not OpenSUSE? These files are usual for OpenSUSE Plesk installations.

 

[Wikibear]

Yes totally sure. But i started a migration with Plesk internal migration script from OpenSUsE Plesk to Ubuntu Plesk. Maybe the error occure from migration script?

 

[Wikibear]

So again i get this mail today:

Cron <root@noreply> /usr/local/psa/bin/run-parts.sh /etc/psa/plesk-cron.daily

/bin/sh: 1: /usr/local/psa/bin/run-parts.sh: not found

 

[IgorG]

I can only recommend to create a request to support team to do in-depth investigation to find the reason and to fix it. Please create a ticket to support at https://www.odin.com/support/request/ .
You may have free support, please check what kind of Plesk license you use for available support options at http://kb.odin.com/en/121580 .
If there’s no free support in your case, you can order Plesk per-incident support at http://www.odin.com/support/buy-support/ Support team will contact you as soon as purchase is processed, and they will do the best to resolve it.
If it is found that your problem was caused by product bug w/o available solution or workaround from Odin, then your purchase will be re-funded.

 

[Wikibear]

Found the error i think!

After migration, all scheduled task for root was imported into the new system, too. Yes there is no dealy monthly and weekly under Ubuntu on my other system that why i get a mail with this error.

Thats interesting, 'cause the other system was migrate from Suse System, too.

Problem is solved i think.