# Warm-reload not working, how to diagnose?

**URL:** <https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181>\
**Category:** Support\
**Created:** [June 26, 2024, 4:53pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181 "2024-06-26T16:53:18Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![meta\_leap](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/meta_leap/32/1245_2.png) [@meta\_leap](https://zola.discourse.group/u/meta_leap)\
**Post date:** [June 26, 2024, 4:53pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/1 "2024-06-26T16:53:18Z")

</div>

Using `zola serve`, any `*.md` changes **don’t** show up on F5 / Ctrl+F5 / Ctrl+R / Ctrl+Shift+R page reloads: I have to force-quit-and-restart `zola serve` to see those changes.

This is an (Arch-deriv) Garuda Linux.

How to troubleshoot this — seems like there’s no “`verbose`-level logging” (at least, `help` doesn’t mention it).

I can report that `ulimit` returns `unlimited` and `cat /proc/sys/fs/inotify/max_user_watches` returns `524288`.

---

<div class="post-metadata">

**Author:** ![meta\_leap](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/meta_leap/32/1245_2.png) [@meta\_leap](https://zola.discourse.group/u/meta_leap)\
**Post date:** [June 27, 2024, 9:23am UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/2 "2024-06-27T09:23:48Z")

</div>

Solved with 0.19.1, was a bug in 0.19.0 apparently =)

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [June 27, 2024, 1:43pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/3 "2024-06-27T13:43:38Z")

</div>

Yep it should be fixed for Linux. Do you get [zola serve - automatic firefox refresh leads to `Not Found` · Issue #2552 · getzola/zola · GitHub](https://github.com/getzola/zola/issues/2552) by any chance?

---

<div class="post-metadata">

**Author:** ![meta\_leap](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/meta_leap/32/1245_2.png) [@meta\_leap](https://zola.discourse.group/u/meta_leap)\
**Post date:** [June 27, 2024, 2:14pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/4 "2024-06-27T14:14:11Z")

</div>

Just tried with FF, seems to work just fine!

---

<div class="post-metadata">

**Author:** ![meta\_leap](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/meta_leap/32/1245_2.png) [@meta\_leap](https://zola.discourse.group/u/meta_leap)\
**Post date:** [June 28, 2024, 6:28am UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/5 "2024-06-28T06:28:10Z")

</div>

@keats I should add: I **do** see that very “Not Found” rendition sometimes. But rarely, no idea under what circumstances (other than being on Change-Detected), in Chromium (so not FF-specific I’d gather), always solved by F5.

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [October 29, 2024, 3:16pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/6 "2024-10-29T15:16:34Z")

</div>

I have this problem with v0.19.2 on MacOS. Zola recognises when I add a new file into the system, but it does not live reload for any changes to CSS or MD files, and even manually refreshing my browser does not load the updated file: I have to quite `zola serve` and run it again.

I was previously running 0.17.2, it was only after updating to 0.19.2 that the detection stopped working. What can I do to help troubleshoot/fix this?

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [October 31, 2024, 7:20am UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/7 "2024-10-31T07:20:01Z")

</div>

Which editor are you using?

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [November 7, 2024, 9:14pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/8 "2024-11-07T21:14:47Z")

</div>

Hi @keats I’m using Sublime Text 4, build 4180 latest. I run a separate terminal for zola.

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [November 7, 2024, 10:24pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/9 "2024-11-07T22:24:12Z")

</div>

if you can compile the CLI, you can add a `println!` in [zola/src/fs\_utils.rs at master · getzola/zola · GitHub](https://github.com/getzola/zola/blob/master/src/fs_utils.rs#L36) to see what kind of events are emitted when you save edits. Editors do weird things

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [November 7, 2024, 10:36pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/10 "2024-11-07T22:36:15Z")

</div>

Thanks, but unfortunately I don’t have the knowledge to do that, I’m a web designer not a programmer. Is there anything else I can try that doesn’t involve compiling zola sources?

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [November 8, 2024, 8:36am UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/11 "2024-11-08T08:36:18Z")

</div>

What OS are you on? If you’re on a Mac I can try to reproduce it myself, otherwise it’s going to be harder

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [November 9, 2024, 1:43am UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/12 "2024-11-09T01:43:46Z")

</div>

I use Windows and MacOS. The Windows version of 0.19.2 works fine, no problems with live reload. But the MacOS version is broken. This is on MacOS Sonoma 14.7.1.

(BTW sorry for delayed replies, I’m not getting notifications from here despite having them switched on.)

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [December 2, 2024, 7:52pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/13 "2024-12-02T19:52:30Z")

</div>

A bit more info: I noticed that Zola was picking up file changes when I edited the files on a different machine.

I use [syncthing](https://syncthing.net/) to synchronise my files across multiple devices across my home network. When I edit a file on Windows in Sublime Text, the windows version of Zola 0.19.2 will live reload perfectly. But the livereload wasn’t working on MacOS at all when saving through Sublime Text.

Today when I opened my Macbook, I noticed I still had `zola serve` running in an open terminal, and I realised that it was serving the website with all the changes I’d made on my Windows machine. I checked the terminal and it had indeed picked up the changes that had been synschronised by syncthing.

So that seems a clear indicator that Sublime Text on MacOS is no longer compatible with Zola’s filewatcher for live reload.

Does that help at all @keats ??

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [December 3, 2024, 3:05pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/14 "2024-12-03T15:05:24Z")

</div>

Can you build the next branch from the repo and try? There has been some changes for the Nova editor on Mac but that might work for sublime as well

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [December 3, 2024, 5:09pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/17 "2024-12-03T17:09:46Z")

</div>

I had 20 mins to spare and gave it a go: compiled the next branch OK and it works with Sublime! Excellent. And now I know how to build zola too, which is something I didn’t think I’d learn today (OK, fair enough, it’s very easy given the docs, thanks!) @keats

(sorry for the two deleted posts above!)

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [December 10, 2024, 9:18am UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/18 "2024-12-10T09:18:22Z")

</div>

@keats FYI, if I close my macbook and leave `zola serve` running (the new compiled binary from the `next` branch), when I return and re-open the macbook, zola is still running but generating thousands of errors in this format:

`Error: File system event receiver errors: RecvError`

I have to command+c to quit it and then I can re run it OK. Older versions of zola left running in the terminal when the laptop is closed have never done this. Just thought you should know.

---

<div class="post-metadata">

**Author:** ![matthillco](https://yyz2.discourse-cdn.com/free1/user_avatar/zola.discourse.group/matthillco/32/869_2.png) [@matthillco](https://zola.discourse.group/u/matthillco)\
**Post date:** [January 7, 2025, 12:04pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/19 "2025-01-07T12:04:45Z")

</div>

In addition to the above, all those errors eventually consume all resources and the terminal has to be force quit to free up system memory – it was apparently using 92GB RAM! (obviously most of that is a virtual swap disk).

So the filewatcher change seems to have some unintended consequences! Not sure if this helps you at all but I thought you should know.

@keats

---

<div class="post-metadata">

**Author:** ![keats](https://avatars.discourse-cdn.com/v4/letter/k/34f0e0/32.png) [@keats](https://zola.discourse.group/u/keats)\
**Post date:** [January 7, 2025, 2:48pm UTC](https://zola.discourse.group/t/warm-reload-not-working-how-to-diagnose/2181/20 "2025-01-07T14:48:24Z")

</div>

Hm that’s weird, I really am not sure what’s up with that
