Currently i am trying to configure tez-ui. I have put the tez ui web server on tomcat and running it as a service. When i am editing the timeline url with ip:8188 instead of localhost in /opt/tomcat/webapps/tez-ui/config/config.js file, it is throwing error Adapter operation failed » Timeline server (ATS) is out of reach. Either it's down, or CORS is not enabled.
I have notice one thing tez ui is requesting the url http://localhost:8188/ws/v1/timeline/TEZ_DAG_ID instead after editing timeline url in config.js it should point http://ip:8188/ws/v1/timeline/TEZ_DAG_ID. Can anyone guide on why it is happening ?
Related
I'm trying to use SignalR in ASP.NET Core 5; I've added SignalR service in service configuration and also created a hub class and its method with Angular, which is also configured as I saw on websites there codes similar but still getting below error please some help me:
Error: Failed to start the connection:
Error: WebSocket failed to connect. The connection could not be found on the server, either the endpoint may not be a SignalR endpoint, the connection ID is not present on the server, or there is a proxy blocking WebSockets. If you have multiple servers check that sticky sessions are enabled.
This Previous question was from me ,Actually from 4 days i was facing issue in signalr Configuration but the error issue Reason was Port Number Incidently i changed My port number from application properties (Debug Properties) but forgot to change the application path in angular signalR configuration which was not showing any cores issue and i was being confused for 4 days. << I changed angular signalR Configuration withUrl path to right path and issue resolved
I am getting the above error message in production when trying to call the AddImageUrl section of ABCPdf (version 10). This started occurring yesterday just after midday my hosting provider assures me nothing has changed I am the only developer on the project as was working on something else entirely.
The URL provided in the stack trace can be accessed in IE on the web server without any error messages (including SSL). There is also a UAT environment on the same web server in which the PDF works, the UAT environment is identical in code and application pool settings, the only difference is the web address and database.
The HTML the PDF is calling can take a little time to come up on first load. Given that data is different I have increased the timeout from 15 seconds to 2 minutes.
I have arranged a reboot to see if that fixes it, but I have run out of things to check.
Edit: I did think of one further check, could I add the image of a page not on the site (https://www.google.co.uk/), doing this resulted in the same error so it appears not to be a blocking issue on the worker process.
—
Edit2: switched to the gecko engine and it is now working.
You can sometimes get this error if the web browser within Abcpdf cant access the URL.
On the webserver add the URLs directly to the local machine hosts file
C:\Windows\System32\drivers\etc\hosts
The entry should look something like this
127.0.0.1 example.com
I am using hadoop 2.7.2 and have configured HTTPS for yarn and job history server web UIs but the UIs are still served as HTTP and not HTTPS.
I have set up key and trust stores and configuring ssl-server.xml and ssl-client.xml. In addition to that, I have put the following properties in mapred-site.xml using ambari:
mapreduce.jobhistory.http.policy=HTTPS_ONLY
mapreduce.jobhistory.webapp.https.address=JHS:19889
mapreduce.jobhistory.webapp.address=JHS:19889
When I access the https url https://JHS:19889, I receive the following error:
SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The above error is because the job history server is listening for http connections and not https.
When I access the same url with http i.e. http://JHS:19889, I can see the job history server web ui. Same thing happens for yarn's resource manager web UI after having made the following configuration:
yarn.http.policy=HTTPS_ONLY
yarn.log.server.url=https://JHS:19889/jobhistory/logs
yarn.resourcemanager.webapp.https.address=RM:8090
yarn.nodemanager.webapp.https.address=0.0.0.0:8090
How can I make the yarn and job history server web UIs make available on HTTPS?
Map Reduce and YARN are part of the Hadoop project so to enable SSL you need to turn on SSL in Hadoop in the core-site.xml.
hadoop.ssl.enabled=true
Then there are some more settings (search for hadoop.ssl) that you might need but that's the main one.
I'm facing some problems with my WAS setup. The HTTPS link is redirecting to an HTTP. I am sure this is not an application issue since I tested the same application on other environments and it is working.
I had copied the virtual host configuration from the environment that is working, but still not getting it to work. I checked the other environments's Web Container Customer Properties and it does not have any.
Any thing that needs to be checked?
Update :
I saw below the virtual host there is a link called "Update global Web server plug-in configuration". Do I need to click this and copy the generated file to all nodes?
When I visit a web site, my browser sends a request to a an HTTP server, such as Apache or IIS. The HTTP server then forwards the request to the appropriate web server, .NET, PHP, Ruby on Rails, etc. This then returns a response to my browser and the page is rendered.
How does this work on a local web page? Say I create a simply hello world in PHP (hello.php) on my windows desktop. I do not have IIS installed, so what is handling the "request"? That is, what is telling my request to be interpreted by php and how is this getting back to my browser? I have tried several google searches, but I suspect my search terms may be too vague.
The question is a bit ambiguous. A PHP file on a disk simply won't be rendered unless it is present within the Document Root configured for the web server.
For example if your file is present within C:\PHP_Scripts, then C:\PHP_Scripts must be configured as a document root for your web server.
For more information on how to setup document roots within Apache HTTP server refer to the below link :
Apache Web server Document Root creation
Having said this, in your case assuming the file (say test.php) is now present under C:\PHP_Scripts and this has been configured to be part of the Document Root of the web server; the following happens when you request http://localhost/test.php:
The web server refers to the document root and searches for the file named test.php.
Since this is a php file, the PHP interpretor kicks in and processes the script.
The results of the processing are rendered back to the user. In some cases, the processing may be a task like submitting the data to a backend and redirecting the user to another page.
Note that Apache HTTPD server must be configured to work with PHP for all the above to be true.
If you can run PHP on local machine, your machine is probably installed with web server with PHP interpreter (either Apache with PHP, XAMPP, MAMP or similar software installed).