In a fresh Bugzilla installation (5.0.3), on a Scientific Linux 6 server I can't set the mail parameters due to this error: The new value for smtpserver is invalid: Cannot connect to mail.smpt.server Despite the fact that SMTP settings are correct. The SMTP server for the company is fully functional, on that server I downloaded thunderbird and was able to log in to my account smoothly without any problem which should mean the server has no problem with SMTP at all. I'm still searching with no clear hind what the cause could be. Any help is really appreciated! Update: In the old installation I can set these values and I can submit a bug but the email is not sent. This article says that bugzilla does not support SMTP with authentication (Not sure if true or not). Update: I installed the necessary modules here and again no luck. Update: On the old installation (4.something), we managed to setup an email account without authentication. This Bugzilla can now send email and it should work smoothly. Update: I found this useful article which applies a custom send mail script but the error message could not tell me where the error is.

I have registered myself at [Suse's Bugzilla](https://bugzilla.suse.com/) because I'd like to report a bug against a package, but when I open a new bug report I am asked the _component_ against which I want to report a bug. How do I query my system to know the _component_ to which a package belongs?

I installed Bugzilla on my CentOS 7 web server VPS. The install went smoothly, however when I went to set up email, I received the following error: > Can't locate object method "quit" via package "Net::SMTP::SSL" at Bugzilla/Config/Common.pm line 365. > > For help, please send mail to the webmaster (********), giving this error message and the time and date of the error. I set the email configuration to connect to Office 365, which means: SMTP Server: smtp.office365.com:587 smtp_ssl: on Username/password/mailfrom: that of the email address that I am using. I viewed the source file, Config/Common.pm, in question: 344 345 sub check_smtp_server { 346 my $host = shift; 347 my $port; 348 349 if ($host =~ /:/) { 350 ($host, $port) = split(/:/, $host, 2); 351 unless ($port && detaint_natural($port)) { 352 return "Invalid port. It must be an integer (typically 25, 465 or 587)"; 353 } 354 } 355 trick_taint($host); 356 # Let's first try to connect using SSL. If this fails, we fall back to 357 # an unencrypted connection. 358 foreach my $method (['Net::SMTP::SSL', 465], ['Net::SMTP', 25]) { 359 my ($class, $default_port) = @$method; 360 next if $class eq 'Net::SMTP::SSL' && !Bugzilla->feature('smtp_ssl'); 361 eval "require $class"; 362 my $smtp = $class->new($host, Port => $port || $default_port, Timeout => 5); 363 if ($smtp) { 364 # The connection works! 365 $smtp->quit; 366 return ''; 367 } 368 } 369 return "Cannot connect to $host" . ($port ? " using port $port" : ""); 370 } 371 What I deduced is that the connection information was a success and that Bugzilla was merely trying to quit the connection and return, no errors. I found this article on the internet regarding this problem. Mr. Thorsten Schoning said: > Then debug further: Check the version of your installed Net::SMTP::SSL, have a look at the source if a "quit" method is available etc. There should be a file Net/SMTP/SSL.pm somewhere in your perl installation or wherever and however you install packages. If you have used install-module.pl, empty the bugzilla/lib folder and install missing packages again using your package manager. > > Additionally look at the mentioned line of the Bugzilla code to see what Bugzilla thinks: It thinks you have Net::SMTP::SSL available, expects an available method and that seems to be missing. You need to find the reason why because from my understanding it should be available. Well, I did a locate for SSL.pm and came up with: [root@tkts-wtsc /]# locate SSL.pm /usr/lib64/perl5/vendor_perl/Net/SSL.pm /usr/share/perl5/vendor_perl/HTTP/Daemon/SSL.pm /usr/share/perl5/vendor_perl/IO/Socket/SSL.pm /usr/share/perl5/vendor_perl/Net/MQTT/Simple/SSL.pm /usr/share/perl5/vendor_perl/Net/SMTP/SSL.pm /usr/share/perl5/vendor_perl/Net/Server/Proto/SSL.pm /usr/share/perl5/vendor_perl/Software/License/OpenSSL.pm I viewed the contents of Net/SMTP/SSL.pm, but that did not contain any subroutines. I then viewed the contents of /Net/SSL.pm and saw subroutines/methods, but none of them quit, but then quit is an SMTP command, so I am not surprised there. Not sure if Mr. Schoning's response means anything or not, but even HIS linked SSL.pm source does not contain a quit method. I did a sudo yum install mod_ssl openssl as mentioned somewhere else and I get already installed and latest version, nothing to do. I did a sudo yum install perl-Net-SMTP-SSL and got Package perl-Net-SMTP-SSL-1.01-13.el7.noarch already installed and latest version. I installed all packages and updated everything. This question is a server setup issue, not a programming one, hence my placement of this question here and not on SO. I merely mention the source files, as the error mentioned it and I wanted to be complete and give all the details. I set the permissions for key folders: drwxr-x--- 2 jmr-admin psacln 4096 Oct 17 08:33 Config -rwxr-x--- 1 jmr-admin psacln 13547 Oct 16 16:55 Config.pm and all items in the Config folder are the same as: -rwxr-x--- 1 jmr-admin psacln 16836 Oct 16 16:55 Common.pm Now that I am writing this question, I do not think the issue is permissions, as perl found the SMTP module, not to mention SSL module, successfully did a test and was attempting to quit the connection, when perl could not find the quit method. I DID turn On the smtp_debug option, but I got no additional details. I found this reference, lot of good information, such as to include the port in the SMTP server field, which I originally forgot to do. Sadly, this reference did not resolve my problem. For what it is worth, I also tried my gmail account, as this article references Gmail. In that way, I could enter the information EXACTLY as on this page. I copied and pasted the information. I got the same error, immediately with no delay. That was a bit weird, as I would have expected a slight delay from either Gmail or Office 365, but whatever. **UPDATE** I am still looking and ran into this article. The result of sesstatus -b is SELinux status: disabled. That is possibly another problem, but not relating to my inability to send emails. If anything, it is a good thing for troubleshooting. Anyways, I discovered that there is such a thing as /var/log/httpd/error_log. The contents of this file are (keeps repeating for every attempt): [Thu Oct 17 09:17:22 2019] editparams.cgi: ******************************************************************* [Thu Oct 17 09:17:22 2019] editparams.cgi: at Bugzilla/Config/Common.pm line 362. [Thu Oct 17 09:17:22 2019] editparams.cgi: Can't locate object method "quit" via package "Net::SMTP::SSL" at Bugzilla/Config/Common.pm line 365. [Thu Oct 17 09:23:07 2019] editparams.cgi: Odd number of elements in hash assignment at /usr/share/perl5/vendor_perl/IO/Socket/IP.pm line 336. [Thu Oct 17 09:23:07 2019] editparams.cgi: ******************************************************************* [Thu Oct 17 09:23:07 2019] editparams.cgi: Using the default of SSL_verify_mode of SSL_VERIFY_NONE for client [Thu Oct 17 09:23:07 2019] editparams.cgi: is deprecated! Please set SSL_verify_mode to SSL_VERIFY_PEER [Thu Oct 17 09:23:07 2019] editparams.cgi: possibly with SSL_ca_file|SSL_ca_path for verification. [Thu Oct 17 09:23:07 2019] editparams.cgi: If you really don't want to verify the certificate and keep the [Thu Oct 17 09:23:07 2019] editparams.cgi: connection open to Man-In-The-Middle attacks please set [Thu Oct 17 09:23:07 2019] editparams.cgi: SSL_verify_mode explicitly to SSL_VERIFY_NONE in your application. [Thu Oct 17 09:23:07 2019] editparams.cgi: ******************************************************************* [Thu Oct 17 09:23:07 2019] editparams.cgi: at Bugzilla/Config/Common.pm line 362. [Thu Oct 17 09:23:07 2019] editparams.cgi: Can't locate object method "quit" via package "Net::SMTP::SSL" at Bugzilla/Config/Common.pm line 365. ~ This log shows that I have another side task to fix a deprecated CentOS setting and limit a Main-In-The-Middle attack, but that does not appear to be germane to my quit method nonexistence issue. I have to research that a bit more. The real error is line 362. That should have probably returned null / false to indicate an error. I bet that had line 362 really succeeded, then the quit method would exist. Sadly, I this environment is not under Visual Studio, where I can set a breakpoint and view contents. I am in server admin mode, so... my $smtp = $class->new($host, Port => $port || $default_port, Timeout => 5); Okay, I found this article, which helped me solve the SSL_VERIFY_NONE warnings. I opened up /usr/share/perl5/vendor_perl/IO/Socket/SSL.pm did a vi command, :set number, and then issue the command, /DEFAULT_SSL_ARGS, which took me to line 35. I then changed on line 49 from SSL_verify_mode => SSL_VERIFY_NONE, to SSL_verify_mode => SSL_VERIFY_PEER,. I then saved my changes and quit. I tried my email settings again and much better. [root@tkts-wtsc Config]# vi /var/log/httpd/error_log [root@tkts-wtsc Config]# [Thu Oct 17 09:23:07 2019] editparams.cgi: possibly with SSL_ca_file|SSL_ca_path for verification. [Thu Oct 17 09:23:07 2019] editparams.cgi: If you really don't want to verify the certificate and keep the [Thu Oct 17 09:23:07 2019] editparams.cgi: connection open to Man-In-The-Middle attacks please set [Thu Oct 17 09:23:07 2019] editparams.cgi: SSL_verify_mode explicitly to SSL_VERIFY_NONE in your application. [Thu Oct 17 09:23:07 2019] editparams.cgi: ******************************************************************* [Thu Oct 17 09:23:07 2019] editparams.cgi: at Bugzilla/Config/Common.pm line 362. [Thu Oct 17 09:23:07 2019] editparams.cgi: Can't locate object method "quit" via package "Net::SMTP::SSL" at Bugzilla/Config/Common.pm line 365. [Thu Oct 17 11:19:04 2019] editparams.cgi: Odd number of elements in hash assignment at /usr/share/perl5/vendor_perl/IO/Socket/IP.pm line 336. [Thu Oct 17 11:19:04 2019] editparams.cgi: Can't locate object method "quit" via package "Net::SMTP::SSL" at Bugzilla/Config/Common.pm line 365. ~ I am down to only 2 lines. What is interesting is that i do not get the complaint anymore about line 362. Hmm. If anyone is curious, here is the code to IP.pm at line 336: [root@tkts-wtsc Config]# vi /usr/share/perl5/vendor_perl/IO/Socket/IP.pm [root@tkts-wtsc Config]# 325 326 As a special case, if the constructor is passed a single argument (as 327 opposed to an even-sized list of key/value pairs), it is taken to be the value 328 of the C parameter. This is parsed in the same way, according to the 329 behaviour given in the C AND C PARSING section below. 330 331 =cut 332 333 sub new 334 { 335 my $class = shift; 336 my %arg = (@_ == 1) ? (PeerHost => $_) : @_; 337 return $class->SUPER::new(%arg); 338 } 339 (Sorry about the long question, more like me keeping notes, but I am hoping that others might benefit from all this information and the methodology that I used. There is virtually nothing out there, and if I ran into this bug, others will too.) Anyways, so how do I fix the problem?

I have a Bugzilla 4.2.4 install that is now unable to send email. It was able to send email without issue up until about a month ago (after about three months without issue). If someone posts a comment, a new bug or anything else that should generate an email, after they hit submit the following page takes forever to time out but eventually comes back with "Internal Server Error". Whatever they happen to be trying to do succeeds (bug gets created, file attached, comment posted, etc), so it appears that the problem is solely with generating the email. Following the [official guide](http://www.bugzilla.org/docs/3.0/html/general-advice.html) 's advice for troubleshooting I've created any errorlog but the output is nebulous at best: --------------------------------------------------------------------------- 06/03/13 13:02:02 global/code-error.html.tmpl mail_send_error 127.0.0.1 $env(ANSI_COLORS_DISABLED) = 1; $env(HOME) = "/root"; $env(LOGNAME) = "root"; $env(OLDPWD) = "/root"; $env(PATH) = "/usr/lib:/usr/sbin:/usr/ucblib"; $env(PWD) = "/var/www/bugzilla"; $env(SHELL) = "/bin/sh"; $env(SHLVL) = 1; $env(USER) = "root"; $env(_) = "/var/www/bugzilla/whine.pl"; --------------------------------------------------------------------------- 06/03/13 13:17:02 global/code-error.html.tmpl mail_send_error 127.0.0.1 $env(ANSI_COLORS_DISABLED) = 1; $env(HOME) = "/root"; $env(LOGNAME) = "root"; $env(OLDPWD) = "/root"; $env(PATH) = "/usr/lib:/usr/sbin:/usr/ucblib"; $env(PWD) = "/var/www/bugzilla"; $env(SHELL) = "/bin/sh"; $env(SHLVL) = 1; $env(USER) = "root"; $env(_) = "/var/www/bugzilla/whine.pl"; I've verified that SELinux isn't the issue by switching it into Permissive for the full duration of this troubleshooting, and I've created simple perl scripts that send my personal email account when invoked over Apache httpd. httpd's error_log doesn't have anything too interesting for this error: [Wed Jun 12 13:21:20 2013] [warn] [client 152.xx.99.118] Timeout waiting for output from CGI script /var/www/bugzilla/post_bug.cgi, referer: http://bugs.xxx.edu/enter_bug.cgi?product=Banner%20INB [Wed Jun 12 13:21:20 2013] [error] [client 152.xx.99.118] Premature end of script headers: post_bug.cgi, referer: http://bugs.xxx.edu/enter_bug.cgi?product=Banner%20INB Basically, I'm unsure where to take it from here, I don't know how to get Bugzilla to give me more descriptive error information. I know that administratively I didn't change anything, there's plenty of processor time and storage space available, so I'm not sure why it all of a sudden broke. This is on a RHEL5 machine with Perl 5.8.8

I've installed Bugzilla following the guide here , however, when I restart my Apache server (so I can login to the Bugzilla system), I get the following error... Jun 27 16:10:30 localhost.localdomain systemd[1] : Starting The Apache HTTP Server... Jun 27 16:10:30 localhost.localdomain httpd: AH00526: Syntax error on line 354 of /etc/httpd/conf/httpd.conf: Jun 27 16:10:30 localhost.localdomain httpd: Can't locate /var/www/html/bugzilla/mod_perl.pl in @INC (@INC contains: /var/www/html/bugzilla /var/www/html/bugzilla/li...) line 1.\n Jun 27 16:10:30 localhost.localdomain systemd[1] : httpd.service: main process exited, code=exited, status=1/FAILURE Jun 27 16:10:30 localhost.localdomain httpd: AH00526: Syntax error on line 354 of /etc/httpd/conf/httpd.conf: Jun 27 16:10:30 localhost.localdomain httpd: Can't locate /var/www/html/bugzilla/mod_perl.pl in @INC (@INC contains: /var/www/html/bugzilla /var/www/html/bugzilla/li...) line 1.\n Jun 27 16:10:30 localhost.localdomain systemd[1] : httpd.service: control process exited, code=exited status=1 Jun 27 16:10:30 localhost.localdomain systemd[1] : Failed to start The Apache HTTP Server. Jun 27 16:10:30 localhost.localdomain systemd[1] : Unit httpd.service entered failed state. This is despite the fact that the /var/www/html/bugzilla/mod_perl.pl file is present and has sufficient file permissions. Any ideas on how to fix this? (I'm working on Fedora v16) Edit: Seemed like the SELinux tags were the problem, server starts now and I can access the bugzilla page, however the cgi file isn't executing it's just displaying at text. Thoughts?

What an hour of Googling bring out that **mainstream** Linux kernel bugs are being logged in two distinct systems: Mailing list ------------ > This is the Linux kernel development discussion and bug reporting > mailing list. The mailing list is archived by a number of services, *e.g.* - Gmane - lkml - MARC - Mail archive - Indiana Bugzilla -------- > This is the Kernel Tracker system (based on Bugzilla) for posting bugs > against the mainline Linux kernels (not distribution kernels). Distributions, *e.g.* Ubuntu have their own bug tracker which may be set to track upstream bugs. I wonder that, - Are the bugs reported on the either of the services synced back to the other? - Assuming that the mailing list and the bugzilla are not mirrors of each other (*i.e.* those are independent and bugs are *not* synced), how do Linux developers coordinate between the bugs reported across services? - Isn't it inconvenient to refer to the bugs reported to mailing list later on due to not having any bug ID? (I understand that one can refer by a mailing archive URL, however doesn't look professional IMO) - Should a new bug be reported to any one of the services or both?

I installed bugzilla and added the following code to httpd.conf to access it from my browser AddHandler cgi-script .cgi Options +Indexes +ExecCGI DirectoryIndex index.cgi AllowOverride Limit But if I try to access it from browser I'm getting the following error The server encountered an internal error or misconfiguration and was unable to complete your request.

Several months ago I've successfully installed bugzilla on local test server. Now, I wanted to change my credentials email in bugzilla and I've got following email: > Bugzilla has received a request to change the email address for the > account user@test.com to your address. > > To confirm the change, visit the following link: > > http://84.21.236.183/bugzilla/token.cgi?t=8aiQF72AFE&a=cfmem > > If you are not the person who made this request, or you wish to cancel > this request, visit the following link: > > http://84.21.236.183/bugzilla/token.cgi?t=8aiQF72AFE&a=cxlem > > If you do nothing, the request will lapse after 3 days (on October 10, > 2015 at 15:46 CEST). The problem is, that I've moved server to new location and got new internet provider, which gave me new static IP address, so 84.21.236.183 is no longer valid. Where do I setup this IP in bugzilla settings files so it will point to new IP address?

The current email format is as below – > ID, Severity, Priority, Plt, Assignee, Status, Resolution, Summary What I need is as below – > ID, Product, Component, Assignee, Status, Resolution, Summary My bugzilla Version is: 4.2.4 I have edited below files but no avail: /var/www/bugzilla/whine.pl # Execute the saved query my @searchfields = qw( bug_id product component assigned_to bug_status resolution short_desc ); /var/www/bugzilla/template/en/default/whine/mail.txt.tmpl [% FOREACH bug=query.bugs %] [% terms.Bug +%] [%+ bug.bug_id %]: [%+ urlbase %]show_bug.cgi?id=[% bug.bug_id +%] Product: [%+ display_value("product", bug.product) -%] Component: [%+ display_value("component", bug.component) -%] Assignee: [%+ bug.assigned_to %] Status: [%+ display_value("bug_status", bug.bug_status) %] [%- IF bug.resolution -%] Resolution: [% display_value("resolution", bug.resolution) -%] [%- END %] Summary: [% bug.short_desc %] [% END %] [% END %] /var/www/bugzilla/template/en/default/whine/mail.html.tmpl [% FOREACH query=queries %]

[%+ query.title FILTER html %]

ID Product Component Assignee Status Resolution Summary [% FOREACH bug=query.bugs %] [% bug.bug_id %] [% display_value("product", bug.bug_product) FILTER html %] [% display_value("component", bug.component) FILTER html %] [% bug.assigned_to FILTER html %] [% display_value("bug_status", bug.bug_status) FILTER html %] [% display_value("resolution", bug.resolution) FILTER html %] [% bug.short_desc FILTER html %] [% END %] [% END %]

I have a bugzilla instance. I also have an IRC channel. I need a bot which can spew out any changes happening in bugzilla. The bot should prompt or tell when any action from :- a. Raising a bug b. Comments on the bug c. Resolution changes on the bug (confirmed,Will not fix,RESOLVED-fixed etc.) are also shared. I looked around and found bugzilla-linker, see https://wiki.mozilla.org/Bugzilla:Addons but neither the code or the binary is there anywhere. Can somebody share an alternative of that if it exists ? Update - In addition it would be nice if it is able to have it log conversations on the channel as well, kinda channel logging. @Mikel did find those but they don't seem to have the logging feature. It would be nice if one bot has it all.

We have over 10000 servers to patch for bash vulnerability (shellshock) bug. Now my question is what is the command to patch this bug ? And how we can check whether the patch has been installed and the bug has been fixed ?