Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 3 subscribers
  • Views 4447 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Can't use an undefined value as an ARRAY reference at /wfe/asg/modules/reporting/accounting.pm line 624

roney ramos

 

Hello!!

After we renew our license and update our sophos firewall i encounter this error in network usage tab:

Can't use an undefined value as an ARRAY reference at /wfe/asg/modules/reporting/accounting.pm line 624. 

As I check it seems the rrd folder for reporting was been removed from the root. I check the system messages in the log file and I found this messages:

2018:10:20-09:35:00 freshsolutions syslog-ng[4953]: I/O error occurred while writing; fd='72', error='Broken pipe (32)'
2018:10:20-09:35:00 freshsolutions syslog-ng[4953]: Suspending write operation because of an I/O error; fd='84', time_reopen='60'
2018:10:20-09:35:01 freshsolutions /usr/sbin/cron[31479]: (root) CMD (   /usr/local/bin/reporter/system-reporter.pl)
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - Error updating sysmon based data
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - Error updating mem/swap rrd
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - Error updating load average rrd
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - Error updating rrd
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - Error updating rrd
2018:10:20-09:35:02 freshsolutions system-reporter.pl: WARN - updating rrd: socket no found - daemon running?
2018:10:20-09:35:06 freshsolutions syslog-ng[4953]: I/O error occurred while writing; fd='84', error='Broken pipe (32)'
2018:10:20-09:35:06 freshsolutions syslog-ng[4953]: Suspending write operation because of an I/O error; fd='72', time_reopen='60'
2018:10:20-09:35:10 freshsolutions syslog-ng[4953]: I/O error occurred while writing; fd='72', error='Broken pipe (32)'
2018:10:20-09:35:10 freshsolutions syslog-ng[4953]: Suspending write operation because of an I/O error; fd='85', time_reopen='60'
2018:10:20-09:35:16 freshsolutions syslog-ng[4953]: I/O error occurred while writing; fd='85', error='Broken pipe (32)'
2018:10:20-09:35:16 freshsolutions syslog-ng[4953]: Suspending write operation because of an I/O error; fd='84', time_reopen='60'
2018:10:20-09:35:21 freshsolutions syslog-ng[4953]: I/O error occurred while writing; fd='84', error='Broken pipe (32)'
2018:10:20-09:35:21 freshsolutions syslog-ng[4953]: Suspending write operation because of an I/O error; fd='85', time_reopen='60'
2018:10:20-09:35:27 freshsolutions syslog-ng[4953]: I/O error occurred while writing; fd='85', error='Broken pipe (32)'

Does anyone have any idea on how to fix this?thank you so much


This thread was automatically locked due to age.
  • 0

    Hala and welcome to the UTM Community!

    I got "How to fix Graphs with empty content" from Scott Klassen almost 7 years ago.  From your post, it might fix your issue.  You can copy the entire block and paste it on the command line at once.  As root:

    rm /var/log/reporting/rrd/*
    /etc/init.d/syslogng restart
    /etc/init.d/rrdcache restart
    /usr/local/bin/reporter/system-reporter.pl

    Please let us know your results.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson

    After I upgrade my firmware the problem has been solved. Before this error happened our sophos was using 9.403 I try to upgrade it to 9.404 then after observing it for 2 days change the firmware to 9.415. 

Unfiltered HTML