I understand we have multiple post regarding viewpoint is not working on TD Express but didn't find solution on it and also those people have issues in starting the viewpoint using vp-control.sh start command but my issue is different.
I have installed TD Express 16.10 and everything is working perfectly except viewpoint.
I used Viewpoint Start icon to start the viewpoint and it started without any issue,
I also checked the status of viewpoint using vp-control.sh status and all services are running except the viewpoint is Unused
Then I tried to open Viewpoint in firefox provided in the image of TD Express by entering the various options like localhost\c , 127.0.0.1\c , 127.0.0.1:80,etc but Viewpoint did not open,
I tried wget localhost then I could discover that it failed to establish connection,
Can someone guide me or point any issues that I am not able to understand here, As per below post, it looks straight forward but it is not,
https://downloads.teradata.com/database/articles/teradata-express-14-0-for-vmware-user-guide
Related
I've just created a feature for our application which generates a powerpoint report from the data a given user has in our system.
In short, the server spawns an instance of google chrome using Selenium's ChromeDriver, and from there scrapes out the charts from our application running in chrome. It was done this way to ensure the charts in the report look exactly the same as they appear in the clients' browsers.
We use Azure Web Apps to host our development and production environments, and while my reporting feature works fine in local environments, it doesn't work once deployed to any other environments, because it depends on chrome being installed, and I can't get it installed in the Azure Web App sandboxed environment.
(you can see this other question of mine for a bit of a reference to where things are going wrong: PowerShell StartProcess: invalid handle )
SO
What I pretty much want to know is, if an Azure Web App environment isn't going to allow me to install google chrome, where should I look next?
It looks like using Service Fabric may allow me to install what I need appropriately (https://learn.microsoft.com/en-us/azure/app-service/choose-web-site-cloud-service-vm), but it seems like a big change to make just to be able to facilitate this small part of the feature.
Another option is to just re-architect the feature so it doesn't depend on the server spawning an instance of google chrome.. but I'd just prefer to avoid that if there's a straightforward way for me to get what I have working.
Ideally, there'd just be a way to get google chrome installed in the given environment, but I've spent a good 10 hours trying to get that to happen now, and it's not looking promising.
There's a couple of solutions which would work - depending on your code and framework dependencies.
IMO - the simplest way would be to build your code in a docker container (that runs the Selenium ChromeDriver) and deploy it either through the container features on Web Apps or run it on demand through ACI (Azure container instances) and have it create the report and drop it in Azure Storage. In a container you have a lot more options - and you have a great amount of options on how to run it. Spinning up an ACI on-demand to do the job can be done in multiple ways (e.g. from Code or through logic-apps or Powershell/Azure automation).
Here are some links on running containers in your App Service:
https://learn.microsoft.com/en-us/azure/app-service/containers/
https://learn.microsoft.com/en-us/azure/app-service/containers/tutorial-custom-docker-image
You could start off by building and adding your code from this image: https://github.com/SeleniumHQ/docker-selenium
Other alternatives of course - you could have a VM that you can install and do what you want with on-demand - however - it'd add more management overhead and other implications to think about.
Many options - but in the regual Web App Sandbox - you're limited.
I have found myself this problem with chromedriver.exe needing a real Chrome. As I cannot install Chrome in Azure App Service I am trying a portable version of Chrome. When using the chrome webdriver I tell it where to find the chrome binary.
var options = new ChromeOptions();
options.AddArguments("headless"); // any options you need
options.BinaryLocation = "YOUR CHROME BINARY PATH HERE";
var driver = new ChromeDriver("YOUR CHROME DRIVER PATH HERE", options);
You should be able to copy the chrome portable files as no installation is required. Although it is heavy, 250 MB, because it includes the non portable version inside.
Be sure to use a Chrome version compatible with your ChromeDriver as pointed in the documentation
daily motion videos are not playing in my Linux based embedded system.
i am using qt4.8 browser.
server returns forbidden error (http://www.dailymotion.com/stream)
i want to know the reason for this error. please help me
You should rather use http://dailymotion.com/tv , this one works. Your link is the wrong one (old one).
WEIRD HAPPENING.. I am unable to debug meteor app , BREAKPOINTS doesn't work in chrome(can see the server side sources thou).. I have already wasted 2 days over it ..
I have already tried
Meteor: Debug on server side
Also tried similar options changing web-port and other options.
Also tried to reduce the node-inspector version, BUT breakpoints are not working for me..
any suggestions on how to debug this issue?
(Chrome browser, ubuntu, AMD machine, if that matters)
I have the same issue. The only workaround I've found is to put debugger; statements in my code. Those are respected and treated as breakpoints which stop the server for Node Inspector.
you can try observatory or read this article, maybe it'll helps
You are not alone. There is an issue posted to github about this, and it appears to be confirmed by several users.
I was able to get Node Inspector to work a while ago by downgrading to 1.10. It's not as nice as the new version but worked last time I used it. I honestly haven't needed it recently, but hopefully it'll still work.
I need to run R with Node.js, using Rio (https://github.com/albertosantini/node-rio) as the node binding to Rserve.
I like Heroku but this seems like it is pushing the Heroku envelope beyond what it or I am competent with:
I've looked briefly into installing a custom buildpack
https://github.com/virtualstaticvoid/heroku-buildpack-r
to run simultaneously with node.js:
https://github.com/ddollar/heroku-buildpack-multi
This all seems pretty scary. Anyone got any good advice for how best to host this? My app works just fine locally.
http://prgmr.com/xen/
I currently use this solution to run my Node.js server and it's currently great.
They have wonderful support and they're uptime is 100%. I cannot recommend this any higher, but you will need to know how to set up a simple OS and run it from the ground up.
For example, if you want to run a server without having it stop when you close the SSH connection, you would use screen node script.js and press [control] + [A] + [D] keys.
You might already know this, so simply take my advice and view the website.
After some research and recommendations from Heroku, I believe the Heroku solution would be
Use https://github.com/virtualstaticvoid/heroku-buildpack-r
in combination with
https://github.com/ddollar/heroku-buildpack-multi#readme
to build a multi build pack.
I'm using watir-webdriver to navigate around my website and grab screenshots in different browsers.
Sometimes the screenshots taken in IE turn out the right size, but colored entirely black. The firefox tests that get run at the same time look fine.
browser.driver.save_screenshot(screenshot_dir)
Once I remote desktop to the computer running the tests the IE screenshots look okay again. A little bit after leaving remote desktop the IE screenshots go black again.
I'm running these tests on a instance of Windows Server running on ec2.
Based on your comment that remotely accessing the machine resolves the problem for a little while... disable the screensaver on that box. I'm not sure how (if at all) the screenshot functions on IE and FF differ, but it's worth the time it would take to test the change.
Edit: I still feel like it's windows/power setting related as you logging into the box appears to have an effect, but I don't know what else specifically that could be. I tried a programmatic approach below vvv.
From what you are saying, it sounds like the Windows system is automatically locking, like it should. This would explain why screenshots work fine when you remote in, and then go to black several minutes later when the screensaver kicks in and locks your system.
If the Windows system is locked, screenshots are blacked out. This is a Windows security feature.
I would be curious to know if FF really does do screen captures on a locked system.
Here's the code I'm using to capture screenshots (Watir-Webdriver, Cucumber). I use remote Windows XP VMs for my test boxes, and have not encountered the issue using Firefox or Internet Explorer.
We did find that when you view the log with the embedded screenshot, it does not seem to work in IE - so you have to use Firefox for viewing. It's base64, so there doesn't seem to be a logical reason for this.
After do |scenario|
if scenario.failed?
encoded_img = #browser.driver.screenshot_as(:base64)
embed("data:image/png;base64,#{encoded_img}", 'image/png')
end #
end