Page MenuHomePhabricator

Restart Pentaho
Closed, ResolvedPublic

Description

Please restart Pentaho so @Tbayer can look up some historical data for the Quarterly Report to the community.

Event Timeline

kevinator raised the priority of this task from to Needs Triage.
kevinator updated the task description. (Show Details)
kevinator moved this task to Next Up on the Analytics-Kanban board.

pentaho is inaccessible via ssh due to stale puppet probably. I didn't want to waste Yuvi's time with it so I didn't ask. I rebooted the instance but that didn't solve anything, the service didn't come up. We need to just puppetize this prooperly.

Hi folks -- Tilman has a time sensitive request that he needs the pentaho data for. If we can't restart the interface, can we give him access to the underlying database?

thanks,

-Toby

FYI we talked to Tilman and showed him around the data, and we're available for any help he needs to dig through it.

For the record, retrieving the information via stat1003 instead worked out great thanks to Dan's and Kevin's help, so Pentaho is no longer needed for this particular purpose. (I guess it would still be useful to produce clarity on whether Pentaho should be regarded as definitely decommissioned or not, so leaving this task open for now.)

Milimetric claimed this task.

This Pentaho instance was never meant to be commissioned in the first place. The service was running from my home folder, which is probably why it's completely dead now as NFS home folders were disabled. I totally see a place for Pentaho in our infrastructure, and I think people whose use cases it satisfies should speak up for it. I might present something about it at a tech talk, but in the meantime, I'll close this task. We can open another one to make a supported proper instance of Mondrian and Saiku.