search

janhq / jan

Jan is an open source alternative to ChatGPT that runs 100% offline on your computer. Multiple engine support (llama.cpp, TensorRT-LLM)
https://jan.ai/
GNU Affero General Public License v3.0
20.75k stars 1.19k forks source link

bug: halt and message: "Message queued. It can be sent once the model has started" #1859

Closed lineality closed 3 months ago

lineality commented 5 months ago

Describe the bug until today Jan always worked, but now I get directed to this message: Message queued. It can be sent once the model has started and nothing happens...no activity on cpu...nothing. It seems to never load a model fully, or even try. once tiny lama or phi worked, but now nothing works.

Steps to reproduce Steps to reproduce the behavior:

  1. try using any model for anything.
  2. see "Message queued. It can be sent once the model has started"
  3. be unable to do anything

Expected behavior Jan...works. The model produces some generated output...

Screenshots

Environment details

Logs If the cause of the error is not clear, kindly provide your usage logs:

Additional context Add any other context or information that could be helpful in diagnosing the problem.

Van-QA commented 5 months ago

@lineality Can you give us the app.log? About the Jan build number, it's in the lower right conner of the Jan app

lineality commented 5 months ago

ok! I figured out some of the factors here maybe! Here is some more data:

This new problem only started when an older problem was 'solved'...cuda was never recognized and cpu mode was always used, and turing on GPU in advanced always gave a "it appears you are missing some dependencies" message.

Now:

  1. the jan/settings.json is always set to gpu by default (even if in Ubuntu I don't select the gpu-mode in startup right click or in advanced (not sure if those are the same or not...))

  2. cuda version 12 is now correctly identified in the settings.json for the first time!!! progress

  3. I still get a "it appears you are missing some dependencies" message if I try turning on gpu mode in settings.

  4. the new problem: model's appear to not ever load.

So...I thought of modifying the settings.json and turning on gpu-mode, and setting cuda to false (not sure if that's needed) but then

  1. and Another new (minor) problem is a 'sticky' model choice, where it keeps auto-reverting to the last model I used even if I set a new one (never used to happen).

As long as the settings.json is set to cpu AND the toggle bar for nvida is OFF, then Jan works fine.

version: I update every time I'm prompted so 'now' 2024.01.30 1am UTC, I'm on jan version: v0.4.5-211 (from lower right corner of screen - thanks for the tip to look there!)

logs...I found that, I'll try to attach that as a file.

lineality commented 5 months ago

Here are the logs! app.log

lineality commented 5 months ago

I'm still not sure about GPU vs CPU e.g. my GPU is not big, only 4gb? so maybe Jan can only use only gpu or zero gpu. Maybe only tiny-lama is small enough to work on only-gpu. That would make sense. So...is there a way to use GPU to boost the other resources? Maybe not. But, e.g. in computer resources, my GPU never shows up, it just shows RAM and CPU...

lineality commented 5 months ago

ALso, even though it seemed to be in gpu mode and maybe running tiny-lama, it still said I lacked dependencies (but not saying which one, and I've been over that list a gazillion times and I have everything mentioned).

Van-QA commented 4 months ago

linking this to https://github.com/janhq/nitro/issues/430, related to queued system.

kucingkembar commented 4 months ago

hi, I have this problem also, stuck at:

Starting model trinity-v1.2-7b
Message queued. It can be sent once the model has started

Can I clean uninstall it from Windows 11? I like to install it to D drive, I hope after I reinstall it, I can run it normally

louis-jan commented 4 months ago

@Van-QA please help verify this issue again with Nightly 270. I think this issue is fixed.

Van-QA commented 4 months ago

@lineality and @kucingkembar, can you help double check using Jan v0.4.6-270, thank you. The issue seems to be resolved from our side.

kucingkembar commented 4 months ago

it still stuck at :

Starting model mistral-ins-7b-q4
Message queued. It can be sent once the model has started

do this software need hidden requirements like direct x? note : i have this 

nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Feb__8_05:53:42_Coordinated_Universal_Time_2023
Cuda compilation tools, release 12.1, V12.1.66
Build cuda_12.1.r12.1/compiler.32415258_0

and do I need to install/update "nitro"?

louis-jan commented 4 months ago

it still stuck at :

Starting model mistral-ins-7b-q4
Message queued. It can be sent once the model has started

do this software need hidden requirements like direct x? note : i have this

nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Wed_Feb__8_05:53:42_Coordinated_Universal_Time_2023
Cuda compilation tools, release 12.1, V12.1.66
Build cuda_12.1.r12.1/compiler.32415258_0

and do I need to install/update "nitro"?

What version are you on? Could you please help attach app.log here?

kucingkembar commented 4 months ago

what version version? windows 11, jan-win-x64-0.4.6-270.exe, jan log, sorry i have delete some of days ago, and the remaining just this:

2024-02-12T18:36:28.213Z [NITRO]::Debug: Request to kill Nitro
2024-02-12T18:36:59.496Z [NITRO]::Debug: Request to kill Nitro
2024-02-12T19:28:27.393Z [NITRO]::Debug: Request to kill Nitro
2024-02-15T11:16:01.114Z [NITRO]::Debug: Request to kill Nitro
2024-02-15T11:16:59.344Z [NITRO]::Debug: Request to kill Nitro
2024-02-15T11:25:39.746Z [NITRO]::Debug: Request to kill Nitro

and this from nvidia

nvidia-smi
Thu Feb 15 18:27:45 2024
+---------------------------------------------------------------------------------------+
| NVIDIA-SMI 546.29                 Driver Version: 546.29       CUDA Version: 12.3     |
|-----------------------------------------+----------------------+----------------------+
| GPU  Name                     TCC/WDDM  | Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |         Memory-Usage | GPU-Util  Compute M. |
|                                         |                      |               MIG M. |
|=========================================+======================+======================|
|   0  NVIDIA GeForce GTX 1660 ...  WDDM  | 00000000:01:00.0  On |                  N/A |
| 25%   42C    P8               6W / 125W |    544MiB /  6144MiB |      2%      Default |
|                                         |                      |                  N/A |
+-----------------------------------------+----------------------+----------------------+

+---------------------------------------------------------------------------------------+
| Processes:                                                                            |
|  GPU   GI   CI        PID   Type   Process name                            GPU Memory |
|        ID   ID                                                             Usage      |
|=======================================================================================|
|    0   N/A  N/A      1080    C+G   ...5n1h2txyewy\ShellExperienceHost.exe    N/A      |
|    0   N/A  N/A      1724    C+G   ...m Files\Mozilla Firefox\firefox.exe    N/A      |
|    0   N/A  N/A      4652    C+G   ...2txyewy\StartMenuExperienceHost.exe    N/A      |
|    0   N/A  N/A      6916    C+G   ...nt.CBS_cw5n1h2txyewy\SearchHost.exe    N/A      |
|    0   N/A  N/A      7460    C+G   C:\Windows\explorer.exe                   N/A      |
|    0   N/A  N/A      7684    C+G   ...siveControlPanel\SystemSettings.exe    N/A      |
|    0   N/A  N/A      9512    C+G   ...ekyb3d8bbwe\PhoneExperienceHost.exe    N/A      |
|    0   N/A  N/A     10200    C+G   ...m Files\Mozilla Firefox\firefox.exe    N/A      |
|    0   N/A  N/A     10956    C+G   ...CBS_cw5n1h2txyewy\TextInputHost.exe    N/A      |
|    0   N/A  N/A     11348    C+G   ...Cloudflare WARP\Cloudflare WARP.exe    N/A      |
|    0   N/A  N/A     12316    C+G   ...crosoft\Edge\Application\msedge.exe    N/A      |
+---------------------------------------------------------------------------------------+
louis-jan commented 4 months ago

I see, so that's another issue, the model even not loaded. Also, what does Nitro give you when opening it manually ~/jan/extensions/@janhq/inference-nitro-extension/dist/bin/windows*? (Please try with both CPU and GPU Nitro executable files and see what the problem is on each.)

louis-jan commented 4 months ago

If you get VC*...dll is missing error dialog, please try following: https://github.com/janhq/jan/issues/1683#issuecomment-1925187154

I see, so that's another issue, the model even not loaded. Also, what does Nitro give you when opening it manually ~/jan/extensions/@janhq/inference-nitro-extension/dist/bin/windows*? (Please try with both CPU and GPU Nitro executable files and see what the problem is on each.)

kucingkembar commented 4 months ago

jan\extensions\@janhq\inference-nitro-extension\dist\bin\win-cpu\nitro.exe & jan\extensions\@janhq\inference-nitro-extension\dist\bin\win-cuda-12-0\nitro.exe

      ___                                   ___           ___     
     /__/        ___           ___        /  /\         /  /\    
     \  \:\      /  /\         /  /\      /  /::\       /  /::\   
      \  \:\    /  /:/        /  /:/     /  /:/\:\     /  /:/\:\  
  _____\__\:\  /__/::\       /  /:/     /  /:/  \:\   /  /:/  \:\ 
 /__/::::::::\ \__\/\:\__   /  /::\    /__/:/ /:/___ /__/:/ \__\:\
 \  \:\~~\~~\/    \  \:\/\ /__/:/\:\   \  \:\/:::::/ \  \:\ /  /:/
  \  \:\  ~~~      \__\::/ \__\/  \:\   \  \::/~~~~   \  \:\  /:/ 
   \  \:\          /__/:/       \  \:\   \  \:\        \  \:\/:/  
    \  \:\         \__\/         \__\/    \  \:\        \  \::/   
     \__\/                                 \__\/         \__\/    
20240215 11:46:07.029000 UTC 4756 INFO  Nitro version:  - main.cc:50
20240215 11:46:07.029000 UTC 4756 INFO  Server started, listening at: 127.0.0.1:3928 - main.cc:54
20240215 11:46:07.029000 UTC 4756 INFO  Please load your model - main.cc:55
20240215 11:46:07.029000 UTC 4756 INFO  Number of thread is:4 - main.cc:62

it stuck at that point,

jan\extensions\@janhq\inference-nitro-extension\dist\bin\win-cuda-11-7\nitro.exe

nitro.exe - System Error
The code execution cannot proceed because cudart64_110.dll was not found. Reinstalling the program may fix this problem.
louis-jan commented 4 months ago

Since you are on cuda 12. Please try

jan\extensions@janhq\inference-nitro-extension\dist\bin\win-cuda-12-*\nitro.exe

Confirm again, you are trying to run model with GPU accelerated turned on right? And CPU does work? Check in Jan > Settings > Advanced > GPU *

kucingkembar commented 4 months ago 
jan\extensions\@janhq\inference-nitro-extension\dist\bin\win-cuda-12-0\nitro.exe
      ___                                   ___           ___     
     /__/        ___           ___        /  /\         /  /\    
     \  \:\      /  /\         /  /\      /  /::\       /  /::\   
      \  \:\    /  /:/        /  /:/     /  /:/\:\     /  /:/\:\  
  _____\__\:\  /__/::\       /  /:/     /  /:/  \:\   /  /:/  \:\ 
 /__/::::::::\ \__\/\:\__   /  /::\    /__/:/ /:/___ /__/:/ \__\:\
 \  \:\~~\~~\/    \  \:\/\ /__/:/\:\   \  \:\/:::::/ \  \:\ /  /:/
  \  \:\  ~~~      \__\::/ \__\/  \:\   \  \::/~~~~   \  \:\  /:/ 
   \  \:\          /__/:/       \  \:\   \  \:\        \  \:\/:/  
    \  \:\         \__\/         \__\/    \  \:\        \  \::/   
     \__\/                                 \__\/         \__\/    
20240215 12:03:01.628000 UTC 10916 INFO  Nitro version:  - main.cc:50
20240215 12:03:01.628000 UTC 10916 INFO  Server started, listening at: 127.0.0.1:3928 - main.cc:54
20240215 12:03:01.639000 UTC 10916 INFO  Please load your model - main.cc:55
20240215 12:03:01.639000 UTC 10916 INFO  Number of thread is:4 - main.cc:62

it turned on as i open it

louis-jan commented 4 months ago

Everything looks great. Please try running the app (jan-win-x64-0.4.6-270.exe) again. If any problems occur, please observe the app.log. Also, try using smaller models to see if the problem persists.

kucingkembar commented 4 months ago

same result

Starting model tinyllama-1.1b
Message queued. It can be sent once the model has started

any way to clean uninstall this software?

louis-jan commented 4 months ago

same result

Starting model tinyllama-1.1b
Message queued. It can be sent once the model has started

any way to clean uninstall this software?

Delete the entire jan data folder and exe should work. Could I ask for the app log at this point? Make sure its under App > Settings > Advanced Settings > Jan Data Folder > Folder Icon.

There is also a known issue related to this, where user's base path contains non-latin characters. Idk if this is the case https://github.com/janhq/jan/issues/1840#issuecomment-1914125406

kucingkembar commented 4 months ago

delete Jan folder at %username% and delete Jan folder at App > Settings > Advanced Settings > Jan Data Folder > Folder Icon (plus up button in explorer once) open jan-win-x64-0.4.6-270.exe

the result is still stuck at 

Starting model tinyllama-1.1b
Message queued. It can be sent once the model has started

if you need other tasks, i am happy to help, but I am so tired and need to sleep now

kucingkembar commented 4 months ago

tried jan-win-x64-0.4.6-271.exe still stuck at "Starting model"

louis-jan commented 4 months ago

tried jan-win-x64-0.4.6-271.exe still stuck at "Starting model"

Hi @kucingkembar, how is the app.log? Could you please help attach it here?

kucingkembar commented 4 months ago 
2024-02-15T13:24:12.779Z [NITRO]::Debug: Request to kill Nitro
2024-02-16T12:54:29.909Z [NITRO]::Debug: Request to kill Nitro
louis-jan commented 4 months ago 
2024-02-15T13:24:12.779Z [NITRO]::Debug: Request to kill Nitro
2024-02-16T12:54:29.909Z [NITRO]::Debug: Request to kill Nitro

Where did you obtain this information? Is it from the server screen or the app.log file? It appears to be from the server screen. Please locate the app log from Jan > Settings > Advanced Settings > Jan Data Folder

Screenshot 2024-02-16 at 20 05 54
kucingkembar commented 4 months ago

app.log, Untitled (note i modified it because the "\n" somehow not "writed") as i said before in previous reply:

delete Jan folder at %username%
and
delete Jan folder at App > Settings > Advanced Settings > Jan Data Folder > Folder Icon (plus up button in explorer once)
louis-jan commented 4 months ago

It's unusual not to have app.log written or very brief. Would you mind restarting your computer and trying to run the app again?

kucingkembar commented 4 months ago

it still tuck at this point Untitled

2024-02-15T13:24:12.779Z [NITRO]::Debug: Request to kill Nitro
2024-02-16T12:54:29.909Z [NITRO]::Debug: Request to kill Nitro
2024-02-16T13:11:43.944Z [NITRO]::Debug: Request to kill Nitro
louis-jan commented 4 months ago

@kucingkembar, it seems like you have a running service on port 3928. Please help check with netstat -ab. Remember to close all running nitro shells.

kucingkembar commented 4 months ago

sorry for late reply this is where jan is loading data

C:\WINDOWS\system32>netstat -ab Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:135 GIGABYTE:0 LISTENING RpcSs [svchost.exe] TCP 0.0.0.0:445 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 0.0.0.0:1688 GIGABYTE:0 LISTENING [KMSSS.exe] TCP 0.0.0.0:5040 GIGABYTE:0 LISTENING CDPSvc [svchost.exe] TCP 0.0.0.0:8080 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 0.0.0.0:49664 GIGABYTE:0 LISTENING [System] TCP 0.0.0.0:49665 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 0.0.0.0:49666 GIGABYTE:0 LISTENING Schedule [svchost.exe] TCP 0.0.0.0:49667 GIGABYTE:0 LISTENING EventLog [svchost.exe] TCP 0.0.0.0:49668 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:53 GIGABYTE:0 LISTENING [dnscrypt-proxy.exe] TCP 127.0.0.1:1001 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:9665 GIGABYTE:0 LISTENING [JDownloader2.exe] TCP 127.0.0.1:9666 GIGABYTE:0 LISTENING [JDownloader2.exe] TCP 127.0.0.1:12025 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12110 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12119 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12143 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12465 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12563 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12993 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12995 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:27275 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 127.0.0.1:54777 GIGABYTE:0 LISTENING [explorer.exe] TCP 127.0.0.1:54777 msmonplat:59216 ESTABLISHED [explorer.exe] TCP 127.0.0.1:56187 msmonplat:56188 ESTABLISHED [qbittorrent.exe] TCP 127.0.0.1:56188 msmonplat:56187 ESTABLISHED [qbittorrent.exe] TCP 127.0.0.1:59193 msmonplat:59194 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59194 msmonplat:59193 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59195 msmonplat:59196 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59196 msmonplat:59195 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59216 msmonplat:54777 ESTABLISHED [firefox.exe] TCP 172.29.192.1:139 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 172.29.192.1:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 192.168.1.7:139 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 192.168.1.7:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 192.168.1.7:29365 39.173.58.188:22548 TIME_WAIT TCP 192.168.1.7:29365 061239066122:39191 TIME_WAIT TCP 192.168.1.7:29365 178:23213 ESTABLISHED [qbittorrent.exe] TCP 192.168.1.7:29365 h180-200-080-095:14505 TIME_WAIT TCP 192.168.1.7:49693 55:https ESTABLISHED Can not obtain ownership information TCP 192.168.1.7:59292 a23-52-40-90:https CLOSE_WAIT [SearchHost.exe] TCP 192.168.1.7:59293 a23-215-35-25:https CLOSE_WAIT [SearchHost.exe] TCP 192.168.1.7:59294 a23-215-35-25:https CLOSE_WAIT [SearchHost.exe] TCP 192.168.1.7:59760 93:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:59788 192.168.1.10:8009 ESTABLISHED [msedge.exe] TCP 192.168.1.7:59810 dns:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60233 ec2-107-21-27-189:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60494 104.21.73.129:https TIME_WAIT TCP 192.168.1.7:60507 65:http TIME_WAIT TCP 192.168.1.7:60508 246:http TIME_WAIT TCP 192.168.1.7:60509 65:http TIME_WAIT TCP 192.168.1.7:60510 65:http TIME_WAIT TCP 192.168.1.7:60511 211:https TIME_WAIT TCP 192.168.1.7:60512 246:http TIME_WAIT TCP 192.168.1.7:60515 65:http TIME_WAIT TCP 192.168.1.7:60516 104.21.73.129:https ESTABLISHED [Jan.exe] TCP 192.168.1.7:60518 server-18-161-49-101:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60524 104.18.42.54:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60525 192.229.232.240:http ESTABLISHED CryptSvc [svchost.exe] TCP 192.168.1.7:60527 ip210-145-163:https ESTABLISHED Can not obtain ownership information TCP 192.168.1.7:60528 bras-109-160-25-42:29365 SYN_SENT [qbittorrent.exe] TCP 192.168.1.7:62656 20.198.119.84:https ESTABLISHED WpnService [svchost.exe] TCP [::]:135 GIGABYTE:0 LISTENING RpcSs [svchost.exe] TCP [::]:445 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::]:1688 GIGABYTE:0 LISTENING [KMSSS.exe] TCP [::]:8080 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP [::]:49664 GIGABYTE:0 LISTENING [System] TCP [::]:49665 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::]:49666 GIGABYTE:0 LISTENING Schedule [svchost.exe] TCP [::]:49667 GIGABYTE:0 LISTENING EventLog [svchost.exe] TCP [::]:49668 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:53 GIGABYTE:0 LISTENING [dnscrypt-proxy.exe] TCP [::1]:9666 GIGABYTE:0 LISTENING [JDownloader2.exe] TCP [::1]:12025 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12110 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12119 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12143 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12465 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12563 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12993 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12995 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:27275 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP [fe80::2eb0:53d9:ebd8:c85c%24]:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] UDP 0.0.0.0:500 *:* IKEEXT [svchost.exe] UDP 0.0.0.0:4500 *:* IKEEXT [svchost.exe] UDP 0.0.0.0:5050 *:* CDPSvc [svchost.exe] UDP 0.0.0.0:5353 *:* Dnscache [svchost.exe] UDP 0.0.0.0:5355 *:* Dnscache [svchost.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:49541 *:* Dnscache [svchost.exe] UDP 127.0.0.1:53 *:* [dnscrypt-proxy.exe] UDP 127.0.0.1:1900 *:* SSDPSRV [svchost.exe] UDP 127.0.0.1:29365 *:* [qbittorrent.exe] UDP 127.0.0.1:49664 127.0.0.1:49664 iphlpsvc [svchost.exe] UDP 127.0.0.1:59494 *:* SSDPSRV [svchost.exe] UDP 172.29.192.1:137 *:* Can not obtain ownership information UDP 172.29.192.1:138 *:* Can not obtain ownership information UDP 172.29.192.1:1900 *:* SSDPSRV [svchost.exe] UDP 172.29.192.1:29365 *:* [qbittorrent.exe] UDP 172.29.192.1:59492 *:* SSDPSRV [svchost.exe] UDP 192.168.1.7:137 *:* Can not obtain ownership information UDP 192.168.1.7:138 *:* Can not obtain ownership information UDP 192.168.1.7:1900 *:* SSDPSRV [svchost.exe] UDP 192.168.1.7:1900 *:* [qbittorrent.exe] UDP 192.168.1.7:29365 *:* [qbittorrent.exe] UDP 192.168.1.7:58604 *:* [qbittorrent.exe] UDP 192.168.1.7:58605 *:* [qbittorrent.exe] UDP 192.168.1.7:59493 *:* SSDPSRV [svchost.exe] UDP [::]:500 *:* IKEEXT [svchost.exe] UDP [::]:4500 *:* IKEEXT [svchost.exe] UDP [::]:5353 *:* Dnscache [svchost.exe] UDP [::]:6771 *:* [qbittorrent.exe] UDP [::]:6771 *:* [qbittorrent.exe] UDP [::]:49541 *:* Dnscache [svchost.exe] UDP [::1]:53 *:* [dnscrypt-proxy.exe] UDP [::1]:1900 *:* SSDPSRV [svchost.exe] UDP [::1]:29365 *:* [qbittorrent.exe] UDP [::1]:60600 *:* SSDPSRV [svchost.exe] UDP [fe80::2eb0:53d9:ebd8:c85c%24]:1900 *:* SSDPSRV [svchost.exe] UDP [fe80::2eb0:53d9:ebd8:c85c%24]:29365 *:* [qbittorrent.exe] UDP [fe80::2eb0:53d9:ebd8:c85c%24]:60599 *:* SSDPSRV [svchost.exe]

and this where jan not running

C:\WINDOWS\system32>netstat -ab Active Connections Proto Local Address Foreign Address State TCP 0.0.0.0:135 GIGABYTE:0 LISTENING RpcSs [svchost.exe] TCP 0.0.0.0:445 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 0.0.0.0:1688 GIGABYTE:0 LISTENING [KMSSS.exe] TCP 0.0.0.0:5040 GIGABYTE:0 LISTENING CDPSvc [svchost.exe] TCP 0.0.0.0:8080 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 0.0.0.0:49664 GIGABYTE:0 LISTENING [System] TCP 0.0.0.0:49665 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 0.0.0.0:49666 GIGABYTE:0 LISTENING Schedule [svchost.exe] TCP 0.0.0.0:49667 GIGABYTE:0 LISTENING EventLog [svchost.exe] TCP 0.0.0.0:49668 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:53 GIGABYTE:0 LISTENING [dnscrypt-proxy.exe] TCP 127.0.0.1:1001 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:9665 GIGABYTE:0 LISTENING [JDownloader2.exe] TCP 127.0.0.1:9666 GIGABYTE:0 LISTENING [JDownloader2.exe] TCP 127.0.0.1:12025 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12110 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12119 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12143 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12465 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12563 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12993 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:12995 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:27275 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 127.0.0.1:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 127.0.0.1:54777 GIGABYTE:0 LISTENING [explorer.exe] TCP 127.0.0.1:54777 msmonplat:59216 ESTABLISHED [explorer.exe] TCP 127.0.0.1:56187 msmonplat:56188 ESTABLISHED [qbittorrent.exe] TCP 127.0.0.1:56188 msmonplat:56187 ESTABLISHED [qbittorrent.exe] TCP 127.0.0.1:59193 msmonplat:59194 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59194 msmonplat:59193 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59195 msmonplat:59196 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59196 msmonplat:59195 ESTABLISHED [firefox.exe] TCP 127.0.0.1:59216 msmonplat:54777 ESTABLISHED [firefox.exe] TCP 172.29.192.1:139 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 172.29.192.1:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 192.168.1.7:139 GIGABYTE:0 LISTENING Can not obtain ownership information TCP 192.168.1.7:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP 192.168.1.7:29365 39.173.58.188:25757 TIME_WAIT TCP 192.168.1.7:29365 061239066122:40527 TIME_WAIT TCP 192.168.1.7:29365 178:23213 ESTABLISHED [qbittorrent.exe] TCP 192.168.1.7:49693 55:https ESTABLISHED Can not obtain ownership information TCP 192.168.1.7:59292 a23-52-40-90:https CLOSE_WAIT [SearchHost.exe] TCP 192.168.1.7:59293 a23-215-35-25:https CLOSE_WAIT [SearchHost.exe] TCP 192.168.1.7:59294 a23-215-35-25:https CLOSE_WAIT [SearchHost.exe] TCP 192.168.1.7:59760 93:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:59788 192.168.1.10:8009 ESTABLISHED [msedge.exe] TCP 192.168.1.7:59810 dns:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60516 104.21.73.129:https ESTABLISHED [Jan.exe] TCP 192.168.1.7:60532 91.194.110.3:https ESTABLISHED [JDownloader2.exe] TCP 192.168.1.7:60547 104.22.76.171:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60548 104.22.54.87:https TIME_WAIT TCP 192.168.1.7:60550 104.22.54.87:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60551 104.22.54.87:https TIME_WAIT TCP 192.168.1.7:60553 104.22.54.87:https TIME_WAIT TCP 192.168.1.7:60554 172.67.75.105:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60555 server-18-161-49-101:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60558 si-in-f99:https TIME_WAIT TCP 192.168.1.7:60560 si-in-f94:http ESTABLISHED [firefox.exe] TCP 192.168.1.7:60561 si-in-f99:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60564 152.195.38.76:http ESTABLISHED [firefox.exe] TCP 192.168.1.7:60566 cdn-185-199-109-154:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60581 cdn-185-199-109-133:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60589 lb-140-82-113-26-iad:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60591 edge-star-shv-02-cgk1:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60592 edge-star-mini-shv-02-cgk1:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60593 ec2-34-232-26-170:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60594 ec2-18-213-135-113:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:60595 ip210-145-163:https ESTABLISHED Can not obtain ownership information TCP 192.168.1.7:60596 ec2-107-21-27-189:https ESTABLISHED [firefox.exe] TCP 192.168.1.7:62656 20.198.119.84:https ESTABLISHED WpnService [svchost.exe] TCP [::]:135 GIGABYTE:0 LISTENING RpcSs [svchost.exe] TCP [::]:445 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::]:1688 GIGABYTE:0 LISTENING [KMSSS.exe] TCP [::]:8080 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP [::]:49664 GIGABYTE:0 LISTENING [System] TCP [::]:49665 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::]:49666 GIGABYTE:0 LISTENING Schedule [svchost.exe] TCP [::]:49667 GIGABYTE:0 LISTENING EventLog [svchost.exe] TCP [::]:49668 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:53 GIGABYTE:0 LISTENING [dnscrypt-proxy.exe] TCP [::1]:9666 GIGABYTE:0 LISTENING [JDownloader2.exe] TCP [::1]:12025 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12110 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12119 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12143 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12465 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12563 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12993 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:12995 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:27275 GIGABYTE:0 LISTENING Can not obtain ownership information TCP [::1]:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] TCP [fe80::2eb0:53d9:ebd8:c85c%24]:29365 GIGABYTE:0 LISTENING [qbittorrent.exe] UDP 0.0.0.0:500 *:* IKEEXT [svchost.exe] UDP 0.0.0.0:4500 *:* IKEEXT [svchost.exe] UDP 0.0.0.0:5050 *:* CDPSvc [svchost.exe] UDP 0.0.0.0:5353 *:* Dnscache [svchost.exe] UDP 0.0.0.0:5355 *:* Dnscache [svchost.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:6771 *:* [qbittorrent.exe] UDP 0.0.0.0:49681 142.251.10.95:443 [msedge.exe] UDP 127.0.0.1:53 *:* [dnscrypt-proxy.exe] UDP 127.0.0.1:1900 *:* SSDPSRV [svchost.exe] UDP 127.0.0.1:29365 *:* [qbittorrent.exe] UDP 127.0.0.1:49664 127.0.0.1:49664 iphlpsvc [svchost.exe] UDP 127.0.0.1:59494 *:* SSDPSRV [svchost.exe] UDP 172.29.192.1:137 *:* Can not obtain ownership information UDP 172.29.192.1:138 *:* Can not obtain ownership information UDP 172.29.192.1:1900 *:* SSDPSRV [svchost.exe] UDP 172.29.192.1:29365 *:* [qbittorrent.exe] UDP 172.29.192.1:59492 *:* SSDPSRV [svchost.exe] UDP 192.168.1.7:137 *:* Can not obtain ownership information UDP 192.168.1.7:138 *:* Can not obtain ownership information UDP 192.168.1.7:1900 *:* [qbittorrent.exe] UDP 192.168.1.7:1900 *:* SSDPSRV [svchost.exe] UDP 192.168.1.7:29365 *:* [qbittorrent.exe] UDP 192.168.1.7:58604 *:* [qbittorrent.exe] UDP 192.168.1.7:58605 *:* [qbittorrent.exe] UDP 192.168.1.7:59493 *:* SSDPSRV [svchost.exe] UDP [::]:500 *:* IKEEXT [svchost.exe] UDP [::]:4500 *:* IKEEXT [svchost.exe] UDP [::]:5353 *:* Dnscache [svchost.exe] UDP [::]:6771 *:* [qbittorrent.exe] UDP [::]:6771 *:* [qbittorrent.exe] UDP [::1]:53 *:* [dnscrypt-proxy.exe] UDP [::1]:1900 *:* SSDPSRV [svchost.exe] UDP [::1]:29365 *:* [qbittorrent.exe] UDP [::1]:60600 *:* SSDPSRV [svchost.exe] UDP [fe80::2eb0:53d9:ebd8:c85c%24]:1900 *:* SSDPSRV [svchost.exe] UDP [fe80::2eb0:53d9:ebd8:c85c%24]:29365 *:* [qbittorrent.exe] UDP [fe80::2eb0:53d9:ebd8:c85c%24]:60599 *:* SSDPSRV [svchost.exe] C:\WINDOWS\system32>

Note : i use the nighty version, so it always (auto) updated

louis-jan commented 4 months ago

@kucingkembar. Could you please help attach your computer specs here again. Sorry forgot to ask this earlier

kucingkembar commented 4 months ago

System Information : Current Date/Time: 20 February 2024, 21:59:06 Computer Name: GIGABYTE Operating System: Windows 11 Pro 64-bit (10.0, Build 22000) Language: English (Regional Setting: English) System Manufacturer: Gigabyte Technology Co., Ltd. System Model: H97-Gaming 3 BIOS: BIOS Date: 04/21/15 10:37:53 Ver: 04.06.05 Processor: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz (4 CPUs), ~3.2GHz Memory: 16384MB RAM Page file: 16165MB used, 2501MB available DirectX Version: DirectX 12

GPU : Chip Type: NVIDIA GeForce GTX 1660 SUPER DAC Type: Integrated RAMDAC Device Type: Full Display Device Approx. Total Memory: 14098 MB Display Memory (VRAM): 5981 MB Shared Memory: 8117 MB

louis-jan commented 4 months ago

That's weird, could I ask for your discord ID so we can continue the debug session there. You can find me on Jan Discord as well.

kucingkembar commented 4 months ago

i dont have discord, do i need one? anyway i using this before 2024 seems fine, and using trinity-v1.2-7b (size : 4gb)

but after update in January the load are stuck, even i using tinyllama-1.1b (700mb) in task manager : my free memory about 8+gb

louis-jan commented 4 months ago

i dont have discord, do i need one? anyway i using this before 2024 seems fine, and using trinity-v1.2-7b (size : 4gb)

but after update in January the load are stuck, even i using tinyllama-1.1b (700mb) in task manager : my free memory about 8+gb

nvm, we can keep discussing here, could I get the latest log (after restarted, latest nightly build 276). Do you have curl installed or Postman here? We can try with raw curl.

kucingkembar commented 4 months ago

app.log

2024-02-17T09:45:50.524Z [NITRO]::Debug: Request to kill Nitro
2024-02-17T11:08:25.556Z [NITRO]::Debug: Request to kill Nitro
2024-02-18T16:00:37.531Z [NITRO]::Debug: Request to kill Nitro
2024-02-19T14:26:49.727Z [NITRO]::Debug: Request to kill Nitro
2024-02-20T14:39:23.090Z [NITRO]::Debug: Request to kill Nitro
2024-02-20T14:48:47.329Z [NITRO]::Debug: Request to kill Nitro
2024-02-20T14:48:47.375Z [NITRO]::Debug: Nitro process is terminated
2024-02-20T15:07:54.835Z [NITRO]::Debug: Request to kill Nitro
2024-02-20T15:16:20.152Z [NITRO]::Debug: Request to kill Nitro

for the curl or Postman, i don't have both, sorry, I think lineality better explain this rather myself, he probably has the software installed

louis-jan commented 4 months ago

Could you try installing a CUDA version that is the same as the driver, please, @kucingkembar? Also please try run WMIC CPU Get NumberOfCores to see how is the outputs.

kucingkembar commented 3 months ago

sorry for late reply . 1."Could you try installing a CUDA version that is the same as the driver" <= update latest both cuda and GPU driver?

  1. Also please try run WMIC CPU Get NumberOfCores to see how is the outputs. as i already typed => Processor: Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz (4 CPUs), ~3.2GHz CPU Get NumberOfCores NumberOfCores 4
kucingkembar commented 3 months ago

hi, i tried "Jan v0.4.8-328" the program running good, yay

Van-QA commented 3 months ago

thank everyone, I'm closing this as the issue seems to be resolved, feel free to reopen it if the issue persist 🙏