ws4py/client/__init__.py self.sock.recv(128)

[chill]

I was copying a few files to an smb share and it did stop responding. I made a picture of the err msg that I have on the screen.

I run TrueNAS CORE 12.0-U7
I can ping the device.
I can't access/list any shares.
When I open the website I get the forward to "/ui/sessions/signin" but no login.
SSH I can login but it hangs after accepting the password, I do not get a shell. TTYs are the same.
The Hardware is just a few weeks old.
The 2 HDDs and the system sem to have an average temp.

Any ideaswhat to do about it? Or how to debug this?

 

[sretalla]

That looks like some unhappy middleware... if you can get to a console (keyboard and screen... seems you have that at least... or IPMI), you may get back to normal by service middlewared restart

With no information about your hardware, I don't have a lot to offer about why that kind of thing might be happening. I see a few references to collectd, so maybe it's a misbehaving NIC (possibly not Intel?) unable to give its data over.

 

[chill]

I have a keyb and screen but I cant interact with it. Status msg are printed but I cant enter any commands. I can switch to other tty's but after login I can't use the shell. The LAN is connected by the Intel i211AT NIC. Repluging the cable made no diffrence.

Components​	ODYSSEY - X86J4105​
Processor​	Intel® Celeron® J4105 (Frequency: 1.5 - 2.5GHz)​
Coprocessor​	Microchip® ATSAMD21G18 32-Bit ARM® Cortex® M0+​
Graphics​	Intel® UHD Graphics 600 (Frequency: 250 – 750MHz)​
Memory​	LPDDR4 8GB​
Wireless​	Wi-Fi 802.11 a/b/g/n/ac @ 2.4/5 GHz HT160 & Bluetooth® 5.0​
Networking​	Intel® I211AT PCIe Gigabit LAN, Supports Wake-On-LAN, Supports PXE​
Audio​	Microphone + headphone Combo Connector​
Headers​	1 × 40-Pin header compatible with Raspberry Pi 1 × 28-Pin header (SAMD21G18) 1 × Front Panel Audio Connector 1 × 4-Pin herder (UART function from SAMD21G18) 1 × Fan Port (4 pin 1.25mm PWM 5V） 3 × 4-Pin SATA Power Connector 1 × 4-Pin herder (Power and Switch) ​
USB​	USB 2.0 Type-A x2, USB 3.1 Type-A x1, USB 3.1 Type-C x1​
Video Interfaces​	HDMI2.0a: Up to 4096x2160 @ 60Hz 24bpp / DP1.2a: Up to 4096x2160 @ 60Hz 24bpp​
Expansion Slots​	M.2(Key B, 2242/2280): SATA III, USB2.0, UIM; M.2 (Key M, 2242/2280): PCIe 2.0 ×4; Micro SD card Socket; SIM Card Socket; SATA III​
RTC​	JST 1.0 CR2032 3V​
TPM​	Built-in TPM (2.0)​
Power​	DC Jack 5.5/2.1mm or Type-C PD; DC Jack input: 12-19V DC; Type-C input: 15V DC​
Dimensions​	110x110mm​
Certifications​	FCC, CE, TELEC​

 

[sretalla]

ODYSSEY - X86J4105

That's really a bad choice for TrueNAS.

How have you installed the OS? (USB stick?) This may be a source of problems, particularly around the system dataset, which if it's still on the boot pool or on a disk that's not in good shape, the system will freeze with collectd being one of the first services to notice.

How are you attaching your drives? (USB?) and are the drives in enclosures where they will power/spin down? Also are they SMR or CMR disks?

 

[chill]

One WD SATA 3.5" HDD is connected via the SATA Port on the board and the other WD SATA 3.5" HDD is connected by the PCIe 3.0x2 M.2 NGFF Key-M to 2-Port (stacked) 6Gbps SATA 3.0 Converter with JMB582 Chip. The 2 HDDs get there power from the board and the board is connected to a 3A/12V Powersupply.

The OS is installed on the on board 64GB eMMC

I pluged/unpluged the network (once again) a couple of times and suddenly the folow line was printed between all the other err msg in the picture.

Code:

sonewconn: pcb 0xfffff80218c585b8: Listen queue overflow: 193 already in queue awaiting acceptance (8 occurrences)

shall I reinstall the OS? And if so is there any setting I have to adapt e.g. regarding the boot pool.

 

[sretalla]

I would start with a reboot and see if you can get back into the web interface.

From there check out the system dataset location under System | System Dataset.

If that's on your boot pool, then a re-think about using that eMMC might be in order. At very least you would move the system dataset to one of your other pools.

Don't worry about the sonewconn errors for now.

 

[chill]

I did a reboot. Every thing looks fine.
Then I started writing data to the SMB-share again. The system became unresposive similar to what I described above. But with other warnings on the screen. See file attached.

While it happend I had an SSH session with the command "tail -F /var/log/messages" running but the SSH shell became unresponsive (also the SSH connection remaind active) so no output was created.

regarding the boot-pool

Code:

zpool status boot-pool
  pool: boot-pool
 state: ONLINE
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          mmcsd0p2  ONLINE       0     0     0

Code:

zfs list -r | grep boot
boot-pool                       2.38G  37.8G       24K  none
boot-pool/ROOT                  2.38G  37.8G       24K  none
boot-pool/ROOT/12.0-U7          2.38G  37.8G     1.20G  /
boot-pool/ROOT/Initial-Install     1K  37.8G     1.18G  legacy
boot-pool/ROOT/default           188K  37.8G     1.18G  legacy

Code:

dmesg -a | grep mmc
mmc0: <MMC/SD bus> on sdhci_pci0
mmc1: <MMC/SD bus> on sdhci_pci1
mmcsd0: 63GB <MMCHC DA4064 0.1 SN *********** MFG 08/2019 by 69 0x0000> at mmc0 200.0MHz/8bit/8192-block
mmcsd0boot0: 4MB partition 1 (read-only) at mmcsd0
mmcsd0boot1: 4MB partition 2 (read-only) at mmcsd0
mmcsd0rpmb: 17MB partition 3 at mmcsd0
mmc1: No compatible cards found on bus

 

[chill]

what I just forgot:
the folders .system and iocage are stored on /mnt/my_pool
my_pool is the pool with the 2 HDDs as a mirror