-
Notifications
You must be signed in to change notification settings - Fork 174
Uchiwa doesn't start, multiple versions #332
Comments
Updated stack trace to output from current master branch (original post had the trace from a 0.5.1 build - this should be more helpful) |
@palourde You're awesome! Thank you!!! Just FYI I now see an error printed out quite a bit when: config.json: {
"sensu": [
{
"name": "Site 1",
"host": "localhost",
"port": 4567
}
],
"uchiwa": {
"host": "0.0.0.0",
"port": 3000,
"refresh": 5
}
} Error is:
Still, it works now! Thank you! Edit: After looking at the code, my thought is that I have some heinous event data stored in Sensu somehow. uchiwa/uchiwa/daemon/clients.go Line 36 in 7c52df2
I'm gonna see if I can't debug this one myself and have it print some useful info about the event that it failed to decode 👍 Thanks again for all your help! |
@erulabs Awesome! The warning message you see is probably caused by an invalid event. I suggest you to flush the redis cache ( If you still see this message, could you provide me the output of the events endpoint on the Sensu API?(e.g. |
Flushing the redis queue resolved the error message. Sort of upset with myself for not trying to figure out exactly what the malformed event was, but never-the-less, things are much much better now. I'll leave this open (feel free to close it) - might be a good idea to leave open until this is released as a package as others may run into this. |
@erulabs Uchiwa 0.9.0, which include this fix, has been released as today: http://blog.uchiwa.io/uchiwa-0-9-0/ so I'll close this issue but do not hesitate to let us know if you face any other issue! |
panic: interface conversion: interface is []interface {}, not string
It seems like this may be a duplicate of issue #236 - however I've tested with Uchiwa 0.5.1, 0.7.0 and from source against master branch of this repository.
When running the binary directly
/opt/uchiwa/bin/uchiwa -c /etc/sensu/uchiwa.json -p /opt/uchiwa/src/public
, OR from source viago run uchiwa.go -c /etc/sensu/uchiwa.json
- assuming my /etc/sensu/uchiwa.json has the following content:I see the following crash:
If I define a path, I get
My thought is that this might not be Uchiwa's issue - Since it appears to be starting properly then crashing on a reply from Sensu API. Just to be sure, I tried 3 versions of Uchiwa (including current master as of about an hour ago), and I have loaded the default configuration file and played with it until I felt dizzy (The only thing that has any effect is breaking the connection to sensu-api - Uchiwa behaves normally if it can't reach sensu-api - if it can, it throws the error above).
My Sensu API is at version
0.17.0-1
.Any help would be appreciated! I'm sure there is some obvious issue here like me failing to understand the configuration or the version of Sensu-api.
Thanks!
The text was updated successfully, but these errors were encountered: