# change in service module 1.1 -\> 1.2 for Solaris 10

**URL:** <https://forum.ansible.com/t/change-in-service-module-1-1-1-2-for-solaris-10/12752>\
**Category:** Ansible Project\
**Created:** [May 2, 2013, 11:27am UTC](https://forum.ansible.com/t/change-in-service-module-1-1-1-2-for-solaris-10/12752 "2013-05-02T11:27:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Serge\_van\_Ginderacht](https://avatars.discourse-cdn.com/v4/letter/s/b782af/32.png) [@Serge\_van\_Ginderacht](https://forum.ansible.com/u/Serge_van_Ginderacht)\
**Post date:** [May 2, 2013, 11:27am UTC](https://forum.ansible.com/t/change-in-service-module-1-1-1-2-for-solaris-10/12752/1 "2013-05-02T11:27:39Z")

</div>

Something changed in the service module, when run on Solaris (v10):

with ansible 1.1, OK:

{“changed”: true, “item”: “”, “name”: “svc:/application/tomcat-6035-01:default”, “state”: “started”}

with ansible 1.2, error:

{“failed”: true, “item”: “”}  
msg: svcs: Pattern ‘svc:/application/tomcat-6.0.35-01:default’ doesn’t match any instances

The relevant task is noted as:

service name=‘svc:/application/tomcat-${tomcat\_version}:default’ pattern=‘/usr/jdk/latest/bin/java -Dnop -server’ state=stopped

where tomcat\_version = 6.0.35-01

Not sure if this is a bug or me using a corner case.

Serge

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [May 2, 2013, 12:05pm UTC](https://forum.ansible.com/t/change-in-service-module-1-1-1-2-for-solaris-10/12752/2 "2013-05-02T12:05:39Z")

</div>

No idea.

I would recommend debugging the module locally with the “./hacking/test-module” script to find out what is up.