Bug 8274 - ResourceWarning if stopping vsmserver/vsmagent with active client
Summary: ResourceWarning if stopping vsmserver/vsmagent with active client
Status: NEW
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Other (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: LowPrio
Assignee: Bugzilla mail exporter
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-28 11:19 CET by Pierre Ossman
Modified: 2024-01-02 13:05 CET (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Pierre Ossman cendio 2023-12-28 11:19:43 CET
(moved from bug 7636:)

If you shut down the service with an active connection, then you get a ResourceWarning for that socket and transport:

> 2023-12-28 10:05:41 INFO vsmserver: Got SIGTERM, signaling process to quit
> 2023-12-28 10:05:41 INFO vsmserver: Terminating. Have a nice day!
> sys:1: ResourceWarning: unclosed <socket.socket fd=6, family=10, type=1, proto=6, laddr=('::1', 9000, 0, 0), raddr=('::1', 60516, 0, 0)>
> ResourceWarning: Enable tracemalloc to get the object allocation traceback
> /usr/lib64/python3.12/asyncio/selector_events.py:875: ResourceWarning: unclosed transport <_SelectorSocketTransport fd=6>
>   _warn(f"unclosed transport {self!r}", ResourceWarning, source=self)
> ResourceWarning: Enable tracemalloc to get the object allocation traceback

There doesn't seem to be any mechanism to terminate ongoing connections. I've reported this problem here:

https://github.com/python/cpython/issues/113538
Comment 1 Pierre Ossman cendio 2023-12-28 12:43:55 CET
Also note bug 8224, comment 80, where a similar issue occurred and was (mostly?) resolved. In that case, the issue was with outgoing connections, whilst this bug here is about incoming connections.

Note You need to log in before you can comment on or make changes to this bug.