I have my influxdb working in server. When I try to open the influxdb UI using http://my_host:8086. I'm receiving 404 as response. What am I missing ? help me with this please.
In version 1.3, the web admin interface is no longer available in InfluxDB. The interface does not run on port 8083 and InfluxDB ignores the [admin] section in the configuration file if that section is present. Chronograf replaces the web admin interface with improved tooling for querying data, writing data, and database management. See Chronograf’s transition guide for more information.
enter link description here
Related
I have SAP BTP trial account in which Im trying to run a SAPUI5 application via the SAP Business Application Studio (BAS). I have added nothing fancy to it. Just created one from the one of the many UI5 templates and tried running it from the terminal via the command ui5 serve.
The command does execute without any problems and also provides me with the standard localhost:8080 URL. Im using Firefox since BAS doesn't seem to work with Edge as well as Chrome.
I even get a message popping on the right bottom corner telling me a service is listening to port 8080 with a button that says "open in New Tab" pressing it however does nothing.
Im new to SAP BTP and BAS. Are there more things to configure before running the application? Or perhaps I have to configurate the browser itself? The error message:
I have also had some experience with the Business Application Studio.
You don't work locally here like in VS Code, for example. That's why you can't access it via localhost:8080, but have to use the link that provides the BAS. In this case, something like
port8080-workspaces-....applicationstudio.cloud.sap.
The best thing you can do is to press "Open in new tab" on the screenshot with "A service is listening to port 8080", then you will be redirected to the working link.
Kind regards
Sebastian
I wrote microservices using spring boot. some time showing its active in status and sometimes showing inactive, I can't understand the behaviour of microservice and how can debug it
Have you tested running the microservice locally?
I've been getting inconsistent reports from the status tab in the UI. Sometimes it says the service is down when it's actually up. I check the /health endpoint to be sure(it's not available right after you upload the zip, takes 5-6 minutes).
The logs in the UI are a bit clunky, so I've added a rolling file appender to logback.xml and a rest endpoint to expose the log file for debugging.
Try to override health check timeout value (timeoutSeconds property of Probe). By default it's 1 second and it's often not enough. Please refer our specification: https://cumulocity.com/guides/reference/microservice-manifest/
In the administration application you will find the status details for each of your applications.
When the status is switching all the time probably the docker container is terminating all the time (probably because the application is crashing). You should the that on the status tab of the application in the event log (container is restarted all the time).
If you are on the newest Cumulocity version (9.19.x) you should also have access to the logs of the microservice at the same place in UI. You need to log to stdout in order to be able to get the logs through administration application.
I have a Neo4j (CE) running on a linux server with only one port open (the one I use for the https connection). It's very difficult for me to open any other port.
With Neo4j 3.0, it worked like a charm. I've just installed the 3.2, and I can't manage any more to connect to the Neo4j browser. I get the UI, but when I tried ":serve connect", I now get a "Host" field (together with the Username and Password"). I've tried many combinations, and I always get the message "N/A: WebSocket connection failure. Due to security constraints in your web browser, the reason for the failure is not available to this Neo4j Driver. (...)".
By default, the host field is "bolt://[my-server-name]:7687", which is not reachable from my browser (and I see in my browser webdev console that it tries to reach it, and fails).
I tried in the neo4j.conf to set "dbms.connector.bolt.enabled=false", or to check/uncheck the "Use bolt+routing" box in the "browser settings" of the neo4j browser.
Is there any way to use Neo4j 3.2 with only one port open ?
Thanks
It is possible to reach the database itself directly over one (http or https) connection ... however ... if you want to use the Neo4j Browser you currently have no other option than to use the bolt protocol (and that requires an extra port). The browser does currently only connect over bolt. This is an open issue for the Neo4j development team.
Hope this helps,
Tom
The server is running a custom REST endpoint configured using the following line
org.neo4j.server.webadmin.data.uri=/db/abc
in neo4j-server.properties. REST is then working fine using /db/abc, but then the browser client (http://$SERVERHOST:7474/browser) stops working and displays the Disconnected from Neo4j message. Packet sniffing indicates it is still trying to connect to db/data. Clearing local web caches doesn't help. Is there a way to point the browser client to use a custom endpoint?
Sources indicate that /db/data is possibly hardcoded into the browser as part of client "Settings" (see line 23). There is supposedly a way to reconfigure these settings using the :config command in the client, but the command bar is only available when the client is already connected to the server.
Is there a way to get this to work, or is it possibly a bug in the browser client?
Current option is to download source code of the browser and change what you need.
https://github.com/neo4j/neo4j/tree/2.3/community/browser
I had created a web application and committed the code in CVS. The web application is working good in my machine. When i tried to import the same code in another machine i am getting 404 error. I tried importing the code via ftp from my machine to another machine and also checking out the code from CVS. But still i get 404 error.
I also noticed that there is no error that had been captured in the console or in the application's log. Could someone help me in how to proceed further in identifying the issue. Please let me know if i need to post any further details regarding the issue.
I notice this issue to be in the Websphere server. I tried hosting the application in different machine and found that in few machine the same code is working good and some it is not. Is there any way to compare the server configuration?
In the WAS server 6.1 i added the below value in the web container and the application worked fine.
Steps:
In the server admin console, click on Application Server--> --> Web container--> custom properties.
Add the name as com.ibm.ws.webcontainer.invokefilterscompatibility and value as true.
Thank you all for the response.