Juliaup configuration is locked by another process, waiting for it to unlock

General Usage
, ,
1

Whenever I launch Julia in the bash terminal of VSCode in Ubuntu Linux I get the message:

Juliaup configuration is locked by another process, waiting for it to unlock.

What could be the reason?

2

You probably installed Julia through juliaup, the latter does show this message sometimes. I guess it tries to auto-update Julia or something?..
Official binary downloads don’t do that, they just always start immediately.

3

Looks like Unlock configuration file during download ¡ Issue #435 ¡ JuliaLang/juliaup ¡ GitHub

Or maybe Don't lock the juliaup config file when only reading ¡ Issue #561 ¡ JuliaLang/juliaup ¡ GitHub

And see this comment for a potential workaround.

4

It does not always show this message. But I could not figure out yet when it does and when it doesn’t. Who might auto-update Julia? The VSCode language server? Or juliaup?

5

As far as I know juliaup doesn’t auto-update julia but it may auto-update itself and/or update the list of available julia releases.

6

Yes, Juliaup auto-updates itself and the list of available Julia versions. It will never update any Julia version itself without explicit opt-in from the user.

This locked message is annoying, I know how to fix it, just need to find the time to do it…

7

I am facing the same error now. My juliaup version is 1.20.4, julia version is 1.11.1 and operating system is Linux. Can someone suggest what is the working solution?

8

On a Mac

be@HPH-iMac-02 ~ % juliaup --version
Juliaup 1.20.1
be@HPH-iMac-02 ~ % juliaup self update
    Checking for new Julia versions
Checking for self-updates
Found new version 1.20.4 on channel release.
Juliaup configuration is locked by another process, waiting for it to unlock.
^C
be@HPH-iMac-02 ~ % juliaup self update
    Checking for new Julia versions
Checking for self-updates
Juliaup unchanged on channel 'release' - 1.20.4
be@HPH-iMac-02 ~ %

The same thing was observed on my another Mac: Juliaup cannot find Julia - #6 by Eben60 - the juliaup self update apparently performed, but then the command stalled

10

First time Ive gotten this error after many years, so seems to be a juliaup blip with the last update. Works fine after restarting the computer.

11

Thank you for your responses. Unfortunately, I could not restart the server as it is used by several other people. What worked in my case was to kill all the Julia processes across multiple servers (a single disk storage is shared among 3 different servers). The kill command I used is pkill -U username -f bin/julia.

12

It was a bug released, and already fixed, in juliaup

13

I solved it by killall juliaup

14

See

and the issues linked there.