# Installation on arch linux won't start due to missing exiftool

**URL:** <https://meta.akkoma.dev/t/installation-on-arch-linux-wont-start-due-to-missing-exiftool/164>\
**Category:** Support\
**Created:** [25 November 2022 00:07 UTC](https://meta.akkoma.dev/t/installation-on-arch-linux-wont-start-due-to-missing-exiftool/164 "2022-11-25T00:07:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![bunnegirl](https://meta.akkoma.dev/user_avatar/meta.akkoma.dev/bunnegirl/32/102_2.png) [@bunnegirl](https://meta.akkoma.dev/u/bunnegirl)\
**Post date:** [25 November 2022 00:07 UTC](https://meta.akkoma.dev/t/installation-on-arch-linux-wont-start-due-to-missing-exiftool/164/1 "2022-11-25T00:07:30Z")

</div>

i followed the arch linux installation instructions and during the configuration phase i selected the option to have geolocation data stripped from image uploads, this requires exiftools which are installed:

```auto
[root@localhost akkoma]# which exiftool
/usr/bin/vendor_perl/exiftool

```

the akkoma service is stuck starting up because:

```auto
23:54:32.153 [error] Elixir.Pleroma.Upload.Filter.Exiftool is specified in list of Pleroma.Upload filters, but the exiftool command is not found
23:54:32.161 [notice] Application pleroma exited: exited in: Pleroma.Application.start(:normal, [])
     ** (EXIT) an exception was raised:
         ** (Pleroma.ApplicationRequirements.VerifyError) System commands missing. Check logs and see `docs/installation` for more details.
             (pleroma 3.4.0-121-g2fe1484e-develop) lib/pleroma/application_requirements.ex:32: Pleroma.ApplicationRequirements.handle_result/1
             (pleroma 3.4.0-121-g2fe1484e-develop) lib/pleroma/application.ex:55: Pleroma.Application.start/2
             (kernel 8.5.1) application_master.erl:293: :application_master.start_it_old/4

```

anyone know what’s up?

---

<div class="post-metadata">

**Author:** ![FloatingGhost](https://meta.akkoma.dev/letter_avatar_proxy/v4/letter/f/d07c76/32.png) [@FloatingGhost](https://meta.akkoma.dev/u/FloatingGhost)\
**Post date:** [25 November 2022 10:15 UTC](https://meta.akkoma.dev/t/installation-on-arch-linux-wont-start-due-to-missing-exiftool/164/2 "2022-11-25T10:15:16Z")

</div>

i develop on arch so it shooooould work

the command checking is done via :os.find\_executable [os — kernel v10.3.2](https://www.erlang.org/doc/man/os.html#find_executable-2) - how are you starting the service? does the `PATH` provided to akkoma on start inlude /usr/bin/vendor\_perl?

---

<div class="post-metadata">

**Author:** ![r3g\_5z](https://meta.akkoma.dev/user_avatar/meta.akkoma.dev/r3g_5z/32/101_2.png) [@r3g\_5z](https://meta.akkoma.dev/u/r3g_5z)\
**Post date:** [26 November 2022 04:55 UTC](https://meta.akkoma.dev/t/installation-on-arch-linux-wont-start-due-to-missing-exiftool/164/3 "2022-11-26T04:55:00Z")

</div>

> [@FloatingGhost](#):
>
> does the `PATH` provided to akkoma on start inlude /usr/bin/vendor\_perl?

Seems like it doesn’t here on Arch Linux using OTP using a systemd service.

```auto
Nov 26 04:23:02 plem.sapphic.site systemd[1]: Starting Akkoma social network...
Nov 26 04:23:02 plem.sapphic.site echo[25376]: /usr/local/sbin:/usr/local/bin:/usr/bin

```

```auto
# akkoma.service
ExecStartPre=echo $PATH ExecStart=/opt/akkoma/bin/pleroma start

```

```auto
# my normal PATH
adm-tpyrope@corp.terezi.dev √ /home/tpyrope % echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

```

This is an intended design by systemd because it heavily discourages modifying PATH during runtime for any services. This also means it does _not_ execute anything under `/etc/profile.d/*`, which is where one of the necessary Perl shell scripts are (perlbin.sh). Ideally you could just set `ExecStartPre=/bin/bash -c "/etc/profile.d/perlbin.sh"`, but [Arch Linux installs the script’s permissions as 644](https://github.com/archlinux/svntogit-packages/blob/df7a2fcf4415f030462564a9fbd26c2f0efa2da3/trunk/PKGBUILD#L215-L217) which are not executable.

The only proper solution I’ve found is to manually define your path with `Environment=/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl` in the systemd unit (akkoma.service).

```auto
Nov 26 04:50:20 plem.sapphic.site echo[26391]: /usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl

```
