Jump to content

Server randomly crashing


Recommended Posts

Hey guys, Unraid had always been rock solid on my hardware but after upgrading to 6.9.2 every couple of days Unraid just crashes. I enabled the syslog and writing to flash, unfortunately it seems to have not captured anything of interest. The syslog just has the samba server becoming master and relinquishing it, and then nothing until I start it again where it logs the normal boot process.


What other things can I check?

 

Syslog excerpt:

 

Jul 25 17:44:10 Tower nmbd[3606]: [2021/07/25 17:44:10.593204,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce)
Jul 25 17:44:10 Tower nmbd[3606]:   process_local_master_announce: Server SMBSHARE at IP 82.213.235.42 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Jul 25 17:44:10 Tower nmbd[3606]: [2021/07/25 17:44:10.593576,  0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
Jul 25 17:44:10 Tower nmbd[3606]:   *****
Jul 25 17:44:10 Tower nmbd[3606]:   
Jul 25 17:44:10 Tower nmbd[3606]:   Samba name server TOWER has stopped being a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Jul 25 17:44:10 Tower nmbd[3606]:   
Jul 25 17:44:10 Tower nmbd[3606]:   *****
Jul 25 17:44:26 Tower nmbd[3606]: [2021/07/25 17:44:26.647335,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Jul 25 17:44:26 Tower nmbd[3606]:   *****
Jul 25 17:44:26 Tower nmbd[3606]:   
Jul 25 17:44:26 Tower nmbd[3606]:   Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Jul 25 17:44:26 Tower nmbd[3606]:   
Jul 25 17:44:26 Tower nmbd[3606]:   *****
Jul 25 17:48:20 Tower nmbd[3606]: [2021/07/25 17:48:20.760951,  0] ../../source3/nmbd/nmbd_incomingdgrams.c:302(process_local_master_announce)
Jul 25 17:48:20 Tower nmbd[3606]:   process_local_master_announce: Server SMBSHARE at IP 82.213.235.42 is announcing itself as a local master browser for workgroup WORKGROUP and we think we are master. Forcing election.
Jul 25 17:48:20 Tower nmbd[3606]: [2021/07/25 17:48:20.761190,  0] ../../source3/nmbd/nmbd_become_lmb.c:150(unbecome_local_master_success)
Jul 25 17:48:20 Tower nmbd[3606]:   *****
Jul 25 17:48:20 Tower nmbd[3606]:   
Jul 25 17:48:20 Tower nmbd[3606]:   Samba name server TOWER has stopped being a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Jul 25 17:48:20 Tower nmbd[3606]:   
Jul 25 17:48:20 Tower nmbd[3606]:   *****
Jul 25 17:48:38 Tower nmbd[3606]: [2021/07/25 17:48:38.811609,  0] ../../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
Jul 25 17:48:38 Tower nmbd[3606]:   *****
Jul 25 17:48:38 Tower nmbd[3606]:   
Jul 25 17:48:38 Tower nmbd[3606]:   Samba name server TOWER is now a local master browser for workgroup WORKGROUP on subnet 172.17.0.1
Jul 25 17:48:38 Tower nmbd[3606]:   
Jul 25 17:48:38 Tower nmbd[3606]:   *****
Jul 25 21:40:37 Tower kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12
Jul 25 21:40:37 Tower 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 25 21:40:37 Tower kernel: Command line: BOOT_IMAGE=/bzimage initrd=/bzroot
Jul 25 21:40:37 Tower kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jul 25 21:40:37 Tower kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jul 25 21:40:37 Tower kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jul 25 21:40:37 Tower kernel: x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
Jul 25 21:40:37 Tower kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
Jul 25 21:40:37 Tower kernel: BIOS-provided physical RAM map:
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000c2c33fff] usable
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x00000000c2c34000-0x00000000c2c3afff] ACPI NVS
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x00000000c2c3b000-0x00000000c35e6fff] usable
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x00000000c35e7000-0x00000000c38a6fff] reserved
Jul 25 21:40:37 Tower kernel: BIOS-e820: [mem 0x00000000c38a7000-0x00000000d5c73fff] usable

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...