Failed Extras Installation - How to recover

416 Posts

Terry Reply #1, 6 years, 11 months ago

I'm setting up a new site on the client's hosting account, Pair Networks. After struggling to get past some permission issues I finally got Modx up and running. I proceeded to install three extras. There were some errors in the messages that scroll past, but since this isn't so unusual, I didn't pay too much attention.

Big mistake.

When I tried to go back to the Modx dashboard I got a 500 error. In the Modx install.config log I found these.

[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/ab9c7d5d8fb0cd14c9b615ff69bbcf3a/0/ to /usr/www/users/xxxxxx/modx/index.php
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/ab9c7d5d8fb0cd14c9b615ff69bbcf3a/1/ to /usr/www/users/xxxxxx/modx/ht.access
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) xPDOVehicle resolver failed: type php (/usr/www/users/xxxxxx/modx/core/packages/core/modContext/ab9c7d5d8fb0cd14c9b615ff69bbcf3a.resolve.core.resolver)
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 88) Could not resolve vehicle for object of class modContext; criteria: Array
(
    [key] => web
)

[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/61274fabfa9b8299843a2df060250654/0/ to /usr/www/users/xxxxxx/modx/manager/assets
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/61274fabfa9b8299843a2df060250654/1/ to /usr/www/users/xxxxxx/modx/manager/controllers
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/61274fabfa9b8299843a2df060250654/2/ to /usr/www/users/xxxxxx/modx/manager/templates
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/61274fabfa9b8299843a2df060250654/3/ to /usr/www/users/xxxxxx/modx/manager/min
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/61274fabfa9b8299843a2df060250654/4/ to /usr/www/users/xxxxxx/modx/manager/ht.access
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) Could not copy /usr/www/users/xxxxxx/modx/core/packages/core/modContext/61274fabfa9b8299843a2df060250654/5/ to /usr/www/users/xxxxxx/modx/manager/index.php
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 227) xPDOVehicle resolver failed: type php (/usr/www/users/xxxxxx/modx/core/packages/core/modContext/61274fabfa9b8299843a2df060250654.resolve.core.resolver)
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdoobjectvehicle.class.php : 88) Could not resolve vehicle for object of class modContext; criteria: Array
(
    [key] => mgr
)

[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /usr/www/users/xxxxxx/modx/core/packages/core/xPDOFileVehicle/40217aff2b50685cc7d90958df78ca16/ to /usr/www/users/xxxxxx/modx/connectors/
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /usr/www/users/xxxxxx/modx/core/packages/core/xPDOFileVehicle/a5a91bd010cc244459de477ea5769987/ to /usr/www/users/xxxxxx/modx/connectors/
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /usr/www/users/xxxxxx/modx/core/packages/core/xPDOFileVehicle/a5c62955373a48695cc04089bb26c4d6/ to /usr/www/users/xxxxxx/modx/connectors/
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdofilevehicle.class.php : 40) Could not install files from /usr/www/users/xxxxxx/modx/core/packages/core/xPDOFileVehicle/6fffb2d95186a85842d9683431fc6066/ to /usr/www/users/xxxxxx/modx/connectors/
[2017-04-23 12:00:25] (ERROR @ /usr/www/users/xxxxxx/modx/core/xpdo/transport/xpdofilevehicle.class.php : 105) xPDOVehicle resolver failed: type php (/usr/www/users/xxxxxx/modx/core/packages/core/xPDOFileVehicle/6fffb2d95186a85842d9683431fc6066.resolve.core.resolver)

I assume, to get the manager back, I need to either remove the incomplete extras or finish them some how.

Is this correct? How do I do this?

Modx 2.5.6

24,544 Posts

BobRay Reply #2, 6 years, 11 months ago

I assume, to get the manager back, I need to either remove the incomplete extras or finish them some how.

Sometimes there's no practical way to do that, though since you have the file list, it's likely that you could just extract the missing files from the transport.zip file and put them in place manually. That will probably solve the problem unless the permissions are such that the files are there but still can't be used.

On the other hand, you may get the Manager back faster if you just disable some things. The most likely culprit is a plugin and you can disable them by going to the modx_site_plugins table in PhpMyAdmin and putting a 1 in the disabled field for the most recently installed plugins (usually, the ones with the highest IDs).

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

416 Posts

Terry Reply #3, 6 years, 11 months ago

First thing I tried was disabling all the plugins. No change.

I wondered if I could just upload those files. I give it a try and report back.

Worst case, I'll just start over. Although I'll still have to sort out the permission issues. Not sure why this is a problem though.

Thanks Bob.

416 Posts

Terry Reply #4, 6 years, 11 months ago

It turns out the errors I reported above are for the initial modx install. All those files were actually present when I checked them.

In the regular error log, there were similar messages for the extras I installed, however in this case, the folders & files were missing. I restored them and the manager reappeared.

However, when I attempt to reinstall the extras, I still get those permission errors.

/usr/www/users/xxxxxx/modx/core/components is not writable and permissions could not be modified.
/usr/www/users/xxxxxx/modx/core/components/upgrademodx is not writable and permissions could not be modified.
/usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs is not writable and permissions could not be modified.
PHP warning: copy(/usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/license.txt): failed to open stream: Permission denied
xPDOCacheManager->copyFile(): Could not copy file /usr/www/users/xxxxxx/modx/core/packages/upgrademodx-1.5.4-pl/modCategory/be2f977a917f560f9e7b33ff2e5ede53/0/upgrademodx/docs/license.txt to /usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/license.txt
Could not copy file /usr/www/users/xxxxxx/modx/core/packages/upgrademodx-1.5.4-pl/modCategory/be2f977a917f560f9e7b33ff2e5ede53/0/upgrademodx/docs/license.txt to /usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/license.txt; could not create directory.
PHP warning: copy(/usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/changelog.txt): failed to open stream: Permission denied

I changed the folder and file permissions to 0755, tried again, no change. I even tried 0777, no change.

Also the manager extra page has these warning at the top

Warning!

Your assets/ directory was not able to be created at: /usr/www/users/astinc/modx/assets/ 
You will need to create this directory and make it writable if you want to use Package Management or 3rd-Party Components.
,
Your core/components/ directory was not able to be created at: /usr/www/users/astinc/modx/core/components/ 
You will need to create this directory and make it writable if you want to use Package Management or 3rd-Party Components.

These folders are present and have 0777 permission.

I'm also unable to manually clear the cache with Fireftp. Again, permission denied. Clearing the cache in the Modx manager seems to work as usual.

Might this be an ownership issue? If it is, how do I fix this?

416 Posts

Terry Reply #5, 6 years, 11 months ago

I'm not sure how/why, but my last response got posted out of order. So here it is again.

It turns out the errors I reported above are for the initial modx install. All those files were actually present when I checked them.

In the regular error log, there were similar messages for the extras I installed, however in this case, the folders & files were missing. I restored them and the manager reappeared.

However, when I attempt to reinstall the extras, I still get those permission errors.

/usr/www/users/xxxxxx/modx/core/components is not writable and permissions could not be modified.
/usr/www/users/xxxxxx/modx/core/components/upgrademodx is not writable and permissions could not be modified.
/usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs is not writable and permissions could not be modified.
PHP warning: copy(/usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/license.txt): failed to open stream: Permission denied
xPDOCacheManager->copyFile(): Could not copy file /usr/www/users/xxxxxx/modx/core/packages/upgrademodx-1.5.4-pl/modCategory/be2f977a917f560f9e7b33ff2e5ede53/0/upgrademodx/docs/license.txt to /usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/license.txt
Could not copy file /usr/www/users/xxxxxx/modx/core/packages/upgrademodx-1.5.4-pl/modCategory/be2f977a917f560f9e7b33ff2e5ede53/0/upgrademodx/docs/license.txt to /usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/license.txt; could not create directory.
PHP warning: copy(/usr/www/users/xxxxxx/modx/core/components/upgrademodx/docs/changelog.txt): failed to open stream: Permission denied

I changed the folder and file permissions to 0755, tried again, no change. I even tried 0777, no change.

Also the manager extra page has these warning at the top

Warning!
 
Your assets/ directory was not able to be created at: /usr/www/users/astinc/modx/assets/ 
You will need to create this directory and make it writable if you want to use Package Management or 3rd-Party Components.
,
Your core/components/ directory was not able to be created at: /usr/www/users/astinc/modx/core/components/ 
You will need to create this directory and make it writable if you want to use Package Management or 3rd-Party Components.

These folders are present and have 0777 permission.

I'm also unable to manually clear the cache with Fireftp. Again, permission denied. Clearing the cache in the Modx manager seems to work as usual.

Might this be an ownership issue? If it is, how do I fix this?

416 Posts

Terry Reply #6, 6 years, 11 months ago

This is resolved. It was in fact an php ownership problem.

24,544 Posts

BobRay Reply #7, 6 years, 11 months ago

I'm glad you got it sorted.

I'd recommend setting the folders back to 755.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting