Tensorboard on Windows: 404 _traceDataUrl error - tensorboard

On Windows when I execute:
c:\python35\scripts\tensorboard --logdir=C:\Users\Kevin\Documents\dev\Deadpool\Tensorflow-SegNet\logs
and I web browse to http://localhost:6006 the first time I am redirected to http://localhost:6006/[[_traceDataUrl]] and I get the command prompt messages:
W0913 14:32:25.401402 Reloader tf_logging.py:86] Found more than one graph event per run, or there was a metagraph containing a graph_def, as well as one or more graph events. Overwriting the graph with the newest event.
W0913 14:32:25.417002 Reloader tf_logging.py:86] Found more than one metagraph event per run. Overwriting the metagraph with the newest event.
W0913 14:32:36.446222 Thread-2 application.py:241] path /[[_traceDataUrl]] not found, sending 404
When I try http://localhost:6006 again, TensorBoard takes a long time presents the 404 message again but this time displays a blank web page.
Logs directory:
checkpoint
events.out.tfevents.1504911606.LTIIP82
events.out.tfevents.1504912739.LTIIP82
model.ckpt-194000.data-00000-of-00001
model.ckpt-194000.index
model.ckpt-194000.meta
Why am I getting redirected and 404ed?

i'am having the exact same error. Maybe it is because of this issue. So try to Change the env-variable to --logdir=foo:C:\Users\Kevin\Documents\dev\Deadpool\Tensorflow-SegNet\logs.
Hope it helps.

Could it be that you try to access the webpage with IE? Apparently IE is not supported by Tensorboard yet(https://github.com/tensorflow/tensorflow/issues/9372). Maybe use another Browser.

I encountered the same error before, and found that it was due to internet setting problem.
On Internet Explorer, Go to Tools -> Internet Options -> Connections, click LAN settings, and then click Automatic detect settings.

Related

Google Cloud Dataprep: Transformation engine unavailable due to prior crash (exit code: -1)

I am trying to create a flow using Google Cloud Dataprep. The flow takes a data set from Big Query which contains app events data from Firebase Analytics to flatten event parameters for easier analysis. I keep getting the following error before even being able to create the first step (recipe):
Transformation engine unavailable due to prior crash (exit code: -1)
See top right corner in the screenshot below
Screenshot
The error message you received is particularly challenging in that it
is so generic. The root cause could be within the platform, or it
could be in whatever execution environment you used for the job.
Unfortunately, we don't have the resources right now to capture and
document all of the error messages that can be emitted during the job
execution process, which can span a wide variety of servers and other
software platforms.
I encountered the same problem. First I tried following steps:
Refresh the browser (i.e., click the Reload button top left)
"Hard refresh" the browser (i.e., ctrl + Reload)
Clear cache + cookies (i.e., https://support.google.com/accounts/answer/9098093?co=GENIE.Platform=Desktop&hl=en&visit_id=636802035537591679-2642248633&rd=1)
References:
https://community.trifacta.com/s/question/0D51L00005dG3MXSA0/i-was-working-on-a-recipe-and-i-received-the-error-message-transformation-engine-unavailable-due-x-to-prior-crash-exit-code-1-why-am-i-getting-this-error
https://community.trifacta.com/s/question/0D51L00005choIbSAI/unable-to-develop-on-our-trifacta-42-platform-for-the-past-12-hours-steps-added-to-recipes-are-lost-and-having-to-recode-the-error-given-is-transformation-engine-unavailable-what-is-causing-this-error
However this did not solve the problem. Then I tried:
Confirm that your Chrome version is 68+. If not, please upgrade.
Navigate to chrome://nacl/ and ensure that PNaCl is enabled.
Navigate to chrome://components/ and ensure that the PNaCl Version is not 0.0.0.0. Click on Check for Updates
Did not solve the problem either.
References:
https://community.trifacta.com/s/question/0D51L00005dDrcmSAC/not-able-to-preview-data-sources-or-edit-recipes
I got the info from Trifacta, that there has been an internal issue after maintenance. So if non of the above solutions work, you just have to wait and see when they fix the problem.

AWS Lambda Edit Code Inline shows "Loading your function..." continuously

Edit Code Inline shows "Loading your function..." continuously and never actually loads the function.
And since function does not load, you obviously can not edit it.
I think there was some kind of update today (Nov 30, 2017) to Lambda because when you click on a function to edit it, there is a new section at the top that shows CONFIGURATION and says ADD TRIGGER which was not there yesterday.
And when you scroll down to the Function Code section, it just says "Loading your function..." and never does anything else.
Anybody else seeing this odd behavior?
EDIT: Using Firefox 57 on Windows 10. I get the following warnings/errors when I check Firefox console:
WARNINGS:
window.controllers/Controllers is deprecated. Do not use it for UA detection. ace.js:1:18479
Use of getPreventDefault() is deprecated. Use defaultPrevented instead. globalnav-fe3b9e5995ba8d342d395cb57493ce54ac2b40bb.gz.js:2:39229
window.controllers/Controllers is deprecated. Do not use it for UA detection. environment-default.js:5987
The ‘content’ attribute of Window objects is deprecated. Please use ‘window.top’ instead. home
ERRORS:
Unhandled promise rejection
DOMException { }
polyfill.js:4326:11
onUnhandled/https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:4326:11
[90]https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:1786:27
onUnhandled/<
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:4320:16
[46]https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:993:25
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:2154:7
run
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:2140:5
listener
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:2144:3
Unhandled promise rejection
DOMException { }
polyfill.js:4326:11
onUnhandled/https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:4326:11
[90]https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:1786:27
onUnhandled/<
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:4320:16
[46]https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:993:25
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:2154:7
run
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:2140:5
listener
https://d3ifj4k507k5fs.cloudfront.net/ide-164cb54be56918ce7c55af08ee13c6339e8ebc5c/polyfill.js:2144:3
I was facing the same issue on Chrome 63.
What worked for me:
Right Click on the "Loading your function..."
Click on Reload Frame.
It should load the IDE.
What browser do you use? Chrome 62 and Firefox 57 fail at inline editing lambdas and both throw DOMExceptions, but Safari 11 seems to work. Try Safari(or some other browser) for editing while waiting for Amazon to fix this.
This is happening in chrome as chrome is disabling the use of cookies from cloudfront domain.
Go to address bar and there you would see a icon that says there are some cookies blocked on this website.
Click on it.
Click on manage.
Click on Blocked.
Click on allow to couldfront domain.
Reload page.
I have tried it and it's working for me.
Edit: This could also be tried on other browsers that are facing this issue.
This happened to me using the 64-bit version of Google Chrome 75.0.3770.142 on Windows 10 circa July 31st 2019. To resolve, I trashed all browser data e.g., cookies, etc. Steps to remove that data can be found here.
Things that did not work for me...
Refresh frame.
Refresh tab.
Close and re-open browser.
Restart computer.
Cry quietly to myself and question my decisions in life.
The Lambda editor in the console is AWS Cloud9, which needs some stuff (e.g., cookies) that is spelled out here.
None of these worked for me.
Try clearing all aws cookies. That did work.
I found that it was FireFox's content blocking causing the problem - click the shield next to "HTTPS Secure" lock on the left hand end of the address bar and click "Turn off blocking for this site".
Request to access cookie or storage on “https://….cloudfront.net/ide-…/modules/#c9/ide/plugins/c9.ide.language.core/worker.js” was blocked because we are blocking all third-party storage access requests and content blocking is enabled.home
Blocking on (editor not working):
Blocking off (editor not working):
Try using a different browser. Worked for me.

Coldfusion Builder check for updates not working

Running CF builder 3, Help > Check for Updates throws an error -- "Unable to read repository at http://ahtik.com/eclipse-update/content.xml.
peer not authenticated". Not sure why it's looking there, but I pasted the url in browser and indeed got a 404 error. Is there a way to change where CFB looks for this update check?
Okay, I was getting the "No repository found at file:/Y:/.." message because the path was listed under window > preferences > Install/Update > Available Software Sites. Y was a network drive that we disabled, but beyond that, it looks like my CFB was incorrectly configured for updates anyway. I spent some time trying to add in the standalone patch at the top of https://helpx.adobe.com/coldfusion/kb/coldfusion-builder-3-updates.html, but kept getting error messages. I inherited this copy of CFB a year ago, so I just did a clean reinstall. After that did Help > Check for Updates, it found and installed an update, restarted CFB, and now everything's good.

One or more services have started or stopped unexpectedly SPTimerService (SPTimerV4)

I have stop and restart services(Sharepoint Administration & Sharepoint Timer Service)
I cleaned the Configuration Cache by using mentioned steps.
Summary of the steps to clear the timer job:
Stop SharePoint Timer service on all servers in the farm.
Browse to C:\ProgramData\Microsoft\SharePoint\Config{GUID} where the {GUID} folder contains a bunch of XML files and NOT the files with a “.PERSITEDFILE” extension.
Delete all the XML files
Update the contents of the Cache.ini file to just say “1” (without quotes).
Restart the SharePoint Timer service on each server
Reanalyze the issue in Health Analyzer
Does anyone know why this keeps occurring and how I can stop it?
First of all try and check your ULS Logs and see if there is any error that arise.
Secondly try and maybe check the event viewer on your SharePoint server to see if any errors are shown and make sure you have enough disk space available.
and also you might want to check this :Clearing Timer Services
Let me know if you see any error post it here.
hope it helps.
Yotam.

sitecore session time-out or server failure on publish or browse for package to install

I am at my wits end on this and can't figure this out. In sitecore v6.2 something has changed that is causing an error message as follows
"The operation could not be completed. Your session may have been lost due to a time-out or server failure".
looks like this is coming from Sitecore.Web.UI.Sheer.ClientPage?
The request info:
https://sitecore.test.domain.com/sitecore/shell/sitecore/content/Applications/Content%20Editor.aspx?ic=People%2f16x16%2fcubes_blue.png
the response:
{"commands":[{"command":"Alert","value":"The operation could not be completed.\n\nYour session may have been lost\ndue to a time-out or a server failure.\n\nTry again."}]}
At first, I assumed it was because plugged in some new HttpModules so I moved them into the sitecore pipeline model and the problem kept persisting. I removed them from the entire application and the problem kept persisting.
A google search on the error gets me to some information on the keepalive.aspx stuff, but addressing that has no bearing.
I decompiled the code with reflector, but can't find anywhere this particular error is raised. It must be in sitecore.nexus or something.
According to my superiors we will open a ticket once we get the build resolved, but here's to hoping someone here has some suggestions.
The constant for this error message is THE_OPERATION_COULD_NOT_BE_COMPLETED_YOUR_SESSION_MAY_HAVE_BEEN_LOSTDUE_TO_A_TIMEOUT_OR_A_SERVER_FAILURE_PLEASE_TRY_AGAIN
This might happened if you server restarts while some dialog opened