While combing through some log data I noticed that there are a large number of errors generated by an alarm notification profile that doesn't appear in any of my projects. Here are 2 instances of the profile throwing an error:
Instance 1
INFO | jvm 1 | 2024/08/28 07:50:31 | com.sun.mail.util.MailConnectException: Couldn't connect to host, port: Smtp.gmail.com, 25; timeout 10000
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2053)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:697)
INFO | jvm 1 | 2024/08/28 07:50:31 | at javax.mail.Service.connect(Service.java:386)
INFO | jvm 1 | 2024/08/28 07:50:31 | at javax.mail.Service.connect(Service.java:245)
INFO | jvm 1 | 2024/08/28 07:50:31 | at javax.mail.Service.connect(Service.java:194)
INFO | jvm 1 | 2024/08/28 07:50:31 | at javax.mail.Transport.send0(Transport.java:253)
INFO | jvm 1 | 2024/08/28 07:50:31 | at javax.mail.Transport.send(Transport.java:124)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.inductiveautomation.ignition.alarming.notification.email.OneWayNotificationProfile$EmailTask.run(OneWayNotificationProfile.java:271)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.inductiveautomation.ignition.alarming.notification.email.OneWayNotificationProfile.lambda$new$0(OneWayNotificationProfile.java:73)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.inductiveautomation.ignition.common.util.ThrottlingAggregator.check(ThrottlingAggregator.java:94)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.inductiveautomation.ignition.common.util.ThrottlingAggregator$1.run(ThrottlingAggregator.java:113)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.lang.Thread.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | Caused by: java.net.SocketTimeoutException: connect timed out
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at java.base/java.net.Socket.connect(Unknown Source)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:310)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:236)
INFO | jvm 1 | 2024/08/28 07:50:31 | at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2019)
INFO | jvm 1 | 2024/08/28 07:50:31 | ... 16 common frames omitted
Instance 2
08:44 | E [a.N.OneWayNotificationProfile ] [12:08:44]: Error sending notification email: alarm-source=Infrastructure Live Tags/Access_Controls/_8X_Plug_Door_Open/8X Plug Door Open, alarm-notification-profile=One-Way Email Alarms, alarm-name=8X Plug Door Open
INFO | jvm 1 | 2024/08/28 08:08:44 | com.sun.mail.util.MailConnectException: Couldn't connect to host, port: Smtp.gmail.com, 25; timeout 10000
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2053)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:697)
INFO | jvm 1 | 2024/08/28 08:08:44 | at javax.mail.Service.connect(Service.java:386)
INFO | jvm 1 | 2024/08/28 08:08:44 | at javax.mail.Service.connect(Service.java:245)
INFO | jvm 1 | 2024/08/28 08:08:44 | at javax.mail.Service.connect(Service.java:194)
INFO | jvm 1 | 2024/08/28 08:08:44 | at javax.mail.Transport.send0(Transport.java:253)
INFO | jvm 1 | 2024/08/28 08:08:44 | at javax.mail.Transport.send(Transport.java:124)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.inductiveautomation.ignition.alarming.notification.email.OneWayNotificationProfile$EmailTask.run(OneWayNotificationProfile.java:271)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.inductiveautomation.ignition.alarming.notification.email.OneWayNotificationProfile.lambda$new$0(OneWayNotificationProfile.java:73)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.inductiveautomation.ignition.common.util.ThrottlingAggregator.check(ThrottlingAggregator.java:94)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.inductiveautomation.ignition.common.util.ThrottlingAggregator$1.run(ThrottlingAggregator.java:113)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.lang.Thread.run(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | Caused by: java.net.SocketTimeoutException: connect timed out
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.net.PlainSocketImpl.socketConnect(Native Method)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.net.AbstractPlainSocketImpl.connect(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.net.SocksSocketImpl.connect(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at java.base/java.net.Socket.connect(Unknown Source)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:310)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:236)
INFO | jvm 1 | 2024/08/28 08:08:44 | at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2019)
INFO | jvm 1 | 2024/08/28 08:08:44 | ... 16 common frames omitted
I've checked both tags that generated the error, and neither has an alarm, active, or clear pipeline associated with their configured alarms. I tried to pull a list of all the alarm pipelines with the following script:
for proj in system.project.getProjectNames():
print '%s: %s' % (proj, system.alarm.listPipelines(proj))
And received the following:
Chiller: []
ECW_Interlocks: []
EmCAL_LV: []
INTT: []
Copy_Of_TPC_Cooling: []
EmCal_Cooling: []
HCAL_LV: []
EmCal_Humidity: []
TPC_Cooling: []
INTT_Cooling: []
SOB_LV: []
INTT_All: []
TPC_LV: []
Test_IPCamera: []
EmCal_All: []
sPHENIX_Infrastructure: [Email Notification]
TPC_All: []
Copy_Of_Chiller: []
HVAC_View: []
INTT_Humidity: []
LV_Test_Crate: []
TPC_Humidity: []
CDU_Err_Ctrl: []
sEPD_LV: []
Back_End_Controls_EXPERT: []
TPC_LV_EXPERT: []
TPC_Temps: []
MBD_TCs: []
The script results look right. To my knowledge there is only the one pipeline active in the one project on my gateway, and when I look at the Alarm Notification Pipelines tree in the designer I see Email Notification and not the One-way Email Alarms that's reported in the logs. The name of the profile throwing the error does sound like the name of an earlier iteration of the profile that was used. Is there a directory I should check for an artifact that may be left over from an earlier pipeline?