Three weeks ago my Meteor projects worked fine, but today I noticed that all my Meteor projects skip the 'start-MongoDB' step, or at least it seems that way. All my projects that rely on one or more collections now get stuck on the 'starting your app' step, while new projects start normally (probably because no MongoDB doesn't cause problems for them). Note: I'm having these problems while running applications locally on my laptop.
Most posts that I can find about apps freezing on 'starting your app' mention that the app can't connect MongoDB, which relates to my case, because it is never started, but I don't know how to tell Meteor it should start up MongoDB first before running any of my apps.
Any tips on this matter?
Have you set the environment variable MONGO_URL? If so, meteor (aka meteor run) will not start MongoDB.
Thx for the tips guys, I fixed it, but the root of the problem was kind of far-fetched. The METEOR_LOG=debug option, as suggested by #aedm, helped me figure out what was wrong though.
One of my older applications posted the error message Meteor 1.2.0.2 - Couldn't run tasklist.exe on Windows 10, and when searching on that error message someone suggested that something might be wrong with my environment variables. Apparently when installing some new software a couple of days ago I created a new 'path' variable, rather than editing the old one, which overwrote the original 'path' variable, which included something essential for Meteor. I deleted the new 'path' variable, and added its contents to the old one, and now everything works and Mongo starts as it should when I run my apps.
Related
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'm having a hard time using eclipse because of the following issue.
It goes like this. I'll code and try to run it. Then, it will throw some errors (of any kind). And so, after I have changed a part of the code, comment out which codes I suspect makes the error, or delete something, I then restart the websphere application server in order to republish my work. Next is to test my work using SoapUI then all of a sudden eclipse throws an error which is the same as before. I've tried to search in here answers to this questions but it involves codes which don't need in my project and also answers that I can't understand well (since I am very new to programming). However, I have found a way to resolve this but it's very inconvenient. To be able for eclipse to detect changes in the src folder, I should restart eclipse after editing my codes then remove my project in the server, start the server and then publish my work in websphere all over again. It solves my problem but I do all of these stuff every now and then even if I only comment out a single line in the code. What I want is to avoid doing this process of resolving the issue since it consumes so much of my time whenever I republish the project in the server.
Can somebody help me with this? Any suggestions would be very helpful. Thanks a lot!
It is a bit strange that you need to restart eclipse. The normal way would be to just re run your application server.
Try only he 3 second steps you mentioned (remove my project in the server, start the server and then publish my work in websphere) and if that works try again without removing the project. Just restart the servers.
And let us know if that worked!
I have started installing mongoDB, got struck like anything.
I can understand the mongoDB is not running even though it shows like mongo auto and a log file. I have deleted almost all the folders and i ran almost all the commands i have seen on net.
I need the commands which removes the mongodb completely from my system.I cannot understand what's happening with the mongodb.
Finally I have decided to remove it completely(not even a single instance of mongo).
provide me the best commands which might help me.
Perhaps this might help for Mongo 3.0
https://docs.mongodb.org/manual/tutorial/install-mongodb-on-ubuntu/
and for Mongo 2.6
https://docs.mongodb.org/v2.6/tutorial/install-mongodb-on-ubuntu/
At the bottom of the page are instructions to remove all files.
I recently uninstalled, then re-installed WAMP, But now my domains(zend projects) are malfunctioning. I can only access the front pages for these domains but not any further pages, which I explained in a previous thread Everything suggested on the thread and more have not worked so far.
So I have another idea from searching google which suggests that WAMP has not been completely uninstalled when I did the first uninstall, and the solution is to go to regedit after uninstall, do a search for "wamp" then delete all records related to wampserver. I'd done this but I'm getting 216-records and only three of them has a mention of "wamp" on the record names. I feel it can't be right to delete all 216-records and i'm scared because these records point to other programs and systems in windows. But this blog seems to suggest that I delete them all as below:
...into the registry. Highlight 'Computer' and press the [Ctrl][F]
key combination to launch a search box. Type in 'wamp' as a search
term. Delete all instances of a record pertaining to WampServer. On
a healthy installation, there may be 70 such entries or more. Just
grit your teeth and get it done, making sure all the while that the
search result is indeed a WampServer related entry...
I have deleted the 3-records I found with mentions of "wampserver", but yet no solution to my problem. So my question is: Could the instruction possibly be to delete the entire 216-records in order to completely clear my system of all traces of the old WAMP installation?
Removing WampServer should consist of:
stopping and uninstalling the services (wampapache and wampmysql) either with the uninstall services batch file included or on the command line
deleting the wamp folder
Bear in mind any changes to:
Your web root folder(s)
Your hosts files
Your firewall
Now, if you've done the above and have problems still, it'll likely there are other problems. Such things as different httpd configs, .htaccess files, different versions of wampserver and components like PHP and it's modules, databases and their security credentials, etc.
Check the above, and if there are more specific errors feel free to post them too.
Thanks guys for your time. I think my actions as in the OP were successful in completely uninstalling wampserver. Just that my fresh instal of WAMP was mis-behaving and not finding pages beyond the home page. It's been sorted by enabling mod_rewrite. Though I'm not quite sure what went wrong as I'd applied the same mod_rewrite severally without a resolution.
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?