zplug: Writing log fails

Problem Summary

zplug tries to log to a file that doesn’t exist.

This is being logged during zplug load

Can't acquire lock for /home/agross/.cache/zplug/log/load_success.log.
__zplug::job::handle::flock:zsystem:28: failed to open /home/agross/.cache/zplug/log/load_success.log for writing: no such file or directory

The directory doesn’t contain the log_success.log:

$ ls /home/agross/.cache/zplug/log/ -la
total 18
drwxr-xr-x 1 agross None     0 Dec 23 11:10 .
drwxr-xr-x 1 agross None     0 Dec 29 11:37 ..
-rw-r--r-- 1 agross None   665 Dec 22 11:09 status.log
-rw-r--r-- 1 agross None 10023 Dec 29 11:37 trace.log
-rw-r--r-- 1 agross None   694 Dec 23 11:10 update.log

When it’s created manually, the error doesn’t show up any more.

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 3
  • Comments: 22 (16 by maintainers)

Commits related to this issue

Most upvoted comments

I too have lots of error messages like the one below logged.

__zplug::job::handle::flock:zsystem:38: failed to open /usr/local/opt/zplug/log/load_success.log for writing: no such file or directory
Can't acquire lock for /usr/local/opt/zplug/log/load_success.log.

The error occurs when I use tmux-resurrect to resurrect my tmux window layout and contents. These error messages occur in many tmux windows (I have two tmux session each have 7-9 windows open).

and I do have the file load_success.log in the directory.

I’m wondering if there’s an option I could turn off logging.

Thanks

I’m having the same issue as well. I have a command that starts 36 tmux sessions each with two zsh and I see this message on most of the ZSH sessions. I believe this is simply a race condition issue as ZSH sessions are competing for the lock. @b4b4r07 is it possible to disable logging?

zshrc sw (start working) tmx

I put a typeset -p _zplug_load_log before this line and when loading the a new shell session (zplug load) it tells me this variable doesn’t exist.

After the shell is started (and lots of errors are logged), the variable is set.