Bugzilla error: Can't locate object method quit via package “Net::SMTP::SSL” line 365

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bugzilla error: Can't locate object method quit via package “Net::SMTP::SSL” line 365

Sarah Weinberger-2
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 posted a detailed write-up in the Stack Exchange forum, no answers, hence here on a dedicated bugzilla forum, so if the above is not enough details, then...

https://unix.stackexchange.com/questions/547324/bugzilla-error-cant-locate-object-method-quit-via-package-netsmtpssl-lin

I contacted my web hosting provider, Media Temple, and they were very unprofessional and refused to even consider helping.

Any thoughts?
_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
PLEASE put [hidden email] in the To: field when you reply.
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla error: Can't locate object method quit via package “Net::SMTP::SSL” line 365

Sarah Weinberger-2
Fixed:

I missed the last response from the customer, when he wrote:

thanks solved using 'cpan upgrade Net::SMTP::SSL' command

That command resolved the issue. The original post is at:
https://support-bugzilla.mozilla.narkive.com/ULqK5oBb/error-while-smtp-setup

My email is now working fine. This command should have been in the installation instructions.
_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
PLEASE put [hidden email] in the To: field when you reply.
Reply | Threaded
Open this post in threaded view
|

Re: Bugzilla error: Can't locate object method quit via package “Net::SMTP::SSL” line 365

Sarah Weinberger-2
In reply to this post by Sarah Weinberger-2
For others, and for that matter a possible future me, I will explain things.

Before that, however, even though Bugzilla works (UI is fine, ability to add users, projects, etc. are all fine), the ./testserver.pl script still fails with being able to read padlock.png.

There is no "theme" support. The gray is drab. Also, upgrades should be simpler. I can imagine either an automatic update or a button that when pressed updates the software, much like Plesk.

----

There is a misunderstanding on how things went down and even if I followed the official Bugzilla docs originally, which I later did, the docs was still incomplete and not applicable to my environment. Also the local configuration file, ./localconfig, is missing a field for the user, not just the group to use.

Before continuing, here is my environment:

* CentOS 7 running Plesk Obsidian in a VPS (what Media Temple calls "DV")

The HTTPD configuration file, /etc/httpd/httpd.conf, showed that the user and group for HTTPD are both "apache". That is what the Bugzilla documents said to use in the ./localconfig file too! Sadly, that is wrong. The correct answer is "psacln" for the group. The best way to figure that out is to create a new temporary subdomain and look at the owner and group of the default files. In my case the answer is "jmr-admin:psacln". Placing psacln in the Bugzilla configuration file took care of the group policy. That means the two changes for apache are:

   # If you set this to anything other than "", you will need to run checksetup.pl
   # as root or as a user who is a member of the specified group.
   $webservergroup = 'psacln';

   # If set to 1, checksetup.pl will set file permissions so that Bugzilla
   # works in a SuexecUserGroup environment.
   $use_suexec = 1;

I had to manually change the user from "root" to "jmr-admin" after I reran ./checksetup.pl.

There are NO direct changes to /etc/httpd/httpd.conf. Nobody on any platform should make changes there, as that file gets overridden. If anything create a custom configuration file and place in the /etc/httpd/conf.d/ directory. The httpd configuration file, httpd.conf, automatically reads this directory. For my case adding something there IS WRONG and messed things up. The correct thing to do is one of two things:

1) (best way): Add a .htaccess file and set the contents to:

   #CGI
   DirectoryIndex index.cgi
   AddHandler cgi-script .cgi
   AddHandler cgi-script .pl
   Options +ExecCGI
   #

2) Inside Plesk edit for the domain (or subdomain as in my case) environment, namely: [domain] > Apache & nginx Settings >

* Handlers: Enter custom values
   cgi-script .cgi
   cgi-script .pl
* Index files: Enter custom value (leave default ones)

Note: Using this leaves out the "Options +ExecCGI", though that does not seem necessary.

The best way to verify CGI is to create a brand new  test subdomain and place a cgi script in the root directory, such as my testcgi2.cgi.

   #!/usr/bin/perl
   
   print "Content-type:text/html\r\n\r\n";
   print '<html>';
   print '<head>';
   print '<title>Hello Word - First CGI Program</title>';
   print '</head>';
   print '<body>';
   print '<h2>Hello Word! This is my first CGI program</h2>';
   print '</body>';
   print '</html>';
   
   1;

If changes to Apache are fine, then the script will show this formatted text with no code:

Hello Word! This is my first CGI program

I then copied the files from the downloaded compressed file to the subdomain. You might have to set permissions to 755 on extra key files.

I did have to run the yum command as indicated in the CentOS 7 and Bugzilla docs.

I had to run that extra script to get SMTP working, so that I do not get that annoying lack of a quit method.

I did look at the original Bugzilla docs and at first thought that Chinese would be easier to read. At least I once saw the mini series Shogun on TV, though that was Japanese. I contacted my web host provider, who gave me the link to the Bugzilla CentOS 7 guide.

That was incomplete as that did not discuss permissions or Plesk or any of the changes that I said need doing. The Bugzilla docs, which now is less Chinese like and more English like after days of suffering would still not have gotten the job done. Letting my web host provider initially make changes was maybe good, so that I saw that the site could come up, but with a lack of explaining and the lack of my current knowledge everything was bound to quickly not work the next time that I ran the ./checksetup.pl script.

I think that covers everything. I am still not an expert by any stretch, but hopefully my write-up helps.
_______________________________________________
support-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/support-bugzilla
PLEASE put [hidden email] in the To: field when you reply.