Cron does not start on FreeBSD 10.1. What to do?

Question

FreeBSD

Hello!
One "beautiful" day, I discovered that on one of the FreeBSD 10.1 servers, cron jobs were not running. Looked, it turned out - cron itself is not running. Started:
service cron start
Received a segmentation fault. There is nothing more sensible in the logs.
Added debugging parameters for cron: -x bit,ext,load,misc,pars,proc,sch
I start - after debugging output the same segmentation fault, and there are no hints of errors in the debugging information.
I commented out all the tasks in crontab, started - the same thing.
I collected cron with debugging information, I run it under gdb - it works. Restored jobs in crontab - they are running. Those. I can't find the error in the debugger.
Where to dig further? I can't keep it under the debugger all the time.
PS: there are no user crontab files in the system.
It is also not clear why he began to fall. Since the first time it crashed, there have been no system upgrades, only minor changes to sendmail and ipfw from the config edits. All jobs that hang in crontab have been running for several years, similar jobs on other servers.

Answer 1

Understood. cron called the getpwnam system function, and since Since my users are taken from the ldap directory via ssl, this call generated a request for the openssl library.
It turned out that the system had 2 versions of openssl from the world and from ports. One of the calls to openssl went to one version, the second - to another, and, apparently, something in this place did not like the system :) I
left the version of openssl from the ports and cron rose as native.

Answer 2

And if you run it with debug information but without a debugger, does it crash?
Does this BSD of yours have core dumps? If there is, let it generate it, load it into gdb and see.