Project

General

Profile

Anomalie #7637

Si le fichier de configuration n'existe pas, le démarrage est bloqué

Added by Emmanuel GARETTE over 9 years ago. Updated over 9 years ago.

Status:
Fermé
Priority:
Haut
Assigned To:
Daniel Dehennin
Category:
-
Target version:
Distribution EOLE - Eole 2.4-RC3
Start date:
03/28/2014
Due date:
04/04/2014
% Done:

100%

Spent time:
0.67 h
Distribution:
EOLE 2.4

Description

Suite au bug #7636 (le fichier /etc/eole/flask/eoleflask.conf n'existe pas), le service reste bloqué et ne rend pas la main.

# /etc/init.d/eoleflask start
 * Starting eole flask server eoleflask                                                                                                                       2014-03-14 12:02:24 [3177] [INFO] Starting gunicorn 0.13.4
2014-03-14 12:02:24 [3177] [INFO] Listening at: http://127.0.0.1:8000 (3177)
2014-03-14 12:02:24 [3177] [INFO] Using worker: sync
2014-03-14 12:02:24 [3180] [INFO] Booting worker with pid: 3180
Missing cookie

Related issues

Related to eole-flask - Anomalie #7636: le fichier de configuration n'est plus présent dans le paquet eole-flask-server Fermé 03/21/2014

Associated revisions

Revision a663785c (diff)
Added by Daniel Dehennin over 9 years ago

Le démon ne démarre pas sans configuration

  • eoleflask.init: Émettre un avertissement si le fichier de
    configuration n’est pas présent.

Fixes: #7637 @15m

History

#1 Updated by Joël Cuissinat over 9 years ago

  • Due date set to 04/04/2014

#2 Updated by Daniel Dehennin over 9 years ago

Sur mon eolebase à jour, j’obtiens le résultat suivant :

root@eolebase:~# /etc/init.d/eoleflask stop
 * Stopping eole flask server eoleflask                         [ OK ] 
root@eolebase:~# mv /etc/eole/flask/eoleflask.conf /tmp/
root@eolebase:~# /etc/init.d/eoleflask start
 * Starting eole flask server eoleflask
2014-03-26 09:29:31 [18353] [INFO] Starting gunicorn 0.13.4
2014-03-26 09:29:31 [18353] [ERROR] Connection in use: ('127.0.0.1', 8000)
2014-03-26 09:29:31 [18353] [ERROR] Retrying in 1 second.
2014-03-26 09:29:32 [18353] [ERROR] Connection in use: ('127.0.0.1', 8000)
2014-03-26 09:29:32 [18353] [ERROR] Retrying in 1 second.
2014-03-26 09:29:33 [18353] [ERROR] Connection in use: ('127.0.0.1', 8000)
2014-03-26 09:29:33 [18353] [ERROR] Retrying in 1 second.
2014-03-26 09:29:34 [18353] [ERROR] Connection in use: ('127.0.0.1', 8000)
2014-03-26 09:29:34 [18353] [ERROR] Retrying in 1 second.
2014-03-26 09:29:35 [18353] [ERROR] Connection in use: ('127.0.0.1', 8000)
2014-03-26 09:29:35 [18353] [ERROR] Retrying in 1 second.
2014-03-26 09:29:36 [18353] [ERROR] Can't connect to ('127.0.0.1', 8000)
                                                                [fail]

Le service ne bloque pas.

#3 Updated by Daniel Dehennin over 9 years ago

  • Status changed from Nouveau to Résolu
  • % Done changed from 0 to 100

#4 Updated by Daniel Dehennin over 9 years ago

  • Assigned To set to Daniel Dehennin
  • Start date set to 03/28/2014

Un peu d’administratif

#5 Updated by Joël Cuissinat over 9 years ago

  • Status changed from Résolu to Fermé

OK avec les paquets : eole-flask 2.4.0-22

root@amon:~# /etc/init.d/eoleflask stop
 * Stopping eole flask server eoleflask                                                                                         [ OK ] 
root@amon:~# mv /etc/eole/flask/eoleflask.conf .
root@amon:~# /etc/init.d/eoleflask start
 * Not starting eole flask server, missing configuration file /etc/eole/flask/eoleflask.conf
root@amon:~#

Also available in: Atom PDF