Re: 5.2 Spinning Beachball
Adding to the discussion of beachballing: I updated my OS X server to 10.3.9 over the weekend. It runs the DNS server. And the DNS Server works fine for web, ssh, afp etc. It also works some time for PM, meaning that connecting via POP to external mail servers work as before. However, at some time running, PM takes forever to connect to the external mail servers: O get no display (yet) in the background processes window, but PM beachballs for about 2 to 5 minutes before starting retrieving email. I did a Sample on PM when this happens, and the prominent trace is: Analysis of sampling pid 409 every 10.00 milliseconds Call graph: 92 Thread_110b 92 start 92 _start 92 main 92 LApplication::Run() 92 CPMApp::ProcessNextEvent() 92 LTSMDocApp::ProcessNextEvent() 92 LEventDispatcher::UseIdleTime(EventRecord const) 92 LPeriodical::DevoteTimeToIdlers(EventRecord const) 92 CPMApp::SpendTime(EventRecord const) 92 CPMApp::SchedulingIdle() 92 CPMApp::SchedulingIdleCallback(void*, void*) 92 CMAS::SchedulingIdle() 92 CRemoteNetworkServicesImp::IsConnected() const 92 gethostbyaddr 92 gethostbyaddrerrno 92 lu_gethostbyaddr 92 _lookup_all 92 _lookup_all_secure 92 mach_msg 92 mach_msg_trap 92 mach_msg_trap The problem is intermittent with no action on my part; if the problem is there, restarting PM does not help. After some 15 minutes, the problem vanishes on its own for some time, then re-occurs. During the beachballing, Interarchy shows outgoing connections to my POP servers being created, slowly (a change very 15 seconds or so). The DNS server log (named.log) on my OS X Server says for one of my POP servers the following (this log was created while the beachballing situation occurred): Jun 06 13:27:15.907 createfetch: mx.freenet.de A Jun 06 13:27:15.944 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:15.946 message has 2 byte(s) of trailing garbage Jun 06 13:27:16.399 createfetch: 20.64.165.213.in-addr.arpa PTR Jun 06 13:27:16.401 message has 4 byte(s) of trailing garbage Jun 06 13:27:20.948 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:20.949 message has 2 byte(s) of trailing garbage Jun 06 13:27:25.950 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:25.952 message has 2 byte(s) of trailing garbage Jun 06 13:27:30.954 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:30.955 message has 2 byte(s) of trailing garbage Jun 06 13:27:36.108 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:36.109 message has 2 byte(s) of trailing garbage Jun 06 13:27:36.656 createfetch: 144.50.97.194.in-addr.arpa PTR Jun 06 13:27:36.658 message has 2 byte(s) of trailing garbage Jun 06 13:27:41.110 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:41.112 message has 2 byte(s) of trailing garbage Jun 06 13:27:46.114 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:46.115 message has 2 byte(s) of trailing garbage Jun 06 13:27:50.493 createfetch: 2.96.201.81.in-addr.arpa PTR Jun 06 13:27:50.495 message has 3 byte(s) of trailing garbage Jun 06 13:27:51.116 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:51.118 message has 2 byte(s) of trailing garbage Jun 06 13:27:56.143 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:27:56.144 message has 2 byte(s) of trailing garbage Jun 06 13:28:01.145 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:28:01.146 message has 2 byte(s) of trailing garbage Jun 06 13:28:06.147 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:28:06.149 message has 2 byte(s) of trailing garbage Jun 06 13:28:11.149 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:28:11.151 message has 2 byte(s) of trailing garbage Jun 06 13:28:16.201 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:28:16.203 message has 2 byte(s) of trailing garbage Jun 06 13:28:21.214 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:28:21.216 message has 2 byte(s) of trailing garbage Jun 06 13:28:24.236 createfetch: 20.64.165.213.in-addr.arpa PTR Jun 06 13:28:24.238 message has 4 byte(s) of trailing garbage Jun 06 13:28:26.217 createfetch: 25.52.30.128.in-addr.arpa PTR Jun 06 13:28:26.218 message has 2 byte(s) of trailing garbage [...] Any clue what this problem might be? Is this an issue with my 10.3.9 DNS implementation? Or a problem with PM that only shows with some change in the 10.3.9 DNS? Or a result of the new 5.3 technique to detect when the net is up? Regards Christian
Re: 5.2 Spinning Beachball
At Mon, 6 Jun 2005 08:23:46 +0100 (CET), Chris Walker [EMAIL PROTECTED] wrote: On 5/6/05 Richard Hart wrote: PM 5.2 works fine for 4 or 5 days. Then, every action begins with a spinning beach ball for a few seconds. Then a spinning beach ball for a few minutes. Eventually, the beach ball spins forever. The database becomes unreadable. This has started to happen for me also, although mostly when retrieving/ sending mail. I'm wondering whether to go back to my 5.1 version in case my Db gets corrupted. PMac G4/400 OS 10.3.9 704Mb Ram Chris I had this identical experience on an iMac, a Dual 2GHz G5, a 733MHz G4, and a new iBook. The first uses a dial-up connection, the next two a DSL router, and the fourth a wireless connection. The only common link is that they are all using OS 10.3.9. I have reverted them all to PM 5.1, and they are working fine, using a backup of the 5.1 version of the databases. However, the 5.2 databases appear to be unrecoverable. Richard Hart I've had several similar problems, which accelerated after installing Tiger. After a lot of trouble-shooting and help from Jérôme, I found that trashing the address book database a creating a new one helped a lot. At least fo a while. Now I experience a lot of beachballing and more and more often I have to force PM to quit and reopen it again. No database failures yet, though. But my overall feeling is PM doesn't feel completely stable and reliable. Max Gossell -- PowerMail 5.2, build 4388 (SpamSieve 2.3.1) OSX v10.4.1 Dual G4 1.2 GHz / 1GB RAM
Re: 5.2 Spinning Beachball
Barbara Needham 5-06-2005: I do have the latest update, 5.2b4 build. At least I think that is the latest one. the last one should be 5.2 release ++not beta++ build 4388 -- marco
Re: 5.2 Spinning Beachball
On 5/6/05 Richard Hart wrote: PM 5.2 works fine for 4 or 5 days. Then, every action begins with a spinning beach ball for a few seconds. Then a spinning beach ball for a few minutes. Eventually, the beach ball spins forever. The database becomes unreadable. This has started to happen for me also, although mostly when retrieving/ sending mail. I'm wondering whether to go back to my 5.1 version in case my Db gets corrupted. PMac G4/400 OS 10.3.9 704Mb Ram Chris I had this identical experience on an iMac, a Dual 2GHz G5, a 733MHz G4, and a new iBook. The first uses a dial-up connection, the next two a DSL router, and the fourth a wireless connection. The only common link is that they are all using OS 10.3.9. I have reverted them all to PM 5.1, and they are working fine, using a backup of the 5.1 version of the databases. However, the 5.2 databases appear to be unrecoverable. Richard Hart
sorting a search by multiple rules
I wrote this msg last january (pwmail 5.1) but nothing happens, what about ctm's folks? could I hope this feature will be added? == I feel good with foxtrot's light-speed (I switched from mailsmith for this) but reading a thread is not comfortable because there is only one sort option: you know, subject or date sent or ... It will be a very appreciate feature sorting it using multiples rules. yes, I can just now refine the search to obtain only one thread but in the golden future of powermail... -- marco
Re: 5.2 Spinning Beachball
== Richard Hart, thank you for your message. = ***REPLYING TO YOUR MESSAGE QUOTED BELOW. REPLY IS ABOVE YOUR MESSAGE*** REPLY: No problem here. Did 10.3.9 for a while and then on to 10.4.1 and it seems to be fine. I suggest that if you move to tiger that you do an archive and install. I didn't and have been cleaning out caches in the system for a while. Seems to be ok now. Sun, 5 Jun 2005 13:30:13 -0700 [EMAIL PROTECTED] == Is anyone else experiencing a gradual corruption of 5.2 databases? Here are the symptoms: PM 5.2 works fine for 4 or 5 days. Then, every action begins with a spinning beach ball for a few seconds. Then a spinning beach ball for a few minutes. Eventually, the beach ball spins forever. The database becomes unreadable. I had this identical experience on an iMac, a Dual 2GHz G5, a 733MHz G4, and a new iBook. The first uses a dial-up connection, the next two a DSL router, and the fourth a wireless connection. The only common link is that they are all using OS 10.3.9. I have reverted them all to PM 5.1, and they are working fine, using a backup of the 5.1 version of the databases. However, the 5.2 databases appear to be unrecoverable. Richard Hart --- Bob Moody, fundraising consultant Owner, Moody Associates Quality Fundraising Products Serving schools, sports teams, daycares, church groups, scouts, and other community groups. *1986-2005 19 years of excellence! *Our mission is to make it easy for you to reach your fundraising goals...over and over...year after year. *Our main product is your profit! office: 540-885-3439 or 800-326-9192 (8-4 M-F) cell: 540-294-9791 toll-free to cell: 866-294-9791 www.fundraisingcentral.net www.bobmoody.org [EMAIL PROTECTED] Mail: 936 Frog Pond Road Staunton VA 24401-8346 fax 540-885-6670 or toll free 877-936-9192 The Four-Way Test of the things we think, say, or do: First: Is it the TRUTH? Second: Is it FAIR to all concerned? Third: Will it build GOOD WILL and BETTER FRIENDSHIPS? Fourth: Will it be BENEFICIAL to all concerned?
Re: 5.2 Spinning Beachball
Richard Hart on 6/5/05 said Is anyone else experiencing a gradual corruption of 5.2 databases? Here are the symptoms: PM 5.2 works fine for 4 or 5 days. Then, every action begins with a spinning beach ball for a few seconds. Then a spinning beach ball for a few minutes. Eventually, the beach ball spins forever. The database becomes unreadable. I had this identical experience on an iMac, a Dual 2GHz G5, a 733MHz G4, and a new iBook. The first uses a dial-up connection, the next two a DSL router, and the fourth a wireless connection. The only common link is that they are all using OS 10.3.9. I have reverted them all to PM 5.1, and they are working fine, using a backup of the 5.1 version of the databases. However, the 5.2 databases appear to be unrecoverable. Well, I DID have a problem but after many hours of rebuilding [and eventually figuring out that process was made shorter by turning off Norton Anti-Virus] all seems to be well now. I do have the latest update, 5.2b4 build. At least I think that is the latest one. -- Barbara Needham
5.2 Spinning Beachball
Is anyone else experiencing a gradual corruption of 5.2 databases? Here are the symptoms: PM 5.2 works fine for 4 or 5 days. Then, every action begins with a spinning beach ball for a few seconds. Then a spinning beach ball for a few minutes. Eventually, the beach ball spins forever. The database becomes unreadable. I had this identical experience on an iMac, a Dual 2GHz G5, a 733MHz G4, and a new iBook. The first uses a dial-up connection, the next two a DSL router, and the fourth a wireless connection. The only common link is that they are all using OS 10.3.9. I have reverted them all to PM 5.1, and they are working fine, using a backup of the 5.1 version of the databases. However, the 5.2 databases appear to be unrecoverable. Richard Hart
