Debug.txt file in /Files folder

[NC Software]

There is a 42 MB "Debug.txt" file in my /Files folder. What is it, why is it, how do I stop it? The latest date is an hour ago so something is still writing to it even in the STABLE release.

[Jamie Edwards]

Hi Neal,

Can you paste a small example of its contents?

[NC Software]

Looks like someone left mail parser in debug mode? I also replaced sensitive information with "{removed}".

Date: Thu, 14 Aug 2008 09:06:46 -0400
Subject: NC Software Product Activation Logbook Pro PC Edition-1.10.26
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailer: aspNetEmail ver 3.6.0.26
Message-ID: <WEB3d7af3f7e293b4223977f26e4314cfbc3@web3>
Dear Ronnie {removed},=0D=0A=0D=0AThank you for activating your software wi=
th NC Software at Thursday, August 14, 2008 9:06:46 AM=2E We recorded the=
following information for your records=2E Please print and save for you=
r permanent records should you need to reactivate your software in the fu=
ture=2E=0D=0A=0D=0A=7ERegistration Data=7E=0D=0AName: Ronnie {removed}=0D=0A=
Company: =0D=0AUnlock Code: {removed}=0D=0AE-Mail: raceair1=40=
yahoo=2Ecom=0D=0AProduct: Logbook Pro PC Edition=0D=0AVersion: 1=2E10=2E2=
6=0D=0AMachine Name: {removed}=0D=0AIP Address: {removed}=0ALicense Activated: 2 times=0D=0AComputers Licensed: 2

[14 Aug 08 9:10 AM] PARSER: Mail Decoded. From Name: "system administrator"@localhost, From Email: "system administrator"@localhost, Subject: Delivery Failure, To Email: {removed}, Text Size: 1503, HTML Size: 0
[14 Aug 08 9:10 AM] PARSER: Processed Charset () and Transfer Encoding ()
[14 Aug 08 9:10 AM] PARSER: Processed Attachments. Total Attachments in Email: 0, Total Attachment Size: 0.00 Bytes
[14 Aug 08 9:10 AM] QUEUECHECK: Found Email Queue for: {removed}[14 Aug 08 9:10 AM] LOOKUP: Searching Ticket ID In text Body!
[14 Aug 08 9:10 AM] LOOKUP: Searching Ticket ID In HTML Body!
[14 Aug 08 9:10 AM] PARSER: Is a New Ticket
[14 Aug 08 9:10 AM] PARSER: Final Content Is:
Could not deliver message to the following recipient(s):
Failed Recipient: {removed}
Reason: Remote host said: 554 delivery error: dd This user doesn't have a yahoo.com account ({removed}) [0] - mta261.mail.mud.yahoo.com
-- The header and top 20 lines of the message follows --
Received: from {removed} by {removed} with SMTP;
Thu, 14 Aug 2008 09:06:46 -0400
From: "NC Software Activation Center" <{removed}>
To: "{removed}" <{removed}>
Date: Thu, 14 Aug 2008 09:06:46 -0400
Subject: NC Software Product Activation Logbook Pro PC Edition-1.10.26
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Mailer: aspNetEmail ver 3.6.0.26
Message-ID: <WEB3d7af3f7e293b4223977f26e4314cfbc3@web3>
Dear Ronnie {removed},=0D=0A=0D=0AThank you for activating your software wi=
th NC Software at Thursday, August 14, 2008 9:06:46 AM=2E We recorded the=
following information for your records=2E Please print and save for you=
r permanent records should you need to reactivate your software in the fu=
ture=2E=0D=0A=0D=0A=7ERegistration Data=7E=0D=0AName: Ronnie {removed}=0D=0A=
Company: =0D=0AUnlock Code: {removed}=0D=0AE-Mail: {removed}=40=
yahoo=2Ecom=0D=0AProduct: Logbook Pro PC Edition=0D=0AVersion: 1=2E10=2E2=
6=0D=0AMachine Name: AER1L030WG9G1=0D=0AIP Address: {removed}
=0ALicense Activated: 2 times=0D=0AComputers Licensed: 2

[Ryan Lederman]

It looks like this has been present for a while; look at /modules/parser/functions_parsercore.php, 26:

$_SWIFT["clidebug"] = true;
$_SWIFT["dbgfilename"] = "debug.txt";

Remove these two lines and it should go away.

[NC Software]

Thanks Ryan. I commented out these two lines, will monitor.

[Ryan Lederman]

I've also removed it and rebuilt the distro so that the spread of it is limited to whoever downloaded between yesterday and right now.

3.30.00 STABLE Released

[NC Software]

I've also removed it and rebuilt the distro so that the spread of it is limited to whoever downloaded between yesterday and right now.

3.30.00 STABLE Released

Ryan,

Although it's trivial, you know better than to "re-release" a software product. Definitely a "never do" in the Windows world, the web world is a little more leniant. How will I know if 3.30.00 STABLE is the same next week and additional "fixes" are in that build vs. yesterday's build? Should I download and install weekly to get better 3.30.00 fixes? Once again my case for better software versioning.

Preaching to the choir!

[Ryan Lederman]

Originally Posted by NC Software

Ryan,

Although it's trivial, you know better than to "re-release" a software product. Definitely a "never do" in the Windows world, the web world is a little more leniant. How will I know if 3.30.00 STABLE is the same next week and additional "fixes" are in that build vs. yesterday's build? Should I download and install weekly to get better 3.30.00 fixes? Once again my case for better software versioning.

Preaching to the choir!

Neal, if it wasn't such a small defect and so close to the original release, I would have agreed with you. However, in this case, I don't believe the 2-line change 15 hours from birth warrants a completely new release.

Obviously, no more changes will be made to the 3.30.00 STABLE release without incrementing the version number.

[NC Software]

But you did follow-up the release announcement nicely - well done, just not my practice to ever re-release like this.

[Ryan Lederman]

Originally Posted by NC Software

But you did follow-up the release announcement nicely - well done, just not my practice to ever re-release like this.

Thanks, yeah, I mean it would sort of be silly to issue a whole new release (and have the legacy of 3.30.00 be a 1-day build) just for a debug statement.

I'm sure the people who have already upgraded won't be too worried that they have to either make the edit or get a patch file from me - if reinstallation were necessary, then it would have warranted moving to a new build #.

[hbidad]

Originally Posted by NC Software

But you did follow-up the release announcement nicely - well done, just not my practice to ever re-release like this.

<vent> You seem to want things fixed NOW but complain when they are fixed</vent>

<opinion>Settle down and be thankful for what you got. Your ongoing ramblings is obsessive.</opinion>

[jnet]

Originally Posted by hbidad

<vent> You seem to want things fixed NOW but complain when they are fixed</vent>

<opinion>Settle down and be thankful for what you got. Your ongoing ramblings is obsessive.</opinion>

that is all I can say

[Ryan Lederman]

3.30.01 is out, which contains the fix for this.