FTL log move error during latest update (Pi-hole FTL v5.16, Web v5.13 and Core v5.11.1)

I got the following error while updating to the latest versions (Pi-hole FTL v5.16, Web v5.13 and Core v5.11.1):

[✓] Enabling lighttpd service to start on reboot...
[i] Restarting services...
[✓] Enabling pihole-FTL service to start on reboot...
mv: cannot move '/var/log/pihole-FTL.log' to '/var/log/pihole/FTL.log': No such file or directory

  Unable to complete update, please contact Pi-hole Support

The update change log contains this likely related change:
Change default log file path to /var/log/pihole/FTL.log by @DL6ER in #1375

The log file is still available at its old path and not at the new one.
Is any action required or can I leave things as they are?

Debug Token:
https://tricorder.pi-hole.net/CLEjWeCn/

a new version has been released a couple of minutes ago. Try again.

1 Like

I either have installed the new version already or it is not available yet, I will try again later.
Thanks

the new core version is v5.11.3. Maybe it take while to become available or the old version is still cached somewhere on the web :slight_smile:

I am indeed on v5.11.2 :slight_smile:

Manually create the dir

mkdir /var/log/pihole and try again

the updater will not do anything anymore until a new version is available. Restarting the service should be fine as well

systemctl restart pihole-FTL

6 posts were merged into an existing topic: Pi-hole FTL v5.16, Web v5.13 and Core v5.11.1 released

This did not work:

pi@PiHole:~ $ mkdir /var/log/pihole
mkdir: cannot create directory ‘/var/log/pihole’: File exists

I think so too. When trying to update, all seems up to date:

  [i] Checking for updates...
  [i] Pi-hole Core:     up to date
  [i] Web Interface:    up to date
  [i] FTL:              up to date

However when I do a version check, pihole knows that a newer FTL core version is available:

pi@PiHole:~ $ pihole version
  Pi-hole version is v5.11.2 (Latest: v5.11.3)
  AdminLTE version is v5.13 (Latest: v5.13)
  FTL version is v5.16 (Latest: v5.16)

maybe @DanSchaper knows why the version is not updated, even if the version check shows a new one,

If you tried to run pihole -up during a small 5 minute window then you may have a tag that is not correct.

If you can run a few commands for me then I can get you the best way forward.

cd /etc/.pihole
sudo git tag

and from the same directory

sudo git log

I only need the last few log entries.

If you already have a tag for v5.11.3 then we'll have to delete that tag and run pihole -up again.

1 Like

Looks like I picked a great moment to start updating :grin:

The last few tags:

v5.10
v5.11
v5.11.1
v5.11.2
v5.11.3
v5.2
v5.2.1
v5.2.2
v5.2.3
v5.2.4
v5.3
v5.3.1
v5.4
v5.5
v5.6
v5.7
v5.8
v5.8.1
v5.9
v5.9.1

Indeed I have tag V5.11.3.

The first few log entries (looks like newest first):

pi@PiHole:/etc/.pihole $ sudo git log
commit ef71ca05a9cfb49ae322a0ac9ace56b604d8a425 (HEAD -> master, tag: v5.11.3, tag: v5.11.2)
Merge: 04abc4da 48d5d6be
Author: Dan Schaper <dan.schaper@pi-hole.net>
Date:   Thu Jul 7 13:41:45 2022 -0700

    Merge pull request #4794 from pi-hole/fix/mkdir_always

    Always create log directory if it doesn't exist

commit 48d5d6bed2d1fe615ad42871b1b4315d261dd2bc
Author: Dan Schaper <dan.schaper@pi-hole.net>
Date:   Thu Jul 7 13:23:13 2022 -0700

    Always create the log target directory before any movements

    Signed-off-by: Dan Schaper <dan.schaper@pi-hole.net>

commit 04abc4dacdfa1f297e05c1689021b30cbbb7822b (tag: v5.11.1)
Merge: 1be082a0 fd418019
Author: Adam Warner <me@adamwarner.co.uk>
Date:   Thu Jul 7 20:18:18 2022 +0100

    Merge pull request #4792 from pi-hole/fix/mkdir_logs

    Create new log directory

commit fd41801977746ee1b3845bd8908b4315784f384b
Author: Dan Schaper <dan.schaper@pi-hole.net>
Date:   Thu Jul 7 12:12:53 2022 -0700

    Create new log directory

    Signed-off-by: Dan Schaper <dan.schaper@pi-hole.net>

commit 1be082a0e15fb7d12580db8b1f736fad4745b26a (tag: v5.11)
Merge: bacb98be 6204698e
Author: Adam Warner <me@adamwarner.co.uk>
Date:   Thu Jul 7 19:48:32 2022 +0100

    Merge pull request #4789 from pi-hole/development

    v5.11 Release

commit 6204698e055b27c851443745542646f25f1e6d2a
Merge: 3d4476c9 edba325a
Author: Adam Warner <me@adamwarner.co.uk>
Date:   Thu Jul 7 19:16:03 2022 +0100

    Merge pull request #4790 from pi-hole/reformat-yml

    [Meta] Reformat yml files

I removed the tag:

sodu git tag -d v5.11.3

After this I managed to successfully update to V5.11.3 :slight_smile:

Many thanks everyone for your help!

3 Likes

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