proftpd service crashing for no apparent reason

anphex

Cadet
Joined
Jan 14, 2021
Messages
3
Good evening,

I just built a TrueNAS system from some spare parts today. The xferlog with personal data removed:

Code:
Thu Jan 14 05:41:06 2021 0 10.1.1.13 134037504 /mnt/RaidZ/xxxx/xxx/Sonderbackups/Archiv_diverser_Daten/_ARCHIV_2.7z.011 a _ d r  xxx ftps 0 * c
Jan 14 06:39:37 truenas proftpd[6904]: 127.0.0.1 - -----BEGIN STACK TRACE-----
Jan 14 06:39:37 truenas proftpd[6904]: 127.0.0.1 - [0] 0x800435c2e <_pthread_sigmask+0x53e> at /lib/libthr.so.3
Jan 14 06:39:37 truenas proftpd[6904]: 127.0.0.1 - -----END STACK TRACE-----
Jan 14 06:39:37 truenas proftpd[6904]: 127.0.0.1 - ProFTPD terminating (signal 11)
Jan 14 06:39:37 truenas proftpd[6904]: 127.0.0.1 - ProFTPD 1.3.6b standalone mode SHUTDOWN
root@truenas[/var/log]#


I kept the first line to show the time between the events, it's weird that this happens in idle seemingly. If there is any other log file I should check I would be glad to know.

My system specs are the following:
Intel i3 6100
16 GB DDR4 Ram @ 2166
Sandisk Ultra 256 GB SSD for OS
MSI H110M Pro-D Mainboard
3 WD RED 3 TB NAS-Drivers in a Raid Z
400 W BeQuiet power supply.


OS Version:
TrueNAS-12.0-U1
Model:
MS-7996

Thank you in advance!
 

Samuel Tai

Never underestimate your own stupidity
Moderator
Joined
Apr 24, 2020
Messages
5,399
Check your motherboard's BIOS settings. It's a gaming-oriented motherboard, so stability won't be as good as with a server-grade board. In particular, DISABLE all overclocking, and run your RAM only at the default JEDEC timings. ProFTPD is crashing when it tries to launch another thread, so make sure your motherboard's enabled HyperThreading properly for your CPU.
 

anphex

Cadet
Joined
Jan 14, 2021
Messages
3
Thank you for your kind response. I just updated my BIOS and opted for the most stable settings. Weirdly I forgot that I used two slightly different RAM sticks, one with CL 15 and another with CL 16. The system opted to apply CL15 for both so it might have been really a hardware stability issue. It's running at Jedec with rather "slow" timings for stability. HyperThreading is enabled.
If I don't report back in a few, everything can be considered fixed.

Again - thank you!
 
Top