SageTV client crashing on attempt to connect

[dinki]

Hey guys. I've installed sagetv-client_9.2.2_amd64.deb on my Linux Mint machine. The gui fires up fine and I see my STV server as expected. I try connecting to it and the window disappears. I took a look at the logs and this is what I see:

Starting MiniClient
Mon 8/10 7:38:00.984 Detecting cryptography support...
Mon 8/10 7:38:01.802 Sending out discovery packets to find SageTVPlaceshifter Servers...
Mon 8/10 7:38:01.807 Starting SageTVPlaceshifter Client
Mon 8/10 7:38:01.809 Starting main loop
Mon 8/10 7:38:01.809 StorageDeviceDetector started...
Mon 8/10 7:38:01.832 Discovery packet received:java.net.DatagramPacket@13b57386
Mon 8/10 7:38:01.858 Added server info:192.168.0.25 192.168.0.25
Mon 8/10 7:38:11.813 Sending out discovery packets to find SageTVPlaceshifter Servers...
Mon 8/10 7:38:11.816 Discovery packet received:java.net.DatagramPacket@1362c403
Mon 8/10 7:38:11.883 Added server info:192.168.0.25 192.168.0.25
Mon 8/10 7:38:18.735 Attempting to connect to server at 192.168.0.25:31099
Mon 8/10 7:38:18.749 Connection accepted by server
Mon 8/10 7:38:18.749 Connected to media server
Mon 8/10 7:38:18.750 Connection accepted by server
Mon 8/10 7:38:18.750 Connected to gfx server
Mon 8/10 7:38:18.856 Loaded
Type size error: sizeof(jint) < sizeof(size_t)
Type size error: sizeof(jint) < sizeof(ssize_t)
Type size error: sizeof(jint) < sizeof(ino_t)
Type size error: sizeof(jint) < sizeof(nlink_t)
Type size error: sizeof(jint) < sizeof(blksize_t)
Type size error: sizeof(jint) < sizeof(nfds_t)
Type size error: sizeof(jint) < sizeof(msgqnum_t)
Type size error: sizeof(jint) < sizeof(msglen_t)
Type size error: sizeof(int) < sizeof(ino_t)
JTUX: We are running in 64bit mode, and JTUX is untested in 64bit mode.  There may be side effects.
Mon 8/10 7:38:18.860 Starting MiniLIRC
Mon 8/10 7:38:18.863 Exception in MiniLIRC: No such file or directory (ENOENT)
Mon 8/10 7:38:18.866 Creating opengl renderer
Mon 8/10 7:38:18.866 Native order: LITTLE_ENDIAN
Mon 8/10 7:38:18.867 Testing to see if server can do a pull mode streaming connection...
Mon 8/10 7:38:18.868 Server can do a pull-mode streaming connection.
Mon 8/10 7:38:18.876 Max screen size=java.awt.Dimension[width=1920,height=1080]
Mon 8/10 7:38:18.879 Staring video server
Mon 8/10 7:38:18.896 Temp file:/tmp/sagevideo17342831549347611601
Mon 8/10 7:38:18.897 Trying to accept fd: 31
Mon 8/10 7:38:18.926 Native order: LITTLE_ENDIAN
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.jogamp.common.os.NativeLibrary$3 (file:/opt/sagetv/client/gluegen-rt-2.3.1.jar) to method java.lang.ClassLoader.findLibrary(java.lang.String)
WARNING: Please consider reporting this to the maintainers of com.jogamp.common.os.NativeLibrary$3
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
Inconsistency detected by ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! _dl_name_match_p (version->filename, map)' failed!

Server is running in a Docker container. I am able to connect and use it fine with the SageTV miniclient on my FireTV.

Can anyone tell me what might be going wrong?

[dinki]

Circling back in the hopes someone can help. This is the last piece to get Sage working as I would like. Here's the sagetv log from when I try to connect:

Tue 9/1 7:28:16.553 [MiniUIServer@3a41eb3c] Dropping old MiniPlayer connection because it's old from:74d435e60f11
Tue 9/1 7:28:42.538 [SageTVMiniDiscoveryServer@1861b989] Server got broadcast packet: java.net.DatagramPacket@5e370855
Tue 9/1 7:28:42.541 [SageTVMiniDiscoveryServer@1861b989] Server sent back mini discovery data:java.net.DatagramPacket@5e370855 to /192.168.0.20 8271
Tue 9/1 7:28:45.655 [MiniUIServer@3a41eb3c] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.0.25:31099 remote=/192.168.0.20:54580]
Tue 9/1 7:28:45.663 [MiniUIServerConnection@25cad079] MiniPlayer is adding to its map:74d435e60f11
Tue 9/1 7:28:45.664 [MiniUIServer@3a41eb3c] MiniUI got connection from java.nio.channels.SocketChannel[connected local=/192.168.0.25:31099 remote=/192.168.0.20:54582]
Tue 9/1 7:28:45.664 [MiniUIServerConnection@25cad079] MiniUI is adding to its map:74d435e60f11
Tue 9/1 7:28:45.664 [MiniUIServerConnection@25cad079] Creating new UI for client:74d435e60f11
Tue 9/1 7:28:45.665 [MiniUIServerConnection@25cad079] Saving properties file to clients/74d435e60f11.properties
Tue 9/1 7:28:45.692 [MiniUIServerConnection@25cad079] Done writing out the data to the properties file
Tue 9/1 7:28:45.692 [MiniUIServerConnection@25cad079] Creating-2 new UI for client:74d435e60f11 UIManager:localhost@@74d435e60f11-310eed1e
Tue 9/1 7:28:45.785 [MediaServerConnection@36e6b9bb] Error in MediaServerConnection of :java.io.EOFException
Tue 9/1 7:28:45.785 [MediaServerConnection@36e6b9bb] java.io.EOFException
Tue 9/1 7:28:45.785 [MediaServerConnection@36e6b9bb]    at sage.MediaServer$Connection.readLineBytes(MediaServer.java:243)
Tue 9/1 7:28:45.785 [MediaServerConnection@36e6b9bb]    at sage.MediaServer$Connection.run(MediaServer.java:1008)
Tue 9/1 7:28:45.785 [MediaServerConnection@36e6b9bb]    at sage.Pooler$PooledThread.run(Pooler.java:254)
Tue 9/1 7:28:45.885 [MiniUIClientReceiver@1ceb43b8] Exception in the MiniUIClientReceiver of: java.io.EOFException
Tue 9/1 7:28:45.886 [MiniUIClientReceiver@1ceb43b8] java.io.EOFException
Tue 9/1 7:28:45.886 [MiniUIClientReceiver@1ceb43b8]     at sage.MiniClientSageRenderer$MiniUIClientReceiver.run(MiniClientSageRenderer.java:7753)
Tue 9/1 7:28:45.886 [KillUIMgr@36e6b9bb] Killing UIMgr UIManager:localhost@@74d435e60f11-310eed1e
Tue 9/1 7:28:45.886 [KillUIMgr@36e6b9bb] Error calling finishWatch from VF goodbye:java.lang.NullPointerException
Tue 9/1 7:28:45.886 [KillUIMgr@36e6b9bb] Killed VideoFrame
Tue 9/1 7:28:45.886 [KillUIMgr@36e6b9bb] Saving properties file to clients/74d435e60f11.properties
Tue 9/1 7:28:45.895 [KillUIMgr@36e6b9bb] Done writing out the data to the properties file
Tue 9/1 7:28:45.895 [KillUIMgr@36e6b9bb] Disposed Window
Tue 9/1 7:28:50.696 [MiniUIServerConnection@25cad079] MiniUI established for 74d435e60f11 status=false
Tue 9/1 7:28:50.697 [MiniUIServerConnection@25cad079] Splash: Rendering Engine is initializing...
Tue 9/1 7:28:50.697 [MiniUIServerConnection@25cad079] UIMgr was asynchronously killed during construction, re-destroy it now that init is done
Tue 9/1 7:28:50.697 [MiniUIServerConnection@25cad079] Killing UIMgr UIManager:localhost@@74d435e60f11-310eed1e
Tue 9/1 7:28:50.697 [MiniUIServerConnection@25cad079] Error calling finishWatch from VF goodbye:java.lang.NullPointerException
Tue 9/1 7:28:50.697 [MiniUIServerConnection@25cad079] Killed VideoFrame
Tue 9/1 7:28:51.197 [FinalRender-74d435e60f11@54bec81f] Terminating the BGResourceLoader for the rendering engine
Tue 9/1 7:28:51.198 [FinalRender-74d435e60f11@54bec81f] deinitMini()
Tue 9/1 7:28:52.697 [MiniUIServerConnection@25cad079] Killed RootPanel
Tue 9/1 7:28:52.697 [MiniUIServerConnection@25cad079] Saving properties file to clients/74d435e60f11.properties
Tue 9/1 7:28:52.732 [MiniUIServerConnection@25cad079] Done writing out the data to the properties file
Tue 9/1 7:28:52.732 [MiniUIServerConnection@25cad079] Disposed Window

and here's the properties file it references at the bottom:

#Sage Preferences
#Tue Sep 01 07:28:52 CDT 2020
force_nonlocal_connection=false
infrared_receive_repeat_delay=250
infrared_receive_repeat_delay_rc5=350
infrared_receive_repeat_period=120
keyboard_accelerators=
linux/load_default_input_plugins=true
ui/accelerated_rendering=false
ui/active_rendering_thread_priority_offset=-3
ui/awt_check_period=750
ui/awt_response_time=750
ui/disable_all_transparency=false
ui/display_wait_indicator=true
ui/final_rendering_thread_priority_offset=-2
ui/parallel_image_load_pause_time=200
ui/wait_icon_prefix=images/tvicon_anim
wheel_down_event_code=12
wheel_up_event_code=11
zzz=true

Can anyone tell me what I can do to get this working? Thanks!

[wnjj]

Looks like 64-bit placeshifter has never worked due to support libraries that aren’t 64-bit compatible.

https://forums.sagetv.com/forums/showthread.php?t=62344

.

[VCRUser]

This may be irrelevant to the OP's issue, but I have had a similar problem with PlaceShifter on Windows 7 (64 bit), but using an older 32-bit PlaceShifter. At any rate, sometimes it will take a few tries to get it to open. Since I usually open it near startup, and since Norton and probably a bunch of other stuff slows down my startup, I attribute the issue to all the other stuff going on; once the system startup completes, PlaceShifter opens as it should.

[Tiki]

One thing to remember is that you can use 32-bit placeshifter with a 64-bit server. And you can use 32-bit applications on a 64-bit operating system. So it’s not really a showstopper if 64-bit placeshifter doesn’t work.

[ojones]

OP - Assume you are not trying to run the client/placeshifter on the same machine (either VM or bare metal) as the docker instance is running? I'm not certain that is a supported scenario (IP/port conflict potentially; java issues?). I may be wrong but think all of the testing used different VMs.

There also were issues some time back where each client connection was assigned a unique port to listen on (each incremented one port; multiple connections from the same client sometimes got new ports each time). If you ended up with port overlap between the HTTP plugin and a real client bad things happened in Java land with very limited error codes.

You may want to run up a separate windows test machine (either VM or metal) to see if you can duplicate the issue on new hardware with a different version of the client/placeshifter.

[dinki]

Running Sage docker on my server and the machine I'm trying to run client on is a desktop Linux box. I do have a Win10 VM that I can install on to verify that it works there to eliminate the possibility that it is server related. I do use Miniclinet on my Firesticks and Android TV without problems so I'm guessing the Win10 client will work. Will report back. Thanks for the troubleshooting tips.

[ojones]

Best of luck with the desktop linux box!

I've had version mis-match errors before (my clumsiness installing the wrong executable) but I can't remember what kind of errors that threw out. I'm not sure how much use the full linux client is getting these days and/or potential dependencies that could be out of date (Java comes to mind).

While not desirable for your end goal a windows test would help eliminate server side vs client issues. Personally I ended up ditching the linux/docker server as file access performance via the full windows server was more reliable for my setup but I know many (most) swear by it!

[dinki]

Sounds like you had a bad Linux experience. I've had nothing but success stories with the exception of this one instance.