Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 3998 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

UTM Randomly Restarting - postgres error in system logs

garpace

Hello.

A machine I help a family member with using the home license restarted Sunday, and then again tonight, which is very odd - I've found UTM rock stable mostly.  I checked the logs just before the most recent restart, and saw this - anyone know what it means?  Memory corruption?  HDD corruption?

 

2018:10:15-20:25:01 ri /usr/sbin/cron[17125]: (root) CMD ( /usr/local/bin/reporter/system-reporter.pl)

2018:10:15-20:25:52 ri postgres[17192]: [3-1] ERROR: could not find block containing chunk 0x7f837f617b90<132>Oct 15 20:25:52 postgres[17192]: [3-2] CONTEXT: automatic analyze of table "reporting.public.accounting"

2018:10:15-20:26:52 ri postgres[17234]: [3-1] ERROR: could not find block containing chunk 0x7f837f617b90<132>Oct 15 20:26:52 postgres[17234]: [3-2] CONTEXT: automatic analyze of table "reporting.public.accounting"

2018:10:15-20:27:52 ri postgres[17273]: [3-1] ERROR: could not find block containing chunk 0x7f837f617b90<132>Oct 15 20:27:52 postgres[17273]: [3-2] CONTEXT: automatic analyze of table "reporting.public.accounting"

2018:10:15-20:28:19 ri dns-resolver[4717]: Updating REF_NetDnsGmailSmtp :: smtp.gmail.com

2018:10:15-20:28:52 ri postgres[17315]: [3-1] ERROR: could not find block containing chunk 0x7f837f617b90<132>Oct 15 20:28:52 postgres[17315]: [3-2] CONTEXT: automatic analyze of table "reporting.public.accounting"

2018:10:15-20:29:52 ri postgres[17354]: [3-1] ERROR: could not find block containing chunk 0x7f837f617b90<132>Oct 15 20:29:52 postgres[17354]: [3-2] CONTEXT: automatic analyze of table "reporting.public.accounting"

2018:10:15-20:30:01 ri /usr/sbin/cron[17396]: (root) CMD ( /usr/local/bin/reporter/system-reporter.pl)

2018:10:15-20:30:01 ri /usr/sbin/cron[17398]: (root) CMD (/sbin/audld.plx --trigger)

2018:10:15-20:30:01 ri /usr/sbin/cron[17397]: (root) CMD ( /usr/local/bin/rpmdb_backup )

2018:10:15-20:30:01 ri /usr/sbin/cron[17399]: (root) CMD (/var/mdw/scripts/pmx-blocklist-update)

2018:10:15-20:30:52 ri postgres[17517]: [3-1] ERROR: could not find block containing chunk 0x7f837f617b90<132>Oct 15 20:30:52 postgres[17517]: [3-2] CONTEXT: automatic analyze of table "reporting.public.accounting"

2018:10:15-20:31:21 ri dns-resolver[4717]: Updating REF_NetDnsIPrep2t :: iprep2.t.ctmail.com

2018:10:15-20:31:52 ri postgres[17641]: [3-1] ERROR: could not find block containing chunk 0x7f837f617b90<132>Oct 15 20:31:52 postgres[17641]: [3-2] CONTEXT: automatic analyze of table "reporting.public.accounting"

2018:10:15-20:32:01 ri /usr/sbin/cron[17661]: (root) CMD ( nice -n19 /usr/local/bin/gen_inline_reporting_data.plx)

2018:10:15-20:34:14 ri syslog-ng[4984]: syslog-ng starting up; version='3.4.7'

2018:10:15-20:34:18 ri ddclient[5311]: WARNING: cannot connect to checkip.dyndns.org:80 socket: IO::Socket::INET: Bad hostname 'checkip.dyndns.org'

2018:10:15-20:34:19 ri dns-resolver[4712]: DNS server failed to contact!

2018:10:15-20:34:29 ri system: System was restarted

2018:10:15-20:34:33 ri dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67

2018:10:15-20:34:33 ri dhclient: DHCPACK from 10.110.0.1

2018:10:15-20:34:33 ri dhclient: bound to IP.RED.ACT.ED -- renewal in 32092 seconds



This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to Jason Klein

    Thanks Jason.  I read the thread - seems like they concluded power issue.  That seems sorta odd in this situation, as its a home environment, with no change in power setup.  It crashed again today; I don't know enough about the logs to understand what's going on, but I figure seeing this "�������������������������������������������������������������������������������������������" in the log files is bad news.  I'll try and get on site and check the power out.

Children
  • 0 in reply to garpace

    You might try re-initializing the PostgreSQL data bases (deletes Reporting history, but doesn't touch the logs):

    /etc/init.d/postgresql92 rebuild

    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

    Bob - thanks for the suggestion.

    I tried re-initializing PostgreSQL - I'm still getting restarts.  

    I had my family member unplug the box from the UPS and plug it right into the wall - still getting restarts (so much for my theory it was the UPS).  I guess it's still possible it could be a faulty circuit, but the chances seem really low).

    I want to get there and inspect myself, and I plan on doing a good bit of cleaning in the case (to see if its hardware related), and possibly reloading UTM from disc and then restoring the config (in case its software related), but until I do that, any ideas?

    Any other logs?  On the system logs, the only consistent thing I see before the issue is "/usr/sbin/cron[XXXXX]:  (root) CMD (    /usr/local/bin/reporter/system-reporter.pl)".  Sometimes its followed by what looks like corruption, other times not.  The system log always starts again 2 mins later with the normal startup stuff.

    I am miffed as I have 4 UTMs running on the same software version (latest), all on similar hardware and configuration...only this one is giving me trouble.

Unfiltered HTML