Following the “Connect Two Sparks” playbook. Once I connect the cable and run netplan, I lose the capability to use Nvidia Sync though the wireless connection remains up (i.e. I can reach the internet from the device). Seems that a network configuration problem. Any assistance ?
Hi, what message do you see from NV Sync?
Nvidia Sync responds with Unexpected Error and recommends me to check logs. Here is the relevant part of the log:
{“level”:“info”,“time”:“2025-12-05T13:27:11.093Z”,“source”:“api-utils”,“message”:[“Connect response:”,{“success”:false,“error”:{“message”:“Process exited with code 1”,“code”:1},“code”:1,“stderr”:“{\n “type”: “error”,\n “heading”: “Unexpected Error”,\n “details”: “not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”\n}\n”,“stdout”:“”}]}
{“level”:“error”,“time”:“2025-12-05T13:27:11.094Z”,“source”:“api-utils”,“message”:[“Connect command failed:”,{“success”:false,“error”:{“message”:“Process exited with code 1”,“code”:1},“code”:1,“stderr”:“{\n “type”: “error”,\n “heading”: “Unexpected Error”,\n “details”: “not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”\n}\n”,“stdout”:“”}]}
{“level”:“error”,“time”:“2025-12-05T13:27:11.118Z”,“source”:“main:libs:api”,“message”:[“Connection failed:”,{“rawError”:“{\n “type”: “error”,\n “heading”: “Unexpected Error”,\n “details”: “not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”\n}\n”}]}
{“level”:“error”,“time”:“2025-12-05T13:27:11.143Z”,“source”:“main:libs:api”,“message”:[“Error connecting device”,{“__syncIpcError”:true,“output”:“{\n “type”: “error”,\n “heading”: “Unexpected Error”,\n “details”: “not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”\n}\n”,“logPath”:“/Users/hdb/Library/Application Support/NVIDIA/Sync/session/nvsync.log”,“header”:“Unexpected Error”,“detail”:“not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”,“message”:“Unexpected Error: not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”,“name”:“SyncIpcError”}]}
{“level”:“error”,“time”:“2025-12-05T13:27:11.328Z”,“source”:“main:libs:api”,“message”:[“Error in API endpoint”,“connectDevice”,{“__syncIpcError”:true,“output”:“{\n “type”: “error”,\n “heading”: “Unexpected Error”,\n “details”: “not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”\n}\n”,“logPath”:“/Users/hdb/Library/Application Support/NVIDIA/Sync/session/nvsync.log”,“header”:“Unexpected Error”,“detail”:“not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”,“message”:“Unexpected Error: not connected, check logs at /Users/hdb/Library/Application Support/NVIDIA/Sync/logs/nvsync.log”,“name”:“SyncIpcError”}]}
{“level”:“error”,“time”:“2025-12-05T13:27:11.336Z”,“source”:“main:window”,“message”:[“connectDevice error:”,{“success”:false,“code”:1,“stderr”:“Failed to connect to device”}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.382Z”,“source”:“main:init-window-events”,“message”:[“resize-window”,295]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.383Z”,“source”:“tray”,“message”:[“Setting main window position, provided height:”,295]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.411Z”,“source”:“tray”,“message”:[“Using height:”,295,“stored height:”,140]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.413Z”,“source”:“tray”,“message”:[“Current tray bounds:”,{“x”:-710,“y”:0,“width”:32,“height”:30}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.436Z”,“source”:“tray”,“message”:[“Current cursor point:”,{“x”:-693,“y”:12}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.438Z”,“source”:“tray”,“message”:[“macOS positioning debug:”,{“trayBounds”:{“x”:-710,“y”:0,“width”:32,“height”:30},“display”:{“scaleFactor”:2,“workArea”:{“x”:-1920,“y”:30,“width”:1920,“height”:1050},“bounds”:{“x”:-1920,“y”:0,“width”:1920,“height”:1080},“targetDisplayId”:2,“trayDisplayId”:2,“useTrayAnchor”:true},“calculatedPosition”:{“x”:-857,“y”:30,“width”:327,“height”:295},“margin”:10}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.461Z”,“source”:“tray”,“message”:[“Calculated window position for macOS:”,{“requested”:{“x”:-857,“y”:-305,“width”:327,“height”:295},“clamped”:{“x”:-857,“y”:30}}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.463Z”,“source”:“tray”,“message”:[“needsPositionUpdate”,{“height”:140,“x”:-857,“y”:30,“newHeight”:295,“newX”:-857,“newY”:30}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.485Z”,“source”:“tray”,“message”:[“needsPositionUpdate”,true]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.487Z”,“source”:“tray”,“message”:[“needsPositionUpdate”,{“height”:140,“x”:-857,“y”:30,“newHeight”:295,“newX”:-857,“newY”:30}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.509Z”,“source”:“tray”,“message”:[“updateWindowPosition called with height:”,295]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.510Z”,“source”:“create-window”,“message”:[“Blur hiding disabled for main window”]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.534Z”,“source”:“tray”,“message”:[“Current window state:”,{“windowBounds”:{“x”:-857,“y”:30,“width”:327,“height”:140},“contentBounds”:{“x”:-857,“y”:30,“width”:327,“height”:140},“requestedSize”:{“width”:327,“height”:295},“requestedPosition”:{“x”:-857,“y”:30}}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.535Z”,“source”:“tray”,“message”:[“Setting window size to:”,327,295,“from current:”,327,140]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.787Z”,“source”:“tray”,“message”:[“After setting size:”,{“windowBounds”:{“x”:-857,“y”:30,“width”:327,“height”:295},“contentBounds”:{“x”:-857,“y”:30,“width”:327,“height”:295},“sizeDifference”:{“width”:0,“height”:0}}]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.790Z”,“source”:“create-window”,“message”:[“Blur hiding enabled for main window”]}
{“level”:“info”,“time”:“2025-12-05T13:27:11.846Z”,“source”:“tray”,“message”:[“Updated window position in activeWindows for macOS”]}
{“level”:“info”,“time”:“2025-12-05T13:27:34.943Z”,“source”:“create-window”,“message”:[“Hiding main window on macOS after blur and no refocus”]}
Thank you for your kind attention @aniculescu
Also note that this problem started after performing the Network Interface Configuration step (step 3) in the Connect Two Sparks playbook. And as soon as I roll back the configuration (per step 6) the problem goes away. Seems that there is an incomplete specification in network interface configuration templates presented that cause an incorrect routing with wireless connection present and used for Sync.
Which method do you use to configure the network? Can you also send me the logs from nvsync.log? The log you sent looks like its from the desktop log
I did use option two. The log snippet was from nvsync.log at the client machine.
I did solve the issue. Here is the reason for everyone’s benefit: When you set up the ip numbers for the fiber ports do NOT assign ip numbers that are on the same subnet of the wireless ip number. As soon as you change this to a different ip range (for all of the fiber ports on each machine) then both the fiber connectivity is established and wireless inbound traffic is replied through the correct nic.
Hope this helps. Should have been mentioned in the playbook.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.