jan

jan copied to clipboard

have same issue with any model

System: Kernel: 5.15.0-91-generic x86_64 bits: 64 compiler: gcc v: 11.4.0 Desktop: Xfce 4.18.1 tk: Gtk 3.24.33 wm: xfwm dm: LightDM Distro: Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy

related issue: #1289

related issue: #1187

How exactly are we solving this common issue @tikikun ?

Namely, are we doing:

• Better error propagation
• What is the OS support matrix?
• From a docs perspective what needs to be documented for users to download the correct models?

Case resolved: https://discord.com/channels/1107178041848909847/1189918006978027613 Case resolved: https://discord.com/channels/1107178041848909847/1190900451353309285/1190966272742146148

Investigated: https://discord.com/channels/1107178041848909847/1190968143334617118

Hi @jasobih, regarding your case, it seems like this one #1187

Case resolved: https://discord.com/channels/1107178041848909847/1192366847446753330

Same Issue on Mixtral 8 x 7B Instruct Q4, Latest rev of Jan.AI, Windows 11: Error: Same a above on chat: Error in code:

× POST http://127.0.0.1:3928/inferences/11amaccp/chat_c index.js:2055 completion net::ERR_CONNECTION_REFUSED (anonymous) Observable._trySubscribe index.js:1971 (anonymous) errorContext index.js:1790 Observable.subscribe index.js:1956 (anonymous) src_awaiter handleMesssageRequest index.js:2275 (anonymous) src_awaiter handleMesssageRequest index.js:2419 (anonymous) emit layout-e26c604d515b7785.js:421 emit layout-e26c604d515b7785.js:420 resendChatMessage 766-0ac4a7e7b205a3b7.js:313 onRegenerateClick page-a61f2038757c5661.js:2149 await in onRegenerateClick (async) Hi 618f8807-c0370e0f59991ad5.js:209 Ni 618f8807-c0370e0f59991ad5.js:210 Oi 618f8807-c0370e0f59991ad5.js:210 Nn 618f8807-c0370e0f59991ad5.js:347 Zm 618f8807-c0370e0f59991ad5.js:348 (anonymous) Ak 618f8807-c0370e0f59991ad5.js:259 Il 618f8807-c0370e0f59991ad5.js:261 zm 618f8807-c0370e0f59991ad5.js:304 xm 618f8807-c0370e0f59991ad5.js:351 wm 618f8807-c0370e0f59991ad5.js:325

Hi, I encounter the same issue.

I did open the dev tools and found an interesting bit:

Checking if something is listening on that port confirms us that it‘s not the case:

❯ lsof -Pi4 | grep 3928

❯ 

Next I tried to launch Jan.app from the CLI to see if I get some log, and indeed:

❯ /Applications/Jan.app/Contents/MacOS/Jan
Checking for update
[65741:0115/192430.345970:ERROR:trust_store_mac.cc(750)] Error parsing certificate:
ERROR: Failed parsing extensions

Update for version 0.4.3 is not available (latest version: 0.4.3, downgrade is disallowed).
Start requesting to kill Nitro...
Nitro is killed
Starting Nitro subprocess...
subprocess error:dyld: Symbol not found: __ZTTNSt3__114basic_ifstreamIcNS_11char_traitsIcEEEE
  Referenced from: /Users/mathieu/jan/extensions/@janhq/inference-nitro-extension/dist/bin/mac-x64/nitro (which was built for Mac OS X 12.7)
  Expected in: /usr/lib/libc++.1.dylib
 in /Users/mathieu/jan/extensions/@janhq/inference-nitro-extension/dist/bin/mac-x64/nitro

stderr: dyld: Symbol not found: __ZTTNSt3__114basic_ifstreamIcNS_11char_traitsIcEEEE
  Referenced from: /Users/mathieu/jan/extensions/@janhq/inference-nitro-extension/dist/bin/mac-x64/nitro (which was built for Mac OS X 12.7)
  Expected in: /usr/lib/libc++.1.dylib
 in /Users/mathieu/jan/extensions/@janhq/inference-nitro-extension/dist/bin/mac-x64/nitro

child process exited with code null
error:  child process exited with code null
(node:65741) UnhandledPromiseRejectionWarning: Error: timeout
    at Timeout.timeoutFunc (/Users/mathieu/jan/extensions/@janhq/inference-nitro-extension/node_modules/tcp-port-used/index.js:204:25)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
(Use `Jan --trace-warnings ...` to show where the warning was created)
(node:65741) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)

So this seems related to an embedded binary "nitro" that is crashing on startup.

Hope this helps