ERROR! Could not generate Meteor bundle #21
Comments
|
Have you configured your application settings on Azure? |
|
This is the bare minimum, yeah?
|
|
App structure is...
|
|
Your values for "METEOR_AZURE_NODE_VERSION" and "METEOR_AZURE_NPM_VERSION" should reflect what is bundled with your current Meteor release (as per docs). The easiest way to confirm this is by running |
|
Hmm... that's a good spot. I've updated the values to 4.6.2 and 3.10.9 respectively but I still get the same error. |
|
Further digging... I've output the path it's looking for which is If I go into the Azure console a cd to |
|
Can you try rebuilding the app (without changing any configuration) then paste the full deployment log here when it's done. |
|
I'm not sure which command you meant exactly for "rebuilding the app". From what I can tell I simply deploy my unbuilt meteor app with the config files and deployment script to Azure and it builds from there. I attempted to deploy onto another App Service and have the same result. I found that I forgot to mention that previously the script times out when downloading Meteor. Perhaps that is the cause? Regardless here is the full deployment log from start to finish including the timeout. Error here 👆🏻Then continue 👇🏻 |
|
Deploying your example app it at least builds but still errors during the deployment... It also hangs during the meteor install. 🤔 |
|
Further digging... it seems like Meteor isn't installing fully. It seems like Azure is timing out before Meteor finishes installing. I'm currently letting Meteor install manually and it's taking nearly an hour, so it's no wonder this script is failing. Will update when I know how this goes. |
|
So I've updated the tar command from So that gets me a bit further along where now it's just stuck on I've tried to leave it running but it doesn't seem to be doing anything as far as I can tell. |
|
I let it run while I was out (for about 4 hours so not sure how long the script took) and I have a deployed Meteor site! I'm struggling to understand why I'm the first person to have this problem with the script. It seems to work flawlessly for everyone else. 🤔 |
|
I am having the same issue. How do you force Meteor to install again on Azure? When I try to deploy it just goes straight to building app after installing NPM dependencies. Here's my output when i |
|
@matfantinel you'll need to at least delete the meteor.bat file at |
|
@mattdell thank you, I have changed the I'm not sure if I should try starting over or wait. :/ |
|
I let it continue, and after 2 hours it stopped with this error: I'm posting on this thread since the root issue appears to be the same. |
|
Another update: I tried installing Meteor again, and it succeeded this time. Then, it started the
Apparently the file is read-only, since I cannot edit it with Kudu either. I guess something that went wrong with the deploy earlier has made this file stay read-only? |
|
So I was able to solve it by deleting the home/site/repository folder and deploying it again. Now my website is working! The issues appear to be all related with timeouts. |
|
That's good to hear @matfantinel ! Glad you got it working. Is it just us who are experiencing problems? |
|
Apparently yes. There is a possibility that the problem may be with the Meteor package or with Azure itself when deploying, maybe some recent update. Sadly I don't know much to help. |
|
Hey guys, sorry for not jumping in earlier. There are a lot of separate points raised here (many of which need to be addressed with better documentation). I've got a lot on my plate at the moment, but I should be able to review this properly early next week. |
|
No problems mate, I wanna thank you for maintaining this project. Saved me from a big headache. Let me know if I can give you any info to help when you look into this issue. |
|
@mattdell Thanks! Also i did a complete resetup of the app service. |
|
I am trying this to see if it helps with the issue I opened. Going on 3.5 hours for deployment and I will update whether this worked or not |
|
Sorry to say, but despite my 1 success I haven't been able to replicate it again. My solution has now become to use demeteorizer as suggested by MSDN: https://blogs.msdn.microsoft.com/azureossds/2016/08/24/meteor-1-4-on-azure-app-services/ This consistently works for me. |
|
@mattdell do you need to delete .demeteorized/ everytime you build with that tool? I think I am going to switch to this too for now. |
|
@jkd65 I just have it as part of my I suppose a better approach is to have it as part of a deployment script which then deletes it after deployment. |
|
Having similar issues, Here is my deployment log Command: bash .config/azure/deploy.sh Can someone help? |
|
@varunkumar17 I ended up switching to demeteorizer as I could not get this issue figured out |
|
@jkd65 @varunkumar17 We're aiming to release v2 this week, which is rewritten as a CLI tool to support local bundling and automatic configuration (as well as addressing pain points like slow initial builds and tracking deployments without opening Kudu). If you're eager to try this out before the official release, we have some tentative instructions in issue #28. We're only working on documentation at this point, so all functionality should be stable/production-ready. |
|
Closing this as v2 has now been officially released. See full announcement here. Please open a new thread for any further issues/questions. |
Script version (listed in .config/azure/deploy.sh)
1.4.5
Deployment log
I'm getting this when I run the script. It seems to be failing in build.sh around here...
Presumably it can't find that package.json file. Any ideas?
The text was updated successfully, but these errors were encountered: