I'm getting this error in pow, maybe one in 30 or 50 requests:
Error starting application
Your Rack app raised an exception when Pow tried to run it.
Error: Response was not received
at Client._finishRequest (/Users/duarte/Library/Application
Support/Pow/Versions/0.4.0/node_modules/nack/lib/client.js:77:27)
at Client.<anonymous> (/Users/duarte/Library/Application
Support/Pow/Versions/0.4.0/node_modules/nack/lib/client.js:38:21)
at Client.emit (events.js:88:20)
at Array.0 (net.js:335:10)
at EventEmitter._tickCallback (node.js:190:38)
I am using:
rails (3.2.11)
ruby 1.9.3p362 (2012-12-25 revision 38607) [x86_64-darwin12.2.1]
rbenv
Anvil (mac app for managing pow symlinks)
I don't have any custom version of ruby set. I've had this for about a month now. When I get the error I reload a few times and it usually goes away by itself within a minute. Sometimes I just start WEBrick and that works. I tried installing node through homebrew and also npm. I've reinstalled pow a few times, but no luck!
It seems like it's a problem with node or something that has a bad install, but I can't figure out what it might be! This is a new laptop and I've been getting the error from the beginning, ever since I first set everything up.
For anyone having the same problem: this was solved by re-installing gcc and rebuilding ruby.
Related
I run my pytorch code well on mac and even on windows system but the same code seems stuck on CentOS6.3.
I debug with ipdb, and found the code was stuck at F.conv2d function:
> /home/work/anaconda2/envs/PyTorch/lib/python2.7/site-packages/torch/nn/modules/conv.py(301)forward()
300 return F.conv2d(input, self.weight, self.bias, self.stride,
--> 301 self.padding, self.dilation, self.groups)
302
ipdb> s
The running env was created with anaconda(python 2.7/3.6), pytorch version is 0.4.0.
I tried for a long time to resolve this problem and i tried. Do you have a suggestion? Thank you so much!
I reinstall CentOS6.3, and then upgrade glibc2.14, glibc2.17 due to the pytorch0.4.0 running error info.
Now everything is ok.
By the way, the pytorch0.3.1 perform well before i upgrade the glibc(up to 2.12). So i think the lastest pytorch0.4.0 may haven’t deal very well with glibc, leave running deadlock appearance and doesn’t tell any error and warning info, just stuck at F.conv2d in torch/nn/modules/conv.py(301).
See also: https://discuss.pytorch.org/t/f-conv2d-stuck-on-my-centos/19794/3
I have been having an issue with application packages where there will be days/times where I just get a null exit code and BlobAccessDenied Error for the exact same application package and exact same command line that previously worked and gave a non-null exit code. For instance, today, I've been getting this error for the exact same packages and commands that I ran yesterday. What am I missing? Or is this a bug in the application packages service? (for VM configuration)
Update:
This fix is been released and deployed, this error will no longer exist for the specified case.
Also something I wrote in an hour jsut to test and might come handy apart from good dotnet samples :
https://github.com/Tatsinnit/quick_sample_batchapppkgworking
https://github.com/Azure/azure-batch-samples
Thanks j.B. & Jan
I created a solution with a few applications, and it worked perfectly. But a day later when I was about to debug the solution again, it suddenly cannot start.
I did have firewall and AV disabled, both when it worked and later when it didn't work.
It works fine when deployed to azure, but not locally.
The error thrown is:
Exception from HRESULT: 0x80071BFF
at System.Fabric.Interop.NativeRuntime.FabricGetNodeContext()
at System.Fabric.FabricRuntime.NativeFabricRuntimeFactory.GetNodeContextHelper()
at System.Fabric.Interop.Utility.WrapNativeSyncInvoke[TResult](Func`1 func, String functionTag, String functionArgs)
A related post register-servicefabricapplicationtype-on-a-secure-cluster-always-times-out
describes a similar thing.
However, I get this while debugging locally and with smallest possible application: I even just created 1 application, 1 actor, did no changes, hit F5 and I get this error.
So, I looked at service-fabric-troubleshoot-local-cluster-setup and while I also get the TypeInitializationException, the solution of:
Your path variable was not correctly set during installation. Please sign out of Windows and sign back in. This will fully refresh your path.
did not work at all.
Nothing else on that page seemed to be related.
Now I begin to feel that I've hit the end of what key words I can google, and still I have no idea what to do.
Any help would be greatly appreciated.
EDIT:
I've tried starting via cluster manager and apps can still not start.
I've removed apps, removed cluster, tried with new solutions, over and over. The only thing I haven't tried is reinstalling SDK and VS. I'm a bit reluctant to reinstall VS, so I'd hope to find some clues before resorting to that.
UPDATE1:
Now I reinstalled Service Fabric v. 5.3.311.9590, SDK and Tools.
Created a solution, added a stateless service. Hit F5. The exact same error is thrown.
I will now try to install on another machine with mostly the same configuration.
UPDATE2:
Installed the SDK on an identical VM, Win10, also with VS2015 Update 3. Created solution, added 1 actor, hit F5 and also on this macchine the exact error is thrown.
I tried Debug without debugging (as mentioned here) to attach later. But the application never starts. It is failed. This is the same on both the machines.
It all worked and from one day to the other it doesn't, and it's a problem that I cannot find anywhere on the net. What can this be? I found that the security updates from windows was made about the same date this happened...
I will uninstall and try again.
UPDATE3:
Uninstalling security update was not possible, but I could hide a couple of other updates. To no luck though.
From here I found this https://github.com/Azure/service-fabric-issues/issues/15 and realised I actually was very low on diskspace, and so I increased it (hyper-v manager) to 20 gigs free. But no, still the same problem.
I've been having problems getting debugging working with this setup for the past year. Supposedly, this is fixed in the latest versions, but I just can't seem to get it to work.
I'm using Mac OSX 10.8.5, Eclipse Keplar, PyDev 3.0.0, and Google App Engine 1.8.8.
I set up a run configuration to point to dev_appserver.py, running my project. That works fine. My python version is 2.7.3, and everything works in normal mode. When I try to run in debug mode, however, the app runs, the output specifically states:
pydev debugger: starting
pydev debugger: google app engine integration enabled
But after 20 seconds, the python process terminates with this error message:
'Launching New_configuration' has encountered a problem.
Timed out after 20.0 seconds while waiting for python script to connect.
Accept timed out
Execution works during those 20 seconds, because I can hit URLs connected to my app and see an effect. Breakpoints do not work, though. Is there something I need to do to get python to 'connect'?
Also - I should note that switching back to using 'old_dev_appserver.py' fixes this problem - debugging works fine when I do this. But, this is not really a solution, because I need to use the latest socket additions in the newer releases.
Thanks for any advice.
temporary solution:
edit the pydev_app_engine_debug_startup.py file:
eclipse/plugins/org.python.pydev_${VERSION}/pysrc/pydev_app_engine_debug_startup.py
change the line that reads:
if ':' not in config.version_id:
to:
if ':' not in config.version_id or config.version_id.startswith('default:'):
Looks like this is fixed in 1.9.0. I also had to make sure to update PyDev to the latest (3.3.3 at the time of this writing).
One more thing to add, and this one really tripped me up (on MacOS) -
In Eclipse, under Run -> Run Configurations, set the Main Module to point to this location:
/usr/local/google_appengine/dev_appserver.py
NOT the symlink:
/usr/local/bin/dev_appserver.py
Well, finally I found the answer. It is a Google's bug.
It has been reported and acknowledged.
see Debug is not working with PyDev again 1.8.8!
Update: Until the bug is fixed I am using PyCharm. The pro version has 30 days trial and works with GAE. It works like, well, a charm. I may even consider switching to it from Elicpse/PyDev
But I am used to JetBrains tools with Android Studio recnetly, and WebStorm and Resharper in the past, so I know to find my way around their IDEs. Your milage may and will vary.
Since the question, a new GAE has been released 1.8.9
Running GAE 1.8.9 with PyDev3.3.3 on Windows8.
This timeout issue still occurred.
When I entered the temporary workaround changes to pydev_app_engine_debug_startup described in the earlier answer, then the browser could not connect to the app.
However, on backing out this change, not only did the 'Launching New_configuration' not appear, but the breakpoints worked.
More info on the Python Tool Support for the App Engine Development Server is here
https://docs.google.com/document/d/1CCSaRiIWCLgbD3OwmuKsRoHHDfBffbROWyVWWL0ZXN4/edit
I have a small Sinatra app I'm running on a shared hosting account using Passenger. However, the first time the app is accessed after a while, I get a Passenger error page saying the application could not be started. Usually because Sinatra could not be found.
I am assuming this is just a normal delay from when a new instance is spawned. However, is there a way to delay trying to load Siantra until it Passenger has fully loaded?
I seem to have solved the issue by setting the GEMS_PATH environment variable in the .htaccess file. I haven't encountered the error again. YET!
I took this up with Dreamhost support recently (not a great experience) and eventually they recommended freezing the gems into the application. This is at best a partial solution, because it seems to work for some gems and not for others.
Instead of
require 'sinatra'
I have:
require 'vendor/gems/sinatra-0.9.4/lib/sinatra'
Freezing gems is covered elsewhere, but briefly: to prepare for this, one needs to do
mkdir vendor/gems
cd vendor/gems
gem unpack sinatra
As a result of this change, I never get the startup failure screen quoting sinatra as the file it can't load. However, I still get it for some other gems which require themselves or parts of other gems. Not too clear about the details, but I'm working on the idea of hacking the installed gems to make every "require" use a path directly out of my "vendor" library.
I think you may need to add Gem.clear_paths! in there
I had a similar problem a long time ago. Updating to a newer Sinatra gem helped me - what version are you running?