Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Download of local LLM's initializes, but never proceeds #113

Closed
hercules2209 opened this issue Mar 1, 2024 · 6 comments
Closed

Download of local LLM's initializes, but never proceeds #113

hercules2209 opened this issue Mar 1, 2024 · 6 comments

Comments

@hercules2209
Copy link

Software

Desktop Application, Pieces OS, VS Code

Operating System

Linux

Your Pieces OS Version

8.0.1

Kindly describe the bug and include as much detail as possible on what you were doing so we can reproduce the bug.

I was trying to download a local LLM, but any one of them that I try it is stuck on initialising. It does not start downloading the model. I have tried downloading all the available models, but it does not move further than initialising. I have seen a similar issue on GitHub for somebody using windows, but for them, it went away after updating to version 8.0.0. of pieces OS. This is their GitHub issue #84 I am already on 8.0.1 but on Linux. I am pretty sure my internet is not an issue. The rest of the app functions perfectly. It's just that I cannot download local LLMs. I have also tried to install local LLMs through VS Code, but there instead of getting stuck on initializing it gets stuck on 0% complete.

I am on Linux
pieces OS : 8.0.1
pieces for developers : 2.10.0
OS : Ubuntu 22.04 LTS
CPU: Ryzen 5800H
Ram: 16gb
GPU: RTX 3050 mobile (4gbvram)

image
image

@hercules2209
Copy link
Author

These are the logs
pieces OS
log-03022024.txt
log-03012024.txt

pieces PFD
log-03022024.txt
log-03012024.txt

@mack-at-pieces
Copy link
Collaborator

@hercules2209 Thank you! Our team is looking into this as we speak. We've identified a few things that could alleviate the process from hanging that we hope to include in the next Pieces OS release 👍🏼 This will enable you to re-try the download in the event of a failure.

Unfortauntely, at this time we aren't 100% sure what is causing the failure to begin with, so we are also going to do some work to better understand where this process is failing and why so that we can work towards a better solution.

If you have any information about any special security or firewall tools/configs, network configs, and insight into your internet speed that could be tremendously helpful.

Thanks!

@hercules2209
Copy link
Author

hercules2209 commented Mar 5, 2024

This issue has since been resolved. I simply uninstalled and reinstalled both pieces Os and pfd and now it works.
Thank you

One key difference between both the installations was
While installing it this time I saw this error. It might have been there last time but I did not check it back then so cannot confirm it.

pieces-os
update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/fonts /usr/share/fonts-2 none bind,ro 0 0): permission denied

I have seen this issue before and it is usually because of conflict between snap mount space and app profile.
So to fix this this I ran this command

sudo /usr/lib/snapd/snap-update-ns pieces-os

In any case this might be completely unrelated to the download problem or not don't really know how it got fixed by reinstalling.

@caleb-at-pieces
Copy link
Contributor

This issue has since been resolved. I simply uninstalled and reinstalled both pieces Os and pfd and now it works.

We have managed to produce this internally.

With that said rebooting Pieces OS also seems to function as a good workaround if you face this again (before we manage to fix it).

@hra42
Copy link

hra42 commented Mar 25, 2024

I have the same issue on macOS Sonoma on a macBook Pro M3 Pro 36 GB Ram.

I tried downloading on a ipv6 only W11 VDI on MS Azure VDI, the download of a local model didn't work at all.
CleanShot_2024-03-25_at_21 35 222x

@caleb-at-pieces
Copy link
Contributor

I think this issue has since been fixed by a recent update where our ML engineers significantly changed how local LLM's are handled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment