Unable to fetch Initiatives from Query Server

[cappadona]

Hi Jason,

Trying to install Suma here at Mann Library (Cornell). We were running an original version last Fall but I fetched the latest from github earlier this week at the request of a colleague. Everything seems to be working minus the reports. Here's the error I'm getting:

exception 'Guzzle\Http\Exception\ClientErrorResponseException' with message 'Client error response [status code] 404 [reason phrase] Not Found [url] http://suma.library.cornell.edu/initiatives [request] GET /initiatives HTTP/1.1 Host: suma.library.cornell.edu User-Agent: Guzzle/2.8.3 curl/7.15.5 PHP/5.3.3 openssl/ OpenSSL/0.9.8b [response] HTTP/1.1 404 Not Found Date: Wed, 30 Jan 2013 21:05:12 GMT Server: Apache/2.2.3 (Red Hat) Content-Length: 299 Connection: close Content-Type: text/html; charset=iso-8859-1

I updated line 25 of Suma/analysis/lib/php/ServerIO.php to 'suma.library.cornell.edu' as described in #2 but that gave me a malformed URL so I switched that up to 'http://suma.library.cornell.edu'. I think I'm missing some configuration for the query server.

Any help is appreciated. Thanks.

[cazzerson]

Hi Nick,

It looks like your $_baseURL should actually be set to 'http://suma.library.cornell.edu/sumaserver/query'. Let me know if that helps.

By the way, we made some changes to the database schema this fall, so you should see if you made it under the wire. One quick way to check would be to look for an activity_group table. If you are missing that, let's talk offline about updating your database.

[cappadona]

Thanks Jason...that did the trick. Maybe it's just me, but it wasn't clear that I needed the /sumaserver/query from the install documentation:
https://github.com/cazzerson/Suma/blob/master/INSTALL.md#suma-analysis-tools-configuration

I actually dropped all tables in our DB and started fresh so we're good to go there. Thanks for your help.

[cazzerson]

Great, and thanks for catching that issue in the docs. I just pushed a change that will hopefully clear things up for future users.

[cappadona]

Much clearer...I think even I could get it right the first time :)

Thanks!

[yo-bj]

Sorry for piggybacking on a closed issue, but I'm running into the same issue and it's not getting resolved even after following all the steps above. I downloaded Suma earlier this week, so I think I'm working in the latest version. I've edited the /analysis/lib/php/ServerIO.php file to include our URL path to the query server, but am running into the same 404 error when trying to open one of the reports:

exception 'Guzzle\Http\Exception\ClientErrorResponseException' with message 'Client error response [status code] 404 [reason phrase] Not Found [url] sumaserver/query/initiatives [request] GET /sumaserver/query/initiatives HTTP/1.1 Host:blah User-Agent: Guzzle/2.8.3 curl/7.22.0 PHP/5.3.10-1ubuntu3.7 openssl/OpenSSL/1.0.1 [response] HTTP/1.1 404 Not Found Date: Thu, 29 Aug 2013 19:40:17 GMT Server: Apache/2.2.14 (Ubuntu) Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 252 Content-Type: text/html; charset=iso-8859-1

Out of curiosity, I went to sumaserver/query/initatives and have the following Zend controller exceptions and stack traces:

exception 'Zend_Controller_Action_Exception' with message 'Action "initatives" does not exist and was not trapped in __call()' in /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Action.php:485
Stack trace:
#0 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Action.php(518): Zend_Controller_Action->__call('initativesActio...', Array)
#1 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Dispatcher/Standard.php(308): Zend_Controller_Action->dispatch('initativesActio...')
#2 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#3 /var/www/sumaserver/index.php(60): Zend_Controller_Front->dispatch()
#4 {main}->getMessage()

exception 'Zend_Controller_Action_Exception' with message 'Action "initatives" does not exist and was not trapped in __call()' in /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Action.php:485
Stack trace:
#0 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Action.php(518): Zend_Controller_Action->__call('initativesActio...', Array)
#1 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Dispatcher/Standard.php(308): Zend_Controller_Action->dispatch('initativesActio...')
#2 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http))
#3 /var/www/sumaserver/index.php(60): Zend_Controller_Front->dispatch()
#4 {main}->getTraceAsString()

I must be missing something, right?

[cazzerson]

Hi Becky,

We actually changed the way Suma is configured with the 1.0 release, which you can read about in the four sections that start with this one in updated install docs. Basically, we've (finally!) moved all configuration into configuration files. Still, I'm not sure that this is what is causing the problem. Could you tell me what URL you specified in the file?

By the way, we did push a bug fix a few days ago, so I would recommend that you update to Suma 1.1.1 when you get a chance.

[yo-bj]

That was the day after I cloned the repo. :-P Oh well. FWIW, I did follow the documentation posted beforehand, so I was trying to see if there was anything in the issues list that I may have missed. I did use the URL listed above.

I've updated the instance, and I've managed to break even more things. When I try to access the admin page, this is the error I get:

Fatal error: Uncaught exception 'Zend_Controller_Dispatcher_Exception' with message 'Invalid controller specified (error)' in /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Dispatcher/Standard.php:248 Stack trace: #0 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http)) #1 /var/www/sumaserver/index.php(60): Zend_Controller_Front->dispatch() #2 {main} Next exception 'Zend_Controller_Exception' with message 'Invalid controller specified (error)#0 /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Front.php(954): Zend_Controller_Dispatcher_Standard->dispatch(Object(Zend_Controller_Request_Http), Object(Zend_Controller_Response_Http)) #1 /var/www/sumaserver/index.php(60): Zend_Controller_Front->dispatch() #2 {main}' in /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Plugin/Broker.php:336 Stack trace: #0 /var/www/app/sumaserver/se in /var/www/app/sumaserver/service/lib/zend/library/Zend/Controller/Plugin/Broker.php on line 336 

suma/web/ works, but the connection to the db seems to have been lost since I am unable to retrieve past initiatives - I'm using the same db that I used before, and the config file has the correct login information.

[yo-bj]

Never mind the 'more brokeness' report above. I got the admin portion to work, as well as the web client to recognize the db. However, the reports are still broken in the latest version, with the same error messages.

[cazzerson]

Would you mind sharing your analysis/config/config.yaml file and also
confirming that ServerIO.php is back to the same version as the repository?
On Aug 29, 2013 6:08 PM, "Becky Yoose" notifications@github.com wrote:

Never mind the 'more brokeness' report above. I got the admin portion to
work, as well as the web client to recognize the db. However, the reports
are still broken in the latest version, with the same error messages.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3#issuecomment-23527385
.