From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.help Subject: Re: What does the error "Process not running" mean? Date: Thu, 03 Feb 2022 06:59:45 +0100 Message-ID: <8735l0o518.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="13732"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.7.6; emacs 29.0.50 Cc: help-gnu-emacs@gnu.org To: emacsq Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Feb 03 07:09:59 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nFVJd-0003IK-SZ for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 03 Feb 2022 07:09:58 +0100 Original-Received: from localhost ([::1]:35052 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nFVJc-0004Gu-A7 for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 03 Feb 2022 01:09:56 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:55454) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nFVIv-0004Gk-2u for help-gnu-emacs@gnu.org; Thu, 03 Feb 2022 01:09:13 -0500 Original-Received: from [2001:470:142:3::e] (port=56054 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nFVIu-0005fI-Eh; Thu, 03 Feb 2022 01:09:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:In-reply-to:Date:Subject:To:From: References; bh=AYkTnn13Rvd0CO5lKqzaNK8JXXr2urKWVB8ymzun/MM=; b=i+9lz95715iukv s8/QPy55Vd/2uAm2fkyKuPTmYS/er0X8q4Rc64cQZlQX+BFUaWOfvrnf46UiHNYQe5G/HYXKJ4GwZ bcma0N+H0hTU05rflnkamfJLSkYvOhHA05/sUELLLlnNRti7iyPA4S34PELLn5AYoizKSpjCCemow wfTDG+6shg0q806r693FSEahJvbmS0IXRn0wLT3ltWKhoDS2MjPBTsz1mOuFpnCqfs9jqXqYI0zrc xCO7I3VXOJUrXu3JyKVc3MLqhmBNaZtgIbU7ikkGgdzUlPIA48wy4bEuG6CYzg3on4R4D93zUSWPy QQbgnp/XBmTQzMry564A==; Original-Received: from auth1-smtp.messagingengine.com ([66.111.4.227]:60747) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nFVIu-0003iJ-7r; Thu, 03 Feb 2022 01:09:12 -0500 Original-Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailauth.nyi.internal (Postfix) with ESMTP id A8BFA27C0054; Thu, 3 Feb 2022 01:09:11 -0500 (EST) Original-Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 03 Feb 2022 01:09:11 -0500 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgeeigdeludcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfhgfhffvufffjgfkgggtsehttdertd dtredtnecuhfhrohhmpefvrghsshhilhhoucfjohhrnhcuoehtshguhhesghhnuhdrohhr gheqnecuggftrfgrthhtvghrnhephfdtleegledvfedtieeljedtkedtueduffegvdevve elvdejledvheffffduieeunecuffhomhgrihhnpegvgigrmhhplhgvrdgtohhmnecuvehl uhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhrnhdomh gvshhmthhprghuthhhphgvrhhsohhnrghlihhthidqkeeijeefkeejkeegqdeifeehvdel kedqthhsughhpeepghhnuhdrohhrghesfhgrshhtmhgrihhlrdhfmh X-ME-Proxy: Original-Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 3 Feb 2022 01:09:10 -0500 (EST) In-reply-to: X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:135686 Archived-At: emacsq writes: >> What did you do exactly? > > I have a document with hundreds of urls in it which needs to be > checked if they are still alive and well, so I fetched them one by one > with a code like this: > > (condition-case errmsg > (url-retrieve > "http://www.example.com" > > (lambda (status) > (let ((error (plist-get status :error))) > (if error > (print error)) > > ...do something, then check next url...)) > > ) > (error (print errmsg))) I'd start by printing the complete status plist and see if that sheds some light. I assume that you might be hitting some kind of "max number of child processes" limit since you are talking about hundreds of URLs, and `url-retrieve' is asynchronous. You might want to check if `url-retrieve-synchronously' works. If it does (but takes much longer, obviously), then the above is most probably the cause. In that case, you could try to structure your code so that it doesn't retrieve all URLs in one go but in chunks of, say, 20 and starts the next chunk not before the previous is finished. Bye, Tassilo