fwconsole creating many emails through our Barracuda mail filter
-
I have created a support request with Sangoma as well but they always take a bit longer than one would expect.
I've been getting a notification on high output queue from our Barracuda mail filter saying the following:
Cron asterisk@freepbx /usr/local/sbin/fwconsole userman --syncall -q. This has a message of: /bin/sh: /usr/local/sbin/fwconsole: No such file or directory
I get the same message for:
Cron asterisk@freepbx /usr/local/sbin/fwconsole userman --syncall -q
&
Cron asterisk@freepbx /usr/local/sbin/fwconsole qxactreports --sync -q 2>&1 > /dev/null
I tried to disable/uninstall any commercial modules I know I am not using but got errors for Calendar, Class of Service, and SMS because some modules depend on it. That screenshot is attached. The only module I know for sure that I am using is Zulu as I am testing remote/laptop users with softphone
Thanks in advance for any help you can provide.
Jeff
-
UPDATE:
I checked all modules and all are up to date. I also disabled all the commercial modules that I know I don't use and that didn't change anything.
-
what is the message that you are getting from the Barracuda?
-
What did you change? Because those cron jobs do not normally send anything.
-
@dbeato said in fwconsole creating many emails through our Barracuda mail filter:
what is the message that you are getting from the Barracuda?
Alert: High out-queue length. out-queue length: 2420
This alert applies to the Barracuda Email Security Gateway at IP address 172.16.0.3(MAC address: 4C:CC:6A:24:CB:74 / serial number: 851091) with a default domain of 'wls.wels.net'.
-
@JaredBusch said in fwconsole creating many emails through our Barracuda mail filter:
What did you change? Because those cron jobs do not normally send anything.
I haven't changed anything other than applying updates through Update Manager
-
Whatever it is runs a cron every minute or every 5 depending on the error.
-
@WLS-ITGuy said in fwconsole creating many emails through our Barracuda mail filter:
@dbeato said in fwconsole creating many emails through our Barracuda mail filter:
what is the message that you are getting from the Barracuda?
Alert: High out-queue length. out-queue length: 2420
This alert applies to the Barracuda Email Security Gateway at IP address 172.16.0.3(MAC address: 4C:CC:6A:24:CB:74 / serial number: 851091) with a default domain of 'wls.wels.net'.
Yeah, that is normal but on the queue. What does it show as the error that is sending on an email?
-
@dbeato said in fwconsole creating many emails through our Barracuda mail filter:
@WLS-ITGuy said in fwconsole creating many emails through our Barracuda mail filter:
@dbeato said in fwconsole creating many emails through our Barracuda mail filter:
what is the message that you are getting from the Barracuda?
Alert: High out-queue length. out-queue length: 2420
This alert applies to the Barracuda Email Security Gateway at IP address 172.16.0.3(MAC address: 4C:CC:6A:24:CB:74 / serial number: 851091) with a default domain of 'wls.wels.net'.
Yeah, that is normal but on the queue. What does it show as the error that is sending on an email?
For this one: Cron asterisk@freepbx /usr/local/sbin/fwconsole util cleanplaybackcache -q
I get: /bin/sh: /usr/local/sbin/fwconsole: No such file or directory
-
Sangoma's response was to turn off the cron jobs that were causing the issues.
That doesn't answer the question of why they are suddenly happening and what changed to make them happen.
-
@WLS-ITGuy said in fwconsole creating many emails through our Barracuda mail filter:
Sangoma's response was to turn off the cron jobs that were causing the issues.
That doesn't answer the question of why they are suddenly happening and what changed to make them happen.
I would check on the system you have and check what is sending emails instead.
-
@dbeato said in fwconsole creating many emails through our Barracuda mail filter:
@WLS-ITGuy said in fwconsole creating many emails through our Barracuda mail filter:
Sangoma's response was to turn off the cron jobs that were causing the issues.
That doesn't answer the question of why they are suddenly happening and what changed to make them happen.
I would check on the system you have and check what is sending emails instead.
Freepbx is set to email through Exchange
-
This is what shows up in the barracuda queue:
-
Check this
https://issues.freepbx.org/browse/FREEPBX-11275
On your cronjob do you have the following at the end of it?> /dev/null 2>&1 -
@dbeato said in fwconsole creating many emails through our Barracuda mail filter:
Check this
https://issues.freepbx.org/browse/FREEPBX-11275
On your cronjob do you have the following at the end of it?> /dev/null 2>&1Full cron list:
* * * * * [ -x /var/www/html/admin/modules/dashboard/scheduler.php ] && /var/www/html/admin/modules/dashboard/scheduler.php > /dev/null 2>&1 */1 * * * * /var/lib/asterisk/bin/pagepro-scheduler.php 2>&1 >/dev/null 47 3 * * * /usr/sbin/fwconsole certificates --updateall -q 2>&1 >/dev/null */15 * * * * [ -e /etc/asterisk/firewall.enabled ] && touch /var/spool/asterisk/incron/firewall.firewall @daily [ -e /var/www/html/admin/modules/sysadmin/bin/check_portal.php ] && /var/www/html/admin/modules/sysadmin/bin/check_portal.php >/dev/null 2>&1 @daily [ -x /var/lib/asterisk/agi-bin/ddns_client.php ] && /var/lib/asterisk/agi-bin/ddns_client.php >/dev/null 2>&1 51 * * * * /usr/local/sbin/fwconsole util cleanplaybackcache -q * * * * * [ -x /var/lib/asterisk/bin/schedtc.php ] && /var/lib/asterisk/bin/schedtc.php @hourly [ -x /var/lib/asterisk/bin/storage.php ] && /var/lib/asterisk/bin/storage.php >/dev/null 2>&1 @daily /usr/local/sbin/fwconsole pms mk_dirty > /dev/null 2>&1 * * * * * /usr/local/sbin/fwconsole pms wu_alert > /dev/null 2>&1 * * * * * /usr/local/sbin/fwconsole queuestats --syncall >> /tmp/reader.log 2>&1 30 22 * * * /usr/local/sbin/fwconsole recordingreports -s -c -q > /dev/null 2>&1 0 0 1 * * php /var/lib/asterisk/agi-bin/backuprecordings.php > /dev/null 2>&1 @daily [ -x /var/lib/asterisk/bin/freepbx_sipstation_check ] && /var/lib/asterisk/bin/freepbx_sipstation_check 2>&1 > /dev/null * * * * * php /var/lib/asterisk/bin/vqplus_generate_periodical_events.php > /dev/null 2>&1 @daily [ -x /var/lib/asterisk/agi-bin/update_license.php ] && /var/lib/asterisk/agi-bin/update_license.php --delay 12 5 * * * [ -e /usr/local/sbin/fwconsole ] && /usr/local/sbin/fwconsole ma listonline --sendemail -q > /dev/null 2>&1 -
@WLS-ITGuy said in fwconsole creating many emails through our Barracuda mail filter:
51 * * * * /usr/local/sbin/fwconsole util cleanplaybackcache -q
so change this line to, that way it doesn't send an email.
51 * * * * /usr/local/sbin/fwconsole util cleanplaybackcache -q > /dev/null 2>&1 -
@dbeato said in fwconsole creating many emails through our Barracuda mail filter:
@WLS-ITGuy said in fwconsole creating many emails through our Barracuda mail filter:
51 * * * * /usr/local/sbin/fwconsole util cleanplaybackcache -q
so change this line to, that way it doesn't send an email.
51 * * * * /usr/local/sbin/fwconsole util cleanplaybackcache -q > /dev/null 2>&1Done. We'll see what happens in an hour
-
Or, put the symlink back as the bug report stated.
-
Well, editing the cron worked. I suppose I could put the symlink back but it isn't spitting emails to the queue anymore so...
-
@WLS-ITGuy said in fwconsole creating many emails through our Barracuda mail filter:
Well, editing the cron worked. I suppose I could put the symlink back but it isn't spitting emails to the queue anymore so...
Awesome!
