Re: [systemd-devel] socket failed to queue socket startup job: Transport endpoint is not connected
Albert Strasheim wrote: Any chance this can be rolled into an update for Fedora 16? Yes. systemd-37-10.fc16 is in updates-testing: https://admin.fedoraproject.org/updates/FEDORA-2012-0409 It's probably a bit tricky since journald landed in v38. I guess you would either have to branch off v37.1 for fixes only, or package v39 without enabling journald and related changes on F16? You are right that journald makes it a bit tricky. I maintain systemd in F16 using a local git branch I call 'f16'. I use: git format-patch -o $FEDPKG_SYSTEMD_DIR -N v37..f16 to export it as patch files for building the RPM package. I do not publish this 'f16' branch itself (should I?), but you can see the patch files stored in Fedora Git using: fedpkg clone -a systemd cd systemd # note that this is not the 'f16' mentioned above, # it's an entirely different repo: git checkout f16 Or browse: http://pkgs.fedoraproject.org/gitweb/?p=systemd.git;a=tree;h=refs/heads/f16 Regards, Michal ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] socket failed to queue socket startup job: Transport endpoint is not connected
On 01/21/2012 05:33 AM, Kay Sievers wrote: It needs to be backported to F16's version then. We usually do not do version updates in released products. What do you think are the pros and cons in such a model? JBG ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] socket failed to queue socket startup job: Transport endpoint is not connected
On Saturday 2012-01-21 12:23, Jóhann B. Guðmundsson wrote: On 01/21/2012 05:33 AM, Kay Sievers wrote: It needs to be backported to F16's version then. We usually do not do version updates in released products. What do you think are the pros and cons in such a model? Cons: workload to create the patches (not always is cherry-picking conflict-free), potential to screw it up while doing so (cf. iptables mess in debian etchnhalf),.. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] socket failed to queue socket startup job: Transport endpoint is not connected
On Sat, Jan 21, 2012 at 06:11, Albert Strasheim full...@gmail.com wrote: On Sat, Jan 21, 2012 at 5:05 AM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 18.01.12 12:06, Albert Strasheim (full...@gmail.com) wrote: Just for the sake of the Google archives: Michal fixed that in git today. That was quick. Thanks very much. Any chance this can be rolled into an update for Fedora 16? It's probably a bit tricky since journald landed in v38. I guess you would either have to branch off v37.1 for fixes only, or package v39 without enabling journald and related changes on F16? It needs to be backported to F16's version then. We usually do not do version updates in released products. Do you have a general plan for how systemd's quick development cycle is going to interact with distributions packaging slightly older versions and finding bugs? It's still some way off, but how is it going to work when someone finds a bug in RHEL 7's systemd? Bugs will be fixed in the package, independently for that version, or by backporting upstream fixes from newer versions. Upstream is usually not involved in releasing branches for older releases used in distributions. Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] socket failed to queue socket startup job: Transport endpoint is not connected
Hello all We've had a machine up for about 9 days with lots of connections to a socket unit: [Socket] ListenStream=2 Accept=yes MaxConnections=128 [Install] WantedBy=sockets.target We noticed today that the socket had stopped listening. syslog said: systemd[1]: foo.socket failed to queue socket startup job: Transport endpoint is not connected systemd[1]: Unit foo.socket entered failed state. systemctl status said: foo.socket Loaded: loaded (/etc/systemd/system/foo.socket; enabled) Active: failed since Wed, 18 Jan 2012 04:53:40 +; 5h 1min ago Accepted: 902; Connected: 0 What does this error mean? Should the socket be failing? We are running systemd v37 on Fedora 16. Regards Albert ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
