Project

General

Profile

Tâche #21230

Scénario #21122: Tester e2guardian V4

Impossible de déclarer plus de 4091 workers e2guardian dans l'etb1

Added by Joël Cuissinat over 3 years ago. Updated over 3 years ago.

Status:
Fermé
Priority:
Normal
Assigned To:
Start date:
09/04/2017
Due date:
% Done:

100%

Estimated time:
3.00 h
Spent time:
Remaining (hours):
0.0

Description

Exemple, avec httpworkers = 5000 ("bonne valeur pour un serveur moyen") :

2017-09-04T12:27:31.103527+02:00 amon.etb1.lan eole-guardian[23812]:  * Starting e2guardian
2017-09-04T12:27:31.104307+02:00 amon.etb1.lan eole-guardian[23812]:  * Instance #guardian0
2017-09-04T12:27:42.200836+02:00 amon.etb1.lan eole-guardian[23812]:  httpworkers option in e2guardian.conf has a value too high for current file id limit (8192)
2017-09-04T12:27:42.201027+02:00 amon.etb1.lan eole-guardian[23812]: httpworkers 5000 must not exceed 50% of 8183
2017-09-04T12:27:42.201188+02:00 amon.etb1.lan eole-guardian[23812]: in this configuration.
2017-09-04T12:27:42.201366+02:00 amon.etb1.lan eole-guardian[23812]: Reduce httpworkers
2017-09-04T12:27:42.201479+02:00 amon.etb1.lan eole-guardian[23812]: Or increase the filedescriptors available with ulimit -n to at least=10009
2017-09-04T12:27:42.207464+02:00 amon.etb1.lan eole-guardian[23812]:    ...fail!

J'ai essayé d'augmenter la clé "LimitNOFILE" dans le .service mais sans succès.
Pourtant cela semble être la solution : https://github.com/e2guardian/e2guardian/issues/208

Associated revisions

Revision 36dd1d8b (diff)
Added by Daniel Dehennin over 3 years ago

Manage e2guardian ulimit in systemd .service

  • init/eole-guardian.service (LimitNOFILE): Set to 65535 (max).
  • scripts/eole-guardian (start_guardians): Remove hard coded ulimit
    value.

Ref: #21230

History

#1 Updated by Daniel Dehennin over 3 years ago

  • Project changed from Distribution EOLE to eole-proxy

Le problème vient d’un ulimit en dur dans le script source:scripts/eole-guardian@02042aa#L49

#2 Updated by Daniel Dehennin over 3 years ago

  • Status changed from Nouveau to En cours
  • Assigned To set to Daniel Dehennin

#3 Updated by Daniel Dehennin over 3 years ago

  • % Done changed from 0 to 100

#4 Updated by Daniel Dehennin over 3 years ago

À notez qu’au niveau utilisation ça mange un peu de ressource avec 18000 httpworkers:

 PID UTIL.     PR  NI    VIRT    RES    SHR S  %CPU %MEM    TEMPS+ COM.
6489 proxy     20   0  0,140t 466940     92 S   0,0 11,5   0:02.11 e2guardian
  • 500M en RAM
  • 140G en mémoire virtuelle

#5 Updated by Scrum Master over 3 years ago

  • Project changed from eole-proxy to Distribution EOLE
  • Status changed from En cours to Résolu

#6 Updated by Joël Cuissinat over 3 years ago

  • Remaining (hours) changed from 3.0 to 0.0

#7 Updated by Joël Cuissinat over 3 years ago

  • Status changed from Résolu to Fermé

Ok + ajout du test squash en remplacement de l'ancien pour e2guardian v3 : http://squash-tm.eole.lan/squash/executions/5979

Also available in: Atom PDF