Displaying 20 results from an estimated 44 matches for "ts130".
2018 Jul 24
2
Mail has quit working
...nd
output?
_______________________________________________
CentOS mailing list
<mailto:CentOS at centos.org> CentOS at centos.org
<https://lists.centos.org/mailman/listinfo/centos>
https://lists.centos.org/mailman/listinfo/centos
Thanks,
Output from tail:
Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK.
Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK.
Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK.
Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK.
Jul 24 10:35:59 ts130 postfix/qmgr[8283]: C33128410546: f...
2018 Jul 24
2
Mail has quit working
...os.org] On Behalf Of Alexander
> Dalloz
> Sent: Tuesday, July 24, 2018 4:19 PM
> To: centos at centos.org
> Subject: Re: [CentOS] Mail has quit working
>
> Am 24.07.2018 um 21:07 schrieb TE Dukes:
> > Output from tail:
> >
> >
> >
> > Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> > Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> > Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> > Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> > Jul 24 10:35:59 t...
2017 Jan 30
2
firewalld
...ffic to localhost. If
you're
> getting connection refused, then those services aren't running.
>
> As for dealing with login denied errors, you should be looking at the IMAP
> server's logs, not the HTTP server's.
Here's the excerpts from maillog:
Jan 29 13:52:28 ts130 MailScanner[3941]: MailScanner Email Processor version
5.0.3 starting...
Jan 29 13:52:28 ts130 logger[3944]: MailScanner started
Jan 29 13:52:28 ts130 MailScanner[3941]: Reading configuration file
/etc/MailScanner/MailScanner.conf
Jan 29 13:52:28 ts130 MailScanner[3941]: Reading configuration file...
2018 Jul 24
0
Mail has quit working
Am 24.07.2018 um 21:07 schrieb TE Dukes:
> Output from tail:
>
>
>
> Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> Jul 24 10:35:59 ts130 postfix/qmgr[82...
2018 Jul 25
6
Mail has quit working
...rg
> >> Subject: Re: [CentOS] Mail has quit working
> >>
> >>
> >> Am 24.07.2018 um 21:07 schrieb TE Dukes:
> >>
> >>> Output from tail:
> >>>
> >>>
> >>>
> >>>
> >>> Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> >>> Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> >>> Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK.
> >>> Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK.
>...
2017 Jan 29
4
firewalld
Still un-resolved. Could be wrong but I think its firewalld preventing me
from accessing mail with roundcube.
I'm getting Connection to storage server failed.
>From roundcubemail log:
[29-Jan-2017 16:45:05 -0500]: <4r5ccifn> IMAP Error: Login failed for tdukes
from 192.168.1.102. AUTHENTICATE PLAIN: * BYE Internal error occurred. Refer
to server log for more information. in
2018 Jul 24
0
Mail has quit working
..., July 24, 2018 4:19 PM
>> To: centos at centos.org
>> Subject: Re: [CentOS] Mail has quit working
>>
>>
>> Am 24.07.2018 um 21:07 schrieb TE Dukes:
>>
>>> Output from tail:
>>>
>>>
>>>
>>>
>>> Jul 24 10:05:02 ts130 clamd[3226]: SelfCheck: Database status OK.
>>> Jul 24 10:15:02 ts130 clamd[3226]: SelfCheck: Database status OK.
>>> Jul 24 10:25:02 ts130 clamd[3226]: SelfCheck: Database status OK.
>>> Jul 24 10:35:02 ts130 clamd[3226]: SelfCheck: Database status OK.
>>> Jul 2...
2018 Jul 24
4
Mail has quit working
...he following:
$ postconf -nf; postconf -Mf
If I need any more info after that I'll let you know.
Peter
_______________________________________________
CentOS mailing list
CentOS at centos.org
https://lists.centos.org/mailman/listinfo/centos
Here's the output from tail:
Jul 24 07:00:21 ts130 postfix/pickup[4017]: 338CA811240E: uid=0
from=<root>
Jul 24 07:00:21 ts130 postfix/cleanup[7047]: 338CA811240E:
message-id=<20180724110021.338CA811240E at ts130.palmettodomains.com>
Jul 24 07:00:21 ts130 postfix/qmgr[8283]: 338CA811240E:
from=<root at ts130.palmettodomains.com>,...
2018 Jul 24
1
Mail has quit working
...gt;>
>> Peter
>> _______________________________________________
>> CentOS mailing list
>> CentOS at centos.org
>> https://lists.centos.org/mailman/listinfo/centos
>>
>>
>> Here's the output from tail:
>>
>>
>> Jul 24 07:00:21 ts130 postfix/pickup[4017]: 338CA811240E: uid=0
>> from=<root> Jul 24 07:00:21 ts130 postfix/cleanup[7047]: 338CA811240E:
>> message-id=<20180724110021.338CA811240E at ts130.palmettodomains.com> Jul 24
>> 07:00:21 ts130 postfix/qmgr[8283]: 338CA811240E:
>> from=<roo...
2018 Aug 26
3
Mail has quit working
On 08/25/2018 10:20 AM, TE Dukes wrote:
>
>> Let's go back to pastebin. What are the contents of /etc/nsswitch.conf
>> and /etc/hosts, now?
>>
> Link to pastebin: https://paste.fedoraproject.org/paste/97keKuhV4lMoLZ8DIrYT8w
"Hosts: files dns"
Try again.? "hosts"
2018 Jul 24
0
Mail has quit working
...eed any more info after that I'll let you know.
>
>
> Peter
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>
> Here's the output from tail:
>
> Jul 24 07:00:21 ts130 postfix/pickup[4017]: 338CA811240E: uid=0
> from=<root>
> Jul 24 07:00:21 ts130 postfix/cleanup[7047]: 338CA811240E:
> message-id=<20180724110021.338CA811240E at ts130.palmettodomains.com>
> Jul 24 07:00:21 ts130 postfix/qmgr[8283]: 338CA811240E:
> from=<root at ts130....
2018 Aug 26
2
Mail has quit working
Am 26.08.2018 um 15:25 schrieb TE Dukes:
> Checked maillog:
>
> Aug 26 09:12:31 ts130 postfix/qmgr[2194]: E5B948331053: from=<fail2ban at palmettodomains.com>, size=469, nrcpt=1 (queue active)
> Aug 26 09:12:31 ts130 postfix/smtp[2307]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
> Aug 26 09:12:32 ts130 postfix/smtp[2307]: E5B948331053: to=<root at ts130...
2017 Feb 01
2
time zone
...heck
>> various logs to see who/what made changes then - including looking
>> to see
> if
>> the apache server was restarted then and loaded changes made
>> previously.
>>
>>
>
> Here's an excerpt from /var/log/messages:
>
> Jan 31 12:15:19 ts130 zmc_dvideo0[13838]: INF [Den: 57000 -
> Capturing at 29.41 fps]
> Jan 31 12:15:19 ts130 zmc_dvideo1[13864]: INF [Deck: 57000 -
> Capturing at 30.30 fps]
> Jan 31 12:15:19 ts130 zmc_dvideo2[13890]: INF [Front: 57000 -
> Capturing at 30.30 fps]
> Jan 31 12:15:19 ts130 zma_m1[13847]:...
2017 Jan 31
2
time zone
> Date: Tuesday, January 31, 2017 18:16:36 -0500
> From: TE Dukes <tdukes at palmettoshopper.com>
>
>> From: CentOS [mailto:centos-bounces at centos.org] On Behalf Of
>> Richard Sent: Tuesday, January 31, 2017 5:19 PM
>>
>>
>> > Date: Tuesday, January 31, 2017 16:59:32 -0500
>> > From: TE Dukes <tdukes at palmettoshopper.com>
2017 Feb 01
0
time zone
..."magically". If this worked until noon, I'd
check
> various logs to see who/what made changes then - including looking to see
if
> the apache server was restarted then and loaded changes made previously.
>
>
Here's an excerpt from /var/log/messages:
Jan 31 12:15:19 ts130 zmc_dvideo0[13838]: INF [Den: 57000 - Capturing at
29.41 fps]
Jan 31 12:15:19 ts130 zmc_dvideo1[13864]: INF [Deck: 57000 - Capturing at
30.30 fps]
Jan 31 12:15:19 ts130 zmc_dvideo2[13890]: INF [Front: 57000 - Capturing at
30.30 fps]
Jan 31 12:15:19 ts130 zma_m1[13847]: INF [Den: 57000 - Analysing a...
2017 Feb 01
0
time zone
...e changes then - including looking to
> >> see
> > if
> >> the apache server was restarted then and loaded changes made
> >> previously.
> >>
> >>
> >
> > Here's an excerpt from /var/log/messages:
> >
> > Jan 31 12:15:19 ts130 zmc_dvideo0[13838]: INF [Den: 57000 - Capturing
> > at 29.41 fps] Jan 31 12:15:19 ts130 zmc_dvideo1[13864]: INF [Deck:
> > 57000 - Capturing at 30.30 fps] Jan 31 12:15:19 ts130
> > zmc_dvideo2[13890]: INF [Front: 57000 - Capturing at 30.30 fps] Jan 31
> > 12:15:19 ts130 zma_...
2018 Aug 24
3
Mail has quit working
> Here's the link for the maillog:
>
> https://paste.fedoraproject.org/paste/kbH2N9Pc~JPuCqVpE1kszQ
OK. There are a couple of things:
Aug 23 21:47:18 ts130 postfix/smtpd[3750]: warning: hostname localhost does not resolve to address 127.0.0.1
Aug 23 21:47:18 ts130 postfix/smtpd[3750]: connect from unknown[127.0.0.1]
That needs to be fixed. What does the entry for 127.0.0.1 look like in
/etc/hosts? Have you also defined ::1 to be localhost in /etc/...
2018 Aug 26
0
Mail has quit working
...eKuhV4lMoLZ8DIrYT8w
>
> "Hosts: files dns"
>
> Try again. "hosts"
>
Thanks!
Made the change above in nsswitch, rebooted, ran dig @localhost localhost +short
Got: dig: couldn't get address for 'localhost': failure
Checked maillog:
Aug 26 09:12:31 ts130 postfix/qmgr[2194]: E5B948331053: from=<fail2ban at palmettodomains.com>, size=469, nrcpt=1 (queue active)
Aug 26 09:12:31 ts130 postfix/smtp[2307]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Aug 26 09:12:32 ts130 postfix/smtp[2307]: E5B948331053: to=<root at ts130.palmettod...
2018 Aug 26
0
Mail has quit working
...tos-bounces at centos.org] On Behalf Of Alexander
> Dalloz
> Sent: Sunday, August 26, 2018 11:01 AM
> To: centos at centos.org
> Subject: Re: [CentOS] Mail has quit working
>
> Am 26.08.2018 um 15:25 schrieb TE Dukes:
> > Checked maillog:
> >
> > Aug 26 09:12:31 ts130 postfix/qmgr[2194]: E5B948331053:
> from=<fail2ban at palmettodomains.com>, size=469, nrcpt=1 (queue active)
> > Aug 26 09:12:31 ts130 postfix/smtp[2307]: connect to
> 127.0.0.1[127.0.0.1]:10024: Connection refused
> > Aug 26 09:12:32 ts130 postfix/smtp[2307]: E5B948331053:...
2018 Aug 24
1
Mail has quit working
...Subject: Re: [CentOS] Mail has quit working
> >
> >
> > > Here's the link for the maillog:
> > >
> > > https://paste.fedoraproject.org/paste/kbH2N9Pc~JPuCqVpE1kszQ
> >
> > OK. There are a couple of things:
> >
> > Aug 23 21:47:18 ts130 postfix/smtpd[3750]: warning: hostname localhost
> > does not resolve to address 127.0.0.1
> > Aug 23 21:47:18 ts130 postfix/smtpd[3750]: connect from
> > unknown[127.0.0.1]
> >
> > That needs to be fixed. What does the entry for 127.0.0.1 look like in
> > /et...