-
Notifications
You must be signed in to change notification settings - Fork 0
Application not configured Application not responding
anandkumarpatel edited this page Mar 22, 2016
·
1 revision
if you get one of these error pages something is wrong with hipache
how hipache works
hipache takes request then looks up that URL in redis
format of keys in redis
frontend:<url>
list all keys
keys frontend:*
view keys
lrange frontend:<url> 0 -1
1) some string that does not matter
2) http://10.10.10.1:4242
2 is the ip and port of where hipache will proxy
Application not configured: means redis is missing an entry for that URL
- if you get this check the person who writes these entries
- ansible writes main hipache entries (api, apisock)
- api writes userland entries
Application not responding: means the key exist in redis BUT it hit an error when proxying
- if they are main hipache, the service is down or security groups are messed up
- if userland, check connection to navi