Trouble with gnus-agent-expire

Trouble with gnus-agent-expire

[Harry Putnam]

I don't use gnus-agent-expire very often... not as often as I should
anyway.  So its probably been at least 2 mnths since I've run it.  This
time its different.  It just runs forever (or at least says
gnus-agent-expire in echo area.  And emacs is building up a pretty
good head of steam, showing 75 percent resource hogging after about 10
minutes.

I measured the size of News... before starting, just out of habit, and
left it runnning for a couple of hours... not really on purpose, just
got busy on other virtual desktops and didn't notice it was still
running.  I did notice sluggishness... and finally started checking.
Killed it with Ctrl-g rechecked the size of ~/News... no change at all.
Still stready at 958M. There are no errors.

I thought to update gnus to todays cvs.. although it wasn't more than
a few wks old... No change... As it happens I'd updated emacs day
before yesterday (I run the cvs 23 version).

One thing I started doing fairly recently is running gnus from a
running emacs --daemon.   So I thought to take that out of the
equation and killed it off, fired up gnus on new instance of emacs
proper... not a daemon.  no change.

Can anyone give me a clue as to how to go about debugging this.

Re: Trouble with gnus-agent-expire

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

Hi Harry,

> I thought to update gnus to todays cvs.. although it wasn't more than
> a few wks old... No change... As it happens I'd updated emacs day
> before yesterday (I run the cvs 23 version).

Did you try with the gnus version that is included with emacs 23?
Basically, that's also No Gnus, but there might be some changes that
aren't synchronized back into the Gnus CVS yet.

Bye,
Tassilo

Re: Trouble with gnus-agent-expire

[Harry Putnam]

Tassilo Horn <tassilo@member.fsf.org> writes:

> Harry Putnam <reader@newsguy.com> writes:
>
> Hi Harry,
>
>> I thought to update gnus to todays cvs.. although it wasn't more than
>> a few wks old... No change... As it happens I'd updated emacs day
>> before yesterday (I run the cvs 23 version).
>
> Did you try with the gnus version that is included with emacs 23?
> Basically, that's also No Gnus, but there might be some changes that
> aren't synchronized back into the Gnus CVS yet.

No, but doing so now... it shows version 5.13.  Its running now and
chewing up between 94-99 percent of cpu.  No messages show up in echo
areas it just shows my last command:

   M-x gnus-agent-expire

Its been running for 5 minutes already... doesn't look too promising

Re: Trouble with gnus-agent-expire

[Harry Putnam]

Harry Putnam <reader@newsguy.com> writes:

> Tassilo Horn <tassilo@member.fsf.org> writes:
>
>> Harry Putnam <reader@newsguy.com> writes:
>>
>> Hi Harry,
>>
>>> I thought to update gnus to todays cvs.. although it wasn't more than
>>> a few wks old... No change... As it happens I'd updated emacs day
>>> before yesterday (I run the cvs 23 version).
>>
>> Did you try with the gnus version that is included with emacs 23?
>> Basically, that's also No Gnus, but there might be some changes that
>> aren't synchronized back into the Gnus CVS yet.
>
> No, but doing so now... it shows version 5.13.  Its running now and
> chewing up between 94-99 percent of cpu.  No messages show up in echo
> areas it just shows my last command:
>
>    M-x gnus-agent-expire
>
> Its been running for 5 minutes already... doesn't look too promising

I let it run for 15 minutes... it didn't do anything but chew up
resources.

What can I do to get the expiration to happen?

It would be ok with me to just delete all numbered files by hand.  

But I don't want to redownload all that.... 

If I keep nov and .agentview will gnus think things are like they were
and just carry on with new messages?

Re: Trouble with gnus-agent-expire

[Tassilo Horn]

Harry Putnam <reader@newsguy.com> writes:

Hi Harry,

>> No, but doing so now... it shows version 5.13.  Its running now and
>> chewing up between 94-99 percent of cpu.  No messages show up in echo
>> areas it just shows my last command:
>>
>>    M-x gnus-agent-expire
>>
>> Its been running for 5 minutes already... doesn't look too promising
>
> I let it run for 15 minutes... it didn't do anything but chew up
> resources.
>
> What can I do to get the expiration to happen?

Dunno, I cannot reproduce your problem.  But the expiry process usually
prints a lot of messages to the *Messages* buffer, like those.

--8<---------------cut here---------------start------------->8---
20090928T211329.614> Expiring articles in nntp+Uni:alt.religion.emacs
20090928T211329.616> gnus-agent-expire: Loading overview...
20090928T211329.617> gnus-agent-expire: Loading overview... Done
20090928T211329.618> gnus-agent-expire: Sorting entries... 
20090928T211329.619> gnus-agent-expire: Sorting entries... Done
20090928T211329.620> gnus-agent-expire: Merging entries... 
20090928T211329.620> gnus-agent-expire: Merging entries... Done
--8<---------------cut here---------------end--------------->8---

Maybe it works for some initial groups and then gets stuck in some
group?  Then something is probably broken with that group's files and
deleting them and redownloading only that group would solve the issue.

But I have to admit that I don't have a deeper understanding of the
agent.  For me it just work... :-)

Bye,
Tassilo

Re: Trouble with gnus-agent-expire

[Harry Putnam]

Tassilo Horn <tassilo@member.fsf.org> writes:

>> What can I do to get the expiration to happen?
>
> Dunno, I cannot reproduce your problem.  But the expiry process usually
> prints a lot of messages to the *Messages* buffer, like those.
>
> 20090928T211329.614> Expiring articles in nntp+Uni:alt.religion.emacs
> 20090928T211329.616> gnus-agent-expire: Loading overview...
> 20090928T211329.617> gnus-agent-expire: Loading overview... Done
> 20090928T211329.618> gnus-agent-expire: Sorting entries... 
> 20090928T211329.619> gnus-agent-expire: Sorting entries... Done
> 20090928T211329.620> gnus-agent-expire: Merging entries... 
> 20090928T211329.620> gnus-agent-expire: Merging entries... Done

Yeah thats what I'm used to seeing too.

> Maybe it works for some initial groups and then gets stuck in some
> group?  Then something is probably broken with that group's files and
> deleting them and redownloading only that group would solve the issue.

Yeah but how to find that out... when there seems to be no output?

> But I have to admit that I don't have a deeper understanding of the
> agent.  For me it just work... :-)

Pretty much has for me to... since way back in quassia days... long
before we had gnus-agent-expire.

But since the advent of gnus-agent-expire which is quite a while
now.. I've always been able to run it successfully.

If I just new that gnus would be tricked into thinking the files were
still here, I'd hand delete all messages leaving the .overview and
.agentview. 

Maybe some kind soul will jump in here with that information..

Probably ought to start a new thread on that subject.... yea.. think
I will.

Re: Trouble with gnus-agent-expire

[Adam Sjøgren]

On Mon, 28 Sep 2009 15:07:40 -0500, Harry wrote:

> Yeah but how to find that out... when there seems to be no output?

Maybe something like this:

  M-x toggle-debug-on-quit
  [... invoke whatever it is you want to investigate ...]
  C-g
  [... get a lisp backtrace ...]
  [... ?!? ...]
  [... profit ...]

Just an idea, I'm only posing as someone who can dole out advice.


  :-),

   Adam

-- 
 "Kom nu jag är kroniskt låg                                  Adam Sjøgren
  Bara mörkret hörs"                                     asjo@koldfront.dk

Re: Trouble with gnus-agent-expire

[Harry Putnam]

asjo@koldfront.dk (Adam Sjøgren) writes:

> On Mon, 28 Sep 2009 15:07:40 -0500, Harry wrote:
>
>> Yeah but how to find that out... when there seems to be no output?
>
> Maybe something like this:
>
>   M-x toggle-debug-on-quit
>   [... invoke whatever it is you want to investigate ...]
>   C-g
>   [... get a lisp backtrace ...]
>   [... ?!? ...]
>   [... profit ...]
>
> Just an idea, I'm only posing as someone who can dole out advice.

Well, looks like you got way with your pose...

Turns out that tramp is involved somehow (backtrace at the end).  I'm
guessing I must have opened a group on a remote sometime or
other... that all I could think of... but the server buffer doesn't
show anything like that.

Also I had a variable `gnus-agent-expire-unagentized-dirs'
set... which may have been causing problems.. but when I set it to nil
and called M-x gnus-agent-expire.... it finished immediately.. I mean
instantaneously.  That's when I noticed I had no agentized groups.

I guess it was a senior moment..Then I remembered having took all
groups out of agent control.

I'm not sure what tramp is doing in the backtrace ... equally baffled by the
presence of anything to do with cygwin.... this is a linux (gentoo)
machine..maybe someone will know.

I finally just ran a find delete cmd deleting anything more than 20
days old with number for a name.  

-------        ---------       ---=---       ---------      -------- 
Back trace
Debugger entered--Lisp error: (quit)
  backquote-process((tramp-completion-file-name-handler cygwin-mount-name-hook-function cygwin-mount-map-drive-hook-function \, (and (eq inhibit-file-name-operation operation) inhibit-file-name-handlers)))
  #[(structure) "\301\b!A\207" [structure backquote-process] 2 1694483]((tramp-completion-file-name-handler cygwin-mount-name-hook-function cygwin-mount-map-drive-hook-function \, (and (eq inhibit-file-name-operation operation) inhibit-file-name-handlers)))
  (\` (tramp-completion-file-name-handler cygwin-mount-name-hook-function cygwin-mount-map-drive-hook-function \, (and ... inhibit-file-name-handlers)))
  (let* ((inhibit-file-name-handlers ...) (inhibit-file-name-operation operation)) (apply operation args))
  tramp-completion-run-real-handler(directory-file-name ("/"))
  (if (and fn tramp-mode (or ... ... ... ... ...)) (save-match-data (apply ... args)) (tramp-completion-run-real-handler operation args))
  (let ((directory-sep-char 47) (fn ...)) (if (and fn tramp-mode ...) (save-match-data ...) (tramp-completion-run-real-handler operation args)))
  tramp-completion-file-name-handler(directory-file-name "/")
  directory-file-name("/")
  #[(d) "\306\b!\307\x19\x1a\n\211A\x12@\211\x11\205b