Hi Matt, Thank you for the reply.
About homestead, yes I tried running "sudo service clearwater-infrastructure restart" did not return any error [homestead]ubuntu@homestead:/var/log/homestead$ sudo service clearwater-infrastructure restart * Restarting clearwater-infrastructure clearwater-infrastructure Configuring monit for only localhost access [ OK ] [homestead]ubuntu@homestead:/var/log/homestead$ On Ellis node the process seems to run, but its not stable process restarts after a while. [ellis]ubuntu@ellis:/etc/clearwater$ sudo monit summary The Monit daemon 5.8.1 uptime: 9h 50m Process 'ntp_process' Running System 'node-ellis' Running Process 'nginx_process' Running Process 'mysql_process' Running Process 'ellis_process' Running Program 'poll_ellis' Status ok Program 'poll_ellis_https' Status ok Process 'clearwater_queue_manager' Running Process 'etcd_process' Running Program 'poll_etcd_cluster' Waiting Program 'poll_etcd' Status ok Process 'clearwater_diags_monitor_process' Running Process 'clearwater_config_manager' Running Process 'clearwater_cluster_manager' Running And the ellis error log file says it failed to ping homestead. "UTC ERROR homestead.py:68: Failed to ping Homestead at http://hs.10.222.5.173:8889/ping. Have you configured your HOMESTEAD_URL?" netstat on homestead shows no processon 8889 port. Shiva On Thu, Jan 21, 2016 at 6:59 PM, Matt Williams <[email protected] > wrote: > Shiva, > > > > It's good to hear from you. > > > > /var/lib/homestead/homestead.conf should be built by the > clearwater-infrastructure script that is run on package installation and > boot. You can rerun it by typing "sudo service clearwater-infrastructure > restart". Do you get any errors out when you do so? > > > > You mention that ellis is displaying the nginx page. Is the ellis process > running? Run "sudo monit summary" on the ellis node to find out. If it > isn't running, please check /var/log/ellis/ for details and, if that > doesn't help, let me know what you see. > > > > Incidentally, please can you subscribe to the clearwater mailing list, so > that your posts are automatically approved and you can see other people's > questions and comments - see > http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org > for details. > > > > Thanks, > > > > Matt > > > > -- > > > > Matt Williams > Lead Architect, Project Clearwater > > +44 (0) 20 8366 1177 > > > > *From:* Clearwater [mailto:[email protected]] > *On Behalf Of *Shiva Charan > *Sent:* 21 January 2016 12:38 > *To:* [email protected] > *Subject:* [Clearwater] Homestead conf file missing. > > > > Hi, > > > > I have a new clearwater manual install setup, homestead process has a > "Execution failed" status. > > > > Also when i open the ellis UI with the ellis IP it goes to nginx page, how > do i get the clearwater UI? > > > > /etc/log/homestead/homestead_current.txt says the /var/lib/homestead.conf > file is missing. How do I get this file? > > > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-EXTEND-MIB: nsExtendResult ::= { nsExtendOutput1Entry 4 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-EXTEND-MIB: nsExtendOutNumLines ::= { nsExtendOutput1Entry 3 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-EXTEND-MIB: nsExtendOutputFull ::= { nsExtendOutput1Entry 2 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-EXTEND-MIB: nsExtendOutput1Line ::= { nsExtendOutput1Entry 1 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-EXTEND-MIB: nsExtendOutLine ::= { nsExtendOutput2Entry 2 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-EXTEND-MIB: nsExtendLineIndex ::= { nsExtendOutput2Entry 1 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-AGENT-MIB: nsNotifyStart ::= { netSnmpNotifications 1 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-AGENT-MIB: nsNotifyShutdown ::= { netSnmpNotifications 2 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > NET-SNMP-AGENT-MIB: nsNotifyRestart ::= { netSnmpNotifications 3 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laErrMessage ::= { laEntry 101 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laErrorFlag ::= { laEntry 100 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laLoadFloat ::= { laEntry 6 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laLoadInt ::= { laEntry 5 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laConfig ::= { laEntry 4 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laLoad ::= { laEntry 3 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laNames ::= { laEntry 2 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Cannot adopt OID in > UCD-SNMP-MIB: laIndex ::= { laEntry 1 } > > 21-01-2016 12:33:09.196 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 21-01-2016 12:33:09.197 UTC Status load_monitor.cpp:105: Constructing > LoadMonitor > > 21-01-2016 12:33:09.197 UTC Status load_monitor.cpp:106: Target latency > (usecs) : 100000 > > 21-01-2016 12:33:09.197 UTC Status load_monitor.cpp:107: Max bucket > size : 20 > > 21-01-2016 12:33:09.197 UTC Status load_monitor.cpp:108: Initial token > fill rate/s: 100.000000 > > 21-01-2016 12:33:09.197 UTC Status load_monitor.cpp:109: Min token fill > rate/s : 10.000000 > > 21-01-2016 12:33:09.197 UTC Status dnscachedresolver.cpp:142: Creating > Cached Resolver using servers: > > 21-01-2016 12:33:09.197 UTC Status dnscachedresolver.cpp:152: 127.0.0.1 > > 21-01-2016 12:33:09.197 UTC Status httpresolver.cpp:51: Created HTTP > resolver > > 21-01-2016 12:33:09.197 UTC Status cassandra_store.cpp:154: Configuring > store connection > > 21-01-2016 12:33:09.197 UTC Status cassandra_store.cpp:155: Hostname: > localhost > > 21-01-2016 12:33:09.197 UTC Status cassandra_store.cpp:156: Port: > 9160 > > 21-01-2016 12:33:09.197 UTC Status cassandra_store.cpp:206: Configuring > store worker pool > > 21-01-2016 12:33:09.197 UTC Status cassandra_store.cpp:207: Threads: 10 > > 21-01-2016 12:33:09.197 UTC Status cassandra_store.cpp:208: Max Queue: 0 > > 21-01-2016 12:33:09.198 UTC Status cassandra_store.cpp:223: Starting store > > 21-01-2016 12:33:09.200 UTC Status httpconnection.cpp:146: Configuring > HTTP Connection > > 21-01-2016 12:33:09.200 UTC Status httpconnection.cpp:147: Connection > created for server :9888 > > 21-01-2016 12:33:09.200 UTC Status httpconnection.cpp:148: Connection > will use a response timeout of 500ms > > 21-01-2016 12:33:09.200 UTC Status diameterstack.cpp:78: Initializing > Diameter stack > > 21-01-2016 12:33:09.202 UTC Status diameterstack.cpp:415: Configuring > Diameter stack from file /var/lib/homestead/homestead.conf > > 21-01-2016 12:33:09.202 UTC Error freeDiameter: Unable to open > configuration file for reading; tried the following locations: > /var/lib/homestead/homestead.conf; Error: No such file or directory > > 21-01-2016 12:33:09.202 UTC Error freeDiameter: ERROR: in > '((fd_conf_parse()))' : No such file or directory > > 21-01-2016 12:33:09.202 UTC Error main.cpp:756: Failed to initialize > Diameter stack - function fd_core_parseconf, rc 2 > > 21-01-2016 12:33:09.202 UTC Status main.cpp:757: Homestead is shutting down > > 21-01-2016 12:33:09.202 UTC Status cassandra_store.cpp:245: Stopping store > > 21-01-2016 12:33:09.202 UTC Status cassandra_store.cpp:255: Waiting for > store to stop > > > > Thanks, > > Shiva > > >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
