Page 1 of 1

CRON Email me.

PostPosted: Wed Feb 13, 2019 1:11 pm
by Leckbush
Hi

(SERVER1)
Cron Email me two messages. I set my email to aliases of root.

First time I see this email from Cron First one is:

"problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_vm_update.pl line 197"

and this one:

"problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_conf_update.pl line 259"

Should I ignore this or what? Thanks

Re: CRON Email me.

PostPosted: Mon Feb 18, 2019 2:14 pm
by omarrodriguezt
Make sure that the ip of the server itself is allowed in the firewall.

Re: CRON Email me.

PostPosted: Mon Feb 18, 2019 2:31 pm
by Leckbush
Both LAN and Public?

Currently on whitelist is the local and our VOIP

Both TCP and UDP:
192.168.1.0/24
X.X.X.X - VOIP Provider

Should I add the IP use for external access too?

Re: CRON Email me.

PostPosted: Mon Feb 18, 2019 2:33 pm
by omarrodriguezt
This is correct

Re: CRON Email me.

PostPosted: Mon Feb 18, 2019 2:34 pm
by Leckbush
Okay I will add the public IP too

Re: CRON Email me.

PostPosted: Fri Mar 15, 2019 8:42 am
by Leckbush
Hi add both external and internal IP of the server to the firewall and I thought it was all fix but as I open the server today cron email me again about it. Already bind the address to 127.0.0.1 but doesnt fix it. Any suggestion?

Re: CRON Email me.

PostPosted: Mon Mar 18, 2019 1:55 pm
by omarrodriguezt
Make sure that both IP address are added for all ports in the firewall.

Re: CRON Email me.

PostPosted: Fri Jun 14, 2019 12:24 pm
by williamconley
Leckbush wrote:Hi

(SERVER1)
Cron Email me two messages. I set my email to aliases of root.

First time I see this email from Cron First one is:

"problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_vm_update.pl line 197"

and this one:

"problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_conf_update.pl line 259"

Should I ignore this or what? Thanks

this is normal if the server is rebooting at the moment of the update. note that the latest system takes 1.5 minutes to shut down during reboot ... during which all the "every minute" processes run. so add this to the end of these entries in crontab:
Code: Select all
>/dev/null 2>&1


These two jobs will now be ignored if they succeed or fail. if your system ever has an issue, it'll not likely be one of these two scripts that informs you of failure first anyway. 8-)