Again, errors on update

[Peter-]

Update #33 is available. Install Now -> Click, then I get this:

Execution failed.
Command: autoinstaller
Arguments: Array
(
[0] => --select-product-id
[1] => plesk
[2] => --select-release-current
[3] => --upgrade-installed-components
)

Details:
BUSY: Update operation was locked by another update process.

# service psa restart

Manual install - worked.

 

[abdi]

BUSY: Update operation was locked by another update process.

That means there is already an autoinstaller instance running! You could see by running

ps -A | grep "auto"

 

[Peter-]

Yeah, that's what the error said too. Question is "why?"

 

[abdi]

Could be:

1. You have autoupdates switched on, so at the time of clicking the auto-updates was already running
2. You had earlier clicked the update button, or you were clicking it the second time ...

 

[Peter-]

Hmm

No... autoupdates is off. I clicked on update, indeed, but only saw the first screen with the "continue" button, then clicked on cancel. That should've unlocked it.

 

[abdi]

That should've unlocked it.

It would, you just needed to give it time ..

 

[Peter-]

Ok, anyway.

Side note... to be able to run a cron from a subscription's user, that user needs access to ssh?

 

[abdi]

Not necessarily!

 

[Peter-]

Hmm

I had a cron that refused to work, even though the paths were correct.

cr /var/www/vhosts/blabla/cron.php -> no such file or directory

run the same as root -> working

enable access -> working.

 

[abdi]

Did you use the full path to PHP eg

/usr/bin/php /var/www/vhosts/blabla/cron.php

 

[Peter-]

Yes. Even CD'd, because, for some reason, it has to be in the same folder when running the php script. Otherwise, paths are broken.

cd /var/www/vhosts/zzz.com/httpdocs/cron/ ; /usr/bin/php /var/www/vhosts/zzz.com/httpdocs/cron/apns.php

 

[abdi]

See if this can help:

http://shaun.net/2011/09/solving-plesk-10-3-1-cron-issues/

 

[Peter-]

Okay, thank you.

 

[abdi]

Sure no problem, just let us know if that helped!

 

[Peter-]

From that thread, it looks, indeed, that I was right. Shell execution of script is restricted, unless you grant it.

So either I disable that feature or grant access from admin.