officeboy

Members
 View Profile  See their activity

  • Posts

    3

  • Joined

  • Last visited

 Content Type 

Posts posted by officeboy

    Kernel panic reoccurring

    in General Support

    Posted

    I've had two more lockups since posting this. 

     

    Only guess is that a docker is causing some issues. I'll let the current parity check happen and then turn them on one at a time. 

    Jul 18 11:24:59 Diskstation kernel: docker0: port 5(veth7b8674a) entered forwarding state
Jul 18 11:24:59 Diskstation kernel: docker0: port 5(veth7b8674a) entered disabled state
Jul 18 11:27:19 Diskstation nginx: 2021/07/18 11:27:19 [error] 2471#2471: *29722 upstream timed out (110: Connection timed >
Jul 18 11:27:19 Diskstation nginx: 2021/07/18 11:27:19 [error] 2471#2471: *29755 upstream timed out (110: Connection timed >
Jul 18 11:28:10 Diskstation kernel: docker0: port 5(veth7b8674a) entered disabled state
Jul 18 11:28:10 Diskstation kernel: device veth7b8674a left promiscuous mode
Jul 18 11:28:10 Diskstation kernel: docker0: port 5(veth7b8674a) entered disabled state
Jul 18 14:16:05 Diskstation kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Jul 18 14:16:05 Diskstation kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-sla>
Jul 18 14:16:05 Diskstation kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot

     

    Kernel panic reoccurring

    in General Support

    Posted

    Not much to offer.  I've got syslog writing to flash but it's not seeming to capture anything useful.  Services all start up, finds some parity problems, and then the fresh boot.  

    I've got a picture of one of the bad boots from a couple days ago.  It seems to run fine for a week or so and then get these error bouts and lockup every couple of hours.  Usually during the parity check.


      

    Jul 17 19:47:15 Diskstation kernel: docker0: port 5(vethd360b9b) entered blocking state
Jul 17 19:47:15 Diskstation kernel: docker0: port 5(vethd360b9b) entered forwarding state
Jul 17 19:47:40 Diskstation rc.docker: sabnzbd: started succesfully!
Jul 17 19:47:40 Diskstation rc.docker: sabnzbd: wait 1 seconds
Jul 17 19:51:09 Diskstation rc.docker: Plex-Media-Server: wait 2 seconds
Jul 17 19:51:09 Diskstation rc.docker: Plex-Media-Server: started succesfully!
Jul 17 19:52:31 Diskstation kernel: process '1d9f504654e675d1d436ebc59735f28e772d2ab792b7112dd05516cfc7fefecd/usr/bin/par2' started with executable stack
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833814792
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833814808
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833815160
Jul 17 20:31:30 Diskstation kernel: md: recovery thread: P incorrect, sector=833815168
Jul 17 21:47:59 Diskstation kernel: microcode: microcode updated early to revision 0x21, date = 2019-02-13
Jul 17 21:47:59 Diskstation kernel: Linux version 5.10.28-Unraid (root@Develop) (gcc (GCC) 9.3.0, GNU ld version 2.33.1-slack15) #1 SMP Wed Apr 7 08:23:18 PDT 2021
Jul 17 21:47:59 Diskstation kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot

    ideas?

    IMG_20210713_082939434.jpg

    diskstation-diagnostics-20210717-2200.zip

    [Support] brettm357 - UniFi

    in Docker Containers

    Posted · Edited by officeboy
    new info.

    Updated yesterday and the server died overnight.  WiredTigerLogs filled up 1.8 TB of space, any ideas?

     

    *Wiped out the logs, and fired the container back up. 4.5gb of logs in under 5 min.  I guess I need to just wipe it.  Is there an internal location I can steal a config file from?

     

    ** syslog shows errors started at Jun 18 00:00:36, seems like a job that would be trying to run?