-
Notifications
You must be signed in to change notification settings - Fork 5.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Traefik crashing #458
Comments
@rogeriollacerda thanks for reporting this.
|
@emilevauge thanks for answer. I was using the docker image with from traefik. Today, after your answer, I'm trying with Dockerfile:
I am using the 1.0.0-rc2 now. After the test in production environment, I can post the results here. Now we are receiving 2000 requests per second in a single Traefik instance. |
FYI, you can also use the official rc2 Docker image :) |
Probably link to #462 |
@rogeriollacerda could you try using a lower value for |
@emilevauge I'm still with the same problem. I'll try to change the MaxIdleConnsPerHost but in my first docker image, I used the default value (200). Do you think can be the request number? Yesterday, I changed the GOMAXPROCS to 10 too. Traefik is running in a 24 cores server only for it. |
@rogeriollacerda: I also fixed a memory leak yesterday in PR #464 and think it could be linked to your issue: you can grab the docker image |
@emilevauge I already changed the MaxIdleConnsPerHost and update with the fixed memory leak version in production environment. I'll send you a feedback soon. TKS a lot! |
@emilevauge FYI Traefik docker stats after 22 minutes: CONTAINER CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O No problems yet. |
The same problem after new version. The error was:
stderr file attached. |
OK, you didn't gave me the error part in your previous logs : |
@emilevauge Sure, you are right. By default, mesos delete the failed containers logs. Now, for traefik, I store all logs in another place. Sorry didn't send you the file before. Tks |
OK, the funny part of this is that the crash is due to the health check... |
Is possible disable stats removing 8080 tcp port from configuration? Traefik will collect anyway? |
As a temporary workaround, you can change your health check to |
@emilevauge my container healthcheck is / path. Change to /api is better than / ? |
Yep |
Ok tks |
@emilevauge FYI, it seems Ok with your workaround. Stats: pid: 1, total_status_code_count: |
@emilevauge any news about this? Tks! |
traefik.toml.txt
I'm using traefik with something like 1000 req/sec. Many times during the day, it crash with no error logs. I just can see the goroutines dump with many I/O wait. I'm running oficial docker image with traefik executable.
sysctl parameters applied:
fs.file-max="9999999"
fs.nr_open="9999999"
net.core.netdev_max_backlog="4096"
net.core.rmem_max="16777216"
net.core.somaxconn="65535"
net.core.wmem_max="16777216"
net.ipv4.ip_local_port_range="1025 65535"
net.ipv4.tcp_fin_timeout="30"
net.ipv4.tcp_keepalive_time="30"
net.ipv4.tcp_max_syn_backlog="20480"
net.ipv4.tcp_max_tw_buckets="400000"
net.ipv4.tcp_no_metrics_save="1"
net.ipv4.tcp_syn_retries="2"
net.ipv4.tcp_synack_retries="2"
net.ipv4.tcp_tw_recycle="1"
net.ipv4.tcp_tw_reuse="1"
vm.min_free_kbytes="65536"
vm.overcommit_memory="1"
Traefik version:
2016/06/14 20:08:01 v1.0.0-rc1 built on the 2016-05-30_10:28:25PM
Ubuntu Server 14.04
traefik.log.txt
The text was updated successfully, but these errors were encountered: