I get different error messages every time I try to deploy my ~700MB angular app to firebase hosting with firebase-tools.
It progresses something between 10-30% and comes up randomly with different errors like:
Deploy Error - Storage error
Deploy Error - Request timed out
Deploy Error - Socket hang up
I've got node 0.10+, tried with two machines (both Windows 7, using cmder shell). Tried both "firebase init" to an existing directory and "firebase bootstrap" to an empty one and copied my files over but issues persist.
I've also made sure there are no href or src attributes with expressions in them as some other guy had issues with those.
Am I doing something wrong and is there some more enlightening log-file to read to understand what actually fails?
Related
I have created a standalone unsecured one node cluster.I am trying to do package deployment from powershell.
What i have done so far:
In package, in Deploy-FabricApplication.ps1
i replaced service fabric sdk reference and included ps1 files needed to deply inside my package itself.
I dot sourced those files in Deploy-FabricApplication.ps1 like this
. F:\pkg\Debug\Scripts\New-ServiceFabricApplicationPackage.ps1
. F:\pkg\Debug\Scripts\Utilities.ps1
. F:\pkg\Debug\Scripts\Publish-NewServiceFabricApplication.ps1
4.Now when i run .\Deploy-FabricApplicatin.ps1 from powershell like this
.\Deploy-FabricApplication.ps1 -ApplicationPackagePath 'F:\pkg\Debug' -PublishProfileFile 'f:\pkg\Debug\PublishProfiles\Cloud.xml'
Now I am getting this error
The error message screen shot
I tried opening ports but still im getting this error. The error vanishes and im able to deploy after two or three tries...but everytime when i deploy for the first few times after standalone cluster creation. Why is this error is happening and how do i rectify it.
Thankyou
I would recommend you to double check the ports as mentioned in this and this threads.
We have been running a service using NestJS and TypeORM on fully managed CloudRun without issues for several months. Yesterday PM we started getting Improper path /cloudsql/{SQL_CONNECTION_NAME} to connect to Postgres Cloud SQL instance "{SQL_CONNECTION_NAME}" errors in our logs.
We didn't make any server/SQL changes around this timestamp. Currently there is no impact to the service so we are not sure if this is a serious issue.
This error is not from our code, and our third party modules shouldn't know if we use Cloud SQL, so I have no idea where this errors come from.
My assumption is Cloud SQL Proxy or any SQL client used in Cloud Run is making this error. We use --add-cloudsql-instances flag when deploying with "gcloud run deploy" CLI command.
Link to the issue here
This log was recently added in the Cloud Run data path to provide more context for debugging CloudSQL connectivity issues. However, the original logic was overly aggressive, emitting this message even for properly working CloudSQL connections. Your application is working correctly and should not receive this warning.
Thank you for reporting this issue. The fix is ready and should roll out soon. You should not see this message anymore after the fix is out.
I had deployed my application on the google cloud successfully, tested it and it is running fine.
Now I wanted to push some changes to the code so I tried to push my revised code and used the command: gcloud app deploy to deploy my updated codebase. However I am getting the following error:
Updating service [default] (this may take several minutes)...failed.
ERROR: (gcloud.app.deploy) Operation
[apps/*******/*******/d756b4f7-d9a8-48c8-b6dc-1d87889a18bf] timed out.
This operation may still be underway.
Earlier I was getting the error health check timeout, so I increased the accepted time out time to be max, 3600 after which I am getting the above mentioned error.
I posted on friday regarding this issue and received no response, however since then some updates have occurred which might affect whether people have an answer to my question or not.
I'm trying to deploy an MVC website to Azure, and in this particular project the web deploy receives a Socket Error 10054 and gives up after 10 attempts saying it was Unable to write data to the transport connection. It makes varying progress in between the socket failures but never completes within the 10 attempts.
I have since had a play around with other projects which are deployed to different url locations within this same Azure Account and they deploy fine! I think this means the problem is not on my end, i.e. port 8172 is open and deployment can be achieved with my current local settings.
What are the problems that can cause this socket error 10054? I saw somewhere that I should enable the "Allow untrusted certificate" option when deploying but I can't find that option within VS 2013.
Any ideas are welcome please,
This issue is driving me mad, it seems there's a real mixed bag of solution ideas which have worked for others but not me.
JK
Last week I got to know node-red (what a potential!), and after installing it on a Raspberry Pi B+ and following the basic tutorials, I'm experiencing some issues.
When I follow the Inject + Debug node example, wire them, and deploy them, I get the message "Deploy sucessfull". So far so good. I'm running it locally on http:// localhost:1880.
Then when I click the Inject node or the Debug node, it says: "Error: Inject node not deployed" or "Error: Debug node not deployed".
Anyone know how to fix this error? Is it a server problem?
Was having the same issues and discovered the flow that I was working on was disabled.
You can tell the flow is disabled when the lettering on its tab is in italic and there is a circle with a diagonal line through it ahead of the lettering.
Double click the flow tab and change "status" to "enabled".
Just tried something and it worked:
When you run node --max-old-space-size=128 red.js, the command line shows you "cannot find flows_raspberrypi.json"
So I
1) created a flow (as in the examples) 2) Exported it as
"flows_raspberrypi.json" 3) Stopped node-red 4) Started it again
Bingo! It picked this flow up, which then "sucessfully injected".
Now just create your own flows...
I was also getting same problem of :- Node-red Error: inject node not deployed.
When I have install dashboard on Node-Red which was not working, and started giving error when I hit inject node.
So I manually deleted the files (flows-raspberrypi.json, package.json, settings.js) and also folders (lib, node_modules) from the path /home/pi/.node-red
I used vnc-viewer to delete manually files & folders. Just login to vnc-Viewer and open the file manager and paste the path "/home/pi/.node-red" & delete all the files. Reboot the Raspberry-Pi and start Node-Red, it will function normally, even after installing dashboard it is working.
NOTE:It will delete all your flows and install nodes from Node-Red. So keep backup of your flows.