From 8202eeb574437efe8bfdb50edc63d7012878d954 Mon Sep 17 00:00:00 2001 From: "jk@3f2b4ce16bbac41470815333505aa47b91b7a9a6" Date: Fri, 28 Jun 2019 06:50:53 +0000 Subject: [PATCH] Added a comment: spurious processes being started --- ..._90d6937e95301f83268e0c9190f0f8c5._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/special_remotes/tahoe/comment_10_90d6937e95301f83268e0c9190f0f8c5._comment diff --git a/doc/special_remotes/tahoe/comment_10_90d6937e95301f83268e0c9190f0f8c5._comment b/doc/special_remotes/tahoe/comment_10_90d6937e95301f83268e0c9190f0f8c5._comment new file mode 100644 index 0000000000..942a8e29a9 --- /dev/null +++ b/doc/special_remotes/tahoe/comment_10_90d6937e95301f83268e0c9190f0f8c5._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="jk@3f2b4ce16bbac41470815333505aa47b91b7a9a6" + nickname="jk" + avatar="http://cdn.libravatar.org/avatar/c55729c75302ae278a98d1622b30fe49" + subject="spurious processes being started" + date="2019-06-28T06:50:53Z" + content=""" +On debian buster, copying to or from tahoe seems to alway cause an attempt to start a new tahoe process, even if one is already running, resulting in error messages like this on second or subsequent attempts: + + copy P5273249.JPG STARTING '/home/jk/.tahoe-git-annex/3677c81a-5cd0-4817-9ad3-a7c29b74a7b7' + starting node in '/home/jk/.tahoe-git-annex/3677c81a-5cd0-4817-9ad3-a7c29b74a7b7' + Another twistd server is running, PID 20860 + + This could either be a previously started instance of your application or a + different application entirely. To start a new one, either run it in some other + directory, or use the --pidfile and --logfile parameters to avoid clashes. + +Not a massive problem as everything seems to work. +"""]]