# FTL offline after upgrade to 3.3

**URL:** <https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315>\
**Category:** Help\
**Tags:** v3-3\
**Created:** [March 27, 2018, 12:50am UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315 "2018-03-27T00:50:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![\_dt](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/_/65b543/32.png) [@\_dt](https://discourse.pi-hole.net/u/_dt)\
**Post date:** [March 27, 2018, 12:50am UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315/1 "2018-03-27T00:50:06Z")

</div>

#### Please follow the below template, it will help us to help you!

## Expected Behaviour:

FTL does not seem to want to come up after upgrading my pihole version from 3.2.1. I originally installed pihole through dietpi and today upgraded both dietpi and pihole (in that order). I have run `pihole -r` to repair but to no avail. If I run `service pihole-FTL status` one line shows an error

`Mar 27 01:39:14 pihole su[4160]: pam_env(su:session): Unable to open env file: /etc/environment: No such file or directory `

not sure if this is relevant.

## Actual Behaviour:

FTL comes online and successfully connects to API

## Debug Token:

tdx07fbatz

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [March 27, 2018, 1:02am UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315/2 "2018-03-27T01:02:59Z")

</div>

Can you send us your entire `pihole-FTL.log`?

```auto
cat /var/log/pihole-FTL.log | pihole tricorder

```

---

<div class="post-metadata">

**Author:** ![\_dt](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/_/65b543/32.png) [@\_dt](https://discourse.pi-hole.net/u/_dt)\
**Post date:** [March 27, 2018, 1:08am UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315/3 "2018-03-27T01:08:47Z")

</div>

mbm8o91us6

---

<div class="post-metadata">

**Author:** ![jacob.salmela](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jacob.salmela/32/8_2.png) [@jacob.salmela](https://discourse.pi-hole.net/u/jacob.salmela)\
**Post date:** [March 27, 2018, 2:13am UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315/4 "2018-03-27T02:13:05Z")

</div>

> [@\_dt](#):
>
> mbm8o91us6

```auto
[2018-03-27 01:23:51.530] Error on binding on Unix socket /var/run/pihole/FTL.sock: No such file or directory (2)

```

I've seen this in a few other debug logs recently.

I'd have to ask @DL6ER how we can recreate this file (`var/run/pihole/FTL.sock`)

---

<div class="post-metadata">

**Author:** ![DL6ER](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dl6er/32/281_2.png) [@DL6ER](https://discourse.pi-hole.net/u/DL6ER)\
**Post date:** [March 27, 2018, 6:18pm UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315/5 "2018-03-27T18:18:48Z")

</div>

> [@jacob.salmela](#):
>
> I’d have to ask @DL6ER how we can recreate this file (/var/run/pihole/FTL.sock)

The file itself is generated by `FTL`. The problem in this case is that it cannot find the directory `/var/run/pihole` and hence cannot create the file (sorry for the unspecific error message, but this is what the system gives us (no such directory means the directory we try to create the file in). This directory should be generated by `sudo pihole-FTL start`. Please check if the file `/etc/init.d/pihole-FTL` is equal to this one:  
[https://github.com/pi-hole/pi-hole/blob/master/advanced/pihole-FTL.service#L29-L32](https://github.com/pi-hole/pi-hole/blob/master/advanced/pihole-FTL.service#L29-L32)  
Specifically compare the shown lines.

---

<div class="post-metadata">

**Author:** ![\_dt](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/_/65b543/32.png) [@\_dt](https://discourse.pi-hole.net/u/_dt)\
**Post date:** [March 27, 2018, 10:55pm UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315/6 "2018-03-27T22:55:07Z")

</div>

That seems to have been the problem! the init.d file was missing the mkdirs. Thanks!

```
start() {
  if is_running; then
    echo "pihole-FTL is already running"
  else
    touch /var/log/pihole-FTL.log /run/pihole-FTL.pid /run/pihole-FTL.port /var/log/pihole.log
    chown pihole:pihole /var/log/pihole-FTL.log /run/pihole-FTL.pid /run/pihole-FTL.port /etc/pihole
    chmod 0644 /var/log/pihole-FTL.log /run/pihole-FTL.pid /run/pihole-FTL.port /var/log/pihole.log
    su -s /bin/sh -c "/usr/bin/pihole-FTL" "$FTLUSER"
    echo
  fi
}

```

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [April 17, 2018, 10:55pm UTC](https://discourse.pi-hole.net/t/ftl-offline-after-upgrade-to-3-3/8315/7 "2018-04-17T22:55:23Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.