[Question] SSR Error in linux

HOOPS Communicator
1

I used developer zone 2023_SP2_U2 tar file.
And I un-tar the file.

When I access to the server like this:
http://192.168.0.162:11180/hoops_web_viewer_sample.html?viewer=ssr&model=arboleda

image

Sever tells me below error:
11/23/2023, 10:21:03 AM:warn: ts3d_sc_server failed: reason=‘failed to initialize the stream-cache’, exit-code=4, id=a8841455-3e88-43f4-9e48-e7dd270a7bd8
11/23/2023, 10:21:03 AM:error: file-server: proxy-error: Error: socket hang up

— sever_config.js —
publicHostname: ‘192.168.0.162’
ssrGpuCount: 2 // Machine has 2 GPU Card

Could you give me some clues?

2

Hello @monad1,

One recommendation would be to check the Communicator logs to see if there is additional information on the initialization error. You can find the log directory as indicated by the server cmd window:

communicator_logs
communicator_logs980×512 20.1 KB

Also, what type of Linux environment are you using? Desktop or server? Does client-side rendering (CSR) work?

Thanks,
Tino

1 Like
3

hello @tino ,
Thanks your reply.
Log file tells me

11/23/2023, 10:21:03 AM:warn: ts3d_sc_server failed: reason=‘failed to initialize the stream-cache’, exit-code=4, id=a8841455-3e88-43f4-9e48-e7dd270a7bd8
11/23/2023, 10:21:03 AM:error: file-server: proxy-error: Error: socket hang up

So, I think that the problem is networking setup issue.

  1. uname -a tells me like this:
    Linux 3d 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

    I installed Ubuntu Server 22.04.3

  2. CSR is OK

  3. The ubuntun machine has 2 GPU card.

Now I change the server_config.js:
ssrGpuCount: 2

And in one linux terminal “sudo /usr/bin/X :0 &” and “export DISPLAY=:0.0”

The result: SSR, CSR are OK.

I think the message “socket hang up” make me confused.
In my situation, “hoops communicator has no display” may be correct.

4

Review the logs generated by the server for more detailed error messages. The logs you provided indicate an issue with stream-cache initialization and a socket hang-up. More information in the logs might help pinpoint the problem. Check if there are any updates or patches available for the Hoops Web Viewer. Upgrading to the latest version may resolve known issues. Also try other options, for example buy proxies would be a great idea if you need access from different locations. Consider enabling debugging options in your server configuration to get more detailed information about what is causing the initialization failure. This could include increasing the log verbosity or enabling additional debug flags. Refer to the documentation of the Hoops Web Viewer and the specific version you are using. It may provide insights into common issues and their resolutions. You could also reach out to the support channels provided by the software for assistance.

1 Like