Transport endpoint

General
, , , ,
1

Good morning,

I would like to know whether there are any plans to address this error or an existing issue or discussion thread tracking it.

Whenever this error occurs, CasparCG stops receiving commands via AMCP. Would it be possible to restart the thread that handles AMCP commands so that it can start receiving commands again?

The error appears to occur when a client sends a command to CasparCG and closes the connection before receiving CasparCG’s response.

In my case, restarting CasparCG restores normal operation. This is the only workaround I know of.

[2026-10-28 22:12:01.094] [error] Exception: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
[2026-10-28 22:12:01.094] [error] Dynamic exception type: boost::wrapexceptboost::system::system_error
[2026-10-28 22:12:01.094] [error] std::exception::what: remote_endpoint: Transport endpoint is not connected
[2026-10-28 22:12:01.094] [error]
[2026-10-28 22:12:01.094] [error] 0# 0x00005FB6EE93C170 in casparcg-server-2.4
[2026-10-28 22:12:01.094] [error] 1# 0x00005FB6EE8D176E in casparcg-server-2.4
[2026-10-28 22:12:01.094] [error] 2# 0x000073A65C8DC253 in /lib/x86_64-linux-gnu/libstdc++.so.6
[2026-10-28 22:12:01.094] [error] 3# 0x000073A65C494AC3 in /lib/x86_64-linux-gnu/libc.so.6
[2026-10-28 22:12:01.094] [error] 4# 0x000073A65C5268C0 in /lib/x86_64-linux-gnu/libc.so.6
[2026-10-28 22:12:01.094] [error]

2

See this discussion on GitHub.

3

@MarceloCarvalho does this still happen with the latest release? The backtrace shows you are running 2.4 and the latest is 2.5.1.

This should be easy to fix, once you confirm.

4

@dimitry_ishenko

Yes, I’m using 2.4.3 on Linux 22.04

5

That PR is closed now on github, so we will need to continue that discussion elsewhere. I would support a modularization effort with proper c++ watchdog processes and wrappers with modules for communications, etc. I do think we need to complete the current stability efforts and I think the closed captions feature merge and vulkan feature merges are slightly more important to focus on. Once I get my current crop of PR’s and improvements built and delivered I would be interested in exploring an effort like this.

We do need to deliver a 2.5 or 2.6 executable though that is rock solid and fully production ready first though which hopefully will be available whenever 2.5.2 comes out.