Unable to start error after upgrading Zabbix proxy to 3.0.2

A description of the problem

After upgrading a Zabbix proxy from 2.4.5 to 3.0.2, it crashes directly.

The error message is as follows:

2367:20160508:153246.830 One child process died (pid:42385,exitcode/signal:11). Exiting ...

42367:20160508:153248.904 Zabbix Proxy stopped. Zabbix 3.0.2 (revision 59540).

Turn the log level up, set debuglevel=4, and view the error

 42629:20160508:153529.004 got signal [signal:15 (SIGTERM), sender_pid:42623,sender_uid:498, Reason:0]. exiting ... 42628:20160508:153529.004 got signal [signal:15 (SIGTERM), sender_pid:42623,sender_uid:498,reason:0]. exiting ... 42634:20160508:153529.004 got  Signal [signal:15 (SIGTERM),sender_pid:42623,sender_uid:498,reason:0]. exiting ...  42651:20160508:153529.004 got signal [signal:15 (SIGTERM), Sender_pid:42623,sender_uid:498,reason : 0]. exiting ... 42659:20160508:153529.004 got signal [signal:15 (SIGTERM), sender _pid:42623,sender_uid:498,reason:0]. exiting ... 42661:20160508:153529.005 got signal  [signal:15 (SIGTERM),sender_pid:42623,sender_uid:498,reason:0]. exiting ...  42655:20160508:153529.005 got signal [signal:15 (SIGTERM), Sender_pid:42623,sender_uid:498,reason :0]. exiting ... 42663:20160508:153529.005 got signal [signal:15 (SIGTERM), Sender_pid:42623,sender_uid:498,reason : 0]. exiting ... 42664:20160508:153529.005 got signal [signal:15 (SIGTERM), sender _pid:42623,sender_uid:498,reason:0]. exiting ... 42666:20160508:153529.005 got signal  [signal:15 (SIGTERM),sender_pid:42623,sender_uid:498,reason:0]. exiting ...  42665:20160508:153529.006 got signal [signal:15 (SIGTERM), Sender_pid:42623,sender_uid:498,reason : 0]. exiting ... 42667:20160508:153529.006 got signal [signal:15 (SIGTERM), sender _pid:42623,sender_uid:498,reason:0]. exiting ... 42630:20160508:153529.006 got signal  [signal:15 (SIGTERM),sender_pid:42623,sender_uid:498,reason:0]. exiting ...  42668:20160508:153529.006 got signal [signal:15 (SIGTERM), Sender_pid:42623,sender_uid:498,reason : 0]. exiting ... 42671:20160508:153529.006 got signal [signal:15 (SIGTERM), sender_pid:42623,sender_uid:498,reason:0].  exiting ... 42670:20160508:153529.007 got signal [signal:15 (SIGTERM), sender_pid : 42623,sender_uid:498,reason:0]. exiting ... 42647:20160508:153529.007 got signal  [signal:15 (SIGTERM),sender_pid:42623,sender_uid:498,reason:0]. exiting ...  42674:20160508:153529.007 got signal [signal:15 (SIGTERM), Sender_pid:42623,sender_uid:498,reason : 0]. exiting ... 42680:20160508:153529.007 got signal [signal:15 (SIGTERM), sender _pid:42623,sender_uid:498,reason:0]. exiting ... 42679:20160508:153529.008 got signal  [signal:15 (SIGTERM), sender_pid:42623,sender_uid:498,reason:0]. exiting 

9102:20160508:170455.283 End of Zbx_strpool_destroy () 9102:20160508:170455.283 end of Free_configuration_cache ()  9102:20160508:170455.283 in Free_ipmi_handler () 9102:20160508:170455.283 End of Free_ipmi_handler () 9102:20160508:170455.284 in Free_selfmon_collector () collector:0x7fa793e23000 9102:20160508:170455.284 End of Free_ Selfmon_collector () 9102:20160508:170455.284 in Unload_modules () 9102:20160508:170455.284 End of Unload_modules () 9102 : 20160508:170455.284 Zabbix Proxy stopped. Zabbix 3.0.2 (revision 59540). Zabbix_proxy [9152]: [File: ' Selfmon.c ', line:375] lock failed: [] Invalid argument

Unable to start error after upgrading Zabbix proxy to 3.0.2