Did anyone come across with HTTP code 500 error?

Hello Tsky,

Thank you for your question! A status code of 500 is a generic server failure, and in the case of OneFS, the "server" will be the Platform API (papi). There are a few common causes to this issue, so I will list a few here:

1. The cluster event log (celog) is not functioning. The easiest way to see this is on the node you are trying to connect to teh WebUI on, look at the file /var/log/isi_celog_coalescer.log. If you see messages like this:

2015-07-13T11:10:20-04:00 <3.6> mycluster-1(id1) isi_celog_coalescer[8357:CoalThread:dbbackend:1477] INFO: Got error relaying query: MasterComError("Error in transaction, msg: 'hi 1 1'.",)

2015-07-13T11:10:20-04:00 <3.6> mycluster-1(id1) isi_celog_coalescer[8357:CoalThread:dbbackend:2360] INFO: Error connecting to master: Error in transaction, msg: 'hi 1 1'.

You will want to follow our KB to reset these services and their databases: https://support.emc.com/kb/16586

2. Your node is being used to connect to Isilon InsightIQ. The Platform API is integral to IIQ operations, and from time to time the calls it is making for statistics overwhelm the service and other processes could suffer performance or usability issues if they are reliant on papi as well. The WebUI happens to be such a service. If you have InsightIQ in your environment, please double check which node your instance connects to in the IIQ WebUI:

If the node IP or DNS entry you have listed there is the node you are having issues with, I would recommend creating an SR with Support so we can look in to why IIQ may be hitting your node too hard.

To create a service request, you have a couple options:

1. Log in to your online account on support.emc.com and go to this page: https://support.emc.com/servicecenter/createSR

2. Call in to EMC Isilon Support at 1-800-782-4362 (For a complete local country dial list, please see this document: http://www.emc.com/collateral/contact-us/h4165-csc-phonelist-ho.pdf)

3. Lastly, papi itself may be in bad shape. Since logging on the service is not the most verbose, the best way to determine this is to see if papi is logging at all in /var/log/isi_papi_d.log. If there are no log entries in the past couple days or more, it may be a good idea to restart the service. If you would like to know more about what caused papi to be in the shape it was, please create a case for Support prior to restarting any services and request that Support gather cores of the process for analysis.

Please let me know if you have any other questions about this issue! I would be more than happy to help.