These are chat archives for ushahidi/Community

Nov 2015
Nov 19 2015 08:21
[kisiro] i need some help with installing ushahidi on a linux web server
[kisiro] can some one help me run this through?
[Jess Shorland, Ushahidi] hey @kisiroGuest -- it looks like our devs are offline right at this second (timezone issues ha). But someone should be on in a few hours that can help out if I can't. In the meantime, we've had some other questions about installation. Are you trying to install on Linux?
[Jess Shorland, Ushahidi] right, sorry -- you've already said that
[Jess Shorland, Ushahidi] at which point in the process are you experiencing trouble?
Nov 19 2015 08:30
[kisiro] well
[kisiro] i am using ssh to install oto the web server
[kisiro] so everything goes well till i get to the point in the instructions wher it says
[kisiro] installing the client
Nov 19 2015 08:39
[Jess Shorland, Ushahidi] ahhh ok -- we had another person have an issue with that. Do you get a message that says "sorry, something went wrong, try reloading the page?"
[kisiro] i should say i am new to this
[kisiro] i havent reached the point of loading it or running it
[kisiro] i am at the state of installing the client.. so no i havent seen that error message
[Jess Shorland, Ushahidi] No problem! Ok it seems like I'm not the best person to help you out, but I'll let our devs know to get in touch with you. You posted the question on our site as well, right?
Nov 19 2015 08:48
[kisiro] yes
[Jess Shorland, Ushahidi] great! I'll let the team know.
[kisiro] trhank you
Raghav Sharma
Nov 19 2015 13:48

@eyedol Hey. Been trying to get SMSSync to work but failing.
This is what my web service return

Content-Type: application/json
Content-Length: 99
Server: Werkzeug/0.10.4 Python/2.7.6
Date: Wed, 18 Nov 2015 10:26:04 GMT

  "payload": {
    "error": "Secret key didn't match for LOCALHOST.", 
    "success": false

The messages just don't go to publish list.
I'm running the app on gingerbread.

Nov 19 2015 13:50
[RaghavFTW (guest),] hey, @eyedol are you there?
[eyedol (guest),] RaghavFTW: you should return success true
[eyedol (guest),] if the server receives the same secret key set on the phone
[eyedol (guest),] SMSsync needs it's to be true to acknowlege that it successfully sent the message to the server
[RaghavFTW (guest),] I thought if it isn't returning json then it thinks that the message didn't reach the server.
[eyedol (guest),] it should return json
[RaghavFTW (guest),] I read in documentation that it just needs to return JSON in the desired format for SMSSync to think it reacched the server.
Nov 19 2015 13:55
[eyedol (guest),] oops maybe the doc isn't clear there
[RaghavFTW (guest),] Been messing aroung this for 3 days :/
[eyedol (guest),] Yikes! :(
[RaghavFTW (guest),] Ok so, return success true and make error not = null if I want to show an error?
[eyedol (guest),] yup
[eyedol (guest),] if there is error make success false
[eyedol (guest),] and set an error message
[eyedol (guest),] say if the secret key doesn't match what's set on the server
Nov 19 2015 14:00
[RaghavFTW (guest),] ye, there was an error. secret key didn't match but it reached the server so shouldn't it be in published instead?
[eyedol (guest),] correct,
[eyedol (guest),] it reached the server
[eyedol (guest),] howerver the server didn't return the right response for SMSsync to know the server reached it
[eyedol (guest),] the assumption is once the server sends back success as false
[eyedol (guest),] it will consider it as failed message
[eyedol (guest),] BTW, I have a fix for #356 on github. Let me know if you want to test it. You can install the build I will send you
[RaghavFTW (guest),] Imo, it doesn't make sense. If server didn't returned JSON it should then consider it as failed message.
[eyedol (guest),] side by side with your current install of SMSsync so it shouldn't get in the way
[RaghavFTW (guest),] It's ok. I've switched to JSON as data format.
[RaghavFTW (guest),] And please update your documention. :P
[eyedol (guest),] heh will do so
Nov 19 2015 14:06
[RaghavFTW (guest),] What was the fix if I may ask. Have you pushed it?
[eyedol (guest),] ushahidi/SMSSync@e9d3a44
[eyedol (guest),] RaghavFTW: If you have the bandwidth you can build it to test it
[eyedol (guest),] Going to hit the sack.
[eyedol (guest),] If you still having issues, feel free to reach out, via here or github. I'll do the necessary follow tomorrow
[RaghavFTW (guest),] No, I don't have the resources to test. I'm not an android developer.
[RaghavFTW (guest),] Going to test with success true now. Will get back to you if it didn't work. Thanks.
[eyedol (guest),] No worries
[eyedol (guest),] Sounds good.
[eyedol (guest),] Keep me posted
Raghav Sharma
Nov 19 2015 14:27
@eyedol, nope still not working.
This is what I'm returning now:
Connection: keep-alive
Server: gunicorn/19.3.0
Date: Thu, 19 Nov 2015 14:20:18 GMT
Content-Type: application/json
Content-Length: 98
Via: 1.1 vegur

  "payload": {
    "error": "Secret key didn't match for LOCALHOST.", 
    "success": true
Nov 19 2015 14:29
[RaghavFTW (guest),] :s
[Angela Oduor Lungati, Ushahidi] Announcing v3.1 release! Now you can stay on top of changes to your deployment in a single 'Activity' view.
[Angela Oduor Lungati, Ushahidi] Congrats team v3!!!!!!
Nov 19 2015 14:57
[RaghavFTW (guest),] eyedol: are you there?
[RaghavFTW (guest),] set success=true but still not going to publish list.
Nov 19 2015 21:08
Hum so yeah I think there might actually be an issue on teh server side. I’m doing some SMSSync work and am having dramas with the secret key matching also
I’m getting this in the server logs whenever I hit-up the dataproviders:
2015-11-19 21:02:36 --- EMERGENCY: Aura\Di\Exception\ReflectionFailure [ 0 ]: League\Event\Emitter ~ /var/www/vendor/aura/di/src/Factory.php [ 393 ] in /var/www/vendor/aura/di/src/Factory.php:447
seems the class object is empty
an SMSSync POST request gets through to the backend fine… but loading the request details into $this->request->post('secret’) just aint happening as expected… (although the request details are there if you just spit out $this->request in the log)
Nov 19 2015 21:15
these could be entirely separate issues, of course, and it could just be my JSON formatting is whack for my makeshift SMSSync tester (I’m not using the app - just POST-ing to the backend/smssync endpoint).. but either way, thats what I’m currently tinkering with. Any thoughts are appreciated but I’ll keep prodding at it.