Log Review After Crash - Is there anything weird here?

[David3D]

Hi guys,

Tried accessing the shell via the web browser and my server essentially started slowly locking up. At first, the shell didn't respond, then analytics stopped loading. I went to the physical console and the system wouldn't respond properly with direct input. CIFS shares became unresponsive after that.

It would tell me if I plugged a USB device in or not though.

I had to forcibly reboot as typing "13" in to the console for "reboot" wasn't working.

I saw some weird things in the log, but I need someone who knows what they are looking at to tell me if there is something wrong.

See attached for full dmeseg and log file. Any tips are much appreciated.

Cheers,
David

 

[SweetAndLow]

Your network settings on freenas look like they are wrong, you are missing nameservers and probably a gateway. Also you probably don't want to do a root ftp login, best to setup users for that.

 

[David3D]

Your network settings on freenas look like they are wrong, you are missing nameservers and probably a gateway. Also you probably don't want to do a root ftp login, best to setup users for that.

Hi!

And thanks! Yes, it's a pretty new installation. I had crashing issues before, replaced the boot menue and celebrated 54 days of uptime since the last crash and then this happens.

I'm not 100% sure how I go about correcting nameservers. I'm not sure if there is a separate definition for gateway in FreeBSD terms, but our gateway is on the standard 192.168.1.1 address.

I'll have a look at the documentation and see what I can find.

 

[DrKK]

In the basic system configuration screen for FreeNAS->Network, there is a place to enter your gateway address and/or DNS servers. Try entering those manually.

 

[David3D]

In the basic system configuration screen for FreeNAS->Network, there is a place to enter your gateway address and/or DNS servers. Try entering those manually.

Thanks for the help!

I checked under Network > Global Configuration and I've entered the IPv4 Default Gateway, as well as both of the nameservers for our ISP. Netwait is off.

More curious behavior:

Code:

Jul 19 11:27:55 SERVER ses0: pass0,da0: Element descriptor: 'Dk0'
Jul 19 11:27:55 SERVER ses0: pass0,da0: SAS Device Slot Element: 1 Phys at Slot 0
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf00
Jul 19 11:27:55 SERVER ses0: pass1,da1: Element descriptor: 'Dk1'
Jul 19 11:27:55 SERVER ses0: pass1,da1: SAS Device Slot Element: 1 Phys at Slot 1
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf01
Jul 19 11:27:55 SERVER ses0: pass2,da2: Element descriptor: 'Dk2'
Jul 19 11:27:55 SERVER ses0: pass2,da2: SAS Device Slot Element: 1 Phys at Slot 2
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf02
Jul 19 11:27:55 SERVER ses0: pass3,da3: Element descriptor: 'Dk3'
Jul 19 11:27:55 SERVER ses0: pass3,da3: SAS Device Slot Element: 1 Phys at Slot 3
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf03
Jul 19 11:27:55 SERVER ses0: pass4,da4: Element descriptor: 'Dk4'
Jul 19 11:27:55 SERVER ses0: pass4,da4: SAS Device Slot Element: 1 Phys at Slot 4
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf04
Jul 19 11:27:55 SERVER ses0: pass5,da5: Element descriptor: 'Dk5'
Jul 19 11:27:55 SERVER ses0: pass5,da5: SAS Device Slot Element: 1 Phys at Slot 5
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf05
Jul 19 11:27:55 SERVER ses0: pass6,da6: Element descriptor: 'Dk6'
Jul 19 11:27:55 SERVER ses0: pass6,da6: SAS Device Slot Element: 1 Phys at Slot 6
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf06
Jul 19 11:27:55 SERVER ses0: pass7,da7: Element descriptor: 'Dk7'
Jul 19 11:27:55 SERVER ses0: pass7,da7: SAS Device Slot Element: 1 Phys at Slot 7
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf07
Jul 19 11:27:55 SERVER ses0: pass8,da8: Element descriptor: 'Dk8'
Jul 19 11:27:55 SERVER ses0: pass8,da8: SAS Device Slot Element: 1 Phys at Slot 8
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf08
Jul 19 11:27:55 SERVER ses0: pass9,da9: Element descriptor: 'Dk9'
Jul 19 11:27:55 SERVER ses0: pass9,da9: SAS Device Slot Element: 1 Phys at Slot 9
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf09
Jul 19 11:27:55 SERVER ses0: pass10,da10: Element descriptor: 'Dk10'
Jul 19 11:27:55 SERVER ses0: pass10,da10: SAS Device Slot Element: 1 Phys at Slot 10
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf0a
Jul 19 11:27:55 SERVER ses0: pass11,da11: Element descriptor: 'Dk11'
Jul 19 11:27:55 SERVER ses0: pass11,da11: SAS Device Slot Element: 1 Phys at Slot 11
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf0b

I've read on this forum (this thread: https://forums.freenas.org/index.php?threads/curious-security-output.43693/) that is just happens sometimes. I just find it weird, that suddenly the day after the crash, I'm tempted to say I'm observing a deeper underlying issue somehow.

 

[DrKK]

Thanks for the help!

I checked under Network > Global Configuration and I've entered the IPv4 Default Gateway, as well as both of the nameservers for our ISP. Netwait is off.

More curious behavior:

Code:

Jul 19 11:27:55 SERVER ses0: pass0,da0: Element descriptor: 'Dk0'
Jul 19 11:27:55 SERVER ses0: pass0,da0: SAS Device Slot Element: 1 Phys at Slot 0
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf00
Jul 19 11:27:55 SERVER ses0: pass1,da1: Element descriptor: 'Dk1'
Jul 19 11:27:55 SERVER ses0: pass1,da1: SAS Device Slot Element: 1 Phys at Slot 1
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf01
Jul 19 11:27:55 SERVER ses0: pass2,da2: Element descriptor: 'Dk2'
Jul 19 11:27:55 SERVER ses0: pass2,da2: SAS Device Slot Element: 1 Phys at Slot 2
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf02
Jul 19 11:27:55 SERVER ses0: pass3,da3: Element descriptor: 'Dk3'
Jul 19 11:27:55 SERVER ses0: pass3,da3: SAS Device Slot Element: 1 Phys at Slot 3
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf03
Jul 19 11:27:55 SERVER ses0: pass4,da4: Element descriptor: 'Dk4'
Jul 19 11:27:55 SERVER ses0: pass4,da4: SAS Device Slot Element: 1 Phys at Slot 4
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf04
Jul 19 11:27:55 SERVER ses0: pass5,da5: Element descriptor: 'Dk5'
Jul 19 11:27:55 SERVER ses0: pass5,da5: SAS Device Slot Element: 1 Phys at Slot 5
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf05
Jul 19 11:27:55 SERVER ses0: pass6,da6: Element descriptor: 'Dk6'
Jul 19 11:27:55 SERVER ses0: pass6,da6: SAS Device Slot Element: 1 Phys at Slot 6
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf06
Jul 19 11:27:55 SERVER ses0: pass7,da7: Element descriptor: 'Dk7'
Jul 19 11:27:55 SERVER ses0: pass7,da7: SAS Device Slot Element: 1 Phys at Slot 7
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf07
Jul 19 11:27:55 SERVER ses0: pass8,da8: Element descriptor: 'Dk8'
Jul 19 11:27:55 SERVER ses0: pass8,da8: SAS Device Slot Element: 1 Phys at Slot 8
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf08
Jul 19 11:27:55 SERVER ses0: pass9,da9: Element descriptor: 'Dk9'
Jul 19 11:27:55 SERVER ses0: pass9,da9: SAS Device Slot Element: 1 Phys at Slot 9
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf09
Jul 19 11:27:55 SERVER ses0: pass10,da10: Element descriptor: 'Dk10'
Jul 19 11:27:55 SERVER ses0: pass10,da10: SAS Device Slot Element: 1 Phys at Slot 10
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf0a
Jul 19 11:27:55 SERVER ses0: pass11,da11: Element descriptor: 'Dk11'
Jul 19 11:27:55 SERVER ses0: pass11,da11: SAS Device Slot Element: 1 Phys at Slot 11
Jul 19 11:27:55 SERVER ses0:  phy 0: SATA device
Jul 19 11:27:55 SERVER ses0:  phy 0: parent 50050cc10a98bf00 addr 50050cc10a98bf0b

I've read on this forum (this thread: https://forums.freenas.org/index.php?threads/curious-security-output.43693/) that is just happens sometimes. I just find it weird, that suddenly the day after the crash, I'm tempted to say I'm observing a deeper underlying issue somehow.

OK, but did entering that network information manually solve the initial problem?

 

[David3D]

OK, but did entering that network information manually solve the initial problem?

Sorry man, I should have been more clear. The information was already in the boxes. I had done it already on initial install. I can't imagine what might be causing it otherwise.

I can't remember what the error was, but it was network related and an IP was listed stating there was an issue resolving something. Turned out to be a raspberry pi on the network. Perhaps another computer elsewhere is causing issues. My IT skills flatline on the basics when it comes to networking. I really should sort that out.