Notification by mail stopped after upgrade to 5.5.3

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
biroby
Posts: 21
Joined: Wed Nov 30, 2016 4:29 am

Re: Notification by mail stopped after upgrade to 5.5.3

Post by biroby »

Yes, notification are listed.
You do not have the required permissions to view the files attached to this post.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Notification by mail stopped after upgrade to 5.5.3

Post by scottwilkerson »

Is you Admin -> Mail Settings still set to SMTP?
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
biroby
Posts: 21
Joined: Wed Nov 30, 2016 4:29 am

Re: Notification by mail stopped after upgrade to 5.5.3

Post by biroby »

No is set to sendmail.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Notification by mail stopped after upgrade to 5.5.3

Post by scottwilkerson »

Then you need to look for the messages in /var/log/maillog
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
biroby
Posts: 21
Joined: Wed Nov 30, 2016 4:29 am

Re: Notification by mail stopped after upgrade to 5.5.3

Post by biroby »

Hi,
no entry found in maillog.

[root@itpglnx02 ~]# tail -f /var/log/maillog
Sep 5 09:48:09 itpglnx02 postfix/pickup[22505]: 7C5EF45CE6E: uid=0 from=<root>
Sep 5 09:48:09 itpglnx02 postfix/cleanup[22538]: 7C5EF45CE6E: message-id=<[email protected]>
Sep 5 09:48:09 itpglnx02 postfix/qmgr[22506]: 7C5EF45CE6E: from=<[email protected]>, size=275, nrcpt=1 (queue active)
Sep 5 09:48:11 itpglnx02 postfix/smtp[22540]: 7C5EF45CE6E: to=<[email protected]>, relay=mx0b-001b2d01.pphosted.com[148.163.158.5]:25, delay=1.5, delays=0.01/0/0.82/0.68, dsn=2.0.0, status=sent (250 2.0.0 2ma7jbg7pn-1 Message accepted for delivery)
Sep 5 09:48:11 itpglnx02 postfix/cleanup[22538]: 019B645CE75: message-id=<[email protected]>
Sep 5 09:48:11 itpglnx02 postfix/qmgr[22506]: 019B645CE75: from=<>, size=1937, nrcpt=1 (queue active)
Sep 5 09:48:11 itpglnx02 postfix/bounce[22542]: 7C5EF45CE6E: sender delivery status notification: 019B645CE75
Sep 5 09:48:11 itpglnx02 postfix/qmgr[22506]: 7C5EF45CE6E: removed
Sep 5 09:48:11 itpglnx02 postfix/local[22543]: 019B645CE75: to=<[email protected]>, relay=local, delay=0, delays=0/0/0/0, dsn=2.0.0, status=sent (delivered to mailbox)
Sep 5 09:48:11 itpglnx02 postfix/qmgr[22506]: 019B645CE75: removed
You do not have the required permissions to view the files attached to this post.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Notification by mail stopped after upgrade to 5.5.3

Post by scottwilkerson »

001b2d01.pphosted.com[148.163.158.5]:25, delay=1.5, delays=0.01/0/0.82/0.68, dsn=2.0.0, status=sent (250 2.0.0 2ma7jbg7pn-1 Message accepted for delivery)
this means 001b2d01.pphosted.com accepted the message from your Nagios server. What happens after that is beyond Nagios servers control
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
biroby
Posts: 21
Joined: Wed Nov 30, 2016 4:29 am

Re: Notification by mail stopped after upgrade to 5.5.3

Post by biroby »

Hi Scott,
that record is about the last test email.

No new mail were sent from 5 Sep.
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Notification by mail stopped after upgrade to 5.5.3

Post by scottwilkerson »

Can you PM me a profile.zip from Admin -> System Profile

Thanks
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
scottwilkerson
DevOps Engineer
Posts: 19396
Joined: Tue Nov 15, 2011 3:11 pm
Location: Nagios Enterprises
Contact:

Re: Notification by mail stopped after upgrade to 5.5.3

Post by scottwilkerson »

It appears that your nagios crons aren't running can you send the output of the following:

Code: Select all

chage -l nagios
tail -50  /var/log/cron
Former Nagios employee
Creator:
Human Design Website
Get Your Human Design Chart
biroby
Posts: 21
Joined: Wed Nov 30, 2016 4:29 am

Re: Notification by mail stopped after upgrade to 5.5.3

Post by biroby »

Hi,
this is the command output

[root@itpglnx02 ~]# chage -l nagios
Last password change : May 30, 2018
Password expires : Aug 28, 2018
Password inactive : never
Account expires : never
Minimum number of days between password change : 1
Maximum number of days between password change : 90
Number of days of warning before password expires : 7
[root@itpglnx02 ~]# tail -50 /var/log/cron
Sep 7 15:50:01 itpglnx02 crond[18241]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18238]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18241]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18238]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18240]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18240]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18233]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18233]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18242]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:50:01 itpglnx02 crond[18242]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18299]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18299]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18298]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18303]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18303]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18300]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18300]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18305]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18305]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18302]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18298]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18304]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18304]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18307]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18307]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18306]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18306]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18301]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18301]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:51:01 itpglnx02 crond[18302]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18354]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18354]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18355]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18358]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18356]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18358]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18356]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18357]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18360]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18357]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18360]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18359]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18362]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18359]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18362]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18355]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18361]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18361]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18363]: (nagios) PAM ERROR (Authentication token is no longer valid; new one required)
Sep 7 15:52:01 itpglnx02 crond[18363]: (nagios) FAILED to authorize user with PAM (Authentication token is no longer valid; new one required)
[root@itpglnx02 ~]#
Locked