304012 - Comitting an existing bug (even with no changes) results in "undef error - Invalid argument at C:/Perl/lib/CGI/Carp.pm line 314"

Status: RESOLVED INVALID

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Edward Chan]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: Bugzilla Version 2.20rc2

Comitting an existing bug created using Bugzilla 2.18, even with no changes, 
results in "undef error - Invalid argument at C:/Perl/lib/CGI/Carp.pm line 
314".  The changes are commited to the database correctly however.  This used 
to work fine under Bugzilla 2.18.

This happens 100% of the time with bugs existing created using Bugzilla 2.18.  
This does not happen with bugs created with Bugzilla 2.20rc2 bugs.

Steps taken to resolve: I have run checksetup.pl.  I have tried this using the 
default templates as well as our own.  I have tried to commit with changes 
made as well as with no changes made.  I have upgraded to and am using the 
latest version of Activeperl 5.8.7.

Environment details as follows:
- Bugzilla: Version 2.20rc2
- Operating System: WindowsXP 2002 Sp1
- ActivePerl: ActivePerl-5.8.7.813-MSWin32-x86-148120.msi
- MySQL: mysql-essential-4.1.12-win32.msi
- Browser: IE 6.02
- Web server: IIS

Reproducible: Always

Steps to Reproduce:
1. Select an existing bug that was created using Bugzilla v2.18.
2. (Optional) make a few changes
3. Click on the commit button.
Actual Results:  
Regardless of whether I make changes or not, the following occurs:

Error message as follows (see screenprint for exact image):
Bugzilla has suffered an internal error....
URL: http://egvamapbs101.iws.ch.ml.com:8091/process_bug.cgi
undef error - Invalid argument at C:/Perl/lib/CGI/Carp.pm line 314.  

If I do make changes prior to commiting, the same error message shows up.  
Checking the bug afterwards shows that the changes are commiting correctly.

Comment 1

[Edward Chan]

Attachment: IMAGE of: "undef error - Invalid argument at C:/Perl/lib/CGI/Carp.pm line 314"

Comment 2

[Edward Chan]

Testing this a bit more finds that it isn't consistant.  Some of the old 
records can be updated without this error occuring.  Any help/suggestions 
would be greatly appreciated.

Comment 3

[:glob ✱]

this could be triggered by an email delivery problem.

Comment 4

[:glob ✱]

i was unable to reproduce this bug on xp with an upgraded 2.18 to 2.20 database.

to help track it down, uncomment the following lines in globals.pl:

sub die_with_dignity {
    use Carp;  # for confess()
    my ($err_msg) = @_;
    print $err_msg;
    confess($err_msg);
}
$::SIG{__DIE__} = \&die_with_dignity;

this'll give us a stack trace that'll show exactly what the trigger of the error
message is.

Comment 5

[Edward Chan]

Byron,

Many thanks for pointing us in the right direction.  It was an email delivery 
issue.  Completely deactivting email (or fully activating it) means that it 
works properly.  We had thought we had turned off email during our brief 
trialling period of 2.20rc2, but obviously not properly.

What really threw us off was that the "undef error" message being produced was 
different to the 2.18 email problem message which gives an error message 
related to SMTP.

I am resolving this as 'invalid' and our organization is continuing with our 
trial of Bugzilla 2.20rc2.

Many thanks again,

Ed

Comment 6

[Frédéric Buclin]

*** Bug 319648 has been marked as a duplicate of this bug. ***

Comment 7

[Frédéric Buclin]

*** Bug 363227 has been marked as a duplicate of this bug. ***