Unfortunately I can’t possibly guess without more information. What do the logs say when pio cannot be started? Are all these pio instances separate, not in a cluster? In other words does each pio server have all necessary services running on them? I assume none is sleeping like a laptop does?
I you are worrying, when properly configured PIO is quite stable on servers that do not sleep. I have never seen a bug that would cause this and have installed it hundreds of time so lets look through logs and check your pio-env.sh on a particular machine that is having this problem. From: bala vivek <bala.vivek...@gmail.com> <bala.vivek...@gmail.com> Date: January 22, 2018 at 11:32:17 PM To: actionml-user <actionml-u...@googlegroups.com> <actionml-u...@googlegroups.com> Subject: Re: PIO error Hi Pat, The PIO has installed on the Ubuntu server, the Dev server and production servers are hosted in other countries and we are connecting through VPN from my laptop. And yes if I do a pio-start-all and pio-stop-all resolves the issue always, but this issue is re-occurring often and sometimes the PIO service is not coming up even after multiple Pio restart. Not sure with the core reason why the service is often getting down. Regards, Bala On Tuesday, January 23, 2018 at 2:47:26 AM UTC+5:30, pat wrote: > > If you are using a laptop for a dev machine, when it sleeps it can > interfere with Zookeeper, which is started and used by HBase. So > pio-stop-all then pio-start-all restarts HBase and therefor Zookeeper > gracefully to solve this. > > Does the stop/start always solve this? > > > > From: bala vivek <bala.v...@gmail.com> > Date: January 21, 2018 at 10:39:31 PM > To: actionml-user <action...@googlegroups.com> > Subject: PIO error > > Hi, > > I'm getting the following error in pio. > > pio status gives me the below result, > > [INFO] [Console$] Inspecting PredictionIO... > [INFO] [Console$] PredictionIO 0.10.0-incubating is installed at > /opt/tools/PredictionIO-0.10.0-incubating > [INFO] [Console$] Inspecting Apache Spark... > [INFO] [Console$] Apache Spark is installed at > /opt/tools/PredictionIO-0.10.0-incubating/vendors/spark-1. > 6.3-bin-hadoop2.6 > [INFO] [Console$] Apache Spark 1.6.3 detected (meets minimum requirement > of 1.3.0) > [INFO] [Console$] Inspecting storage backend connections... > [INFO] [Storage$] Verifying Meta Data Backend (Source: ELASTICSEARCH)... > [INFO] [Storage$] Verifying Model Data Backend (Source: LOCALFS)... > [INFO] [Storage$] Verifying Event Data Backend (Source: HBASE)... > [INFO] [Storage$] Test writing to Event Store (App Id 0)... > [ERROR] [Console$] Unable to connect to all storage backends successfully. > The following shows the error message from the storage backend. > [ERROR] [Console$] Failed after attempts=1, exceptions: > Mon Jan 22 01:00:02 EST 2018, org.apache.hadoop.hbase. > client.RpcRetryingCaller@5c5d6175, org.apache.hadoop.hbase.ipc. > RemoteWithExtrasException(org.apache.hadoop.hbase.PleaseHoldException): > org.apache.hadoop.hbase.PleaseHoldException: Master is initializing > at org.apache.hadoop.hbase.master.HMaster. > checkInitialized(HMaster.java:2293) > at org.apache.hadoop.hbase.master.HMaster.checkNamespaceManagerReady( > HMaster.java:2298) > at org.apache.hadoop.hbase.master.HMaster.listNamespaceDescriptors( > HMaster.java:2536) > at org.apache.hadoop.hbase.master.MasterRpcServices. > listNamespaceDescriptors(MasterRpcServices.java:1100) > at org.apache.hadoop.hbase.protobuf.generated. > MasterProtos$MasterService$2.callBlockingMethod(MasterProtos.java:55734) > at org.apache.hadoop.hbase.ipc.RpcServer.call(RpcServer.java:2180) > at org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:112) > at org.apache.hadoop.hbase.ipc.RpcExecutor.consumerLoop( > RpcExecutor.java:133) > at org.apache.hadoop.hbase.ipc.RpcExecutor$1.run(RpcExecutor.java:108) > at java.lang.Thread.run(Thread.java:748) > > (org.apache.hadoop.hbase.client.RetriesExhaustedException) > [ERROR] [Console$] Dumping configuration of initialized storage backend > sources. Please make sure they are correct. > [ERROR] [Console$] Source Name: ELASTICSEARCH; Type: elasticsearch; > Configuration: TYPE -> elasticsearch, HOME -> /opt/tools/PredictionIO-0.10. > 0-incubating/vendors/elasticsearch-1.7.3 > [ERROR] [Console$] Source Name: LOCALFS; Type: localfs; Configuration: > PATH -> /root/.pio_store/models, TYPE -> localfs > [ERROR] [Console$] Source Name: HBASE; Type: hbase; Configuration: TYPE -> > hbase, HOME -> /opt/tools/PredictionIO-0.10.0-incubating/vendors/hbase-1. > 2.4 > > > This setup is running in our production and this is not a new setup. Often > I get this error and if do a pio-stop-all and pio-start-all, pio will work > fine. > But why often the pio status is showing error. There was no new > configuration changes made in the pio-envi.sh file > -- > You received this message because you are subscribed to the Google Groups > "actionml-user" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to actionml-use...@googlegroups.com. > To post to this group, send email to action...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/actionml-user/4d2f0758-3718-4dc1-a844-ce48747d86dd% > 40googlegroups.com > <https://groups.google.com/d/msgid/actionml-user/4d2f0758-3718-4dc1-a844-ce48747d86dd%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > -- You received this message because you are subscribed to the Google Groups "actionml-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to actionml-user+unsubscr...@googlegroups.com. To post to this group, send email to actionml-u...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/actionml-user/4a3ee346-745b-4ca3-a6bd-e6953695f0c9%40googlegroups.com <https://groups.google.com/d/msgid/actionml-user/4a3ee346-745b-4ca3-a6bd-e6953695f0c9%40googlegroups.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout.
