I should add that whenever I restart the named service when the QMT
host's IP address is used as the nameserver in /etc/resolv.conf I get
the below error.

On 3/26/2015 8:12 AM, Eric Broch wrote:
> Hi Dan,
>
> Thanks!!!
>
> Usually, when the issue Fabian had manifests itself the error is
> logged to the submission, or the smtp, log (if I remember correctly),
> it was absent in Fabian's.
>
> While trouble shooting Fabian's issue, I ran into my own on CentOS 6
> which is my own failover server. Whenever I restart the 'named'
> service, I get a similar error (it happens on the stop portion of
> /etc/init.d/name script) in /var/log/qmail/submission/current.
>
> <error>
> /home/vpopmail/bin/vchkpw: error while loading shared libraries:
> libmysqlclient.so.15: cannot open shared object file: No such file or
> directory
> </error>
>
> If I remove vpopmail and reinstall it, everything starts working again.
>
> Has anyone seen this VERY odd behavior before?
>
> Eric
>
>
>
> On 3/26/2015 7:17 AM, Dan McAllister wrote:
>> Pardon me for being "Johnny come lately" on this, but the softlimit
>> issues comes from the now-default way of using TLS when connecting
>> (whether via SMTP -- which is ports 25, 587, and possibly 465 -- or
>> IMAP [only 143] or POP [only 110]) -- this is the "solution" to the
>> problem that they (they as-in "The Internet Gods") added the secure
>> ports for SSL connections, but then a large majority of people never
>> used them -- so they needed a way to get them to switch without
>> knowing they were switching... thus the TLS negotiation being thrown
>> in by new clients and servers alike.
>>
>> When the qmail-smtp program reads the request for TLS communications
>> (or if you've forced SSL as you might for port 465), it dynamically
>> loads the appropriate libraries... thus crashing your softlimit
>> memory allocation.
>>
>> The point of this overly-specific notation is that this is a
>> long-standing QMT installation weakness.
>>
>> I hope to have a document ready soon that will give some more
>> guidance to new QMT users -- especially NEWBIES.
>>
>> Dan
>> IT4SOHO
>>
>> On 3/25/2015 9:02 PM, Fabian Santiago wrote:
>>> eric,
>>>
>>> for me it was the softlimit. my mysql dir contains:
>>>
>>> total 3168
>>> drwxr-xr-x  3 root root    4096 Mar 25 15:55 .
>>> dr-xr-xr-x 42 root root   20480 Mar 25 15:55 ..
>>> lrwxrwxrwx  1 root root      26 Mar  9  2014 libmysqlclient_r.so.16
>>> -> libmysqlclient_r.so.16.0.0
>>> -rwxr-xr-x  1 root root 1595240 Feb 12  2014 libmysqlclient_r.so.16.0.0
>>> lrwxrwxrwx  1 root root      24 Mar  9  2014 libmysqlclient.so.16 ->
>>> libmysqlclient.so.16.0.0
>>> -rwxr-xr-x  1 root root 1584680 Feb 12  2014 libmysqlclient.so.16.0.0
>>> -rwxr-xr-x  1 root root   12935 Feb 12  2014 mysqlbug
>>> -rwxr-xr-x  1 root root    6399 Feb 12  2014 mysql_config
>>> drwxr-xr-x  2 root root    4096 Mar 25 15:55 plugin
>>>
>>>
>>>
>>> On Wed, Mar 25, 2015 at 9:00 PM, Eric Broch <[email protected]
>>> <mailto:[email protected]>> wrote:
>>>
>>>     Fabian,
>>>
>>>     Not sure of anymore issues, trying to troubleshoot your issue, I
>>>     ran into my own (/home/vpopmail/bin/vchkpw: error while loading
>>>     shared libraries: libmysqlclient.so.15: cannot open shared
>>>     object file). I thought it was the soft limit but no such luck.
>>>     Can you tell me what's in your /usr/lib64/mysql directory?
>>>
>>>     Eric
>>>
>>>
>>>     On 3/25/2015 6:34 PM, Fabian Santiago wrote:
>>>>     eric,
>>>>
>>>>     i got it; had to increase my softlimit in
>>>>     /var/qmail/supervise/submission/run
>>>>
>>>>     i set it to 100000000
>>>>
>>>>     thanks for your help. now i wonder what else i may find? 
>>>>
>>>>     On Wed, Mar 25, 2015 at 8:23 PM, Fabian Santiago
>>>>     <[email protected] <mailto:[email protected]>>
>>>>     wrote:
>>>>
>>>>         eric,
>>>>
>>>>         i've been reading around. my os is 64 bit. some people have
>>>>         complained about that. is that the culprit maybe? 
>>>>
>>>>         On Wed, Mar 25, 2015 at 8:14 PM, Fabian Santiago
>>>>         <[email protected]
>>>>         <mailto:[email protected]>> wrote:
>>>>
>>>>             yes i did:
>>>>
>>>>             @4000000055134e0918cd9df4 tcpserver: ok 2013
>>>>             mail.deviltracks.net:127.0.0.1:587 :127.0.0.1::35577
>>>>             @4000000055134e091a50ea64 tcpserver: end 2013 status 256
>>>>             @4000000055134e091a50fa04 tcpserver: status: 0/100
>>>>             @4000000055134eba1faa48fc tcpserver: status: 1/100
>>>>             @4000000055134eba1fafcb24 tcpserver: pid 2176 from
>>>>             127.0.0.1
>>>>             @4000000055134eba1fb0a1fc tcpserver: ok 2176
>>>>             mail.deviltracks.net:127.0.0.1:587 :127.0.0.1::35579
>>>>             @4000000055134eba20533ee4 tcpserver: end 2176 status 256
>>>>             @4000000055134eba20534a9c tcpserver: status: 0/100
>>>>             @4000000055134ebb1794facc tcpserver: status: 1/100
>>>>             @4000000055134ebb179b5b9c tcpserver: pid 2179 from
>>>>             127.0.0.1
>>>>             @4000000055134ebb179c26bc tcpserver: ok 2179
>>>>             mail.deviltracks.net:127.0.0.1:587 :127.0.0.1::35581
>>>>             @4000000055134ebb1846e994 tcpserver: end 2179 status 256
>>>>             @4000000055134ebb1846f164 tcpserver: status: 0/100
>>>>
>>>>
>>>>             On Wed, Mar 25, 2015 at 8:05 PM, Eric Broch
>>>>             <[email protected]
>>>>             <mailto:[email protected]>> wrote:
>>>>
>>>>                 Did you look in the submission log
>>>>                 (/var/log/qmail/submission/current)?
>>>>
>>>>                 On 3/25/2015 5:51 PM, Fabian Santiago wrote:
>>>>>                 eric,
>>>>>
>>>>>                 no log entries i can see.
>>>>>
>>>>>                 squirrel interface reports:
>>>>>                 Message not sent. Server replied:
>>>>>
>>>>>                     Temporary authentication failure
>>>>>                     454 oops, problem with child and I can't auth
>>>>>                     (#4.3.0)
>>>>>
>>>>>
>>>>>                     and this is centos 6.6.
>>>>>
>>>>>                     thanks.
>>>>>
>>>>>                     Fabian S.
>>>>>
>>>>>
>>>>>                 On Wed, Mar 25, 2015 at 6:11 PM, Eric Broch
>>>>>                 <[email protected]
>>>>>                 <mailto:[email protected]>> wrote:
>>>>>
>>>>>                     And, is this the error in the submission/smtp
>>>>>                     log (if not could you post it) or the error
>>>>>                     that you get at the squirrelmail interface.
>>>>>
>>>>>                     On 3/25/2015 3:47 PM, Fabian Santiago wrote:
>>>>>>                     Eric,
>>>>>>
>>>>>>                     thanks. that was easy. couple initial issues:
>>>>>>
>>>>>>                     1.> dovecot wasn't running upon restart. I
>>>>>>                     started it and set it to run at bootup.
>>>>>>                     correct? Does dovecot need addt'l configuration?
>>>>>>
>>>>>>                     2.> when sending a test msg, squirrelmail
>>>>>>                     tells me:
>>>>>>
>>>>>>                     Message not sent. Server replied:
>>>>>>
>>>>>>                         Temporary authentication failure
>>>>>>                         454 oops, problem with child and I can't
>>>>>>                         auth (#4.3.0)
>>>>>>
>>>>>>                         so I'm guessing something does need to be
>>>>>>                         configured somewhere.
>>>>>>
>>>>>>                         also, what all else do i need configured
>>>>>>                         out of the box?
>>>>>>
>>>>>>                         thanks.
>>>>>>
>>>>>>                         Fabian S.
>>>>>>
>>>>>>
>>>>>>                     On Wed, Mar 25, 2015 at 2:54 PM, Eric Broch
>>>>>>                     <[email protected]
>>>>>>                     <mailto:[email protected]>> wrote:
>>>>>>
>>>>>>                         On 3/25/2015 12:25 PM, Fabian Santiago wrote:
>>>>>>                         > Hello,
>>>>>>                         >
>>>>>>                         > I had stepped away from QMT for some
>>>>>>                         time but am returning. Currently,
>>>>>>                         > what is the best route to deploy QMT on
>>>>>>                         Centos and do you recommend
>>>>>>                         > Centos 6.x or 7 / 32 or 64 bit?
>>>>>>                         >
>>>>>>                         > I was scanning some of the past list
>>>>>>                         traffic and see that advancements
>>>>>>                         > and updates have been made to the whole
>>>>>>                         process and suite but wasn't
>>>>>>                         > sure where to begin. Thanks.
>>>>>>                         >
>>>>>>                         > --
>>>>>>                         >
>>>>>>                         > - Sincerely,
>>>>>>                         >
>>>>>>                         > Fabian S.
>>>>>>                         >
>>>>>>                         Hi Fabian,
>>>>>>
>>>>>>                         The latest stable version is QMT for
>>>>>>                         CentOS 6 found here:
>>>>>>                         https://github.com/QMailToaster/qmailtoaster-util
>>>>>>                         Read the file README.install. This is
>>>>>>                         very easy.
>>>>>>
>>>>>>                         For testing on CentOS 7:
>>>>>>                         1) Install CentOS 7 minimal install (I
>>>>>>                         install both options under
>>>>>>                         minimal install. One is development tools
>>>>>>                         and I can't remember the other).
>>>>>>                         2) curl
>>>>>>                         
>>>>>> ftp://ftp.whitehorsetc.com/pub/qmail/CentOS7/qmt/scripts/qt_prep.sh
>>>>>>                         >
>>>>>>                         qt_prep.sh
>>>>>>                         3) sh qt_prep.sh (Automatic reboot)
>>>>>>                         4) sh qt_install.sh
>>>>>>
>>>>>>                         Eric
>>>>>>
>>
>> -- 
>> IT4SOHO, LLC
>> 33 - 4th Street N, Suite 211
>> St. Petersburg, FL 33701-3806
>>
>> CALL TOLL FREE:
>>   877-IT4SOHO
>>
>> 877-484-7646 Phone
>> 727-647-7646 Local
>> 727-490-4394 Fax 
>>
>> We have support plans for QMail!
>>
>

Reply via email to