Guest User!

You are not Sophos Staff.

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.

Hallo,

ich habe hier ein kurrioses verhalten bei einer UTM 9.502-4

Wenn ich unter Logging auf Netzwerknutzung klicke kommt diese Fehlermeldung:

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

Zeitgleich zeigt das UTM Dashboard in der "heuigen" Bedrohngslage überall zu Zahl 0

Vorher funktionierten die anderen Loogingfunktionen ebenfalls nicht, so dass wir ein rebuild der Postgre SQL Datenbank durchgeführt haben.

Hat zufällig einer eine abhilfe für o.g. Probleme?

Ich möchte die SG ungern neu "betanken"



This thread was automatically locked due to age.
  • Hallo,

     

    bitte system.log anschauen.Gruß

  • Hallo ManBearPig,

    danke für die schnelle Antwort...

    2017:08:08-21:13:30 firewall ulogd[5327]: SIGTERM received
    2017:08:08-21:13:32 firewall postgres[25045]: [3-1] LOG:  received fast shutdown request
    2017:08:08-21:13:32 firewall postgres[25045]: [4-1] LOG:  aborting any active transactions
    2017:08:08-21:13:32 firewall postgres[25630]: [3-1] FATAL:  terminating connection due to administrator command
    2017:08:08-21:13:32 firewall postgres[26346]: [3-1] FATAL:  terminating connection due to administrator command
    2017:08:08-21:13:32 firewall postgres[25542]: [3-1] FATAL:  terminating connection due to administrator command
    2017:08:08-21:13:32 firewall postgres[25534]: [3-1] FATAL:  terminating connection due to administrator command
    2017:08:08-21:13:32 firewall postgres[25535]: [3-1] FATAL:  terminating connection due to administrator command
    2017:08:08-21:13:32 firewall postgres[25054]: [3-1] LOG:  autovacuum launcher shutting down
    2017:08:08-21:13:32 firewall postgres[25051]: [2-1] LOG:  shutting down
    2017:08:08-21:13:34 firewall postgres[25051]: [3-1] LOG:  database system is shut down
    2017:08:08-21:13:36 firewall syslog-ng[21211]: syslog-ng shutting down; version='3.4.7'
    2017:08:08-21:14:33 firewall syslog-ng[5445]: syslog-ng starting up; version='3.4.7'
    2017:08:08-21:14:38 firewall dhclient: DHCPDISCOVER on reds1 to 255.255.255.255 port 67 interval 4
    2017:08:08-21:14:39 firewall dns-resolver[5075]: DNS server failed to contact!
    2017:08:08-21:14:40 firewall dhclient: DHCPDISCOVER on reds2 to 255.255.255.255 port 67 interval 5
    2017:08:08-21:14:42 firewall dhclient: DHCPDISCOVER on reds1 to 255.255.255.255 port 67 interval 6
    2017:08:08-21:14:45 firewall dhclient: DHCPDISCOVER on reds2 to 255.255.255.255 port 67 interval 13
    2017:08:08-21:14:48 firewall dhclient: DHCPDISCOVER on reds1 to 255.255.255.255 port 67 interval 11
    2017:08:08-21:14:58 firewall dhclient: DHCPDISCOVER on reds2 to 255.255.255.255 port 67 interval 3
    2017:08:08-21:14:59 firewall dhclient: No DHCPOFFERS received.
    2017:08:08-21:14:59 firewall dhclient: Trying recorded lease 192.168.108.162
    2017:08:08-21:14:59 firewall dhclient: bound: immediate renewal.
    2017:08:08-21:14:59 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:14:59 firewall dhclient: send_packet: Network is unreachable
    2017:08:08-21:14:59 firewall dhclient: send_packet: please consult README file regarding broadcast address.
    2017:08:08-21:14:59 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.
    2017:08:08-21:15:01 firewall dhclient: No DHCPOFFERS received.
    2017:08:08-21:15:01 firewall dhclient: Trying recorded lease 192.168.88.110
    2017:08:08-21:15:01 firewall dhclient: bound: renewal in 185842 seconds.
    2017:08:08-21:15:02 firewall /usr/sbin/cron[6375]: (root) CMD ( /usr/local/bin/rpmdb_backup )
    2017:08:08-21:15:02 firewall /usr/sbin/cron[6376]: (root) CMD (   /usr/local/bin/reporter/system-reporter.pl)
    2017:08:08-21:15:02 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:15:02 firewall dhclient: send_packet: Network is unreachable
    2017:08:08-21:15:02 firewall dhclient: send_packet: please consult README file regarding broadcast address.
    2017:08:08-21:15:02 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.
    2017:08:08-21:15:06 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:15:06 firewall dhclient: send_packet: Network is unreachable
    2017:08:08-21:15:06 firewall dhclient: send_packet: please consult README file regarding broadcast address.
    2017:08:08-21:15:06 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.
    2017:08:08-21:15:14 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:15:14 firewall dhclient: send_packet: Network is unreachable
    2017:08:08-21:15:14 firewall dhclient: send_packet: please consult README file regarding broadcast address.
    2017:08:08-21:15:14 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.
    2017:08:08-21:15:23 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:15:23 firewall dhclient: send_packet: Network is unreachable
    2017:08:08-21:15:23 firewall dhclient: send_packet: please consult README file regarding broadcast address.
    2017:08:08-21:15:23 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.
    2017:08:08-21:15:42 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:15:42 firewall dhclient: send_packet: Network is unreachable
    2017:08:08-21:15:42 firewall dhclient: send_packet: please consult README file regarding broadcast address.
    2017:08:08-21:15:42 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.
    2017:08:08-21:15:49 firewall dns-resolver[5075]: DNS server failed to contact!
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsResolver1a :: resolver1.ast.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_DefaultSophosUTMSupportHost :: dispatch.apu.sophos.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsResolver5a :: resolver5.ast.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No such IPv4 domain: NB07601 (REF_NetDnsSkypeTestIm)
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsSkypeTestIm :: NB07601
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsIPrep1t :: iprep1.t.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsZeitserver3 :: ptbtime3.ptb.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsHappyloadi :: happyloading.cc
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NVcafkivTc :: remote.haubner-it.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_LogMgmtProvisioningService :: logmgmt.astaro.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsIPrep4t :: iprep4.t.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsVmWareServe :: vdi.kvb-koeln.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No such IPv4 domain: http://www.tarife2015.com/ (REF_NetDnsHttpwwwtar)
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsHttpwwwtar :: http://www.tarife2015.com/
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_CoUrcYfLLg :: manfred.dynvpn.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No such IPv4 domain: NBCBH07 (REF_NetDnsSkypetest)
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsSkypetest :: NBCBH07
    2017:08:08-21:15:49 firewall dns-resolver[5075]: Updating REF_NtpPool :: pool.ntp.org
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsResolver4a :: resolver4.ast.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsIPrep2t :: iprep2.t.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsWwwaerzteb :: www.aerzteblatt.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsZeitserver :: ptbtime1.ptb.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsResolver2a :: resolver2.ast.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsWwwcbhde :: www.cbh.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsZeitserver2 :: ptbtime2.ptb.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsIPrep5t :: iprep5.t.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsIPrep3t :: iprep3.t.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsResolver3a :: resolver3.ast.ctmail.com
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsQscWebserv :: s037.bre.qsc.de
    2017:08:08-21:15:49 firewall dns-resolver[5075]: No change to REF_NetDnsKunzmSharpVon :: dechertfileshare.com
    2017:08:08-21:15:50 firewall ntpd[5176]: Listen normally on 14 tun0 10.242.2.1:123
    2017:08:08-21:15:50 firewall ntpd[5176]: new interface(s) found: waking up resolver
    2017:08:08-21:15:50 firewall system: System was restarted
    2017:08:08-21:15:59 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:15:59 firewall dhclient: send_packet: Operation not permitted
    2017:08:08-21:15:59 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.
    2017:08:08-21:16:20 firewall dhclient: DHCPREQUEST on reds1 to 192.168.108.1 port 67
    2017:08:08-21:16:20 firewall dhclient: send_packet: Operation not permitted
    2017:08:08-21:16:20 firewall dhclient: dhclient.c:2247: Failed to send 300 byte long packet over fallback interface.

    Das ist seit dem letzten Neustart der UTM. Aber ich finde hier nichts was danach aussieht, dass es einen Fehler verursacht.