重启 nginx 后, 观察 logs/error.log:
- 2019/12/06 08:56:53 [alert] 10588#0: worker process 10802 exited on signal 11 (core dumped)
- 2019/12/06 08:56:53 [alert] 10588#0: worker process 10802 exited on signal 11 (core dumped)
- 2019/12/06 08:56:53 [alert] 10588#0: worker process 10802 exited on signal 11 (core dumped)
- 2019/12/06 08:56:53 [notice] 10588#0: start worker process 10806
- 2019/12/06 08:56:53 [notice] 10588#0: start worker process 10806
- ngx_http_fastdfs_process_init pid=10806
- 2019/12/06 08:56:56 [notice] 10588#0: signal 17 (SIGCHLD) received from 10806
- 2019/12/06 08:56:56 [notice] 10588#0: signal 17 (SIGCHLD) received from 10806
- 2019/12/06 08:56:56 [alert] 10588#0: worker process 10806 exited on signal 11 (core dumped)
- 2019/12/06 08:56:56 [alert] 10588#0: worker process 10806 exited on signal 11 (core dumped)
- 2019/12/06 08:56:56 [alert] 10588#0: worker process 10806 exited on signal 11 (core dumped)
- 2019/12/06 08:56:56 [notice] 10588#0: start worker process 10808
- 2019/12/06 08:56:56 [notice] 10588#0: start worker process 10808
- ngx_http_fastdfs_process_init pid=10808
- 2019/12/06 08:56:59 [notice] 10588#0: signal 17 (SIGCHLD) received from 10808
- 2019/12/06 08:56:59 [notice] 10588#0: signal 17 (SIGCHLD) received from 10808
- 2019/12/06 08:56:59 [alert] 10588#0: worker process 10808 exited on signal 11 (core dumped)
- 2019/12/06 08:56:59 [alert] 10588#0: worker process 10808 exited on signal 11 (core dumped)
- 2019/12/06 08:56:59 [alert] 10588#0: worker process 10808 exited on signal 11 (core dumped)
- 2019/12/06 08:56:59 [notice] 10588#0: start worker process 10812
- 2019/12/06 08:56:59 [notice] 10588#0: start worker process 10812
差不多就是循环往复地打这些日志, 然后我就去百度了一下, 查到了这篇:
里面提到了 dmesg 命令, 我这边也执行了一下, 输出如下:
- [55522.992453] nginx[10844]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55526.018405] nginx[10851]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55529.043590] nginx[10853]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55532.070932] nginx[10855]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55535.097444] nginx[10859]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55538.122466] nginx[10861]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55541.148914] nginx[10871]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55544.201955] nginx[10914]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55547.229135] nginx[10921]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55550.254445] nginx[10923]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55553.279543] nginx[10928]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55556.305874] nginx[10932]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55559.331128] nginx[10936]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55562.356655] nginx[10938]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55565.408411] nginx[10943]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55568.434908] nginx[10948]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
- [55571.459719] nginx[10950]: segfault at 4 ip 00007f23d017ff84 sp 00007ffdf82783e0 error 4 in libfdfsclient.so[7f23d0179000+18000]
我注意到, 这里面提到了: libfdfsclient.so, 因为我们的 nginx 对 fastdfs 进行了代理 (这块同事弄的, 暂时没问具体机制, 搜了一下, 大概如下:)
我就想, 之前同事好像和我说, 要把 fastdfs 重新启动起来, 我一想, 可能服务器重启后, fastdfs 没启动导致的.
然后执行了一下命令, 重启了 fastdfs 相关服务:
- /etc/init.d/fdfs_trackerd start
- /etc/init.d/fdfs_storaged start
然后再观察 nginx 的 error.log, 居然就没有一直打印上面的错误日志了:
- 2019/12/06 08:58:21 [notice] 10588#0: signal 17 (SIGCHLD) received from 10950
- 2019/12/06 08:58:21 [notice] 10588#0: signal 17 (SIGCHLD) received from 10950
- 2019/12/06 08:58:21 [alert] 10588#0: worker process 10950 exited on signal 11 (core dumped)
- 2019/12/06 08:58:21 [alert] 10588#0: worker process 10950 exited on signal 11 (core dumped)
- 2019/12/06 08:58:21 [alert] 10588#0: worker process 10950 exited on signal 11 (core dumped)
- 2019/12/06 08:58:21 [notice] 10588#0: start worker process 10954
- 2019/12/06 08:58:21 [notice] 10588#0: start worker process 10954
- ngx_http_fastdfs_process_init pid=10954
- ## 重启 fastdfs 服务后, 这里日志就稳定在下面这一行, 没有一直打印错误了:
- [2019-12-06 08:58:23] INFO - fastdfs apache / nginx module v1.21, response_mode=proxy, base_path=/tmp, url_have_group_name=1, group_name=group1, storage_server_port=23000, path_count=1, store_path0=/home/fastdfs/storage, connect_timeout=2, network_timeout=30, tracker_server_count=1, if_alias_prefix=, local_host_ip_count=3, anti_steal_token=0, token_ttl=0s, anti_steal_secret_key length=0, token_check_fail content_type=, token_check_fail buff length=0, load_fdfs_parameters_from_tracker=1, storage_sync_file_max_delay=86400s, use_storage_id=0, storage server id/ip count=0 / 0, flv_support=1, flv_extension=flv
- 2019/12/06 09:00:32 [info] 10954#0: *2 client timed out (110: Connection timed out) while waiting for request, client: 10.15.4.46, server: 0.0.0.0:80
来源: https://www.cnblogs.com/grey-wolf/p/11993526.html