# Problems starting ipsec with v1.2.2

**URL:** <https://forums.suse.com/t/problems-starting-ipsec-with-v1-2-2/5026>\
**Category:** Rancher 1.x\
**Created:** [December 28, 2016, 6:12pm UTC](https://forums.suse.com/t/problems-starting-ipsec-with-v1-2-2/5026 "2016-12-28T18:12:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![RooSoft](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/roosoft/32/1981_2.png) [@RooSoft](https://forums.suse.com/u/RooSoft)\
**Post date:** [December 28, 2016, 6:12pm UTC](https://forums.suse.com/t/problems-starting-ipsec-with-v1-2-2/5026/1 "2016-12-28T18:12:09Z")

</div>

Since I updated to Rancher 1.2.x, I’ve got problems with the ipsec-ipsec-1 container in the infrastructure services… seems like it cannot start.

Watching the rancher logs, I’ve noticed that it’s looping constantly with those messages:

6-12-28T18:01:48Z 0s c24a7bce INFO ipsec/ipsec(1s19) 1i63 service.instance.start: Starting stopped instance  
2016-12-28T18:01:48Z 0s c24a7bce INFO ipsec/ipsec(1s19) - [service.trigger.info](http://service.trigger.info): Created: 1, Unhealthy: 0, Bad: 0, Incomplete: 0  
2016-12-28T18:01:50Z ? 6efb7d51 INFO ipsec/ipsec(1s19) - service.trigger.wait: Waiting for instances to start  
2016-12-28T18:01:50Z ? 6efb7d51 INFO ipsec/ipsec(1s19) - service.trigger: Re-evaluating state  
2016-12-28T18:01:50Z 0s 6efb7d51 INFO ipsec/ipsec(1s19) - [service.trigger.info](http://service.trigger.info): Created: 1, Unhealthy: 0, Bad: 0, Incomplete: 0  
2016-12-28T18:01:48Z 2s c24a7bce INFO ipsec/ipsec(1s19) - service.trigger.wait: Waiting for instances to start  
2016-12-28T18:01:48Z 2s c24a7bce INFO ipsec/ipsec(1s19) - service.trigger: Re-evaluating state  
2016-12-28T18:01:50Z 0s c24a7bce INFO ipsec/ipsec(1s19) - [service.trigger.info](http://service.trigger.info): Service reconciled: Created: 1, Unhealthy: 0, Bad: 0, Incomplete: 0  
2016-12-28T18:01:51Z 0s 6efb7d51 ERROR ipsec/ipsec(1s19) 1i63 service.trigger.exception: Expected state running but got stopped  
2016-12-28T18:01:51Z 0s 6efb7d51 ERROR ipsec/ipsec(1s19) 1i63 service.trigger.wait.exception: Expected state running but got stopped  
2016-12-28T18:01:50Z 1s 6efb7d51 INFO ipsec/ipsec(1s19) - service.trigger.wait: Waiting for instances to start

The underlying is a Ubuntu 16.04.1 LTS with almost 6GB of memory, 24GB of storage, running docker 1.12.3 with a Linux kernel 4.4.

Do I have to install something specific to make it work?

By the way, I have similar problems with other infrastructure services such as Rancher EBS…

---

<div class="post-metadata">

**Author:** ![RooSoft](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/roosoft/32/1981_2.png) [@RooSoft](https://forums.suse.com/u/RooSoft)\
**Post date:** [December 28, 2016, 6:35pm UTC](https://forums.suse.com/t/problems-starting-ipsec-with-v1-2-2/5026/2 "2016-12-28T18:35:15Z")

</div>

Seems related to [https://github.com/rancher/rancher/issues/6897](https://github.com/rancher/rancher/issues/6897)