Thread Info
  • State Suggested Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 20 replies
  • Answers 2 answers
  • Subscribers 34 subscribers
  • Views 37253 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

How to find cause of strange reboots?

Brad Shannon

Hi folks, appreciate your help in advance.

 

I have an XG85 running SFOS 17.0.2 MR-2.

It is set up to send logs to a Syslog server I set up just yesterday. [https://i.imgur.com/BoNeNsB.png] [https://i.imgur.com/0h1MnvD.png]

That server is receiving some logs. [https://imgur.com/TRA2qDl]

 

Twice in the last 48 hours, the device has rebooted itself during times of high usage. What log settings should I configure to see what could be causing this, in case it happens again?

 

(Also, maybe it's related to SFOS 17?)

 

2/27/18 UPDATE:

  • updated to 17.0.5, same reboot problem.
  • replaced the hardware, restored settings to replacement, same reboot problem.
  • tried factory reset and manually re-entering the settings, same reboot problem.

I have a replacement non-Sophos FW en route. However, I got some interesting data from the COM port just now, which I'll add as a new reply below.



This thread was automatically locked due to age.
Parents
  • 0

    This was printed to the COM port:

     

    [433020.181445] Kernel panic - not syncing: Out of memory: compulsory panic_on_oom is enabled
    [433020.181445]
    [433020.213879] CPU: 1 PID: 16933 Comm: lcdd Tainted: G O 3.14.22-Aum #1
    [433020.237985] Hardware name: Sophos XG/Aptio CRB, BIOS 5.6.5 03/20/2017
    [433020.259508] 000201da 8140abf2 00000002 81408bed 814c5d5c 8166ec40 00000002 000201da
    [433020.285376] 00000000 00000000 8108dc4f 814c95e8 814c8020 e2cee180 000201da 8108de14
    [433020.311241] 00000000 00000000 000201da 00000000 8157b75c 00077dfb 00000000 00000001
    [433020.337107] Call Trace:
    [433020.345444] [<8140abf2>] ? dump_stack+0x3e/0x4e
    [433020.360946] [<81408bed>] ? panic+0x7d/0x15f
    [433020.375301] [<8108dc4f>] ? check_panic_on_oom+0x4f/0x50
    [433020.393098] [<8108de14>] ? out_of_memory+0x94/0x2d0
    [433020.409749] [<81091999>] ? __alloc_pages_nodemask+0x7b9/0x7d0
    [433020.429269] [<8108c6d6>] ? filemap_fault+0x196/0x3b0
    [433020.446206] [<810a4c79>] ? __do_fault+0x59/0x3e0
    [433020.461996] [<810a7821>] ? handle_mm_fault+0x161/0x730
    [433020.479509] [<8104d6c4>] ? lock_hrtimer_base.isra.29+0x14/0x30
    [433020.499316] [<8102cd9e>] ? __do_page_fault+0xfe/0x410
    [433020.516540] [<8104d630>] ? hrtimer_get_res+0x40/0x40
    [433020.533476] [<8104dfee>] ? SyS_nanosleep+0x4e/0x60
    [433020.549841] [<8102d1e0>] ? vmalloc_sync_all+0x130/0x130
    [433020.567640] [<8140efac>] ? error_code+0x30/0x38
    [433020.583144] [<8102d1e0>] ? vmalloc_sync_all+0x130/0x130
    [433020.600949] Kernel Offset: 0x0 from 0x81000000 (relocation range: 0x80000000-0xf7bfdfff)
    [433020.627932] Rebooting in 3 seconds..
    [433023.673641] ACPI MEMORY or I/O RESET_REG.
    $▒

     

     

    So, the device is running out of memory (I'm assuming RAM), while running a config changed minimally from factory-default, on latest firmware. So, the firmware has a memory leak bug, or it just uses more memory than is available on this device.

     

    Sophos should not have rolled out a firmware update that breaks their product.

  • 0 in reply to Brad Shannon

    Hello  

    could you plese tell me witch command dir you run to see this log 

     

    thaks 

  • 0 in reply to rdebraga

    No command -- the device sends those messages to the console automatically. I just happened to have a console window up, to see it.

    I connected the CONSOLE port of the Sophos to my computer's serial port. Then I used PuTTY to open a console session using the serial port's COM #.

     

    i.imgur.com/Yh0eRlY.png

Reply Children
No Data