Bad file descriptor is still exist

[hnzjCoder]

hello,is this bug fixed for branch nginx-upsync-1.8.x ? you say this bug has been resolved in this issue issue we allow use 'kill -USR1' to do log rotation, i find this problem is still unsolved,'Bad file descriptor' is still in nginx error log.

2019/02/23 00:01:02 [emerg] 69696#0: close() "/usr/local/tengine/conf/servers/servers_index-abnormal-analysis-service-base-production-base.conf" failed (9: Bad file descriptor)
2019/02/23 00:01:02 [emerg] 69686#0: close() "/usr/local/tengine/conf/servers/servers_index-abnormal-analysis-service-base-production-base.conf" failed (9: Bad file descriptor)
2019/02/23 00:01:02 [emerg] 69698#0: close() "/usr/local/tengine/conf/servers/servers_index-abnormal-analysis-service-base-production-base.conf" failed (9: Bad file descriptor)
2019/02/23 00:01:02 [emerg] 69710#0: close() "/usr/local/tengine/conf/servers/servers_index-abnormal-analysis-service-base-production-base.conf" failed (9: Bad file descriptor)

[xiaokai-wang]

@mrBob90 建议使用master 分支.

[hnzjCoder]

你好，这个问题对nginx有影响吗，没有影响的话，就先这样。目前除了看到有错误日志，并没有实际性的影响。 后面考虑升级一下nginx版本，因为我们先在用的是tengine,tengine稳定版不支持upsync的master分之。