# kURL: Diagnosing ip\_forward being disabled

**URL:** <https://community.replicated.com/t/kurl-diagnosing-ip-forward-being-disabled/580>\
**Category:** Troubleshooting\
**Tags:** kurl\
**Created:** [September 27, 2021, 3:57pm UTC](https://community.replicated.com/t/kurl-diagnosing-ip-forward-being-disabled/580 "2021-09-27T15:57:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![AJ-Jester](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/aj-jester/32/94_2.png) [@AJ-Jester](https://community.replicated.com/u/AJ-Jester)\
**Post date:** [September 27, 2021, 3:57pm UTC](https://community.replicated.com/t/kurl-diagnosing-ip-forward-being-disabled/580/1 "2021-09-27T15:57:52Z")

</div>

Hello,

I have a VM that has a couple of errors while doing the upgrade:

```auto
Error from server (BadRequest): container "kotsadm" in pod "kotsadm-0" is waiting to start: PodInitializing

```

or

```auto
Error from server (BadRequest): container "restore-db" in pod "kotsadm-57bd644c6f-f2ngx" is waiting to start: PodInitializing

```

Also, in coredns logs I see the following errors

```auto
failed to connect to postgres: failed to connect to postgres: failed to connect to `host=kotsadm-postgres user=kotsadm database=kotsadm`: hostname resolving error (lookup kotsadm-postgres on 10.100.0.10:53: dial udp 10.100.0.10:53: i/o timeout)
Error: failed to connect to postgres: failed to connect to postgres: failed to connect to `host=kotsadm-postgres user=kotsadm database=kotsadm`: hostname resolving error (lookup kotsadm-postgres on 10.100.0.10:53: dial udp 10.100.0.10:53: i/o timeout)

```

What could be causing these issues?

---

<div class="post-metadata">

**Author:** ![AJ-Jester](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.replicated.com/aj-jester/32/94_2.png) [@AJ-Jester](https://community.replicated.com/u/AJ-Jester)\
**Post date:** [September 27, 2021, 4:06pm UTC](https://community.replicated.com/t/kurl-diagnosing-ip-forward-being-disabled/580/2 "2021-09-27T16:06:09Z")

</div>

Generally, but not always, this happens when IP forward is disabled which is required for Docker to operate properly.

In order to diagnose this, run a few of the following commands:

- `systemctl status firewalld`

- `iptables -L -v`

- `docker info`

- `sysctl -a`