Misc Error 6408
Contents |
to try to fix it. We know this is frustrating and hope network connection error android to have it back up and running for you in no time. Thanks for your patience. In the meantime, try our other site sections at www.sprint.com Your Privacy Rights Acceptable Use Policy and Visitor Agreement Copyright Notices Find a Store Contact Us Email Sign Up ©2009 Sprint. All rights reserved.
Sign in Pricing Blog Support Search GitHub This repository Watch 501 Star 6,155 Fork 2,278 elastic/kibana Code Issues 1,163 Pull requests 68 Projects 0 Wiki Pulse Graphs New issue Connection Failed error #6408 Closed thesrinivas opened this Issue Mar 3, 2016 · 1 comment Projects None yet Labels None yet Milestone No milestone Assignees No one assigned 2 participants thesrinivas commented Mar 3, 2016 Kibana (3.1.2) shows the following error. I've tried different setting for http.cors.allow-origin (including "/*/" ) https://community.sprint.com/baw/message/767645 and it doesnt help. I'm restarting elasticsearch after each change of the the elasticsearch.yml. Is there anything else I could try? Trying this on my boot2docker VM on my Mac. Connection Failed Possibility #1: Your elasticsearch server is down or unreachable This can be caused by a network outage, or a failure of the Elasticsearch process. If you have https://github.com/elastic/kibana/issues/6408 recently run a query that required a terms facet to be executed it is possible the process has run out of memory and stopped. Be sure to check your Elasticsearch logs for any sign of memory pressure. Possibility #2: You are running Elasticsearch 1.4 or higher Elasticsearch 1.4 ships with a security setting that prevents Kibana from connecting. You will need to set the following in your elasticsearch.yml: http.cors.enabled: true http.cors.allow-origin to the correct protocol, hostname, and port (if not 80) that your access Kibana from. Note that if you are running Kibana in a sub-url, you should exclude the sub-url path and only include the protocol, hostname and port. For example, http://mycompany.com:8080, not http://mycompany.com:8080/kibana. Click back, or the home button, when you have resolved the connection issue rashidkpc commented Mar 4, 2016 Kibana 3 is EOL, but you can join us http://discuss.elastic.co for help. Try taking docker out of the equation and see if it helps. rashidkpc closed this Mar 4, 2016 Sign up for free to join this conversation on GitHub. Alread
& Support Business Continuity Printable Docs Report Definitions Submit Your Software Featured Items IssuesBug Tracker Feature Requests Customer Support Roadmap TranslateTranslation Portal Translation Forum xTupleAbout Us Solutions Products Partners QA Blog / News Customers Contact Us https://www.xtuple.org/xtincident/view/bugs/6408 Home User login Username: * Password: * Create new account Request new password Get Updates Subscribe for training / product announcements, software updates and specials. xTuple News Collective Brainpower Blog Issue Tracker Bug Reports Feature Requests Customer Support Bug Tracker Incident #6408 Back To Incident List SummaryProjectINCDT-xTupleERPIncident CategoryBugsIncident Number6408VisibilitypublicProduct Version2.3.0Fixed In Version2.3.1RC1SummaryMiscChargedoesnotthrowerrorOnInvoicesDescriptionI found this connection error bug when trying to figure out the freight bug. I accidental enter Misc Charge of 1,000,000.00 instead of the freight line. OOPS I saved the invoice with the misc charge with no account setup no error was thrown telling what the problem would be. I then posted the invoice which throws an error GL Account Null or -1 and rolls back the connection error 6 transaction. We have no idea from this error what causing the problem during posting the invoice DetailsReporterzzzzzCRM AccountxTincident Default AccountStatusClosedAssignedjrogelstadPriorityNormalSeverityMinorUpdated03-04-11 08:25ResolutionFixed CommentsDateUsernameComment03/04/11 08:25mfgadminI found this bug when trying to figure out the freight bug. I accidental enter Misc Charge of 1,000,000.00 instead of the freight line. OOPS I saved the invoice with the misc charge with no account setup no error was thrown telling what the problem would be. I then posted the invoice which throws an error GL Account Null or -1 and rolls back the transaction. We have no idea from this error what causing the problem during posting the invoice 02/25/08 08:13srikanthRetested, Issue Found Fixed. 02/15/08 12:22svnRevision: 1454 http://postbooks.svn.sourceforge.net/postbooks/?rev=1454&view=rev Author: jrogelstad Date: 2008-02-15 08:12:51 -0800 (Fri, 15 Feb 2008) Log Message: ----------- issue #6408: Invoice must have an account specified if there is a misc. charge. Modified Paths: -------------- xtuple/trunk/guiclient/invoice.cpp CharacteristicsOperating SystemCopyright AssignedYesDoc FlagFalse FilesNo Files Related DocumentsTypeNumberDescriptionRelationshipRemoveProjectXTUPLEAPPSPorted From Mantisx SubscribersYou do not have permission to view subscribers. No history available