If you are having PowerPurge failures...

administrator

Please post the following information to this topic:

1) What MySQL version you are using.

2) What O/S you are using.

3) Motherboard and CPU.

4) RAM.

5) Hard drive type, size and free space.

6) Other running software, including services.

7) How is NMP configured when you have Power Purge failures: minimized
to tray, minimized to taskbar, maximized, etc.

8) How is PowerPurge launched when you see PowerPurge failures.

Please add anything else to this list that you think may help.

Regards

BinaryTB · Experienced Joined: 25 May 2005 Posts: 210

1) MySQL 5.0.27

2) Windows XP Pro SP2

3) Asus P5AD2-E Deluxe w/ Intel P4 3.2GHz (HT Enabled)

4) Corsair 2GB RAM (4 x 512MB)

5) 2 x Western Digital 320GB (134GB Free & 68GB Free), SATA

6) Gaim, DirectUpdate, Unison, McAfee Enterprise 8.0i, Logitech SetPoint, UltraVNC, NVIDIA Display Driver Service

7) Manual PowerPurge (also happens via scheduled, but only tried manual with 2.7.0.0); maximized

-------------

*1) MySQL is on drive D:, while NMP is running on C: (also where it stores bodies and final combined files).

*2) I'm using the MySQL/NMP startup script (but I've tried without the script some time ago and PowerPurge still crashed NMP). The script ends normally, thus stopping the MySQL service without any problems it seems.

*3) Background purging works perfectly.

*4) I remember crashes happening with MySQL 4 as well. They started happening after a specific NMP version, I can't seem to find the thread via forum search (doesn't return all my posts via author search).

*5) Clean install of NMP or MySQL or Windows XP doesn't seem to fix the problem (did a an export/import of newgroups settings and nmp.ini though).

*6) Not overclocking anything, using regular Microsoft IDE drivers, latest Intel chipset drivers, newest motherboard bios, no errors in my Event Logs, everything cooled in my case nicely, all drives are using DMA (not falling back to PIO).

BZB · Expert Joined: 26 Apr 2005 Posts: 1390

1. MySQL 5.0.37 (msqld-max)

2. Windows XP Pro SP2

3. Asus A7N8X Deluxe / AMD Athlon XP 2600+

4. Crucial 768 MB RAM (3x256)

5. Seagate ST3120024A (120GB (50 GB free) - System disc with NMP installed)

Seagate ST3200822A (200 GB 50-30 GB free) - data disc with all NMP databases and temp files.

6. Kaspersky AV 6 (mostly off when NMP is running with NMP & databases all excluded), ExtraDNS, CCC/MOM/ati2evxx.exe (ATI Catalyst Drivers), NV Mixer tray (Nvidia Sound utility), mmc.exe (IIRC MS Studio Dr.Watson type of thing), EM_Exec (Logitech mouse driver for older mice), various standard MS system services, though I've disabled the stuff I don't use.

7. All possible variations. Open, minimised to taskbar, minimised to tray, etc.

8. All possible options. Manually, at end of queued jobs for both NMP and system shutdown.

As per Spoon69, this used to work, but at some point it started failing. Unfortunately with me only purging every day or two, it takes a while to notice this is something that now happens nearly every time.

Given the relatively small number of people that downloaded betas and participated in the beta forum, it may become a bigger issue when the release gets out to more users.

administrator · Posted: Tue Apr 17, 2007 1:48 am Post subject:

We've rewritten the PowerPurge process as a stand-alone thread. This encapsulates the entire process into a single step so the NMP can better complete the process.

In addition, NMP no longer requires the MySQL.exe command-line utility to perform a PowerPurge, Optimize or Repair. This makes the whole process much more reliable.

Upgrade to 2.7.0.1 Beta 2 to use this updated process.

Regards

schlong · New User Joined: 14 Oct 2005 Posts: 9

I'm having these issues as well. They started when I upgraded to v2.7.0.1. Installed 2.7.0.2 B2 but still the same issue.

In answer to your questions...

1) MySQL v5.0.27
2) Vista Business
3) ASUS K8N-E Deluxe
4) 2.5 Gb Crucial
5) Western Digital WD3200KS (72Gb free)
6) Kapersky AV6, Daemon Tools, Skype, VMware workstation v6, Outlook, Soundman, ATI Control Center... plus all normal services etc
7) Any variation - make no difference
8.) Automatically at program exit. Haven't tried manually but will do next time. UPDATE - Background purge works perfectly.

As I said this only started for me since going to 2.7.0.1 (from 2.6.x.x). What changed regarding Powerpurge in that version? Is it related to this new "stand-alone thread" change?

administrator · Posted: Sun May 13, 2007 4:28 am Post subject:

The change in 2.7.0.1 was meant to resolve the issue. For those who were having problems, it seems to have done so.

What are the symptoms that you are seeing?

What is in the PowerPurge.log file?

Regards

schlong · New User Joined: 14 Oct 2005 Posts: 9

My symptoms are that on program exit (purge on exit) a popup used to display showing what was being purged, step by step, but now that flashes up quickly, closes. then a simple purging database message is displayed that stays up looking like it has locked up. Newsmanpro just sits there until Vista reports the program has stopped responding causing it to have to be closed manually.

By the powerpurge log below it seems to be completing successfully.

Is the issue now that when a Powerpurge is performed Newsmanpro does not shut itself down correctly and not a Powerpurge issue at all? Is there a different shutdown routine that is run after Powerpurge relative to other application shutdown requests.

On Newsmanpro restart I get the repair database message (I assume due to having to force shutdown Newsmanpro).

(hope this makes sense and hope it helps)

PowerPurge started: 13/05/2007 1:33:44 PM
13/05/2007 1:33:44 PM: Initializing new database session...
13/05/2007 1:33:44 PM: Gathering Workgroups...
13/05/2007 1:33:44 PM: Found 2 Workgroups...
13/05/2007 1:33:44 PM: Purging wgparts00...
13/05/2007 1:33:44 PM: Counting records in wgparts00...
13/05/2007 1:33:44 PM: 0 records found...
13/05/2007 1:33:44 PM: Purging wgparts01...
13/05/2007 1:33:44 PM: Counting records in wgparts01...
13/05/2007 1:33:44 PM: 24207 records found...
13/05/2007 1:33:44 PM: Counting records to be purged in wgparts01...
13/05/2007 1:33:44 PM: 3733 records found...
13/05/2007 1:33:44 PM: Purging records for wgparts01 using DIRECT method...
13/05/2007 1:33:44 PM: Purge complete for wgparts01...
13/05/2007 1:33:44 PM: Checking for orphaned records in wgparts01...
13/05/2007 1:33:45 PM: Check for orphaned records complete for wgparts01...
13/05/2007 1:33:45 PM: Purging wgmessage...
13/05/2007 1:33:45 PM: Purge complete for wgmessage...
13/05/2007 1:33:45 PM: Checking for orphaned records in wgmessage...
13/05/2007 1:33:45 PM: Check for orphaned records completed for wgmessage...
13/05/2007 1:33:45 PM: Purging wgattach...
13/05/2007 1:33:45 PM: Purge completed for wgattach...
13/05/2007 1:33:45 PM: Checking for orphaned records in wgattach...
13/05/2007 1:33:45 PM: Orphaned record check completed for wgattach...
13/05/2007 1:33:45 PM: Purging wgbodies...
13/05/2007 1:33:45 PM: Purge completed for wgbodies...
13/05/2007 1:33:45 PM: Checking for orphaned records in wgbodies...
13/05/2007 1:33:45 PM: Orphan check completed for wgbodies...
13/05/2007 1:33:45 PM: Purging wgheaders...
13/05/2007 1:33:45 PM: Purge completed for wgheaders...
13/05/2007 1:33:45 PM: Truncating purgedata...
13/05/2007 1:33:45 PM: Truncate completed for purgedata...
13/05/2007 1:33:45 PM: Optimizing tables started...
13/05/2007 1:33:45 PM: Optimizing tables finished...
PowerPurge finished: 13/05/2007 1:33:45 PM

administrator · Posted: Sun May 13, 2007 1:45 pm Post subject:

schlong · New User Joined: 14 Oct 2005 Posts: 9

administrator · Posted: Tue May 15, 2007 11:09 am Post subject:

schlong · New User Joined: 14 Oct 2005 Posts: 9

Here's my latest Powerpurge log. This is after NMP locked up at 50% as above... The purge completed so it looks like the issue is elsewhere...

PowerPurge started: 15/05/2007 11:24:27 PM
15/05/2007 11:24:27 PM: Initializing new database session...
15/05/2007 11:24:27 PM: Gathering Workgroups...
15/05/2007 11:24:27 PM: Found 2 Workgroups...
15/05/2007 11:24:27 PM: Purging wgparts00...
15/05/2007 11:24:27 PM: Counting records in wgparts00...
15/05/2007 11:24:27 PM: 0 records found...
15/05/2007 11:24:27 PM: Purging wgparts01...
15/05/2007 11:24:27 PM: Counting records in wgparts01...
15/05/2007 11:24:27 PM: 59695 records found...
15/05/2007 11:24:27 PM: Counting records to be purged in wgparts01...
15/05/2007 11:24:28 PM: 25757 records found...
15/05/2007 11:24:28 PM: Purging records for wgparts01 using DIRECT method...
15/05/2007 11:24:29 PM: Purge complete for wgparts01...
15/05/2007 11:24:29 PM: Checking for orphaned records in wgparts01...
15/05/2007 11:24:30 PM: Check for orphaned records complete for wgparts01...
15/05/2007 11:24:30 PM: Purging wgmessage...
15/05/2007 11:24:30 PM: Purge complete for wgmessage...
15/05/2007 11:24:30 PM: Checking for orphaned records in wgmessage...
15/05/2007 11:24:30 PM: Check for orphaned records completed for wgmessage...
15/05/2007 11:24:30 PM: Purging wgattach...
15/05/2007 11:24:30 PM: Purge completed for wgattach...
15/05/2007 11:24:30 PM: Checking for orphaned records in wgattach...
15/05/2007 11:24:30 PM: Orphaned record check completed for wgattach...
15/05/2007 11:24:30 PM: Purging wgbodies...
15/05/2007 11:24:30 PM: Purge completed for wgbodies...
15/05/2007 11:24:30 PM: Checking for orphaned records in wgbodies...
15/05/2007 11:24:30 PM: Orphan check completed for wgbodies...
15/05/2007 11:24:30 PM: Purging wgheaders...
15/05/2007 11:24:30 PM: Purge completed for wgheaders...
15/05/2007 11:24:30 PM: Truncating purgedata...
15/05/2007 11:24:30 PM: Truncate completed for purgedata...
15/05/2007 11:24:30 PM: Optimizing tables started...
15/05/2007 11:24:30 PM: Optimizing tables finished...
PowerPurge finished: 15/05/2007 11:24:30 PM

schlong · New User Joined: 14 Oct 2005 Posts: 9

I don't know if this helps but the following is what Vista reports...

Description:
A problem caused this program to stop interacting with Windows.

Problem signature:
Problem Event Name: AppHangB1
Application Name: NewsMan.exe
Application Version: 2.7.0.2
Application Timestamp: 2a425e19
Hang Signature: 085e
Hang Type: 4
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 3081
Additional Hang Signature 1: 25f19edd42d0066177bfb8f9e438dcbd
Additional Hang Signature 2: e556
Additional Hang Signature 3: dce259de6e0ff65c8ff580e12f2ed803
Additional Hang Signature 4: e432
Additional Hang Signature 5: dcc3690f5d5bd5000749d4b591eb9bb2
Additional Hang Signature 6: 99f0
Additional Hang Signature 7: d5d298e267ba051ab9524f86f281b235

administrator · Posted: Tue May 15, 2007 2:29 pm Post subject:

This looks like Vista actually thinks NMP is hung while it was busy. Vista is then stopping NMP from completing. While PowerPurge is running, NMP is in a wait cycle until the PowerPurge thread terminates. Perhaps introducing additional message processing during the wait cycle will alleviate the problem, but we won't know until we try it.

Regards

schlong · New User Joined: 14 Oct 2005 Posts: 9

I just updated to 2.7.0.2 Beta3 and now NMP shuts down correctly after a Powerpurge... thought you'd like to know.

administrator · Posted: Fri May 18, 2007 11:12 am Post subject: