339093 - Getting error message while committing bugs.

Status: RESOLVED DUPLICATE of bug 87801

(Bugzilla :: Bugzilla-General, defect)

Description

[Kannan Udayarajan]

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

I have done three installations og bugzilla, but in the last two installations I m faced with this particular problem for some bugs.(some bugs  in some in some components of some products only).The error is randomly reproducible. The server settings are all fine.

When i enter a bug and click on commit button ,Im getting the following error:

Internal Error

Bugzilla has suffered an internal error. Please save this page and send it to
[e-mail] with details of what you were doing at the
time this message appeared. 

URL: http://repository/post_bug.cgi

undef error - Failed to send: Bad file descriptor at Z:/Perl/lib/CGI/Carp.pm
line 314. 

But eventually the bug gets saved.
But we get this particular error message which completely dampens the enthusiasm of using bugzilla.You know how it feels to get blocked by a bug in your bug tracker..

Please resolve this...


Reproducible: Sometimes

Steps to Reproduce:
1.Enter bug
2.Commit
3.Check if bug is saved or not

Actual Results:  
1. gives error message
2.Bug gets saved

Expected Results:  
1.should give message that bug has been saved

A similar software error also occured while trying to attach patches to some products.

Its driving me crazy since i cant see any particular reason for this random occurence of errors.Here again the attachments gets saved eeven though an error message is displayed.

Comment 1

[Kannan Udayarajan]

Attachment: Error screen shot

Comment 2

[Max Kanat-Alexander]

It's a bug in Mail::Mailer. You need to downgrade Mail::Mailer to 1.67.

Comment 3

[Kannan Udayarajan]

The version of MAil::Mailer that Im using is 1.67.
It was downloaded from the bugzilla site and Im using the stable release of 2.20 of Bugzilla.

So i think the problem lies somewhere else.
Any idea?

i did an installation yesterday and the first bug i entered itself returned the same error.A fresh installation should not give such an error under ideal circumstances.Does it have anything to do with the hardware configuration?

Comment 4

[Frédéric Buclin]

This looks like an internal bug in Perl or one of its modules, not a Bugzilla bug => INVALID.

Comment 5

[Kannan Udayarajan]

Attachment: Sanity check result

I got the sam message in the installations which had shown error while committing bugs.

Comment 6

[Kannan Udayarajan]

Hope you went through the sanity check result(attached).This was obtained in all the installations which showed the error while committing the bug.

Does that point to any database incongruency?
If so what must have caused it?

If it is a perl module error,how do we resolve it?

Comment 7

[Max Kanat-Alexander]

That sanitycheck message just means that mail wasn't sent.

Do you use the "SMTP" or the "sendmail" mail_delivery_method for Bugzilla?

The error you're seeing is something that we have experienced to be an error in Mail::Mailer.

Comment 8

[Kannan Udayarajan]

I think i have hit on the reason  ..or atleast what i think could be the reason for the error.I was using SMTP for sending mails in my mail_delivery_method in the first installtion.

But in the second and third installations(where i encountered the error);i had turned the mail_delivery_method to SMTP but did not configure the SMTP server as mail facility was not needed in the installations.I should have changed mail_delivery_method to "none".

Now I changed the mail_delivery_method to "none" and whoosh...the error has vanished.

I guess Bugzilla got confused,since it was asked to sent mails for bugs through SMTP but there was no SMTP server configured; and this confusion reflected in the sanity check.

This is what i think and it seems logical too.
What do you think.?

If it is indeed an issue,we can put a warning to users in the documentation asking them to change the mail_delivery_method parameter to " none" or face dire consequences...

What do you say?

PS: If the error is with Mail:: Mailer; has any resolution been obtained for it? Im using MAIL::MAILER v 1.67

Comment 9

[Max Kanat-Alexander]

Hey Kannan. I think you're right. We just need better error messages to show what's really happening.

*** This bug has been marked as a duplicate of 87801 ***