Skip to content
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

message d'erreur ambigu : vishnu_list_queues < machine inconnue> (Bugzilla #234) #88

Open
bdepardo opened this issue Feb 25, 2013 · 5 comments

Comments

@bdepardo
Copy link
Member

enhancement bug in component UMS
Reported in version 1.2.2 on platform Other

@bdepardo
Copy link
Member Author

On 2011-07-22 01:39:02 +0200, 'Samuel Kortas ([email protected]) wrote:
la commande
vishnu_list_queues xxxxxxxxxxxxxxxx
ou xxxxxxxxxxxxxxxx est une machine inconnue de vishnu*

renvoie l'erreur ambigüe

vishnu_list_queues: Vishnu not available (Service bus failure) [DIET call failure]

SK

@bdepardo
Copy link
Member Author

On 2011-08-17 15:35:40 +0200, 'Benjamin Depardon ([email protected]) wrote:
Changement de version du produit -> 1.2.2

@bdepardo
Copy link
Member Author

On 2011-08-22 13:26:45 +0200, 'Benjamin Depardon ([email protected]) wrote:
Voir si on peut utiliser IMS pour récupérer des informations plus précises sur les erreurs.

@bdepardo
Copy link
Member Author

On 2011-08-30 11:04:50 +0200, 'Benjamin Depardon ([email protected]) wrote:
Lister les erreurs possibles -> voir si on peut détecter les problèmes réseaux dans DIET par rapport aux problèmes de service inexistant.

Erreurs :

  • problème réseaux
  • nom machine pas bon
  • machine existe, mais SeD ne tourne pas

Utilisation d'IMS : cela serait possible, mais du coup ça impliquerait une dépendance de TMS vers IMS, alors que jusque là tous les modules sont indépendants.

@bdepardo
Copy link
Member Author

On 2011-09-02 02:34:11 +0200, 'Samuel Kortas ([email protected]) wrote:
La dependance ne me choque pas.

SK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant