Replacement cabinet wont send embedded emails 9.1 6

[MiamiMax]

Strangest thing happened that I have never had happen before.

I had an IPO 500v2 9.1 that has a power supply that that was causing the cabinet to reboot often.

I had a spare 9.1 cabinet available with a new power supply so I just moved the SD card over and everything came up just fine.

However after a while I started to get complaints that all voice mails to email were not going out same thing for the Events notifications.

I did the usual rebooted, reloaded a back up but still the same problem.

I then moved the SD card back over the original control unit and emails started going out again.

I moved the card back over to the new control unit and once again everything is working ok except for the voice mail to emails.

All cables and connections to the IT network are exactly the same.

Here is the Monitor Trace from the new control unit cabinet below. I hunted around for any threads on this issue but could not find any solution's.


********** Warning: Logging to Screen Started **********
2023-08-17T04:14:36 201436mS PRN: SSITask:rocessExecuteCommandRequestMessage 9
2023-08-17T04:14:36 201436mS PRN: Root::Execute Command
2023-08-17T04:14:36 201436mS SMTP: SMTPServer New Email...
2023-08-17T04:14:36 201436mS PRN: SSITask::CompleteExecuteCommandRequest()
2023-08-17T04:14:36 201438mS SMTP: SMTPServer woken up... Session 00000000 Client 00000000 State 1 Q Size 9 current_message 00000000
2023-08-17T04:14:36 201438mS SMTP: SMTPServer is waiting on DNS server to resolve FQDN [smtp.google.com] - Retry 6 of 8.
2023-08-17T04:14:36 201438mS SMTP: SMTPServer snoozing...

********** SysMonitor v9.1.1.0 build 10 [connected to 192.168.3.31 (Christ Luth_9_1)] **********
2023-08-17T04:14:36 201595mS PRN: Monitor Status IP 500 V2 9.1.1.0 build 10
2023-08-17T04:14:36 201595mS PRN: LAW=U PRI=0, BRI=0, ALOG=4, VCOMP=0, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=1(VER=2 TYP=3) 1-X=0 CALLS=0(TOT=0)
2023-08-17T04:14:36 201830mS PRN: SSITask:rocessExecuteCommandRequestMessage 9
2023-08-17T04:14:36 201830mS PRN: Root::Execute Command
2023-08-17T04:14:36 201831mS SMTP: SMTPServer New Email...
2023-08-17T04:14:36 201831mS PRN: SSITask::CompleteExecuteCommandRequest()
2023-08-17T04:14:36 201833mS SMTP: SMTPServer woken up... Session 00000000 Client 00000000 State 1 Q Size 10 current_message 00000000
2023-08-17T04:14:36 201833mS SMTP: SMTPServer is waiting on DNS server to resolve FQDN [smtp.google.com] - Retry 7 of 8.
2023-08-17T04:14:36 201833mS SMTP: SMTPServer snoozing...
2023-08-17T04:14:37 202141mS PRN: SSITask:rocessExecuteCommandRequestMessage 9
2023-08-17T04:14:37 202141mS PRN: Root::Execute Command
2023-08-17T04:14:37 202141mS PRN: SSITask::CompleteExecuteCommandRequest()
2023-08-17T04:14:37 202498mS PRN: SSITask:rocessExecuteCommandRequestMessage 9
2023-08-17T04:14:37 202498mS PRN: Root::Execute Command
2023-08-17T04:14:37 202499mS PRN: SSITask::CompleteExecuteCommandRequest()
2023-08-17T04:14:37 202699mS PRN: SSITask:rocessExecuteCommandRequestMessage 9
2023-08-17T04:14:37 202699mS PRN: Root::Execute Command
2023-08-17T04:14:37 202700mS PRN: SSITask::CompleteExecuteCommandRequest()
2023-08-17T04:14:51 216833mS SMTP: SMTPServer woken up... Session 00000000 Client 00000000 State 1 Q Size 10 current_message 00000000
2023-08-17T04:14:51 216833mS SMTP: SMTPServer is waiting on DNS server to resolve FQDN [smtp.google.com] - Retry 8 of 8.
2023-08-17T04:14:51 216834mS SMTP: SMTPServer snoozing...
2023-08-17T04:15:06 231834mS SMTP: SMTPServer woken up... Session 00000000 Client 00000000 State 1 Q Size 10 current_message 00000000
2023-08-17T04:15:06 231834mS SMTP: SMTPServer cannot resolve FQDN. No valid response received from DNS server.
2023-08-17T04:15:06 231834mS SMTP: SMTPServer Snoozing for 5 minutes...
2023-08-17T04:15:06 231834mS SMTP: SMTPServer snoozing...

 

[IPid10t]

Looks to be a DNS issue. It is failing to resolve FQDN (smtp.google.com). In Manager go to system>DNS and in the DNS server IP address put 8.8.8.8, and for the backup i usually place the customers DNS server if they have one.

 

[snowman50]

Check with IT company..maybe the port on the data switch is tagged to the MAC address of the IPO.
Therefore changing the ipo may be blocked some out for internet access.

 

[MiamiMax]

IPid10:

Currently I have the following for SYSTEM>DNS:

DNS SERVER IP ADDRESS: 8.8.8.8
BACK UP SERVER DNS IP ADDRESS: 8.8.4.4

 

[IPid10t]

i would check with what snowman50 suggested. See if the IT company has the MAC of the old IPO tagged to that port. Another thing to see if you at least have outside access is go into system status and do a ping test to 8.8.8.8 and see if you receive a response.

 

[Westi]

I agree as it seems that the DNS entry might be in there but either the response is not coming or faulty or it is already blocked outgoing which seems that some IT guys do these days. They block 8.8.8.8 and 8.8.4.4 because they want to force all devices to use their local DNS server.

2023-08-17T04:15:06 231834mS SMTP: SMTPServer cannot resolve FQDN. No valid response received from DNS server.
2023-08-17T04:14:36 201438mS SMTP: SMTPServer is waiting on DNS server to resolve FQDN [smtp.google.com] - Retry 6 of 8

Joe
FHandw, ACSS, ACIS

 

[MiamiMax]

Hi again. I check with the IT guy and he said he never blocks MAC addresses. I also took the control unit and connected it to a simple network with a simple router 192.168.1.1 and I am still seeing the same SNOOZING error from monitor I did before.

The old cabinet works just fine. Could it be something within the new cabinets firmware that is causing it to cat this way?

 

[budbyrd]

The cabinet would have been up or down graded to the version of the SD card. What I have found is sometimes the config gets glitches. Erasing the suspected field (aka DNS) upload the config. Change it back and upload, sometimes fixes the problem. If that doesn't work do the same thing with the SMTP settings. Deleting a user and rebuilding them has cleared more glitchy problems for me than I can count. Could be the same with your problem.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'

 

[MiamiMax]

I tried to delete the entries as suggested but I still get the same error on monitor.

 

[AACon]

You have a default route to 192.168.1.1 right?

-Austin
I used to be an ACE. Now I'm just an Arse.

 

[MiamiMax]

Follow up. I deleted the entire cabinet using the RESET ( hold for 60 seconds ) button then reformatted the SD card and reloaded everything and it came up.

 

[snowman50]

Nice to hear the resolution..

A bit of work there but we’ll done…

 

[budbyrd]

Yep... A ghost in the machine...

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'