404 Not Found errors

[hdezmora]

Apologies if this is a very dummy question, but by following instructions from the README.md, I'm getting "404 Not Found" errors like:

The requested URL /diskstats/detailed.php was not found on this server.

Also, why the differences between code from

https://github.com/cea-hpc/robinhood/wiki

and

https://github.com/numericalalgorithmsgroup/robinhood-reports

First one works fine but content is different to what you presented at LUG2019.

Thanks much!

[shawnahall71]

So sorry I missed your comment! I don’t know why GitHub didn’t notify me that you opened an issue.

I suppose this isn’t well documented, but the code assumes that the url is sitting at is either http(s)://<hostname>/diskstats/ or http(s)://<hostname>/diskstatsdev/. This is one of those things that could be made configurable if desired.

As far as your second question, I’m not sure I follow. The nice folks at CEA have their own Robinhood GUI interface, but we built our interface to meet the needs of our users. The two interfaces I believe give quite different ways of looking at your Robinhood data.

[hdezmora]

Shawn, I have missed this email -took me a while to respond. Do you have any up-to-date documentation we can use? I have abandoned this project but planning to start it again from scratch so any hints/guidance would be greatly appreciated. Essentially, we would like to have a Robinhood WebUI available to retrieve information of the three Lustre filesystems we have in production here in NASA-JSC. Thanks for having the time to respond to my previous email, and hoping to have some input from you soon! Best regards, -Hugo

…

-- *Hugo R Hernandez* "Se seus esforços foram vistos com indeferença, não desanime que o sol faze um espectacolo maravilhoso todas as manhãs enquanto a maioria das pessoas ainda estão dormindo" - Anónimo brasileiro

On Wed, Nov 20, 2019 at 8:13 AM Shawn Hall ***@***.***> wrote: So sorry I missed your comment! I don’t know why GitHub didn’t notify me that you opened an issue. I suppose this isn’t well documented, but the code assumes that the url is sitting at is either http(s):///diskstats/ or http(s):///diskstatsdev/. This is one of those things that could be made configurable if desired. As far as your second question, I’m not sure I follow. The nice folks at CEA have their own Robinhood GUI interface, but we built our interface to meet the needs of our users. The two interfaces I believe give quite different ways of looking at your Robinhood data. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#7?email_source=notifications&email_token=AB34N5IL2WTOQF65O6RWWGDQUVAZXA5CNFSM4IFIITN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEESDF6I#issuecomment-556020473>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB34N5JQ5EHWZEXM2H4WR33QUVAZXANCNFSM4IFIITNQ> .

[shawnahall71]

Hi Hugo - all the written documentation I have for this project is included in the repo either in the README or as comments in the configuration file. I didn't have a lot of time to dedicate to creating pristine documentation before making this open source, but I'm more than happy to answer questions and to add to the documentation to clarify.

There's really two things I can think of that you need to know when setting this up.

1. Because this is hard coded in (we certainly could change this), the code either needs to sit at http(s)://<hostname/diskstats/ or http(s)://<hostname>/diskstatsdev/. The hard coding exists in these places: https://github.com/numericalalgorithmsgroup/robinhood-reports/search?q=diskstats&unscoped_q=diskstats, so with some smarter logic we could remove that requirement. At the time that was a quick code fix that allowed me to have an easy dev and prod environment.
2. Once the code is on your web server in those places, the only file you need to modify is dbroconf.php.example (of course renaming it to dbroconf.php in the process). This file sets the basic configuration the website needs, which is mostly database access credentials for each of your Robinhood databases and a few details about your file systems. There are tips in the example file on how to set up separate read only database users. I can also share the steps we took to improve the performance of our Robinhood databases (MySQL tunings, indices), but let's get you up and running first (I shared those steps in my LUG 2019 presentation).

Everything else is self contained in the code. All dependencies are bundled in the repo. As long as you have a working LAMP server and the above requirements, I can't think of anything else you'd need.

To give more detail to your original question about the differences in https://github.com/cea-hpc/robinhood/wiki and this repo - the first repo is published by CEA - the folks who wrote and maintain Robinhood. CEA has a web GUI bundled with Robinhood itself (https://github.com/cea-hpc/robinhood/tree/master/web_gui), but what we found was that the CEA-written GUI is more focused on higher level statistics of the file system. We had a need for a web GUI that was more focused on the detailed analysis of users' data, and our users were accustomed to a certain presentation of the file system data, so we decided to write Robinhood Reports. I also put a bit of a comparsion (in my opinion) between the two in my LUG presentation. We primarily use Robinhood Reports ourselves to track down where our user's seldomly used data sits to encourage them to archive or delete it (we don't purge).

Hope this helps answer some questions.