Here are some common problems that people may encounter with Deploy

Drupal 7 notes
ensure that the following modules have been downloaded to both environments (source and destination):

deploy-7.x-2.x-dev
services-7.x-3.x-dev
entity_dependency-7.x-1.x-dev
uuid-7.x-1.x-dev

after this, things may still not work. If not, try:

1) rebuild the deployment plan created on the source server
2) edit the service endpoint and resave it on the destination server

Also, make sure that UUID values are the same for users in both environments. This may manifest itself as the following error found in watchdog:

DeployServiceException: Service error: 404 Not found: Could not find the controller. in DeployServiceRest->httpRequest() (line 74 of /var/www/Sites/example.com/sites/all/modules/contrib/deploy/includes/DeployServiceRest.inc).

since the watchdog message doesn't contain the url of the service requested, its all but impossible to diagnose this. I added (at line 74) a debug message that shows the url and traced mine down to a url that looked like this:

http://example.com/inbound/user/df655d48-437d-461b-a554-7083b0360141.json

good luck!

Drupal 6 notes

  • Deploy does not work with CCK Date fields, unless they are of Date type with select box widgets. For more information, see http://drupal.org/node/374346#comment-1532770.
  • Modules that redirect the user on login (such as Login Tobaggan) will not work with Deploy. See #433102: Deploy fails to login to destination server for more details.
  • Deploy does not support the (soon to be deprecated) upload module which comes with core, however it does support CCK filefields so you may want to consider going that route.
  • If, when enabling the various modules the installation instructions tell you to, some of the Services modules appear to be missing or have different names, make sure you're using Services 6.x-2.x-dev, not Services 6.x-3.x-dev.
  • If, when you attempt to deploy a node, you're asked for an API Key and Domain rather than a Username and Password, go back to admin/build/deploy/servers on the source site, click on the edit link for the server you're trying to deploy to, and make sure the authentication type is set to "Session ID", not "Key authentication".

Comments

DuaelFr’s picture

There is a common error which get me hours to understand and fix

Module : login
Description : Remote user login
Result : Error
Message : -none-

It was caused by a redirection directly on the services url !
Put your server URL in your browser and ensure that you get the XMLRPC answer at the same URL without being redirected !!

Example :
- Server URL : http://www.example.com/services/xmlrpc
- Redirected URL : http://www.example.com/en/services/xmlrpc
- Message : XML-RPC server accepts POST requests only.
In this case you may use the redirected URL as your server URL to get deploy working.

I got this issue caused by the Drupal core "Locale" module in which I had configured a prefix for all my website languages.

Not a man. Empathy buddy & NVC trainee. Ally.

toulon’s picture

Or http://www.example.com/?q=services/xmlrpc if not using clean urls

Your response back should look something like:

XML-RPC server accepts POST requests only.

meetmelife’s picture

Module Description Result Message
node story: test story Error An illegal choice has been detected. Please contact site administer

charly57’s picture

I got the same issue when trying to deploy a node for the first time.
I have no idea of the cause of this problem

spidersilk’s picture

Do you have the file upload module enabled? That can apparently cause that error.

adytmro’s picture

Hy,

When i try to deploy an article i get stuck at
Deployment dependency checking is starting.

From firebug i get this:

Failed to load source for: http://my.site.address/admin/build/deploy/deploy_check_batch which results in 302 (redirect).
and
http://my.site.address/batch?op=start&id=383 which has no response.

Where can it be the problem?

Thanks,

adytmro’s picture

I have found out that i had a problem with jquery version.

I had in my site jquery 1.4.3 and batch operations needed 1.3.2, so i've made a template for batch pages and i only included jquery 1.3.2 in that template.

tannerg’s picture

this was helpful

albertomota’s picture

We’ve been following what other technologies are up to recently regarding deployment and hosting. Heroku, for Ruby on Rails, is clearly an awesome platform that has surely played an important role in getting RoR a wider acceptance. Lately some other clones for different technologies have appeared and, while some of them address PHP based deployments, there’s still no specific solution that handles Drupal the “right” way.

Drupal deploying has been a nightmare for a while, and even though there are a few helpers out there (deploy module, features, …) it’s still pretty tough to deploy, specially if you want to do incremental updates. Drupal as is is great, but could be even greater if there was a platform that made it simple to deploy the solutions in a quick and efficient way, allowing for seamless pushes between development, testing, staging and production environments and for websites to grow without infra-structure constraints.

Being so, we’re set to start working with Drupal community to address this shortcomming and create the first real Drupal platform. Anyone can apply for a Beta Membership at www.jaajaw.com. Would love to hear your opinions on this, your feedback is obviously valuable in getting a platform that addresses this the best possible way. What do you think: is this the way to go?

gdd’s picture

One thing you may want to get involved with is the configuration management initiative for Drupal 8. While we are only focused on the next version for now, we are planning to solve the underlying issues once and for all. For more information on this see

http://groups.drupal.org/node/149769

Otherwise I'm pretty curious how you intend to solve the big problems in your platform. Always love to hear what other people are doing!

namita21’s picture

Done with all the configuration mentioned in Deploy project page and then when trying to push node, the deployment process starts with a blue bar but ends up showing up the error of access denied. Both sites source and destination are on same server.
Configuration:
Deployment 6.x-1.0-alpha2
Drupal 6.22
Services 6.x-2.4

Deployment Log Details:
Module Description Result Message
node page: Testing Deployment module Error Access denied
I have used user#1 login information for deploying node to destination server, do I need to change anything on server?
I have tried disabling upload module .
Source site: http://example1.com, Destination http://example2.com/services/xmlrpc
Also tried to go to http://example2.com/services/xmlrpc and getting message :
XML-RPC server accepts POST requests only.
but none of them working for me, any solutions?

kwinz’s picture

I had a very similar problem, and just solved it. I'm logged in as an administrator, but suddenly I started getting unexpected 403 - access denied errors. I hit this problem with a module that tries to access some nodes as an anonymous user, although it should actually have that permission. But I think this fix probably has a more general application, and should be part of any problem solving checklist for this kind of issue.

I ran a content access / node access permissions rebuld, and it fixed the problem for me. Anyone having this kind of problem - try rebuilding your permissions cache (at /admin/reports/status/rebuild ). I hope this will help somebody.

ramkiboy’s picture

5.Go to admin/build/services/settings. Under 'Authentication module' choose 'Key authentication'. Make sure that 'Use sessid' is clicked and 'Use keys' is not (Deployment does not currently support API keys with Services.) Save the settings.

I am not getting the 'Use sessid' and 'Use keys' boxes.

PrineShazar’s picture

From what i found the 404 controller error was directly related to endpoints being blocked, so it was a configuration issue on my end. This may help someone so i'll post this here. This is for deployment of nodes.

Its important to follow steps in original post in above documentation.

  • Ensure you install and enable dev modules as stated above
  • Ensure UUID for nodes match. So from source to destination, the UUID's for nodes in node table must not be different in both directions
  • On destination server, go to admin/structure/services, click edit on desired endpoint which takes you to Resources
  • I initally only had node CRUD options selected. But nodes i was pushing from source also had taxonomies, files and made use of an authenticated user. So tick file, taxonomy_term, taxnomoy_vocab, user, system then save.
  • Go back to /admin/content, select 1 node to deploy, add to deployment plan then deploy.

This is a general setup, ofcourse you should tweak the Resources for endpoints based on security, policy etc but this should at least get you deploying.

I also found, if on my Source server i change settings for deployment plan (admin/structure/deploy/plans) from Queue API processor to Memory processor or Batch API it worked upon every deploy cycle, whereas the default Queue API processor would be hit or miss.