* [sup-talk] CPU at 99% @ 2008-10-31 21:38 Tomas Pospisek ML 2008-10-31 23:53 ` William Morgan 0 siblings, 1 reply; 5+ messages in thread From: Tomas Pospisek ML @ 2008-10-31 21:38 UTC (permalink / raw) When I start Sup, it starts eating my CPU and won't stop. And it doesn't seem to be doing anything either: top - 22:34:10 up 19 days, 1:43, 14 users, load average: 1.12, 0.98, 0.64 Tasks: 169 total, 3 running, 166 sleeping, 0 stopped, 0 zombie Cpu(s): 23.8%us, 27.6%sy, 0.0%ni, 47.9%id, 0.0%wa, 0.7%hi, 0.0%si, 0.0%st Mem: 2054936k total, 2038152k used, 16784k free, 10264k buffers Swap: 1951856k total, 683256k used, 1268600k free, 310932k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 18228 tpo 20 0 185m 85m 3696 R 99 4.3 12:33.83 sup Meanwhile my laptop is blowing hot air like a fumarole. System is amd64 on Ubuntu Heron, Sup 0.6. ? *t ^ permalink raw reply [flat|nested] 5+ messages in thread
* [sup-talk] CPU at 99% 2008-10-31 21:38 [sup-talk] CPU at 99% Tomas Pospisek ML @ 2008-10-31 23:53 ` William Morgan [not found] ` <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7> 0 siblings, 1 reply; 5+ messages in thread From: William Morgan @ 2008-10-31 23:53 UTC (permalink / raw) Reformatted excerpts from Tomas Pospisek ML's message of 2008-10-31: > When I start Sup, it starts eating my CPU and won't stop. And it > doesn't seem to be doing anything either: It could be indexing a large volume of mail. If you swap to the poll buffer, you should be able to confirm that. If you've just added some large mail sources, or something like that, you might want to run sup-sync first to index them offline. -- William <wmorgan-sup at masanjin.net> ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7>]
* [sup-talk] CPU at 99% [not found] ` <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7> @ 2008-11-02 18:50 ` William Morgan 2008-11-03 20:45 ` Tomas Pospisek ML 0 siblings, 1 reply; 5+ messages in thread From: William Morgan @ 2008-11-02 18:50 UTC (permalink / raw) Reformatted excerpts from Tomas Pospisek ML's message of 2008-10-31: > The "[poll-mode]" buffer shows an "infinite amount" of the following > message: > [...] > Found message at 44352220 with labels {Sent, unread} > Found message at 44352220 with labels {Sent, unread} > Found message at 44352220 with labels {Sent, unread} > Found message at 44352220 with labels {Sent, unread} > Found message at 44352220 with labels {Sent, unread} What kind of source is this? I'm guessing mbox. Can you try to figure out what is around byte offset 44352220 in that file? Sup isn't advancing beyond that for some reason. > When I do that I get an "eternal" (?) output of: > > [Sam Nov 01 01:00:53 +0100 2008] faking from for message > sup-faked-b5d74cf19a1ebaf02e979448d059d0f4: Sup Auto-generated Fake > Sender <sup at fake.sender.example.com> > [Sam Nov 01 01:00:53 +0100 2008] faking date header for > sup-faked-b5d74cf19a1ebaf02e979448d059d0f4 > [Sam Nov 01 01:00:53 +0100 2008] faking message-id for message from Sup > Auto-generated Fake Sender <sup at fake.sender.example.com>: > sup-faked-b5d74cf19a1ebaf02e979448d059d0f4 > [Sam Nov 01 01:00:53 +0100 2008] faking from for message > sup-faked-b5d74cf19a1ebaf02e979448d059d0f4: Sup Auto-generated Fake > Sender <sup at fake.sender.example.com> > [Sam Nov 01 01:00:53 +0100 2008] faking date header for > sup-faked-b5d74cf19a1ebaf02e979448d059d0f4 This is almost definitely the same problem as above. -- William <wmorgan-sup at masanjin.net> ^ permalink raw reply [flat|nested] 5+ messages in thread
* [sup-talk] CPU at 99% 2008-11-02 18:50 ` William Morgan @ 2008-11-03 20:45 ` Tomas Pospisek ML 2008-11-03 21:29 ` Tomas Pospisek ML 0 siblings, 1 reply; 5+ messages in thread From: Tomas Pospisek ML @ 2008-11-03 20:45 UTC (permalink / raw) On 11/2/2008, "William Morgan" <wmorgan-sup at masanjin.net> wrote: >Reformatted excerpts from Tomas Pospisek ML's message of 2008-10-31: >> The "[poll-mode]" buffer shows an "infinite amount" of the following >> message: >> [...] >> Found message at 44352220 with labels {Sent, unread} >> Found message at 44352220 with labels {Sent, unread} >> Found message at 44352220 with labels {Sent, unread} >> Found message at 44352220 with labels {Sent, unread} >> Found message at 44352220 with labels {Sent, unread} > >What kind of source is this? I'm guessing mbox. Correct, that's mbox. > Can you try to figure out what is around byte offset 44352220 in that file? Sup isn't >advancing beyond that for some reason. $ hexdump -C -s 44352219 -n 80 /home/tpo/mail/sent-mail/sent-mail-jan-2008 02a4c2db 0a 46 72 6f 6d 20 74 70 6f 32 2e 6c 6f 63 61 6c |.From tpo2.local| 02a4c2eb 20 28 31 30 2e 32 2e 31 35 39 2e 35 30 29 20 69 | (10.2.159.50) i| 02a4c2fb 63 6d 70 5f 73 65 71 3d 35 37 35 35 20 44 65 73 |cmp_seq=5755 Des| 02a4c30b 74 69 6e 61 74 69 6f 6e 20 48 6f 73 74 20 55 6e |tination Host Un| 02a4c31b 72 65 61 63 68 61 62 6c 65 0a 46 72 6f 6d 20 74 |reachable.From t| Thus the byte just before offset 44352220 is a 'a0' thus a newline with a "^From" on the next line and thus I guess it's the same problem as: http://rubyforge.org/pipermail/sup-talk/2008-October/001719.html Regarding the "Sent" label mentioned in the log above I need to add that I did something like this: $ for i in $HOME/mail/sent-mail/*; do sup-add mbox:$i -a -l Sent ; done That went OK, however, when I list labels in Sup I get this: [...] Sent 13 messages, 2 unread Sent 6415 messages, 3271 unread [...] Thus apparently Sup get's a bit mixed up about the 'Sent' label. *t ^ permalink raw reply [flat|nested] 5+ messages in thread
* [sup-talk] CPU at 99% 2008-11-03 20:45 ` Tomas Pospisek ML @ 2008-11-03 21:29 ` Tomas Pospisek ML 0 siblings, 0 replies; 5+ messages in thread From: Tomas Pospisek ML @ 2008-11-03 21:29 UTC (permalink / raw) On 11/3/2008, "Tomas Pospisek ML" <tpo2 at sourcepole.ch> wrote: > >On 11/2/2008, "William Morgan" <wmorgan-sup at masanjin.net> wrote: > >>Reformatted excerpts from Tomas Pospisek ML's message of 2008-10-31: >>> The "[poll-mode]" buffer shows an "infinite amount" of the following >>> message: >>> [...] >>> Found message at 44352220 with labels {Sent, unread} >>> Found message at 44352220 with labels {Sent, unread} >>> Found message at 44352220 with labels {Sent, unread} >>> Found message at 44352220 with labels {Sent, unread} >>> Found message at 44352220 with labels {Sent, unread} >> >>What kind of source is this? I'm guessing mbox. > >Correct, that's mbox. > >> Can you try to figure out what is around byte offset 44352220 in that file? Sup isn't >>advancing beyond that for some reason. > >$ hexdump -C -s 44352219 -n 80 /home/tpo/mail/sent-mail/sent-mail-jan-2008 >02a4c2db 0a 46 72 6f 6d 20 74 70 6f 32 2e 6c 6f 63 61 6c |.From >tpo2.local| >02a4c2eb 20 28 31 30 2e 32 2e 31 35 39 2e 35 30 29 20 69 | >(10.2.159.50) i| >02a4c2fb 63 6d 70 5f 73 65 71 3d 35 37 35 35 20 44 65 73 |cmp_seq=5755 >Des| >02a4c30b 74 69 6e 61 74 69 6f 6e 20 48 6f 73 74 20 55 6e |tination >Host Un| >02a4c31b 72 65 61 63 68 61 62 6c 65 0a 46 72 6f 6d 20 74 >|reachable.From t| > >Thus the byte just before offset 44352220 is a 'a0' thus a newline with >a "^From" on the next line and thus I guess it's the same problem as: > >http://rubyforge.org/pipermail/sup-talk/2008-October/001719.html Oh, and I'm getting the impression, that Sup doesn't like: " From >>From " lines either... *t ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-11-03 21:29 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-10-31 21:38 [sup-talk] CPU at 99% Tomas Pospisek ML
2008-10-31 23:53 ` William Morgan
[not found] ` <6K5DuLg4.1225497709.2001540.tpo2@192.168.3.7>
2008-11-02 18:50 ` William Morgan
2008-11-03 20:45 ` Tomas Pospisek ML
2008-11-03 21:29 ` Tomas Pospisek ML
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox