Merge branch 'docs-pena-team' of https://github.com/janhq/jan into docs-pena-team
This commit is contained in:
commit
59cf970117
31
docs/docs/guides/error-codes/no-assistant-available.mdx
Normal file
31
docs/docs/guides/error-codes/no-assistant-available.mdx
Normal file
@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
title: No Assistant Available
|
||||||
|
sidebar_position: 7
|
||||||
|
description: Troubleshooting steps to resolve issues no assistant available.
|
||||||
|
keywords:
|
||||||
|
[
|
||||||
|
Jan AI,
|
||||||
|
Jan,
|
||||||
|
ChatGPT alternative,
|
||||||
|
local AI,
|
||||||
|
private AI,
|
||||||
|
conversational AI,
|
||||||
|
no-subscription fee,
|
||||||
|
large language model,
|
||||||
|
troubleshooting,
|
||||||
|
no assistant available,
|
||||||
|
]
|
||||||
|
---
|
||||||
|
|
||||||
|
When you encounter the following error message:
|
||||||
|
```
|
||||||
|
No assistant available.
|
||||||
|
```
|
||||||
|
|
||||||
|
This issue arises when a new, unintentional file appears in `/jan/assistants`.
|
||||||
|
|
||||||
|
It can be resolved through the following steps:
|
||||||
|
|
||||||
|
1. Access the `/jan/assistants` directory using a file manager or terminal.
|
||||||
|
|
||||||
|
2. Within `/jan/assistants`, this directory should only contain a folder named `jan`. Identify any file outside of this folder and remove it.
|
||||||
62
docs/docs/guides/error-codes/stuck-on-loading-model.mdx
Normal file
62
docs/docs/guides/error-codes/stuck-on-loading-model.mdx
Normal file
@ -0,0 +1,62 @@
|
|||||||
|
---
|
||||||
|
title: Stuck on Loading Model
|
||||||
|
sidebar_position: 8
|
||||||
|
description: Troubleshooting steps to resolve issues related to the loading model.
|
||||||
|
keywords:
|
||||||
|
[
|
||||||
|
Jan AI,
|
||||||
|
Jan,
|
||||||
|
ChatGPT alternative,
|
||||||
|
local AI,
|
||||||
|
private AI,
|
||||||
|
conversational AI,
|
||||||
|
no-subscription fee,
|
||||||
|
large language model,
|
||||||
|
troubleshooting,
|
||||||
|
stuck on loading model,
|
||||||
|
]
|
||||||
|
---
|
||||||
|
|
||||||
|
## 1. Issue: Model Loading Stuck Due To Missing Windows Management Instrumentation Command-line (WMIC)
|
||||||
|
|
||||||
|
Encountering a stuck-on-loading model issue in Jan is caused by errors related to the `Windows Management Instrumentation Command-line (WMIC)` path not being included in the system's PATH environment variable.
|
||||||
|
|
||||||
|
Error message:
|
||||||
|
```
|
||||||
|
index.js:47 Uncaught (in promise) Error: Error invoking remote method 'invokeExtensionFunc': Error: Command failed: WMIC CPU Get NumberOfCores
|
||||||
|
```
|
||||||
|
|
||||||
|
It can be resolved through the following steps:
|
||||||
|
|
||||||
|
1. **Open System Properties:**
|
||||||
|
- Press `Windows key + R`.
|
||||||
|
- Type `sysdm.cpl` and press `Enter`.
|
||||||
|
|
||||||
|
2. **Access Environment Variables:**
|
||||||
|
- Go to the "Advanced" tab.
|
||||||
|
- Click the "Environment Variables" button.
|
||||||
|
|
||||||
|
3. **Edit System PATH:**
|
||||||
|
- Under "System Variables" find and select `Path`.
|
||||||
|
- Click "Edit."
|
||||||
|
|
||||||
|
4. **Add WMIC Path:**
|
||||||
|
- Click "New" and enter `C:\Windows\System32\Wbem`.
|
||||||
|
|
||||||
|
5. **Save Changes:**
|
||||||
|
- Click "OK" to close and save your changes.
|
||||||
|
|
||||||
|
6. **Verify Installation:**
|
||||||
|
- Restart any command prompts or terminals.
|
||||||
|
- Run `where wmic` to verify. Expected output: `C:\Windows\System32\wbem\WMIC.exe`.
|
||||||
|
|
||||||
|
|
||||||
|
## 2. Issue: Model Loading Stuck Due To CPU Without AVX
|
||||||
|
|
||||||
|
Encountering an issue with models stuck on loading in Jan can be due to the use of older generation CPUs that do not support Advanced Vector Extensions (AVX).
|
||||||
|
|
||||||
|
To check if your CPU supports AVX, visit the following link: [CPUs with AVX](https://en.wikipedia.org/wiki/Advanced_Vector_Extensions#CPUs_with_AVX)
|
||||||
|
|
||||||
|
:::warning [Please use this with caution]
|
||||||
|
As a workaround, consider using an [emulator](https://www.intel.com/content/www/us/en/developer/articles/tool/software-development-emulator.html) to simulate AVX support.
|
||||||
|
:::
|
||||||
26
docs/docs/guides/error-codes/thread-disappreance.mdx
Normal file
26
docs/docs/guides/error-codes/thread-disappreance.mdx
Normal file
@ -0,0 +1,26 @@
|
|||||||
|
---
|
||||||
|
title: Thread Disappearance
|
||||||
|
sidebar_position: 6
|
||||||
|
description: Troubleshooting steps to resolve issues threads suddenly disappearance.
|
||||||
|
keywords:
|
||||||
|
[
|
||||||
|
Jan AI,
|
||||||
|
Jan,
|
||||||
|
ChatGPT alternative,
|
||||||
|
local AI,
|
||||||
|
private AI,
|
||||||
|
conversational AI,
|
||||||
|
no-subscription fee,
|
||||||
|
large language model,
|
||||||
|
troubleshooting,
|
||||||
|
thread disappearance,
|
||||||
|
]
|
||||||
|
---
|
||||||
|
|
||||||
|
When you encounter the error of old threads suddenly disappear. This can happen when a new, unintentional file is created in `/jan/threads`.
|
||||||
|
|
||||||
|
It can be resolved through the following steps:
|
||||||
|
|
||||||
|
1. Go to `/jan/threads`.
|
||||||
|
|
||||||
|
2. The `/jan/threads` directory contains many folders named with the prefix `jan_` followed by an ID (e.g., `jan_123`). Look for any file not conforming to this naming pattern and remove it.
|
||||||
Loading…
x
Reference in New Issue
Block a user