# AWX vs Tower same command is failing

**URL:** <https://forum.ansible.com/t/awx-vs-tower-same-command-is-failing/28417>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [August 24, 2018, 6:22pm UTC](https://forum.ansible.com/t/awx-vs-tower-same-command-is-failing/28417 "2018-08-24T18:22:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Larry\_Bakun](https://avatars.discourse-cdn.com/v4/letter/l/41988e/32.png) [@Larry\_Bakun](https://forum.ansible.com/u/Larry_Bakun)\
**Post date:** [August 24, 2018, 6:22pm UTC](https://forum.ansible.com/t/awx-vs-tower-same-command-is-failing/28417/1 "2018-08-24T18:22:52Z")

</div>

I’m running into a strange problem - the same command runs fine in the Tower but is failing in the AWX:

- name: Search user in the Database  
command: \>  
mysql --user=“{{ dbUserName }}” --password=“{{ dbPassword }}” “{{ dbDatabaseName }}” --host=“{{ dbServerIP }}”  
–batch --skip-column-names --execute=“SELECT user\_id FROM users WHERE username=‘{{ tower\_user\_name }}’;”  
register: existing\_user\_id

When I check the “\_raw\_params”, there is an extra backslash character in the values. I’ve tried all kind of options to remove it but wasn’t lucky.

This example from the Tower and it works:  
“\_raw\_params”: “mysql --user="dbAgent" --password="secret" "db\_table" --host="95.25.220.204" --batch --skip-column-names --execute="SELECT user\_id FROM users WHERE username=‘user1’;"”,

This one from the AWX where is failing:  
“\_raw\_params”: “mysql --user=\“dbAgent\” --password=\“secret\” \“db\_table\” --host=\“95.25.220.204\” --batch --skip-column-names --execute=\“SELECT user\_id FROM users WHERE username=‘user1’;\””,

---

<div class="post-metadata">

**Author:** ![Larry\_Bakun](https://avatars.discourse-cdn.com/v4/letter/l/41988e/32.png) [@Larry\_Bakun](https://forum.ansible.com/u/Larry_Bakun)\
**Post date:** [August 24, 2018, 9:46pm UTC](https://forum.ansible.com/t/awx-vs-tower-same-command-is-failing/28417/2 "2018-08-24T21:46:51Z")

</div>

Found my problem. Just in case somebody runs into the same thing:  
The Docker container that comes with AWX didn’t have ‘mysql’ installed. I’ve installed it to the OS itself “yum install mysql” and that was my mistake.  
After installing ‘mysql’ into the Docker container everything works as it should.