I noticed this afternoon that my Bluemix IoT Application was in the 'Unknown' state. When I mined into the app to see what the problem could be, I got the following pop-up:
App staging failed in the buildpack compile phase
I haven't made any changes to my NodeRED flows in months, and if I spin up a new IOT Foundation app, it starts just fine.
Any ideas on what is going on here?
A recent update to the underlying application stack has caused an incompatibility with older versions of the IoTF boilerplate.
The fix is to edit your application's package.json file and remove the 'mqlight' entry under the dependencies section. New instances of the boilerplate already have this entry removed - hence why they work.
Perhaps check the bluemix server status at https://developer.ibm.com/bluemix/support/#status
There were some issues reported around scheduled maintenance. There are also buildpack updates scheduled.
Related
Node-Red dashboard on IBM Cloud stopped working on 24 SEP after it worked properly for some months.
Node-Red Dashboard nodes have been installed initially. The app hasn’t been changed for a while. Couldn’t find any errors in the log so far, not sure what to look for either.
Check what version of NodeJS your application is deployed on.
Most likely the app has restaged at some point and upgraded some of it's components which now require at least NodeJS 8.x.
NodeJS 6.x went EOL around June 2019
If you enable the continuous integration feature in IBM Cloud you should be able to edit the apps package.json and change the engines entry to bump it up to a supported version of NodeJS (I suggest NodeJS v10)
I'm trying to create a build and release to a actors service in Visual Studio Online. I already created build and release to anothers services fabric without problem. But with this specific service I getting the error below:
The BuildLayout of the application in E:\SFabric\SP\SP2DS\Fabric\work\ImageBuilderProxy\AppType\SchedulerServiceAppType is invalid. Config is missing for service SchedulerServicePkg.
The first time the release works fine, but after the first version is released, the others releases I got this error.
The others services are Stateless, I dont know why this problem happens and just with this service that is Stateful.
New Information
I'm trying to change advantages setting and I got successful sometimes.
Even that, I want to know how I do correctly
# Novac - Just noticed a duplicate post on Github addressing this specific issue. More importantly, a member of Azure's Service Fabric Dev team is actively engaged and waiting for your response to his followup questions - ref snip below:
Currently tracked via GitHub issue:https://github.com/Azure/service-fabric-issues/issues/802. Strongly recommend redirecting this conversation to the Github thread/url above.
After upgrade to sdk 2.5.216 and runtime 5.5.216 Test-ServiceFabricApplicationPackage command works only for complete package. In case of partial app upgrade (some Pkg are removed) it results in "Windows PowerShell has stopped working". I have tested on several computers and several apps. to reproduce:
create test app with 2 services and deploy.
change app version and particular service version.
create package and remove Pkg folder from it for the service without modifications.
connect to Service Fabric and test like Test-ServiceFabricApplicationPackage -ApplicationPackagePath "..path" -ImageStoreConnectionString "fabric:ImageStore"
Maybe somebody was able to overcome this issue? or at least has similar behavior so I'm not alone in Universe.
Thanks!
Alex
Take a look at https://github.com/Azure/service-fabric-issues/issues/259
This is a bug in our code. It happens when a compressed package was uploaded and provisioned in the cluster. Testing a new version of the application fails because settings file was not found in the provisioned version.
We fixed the issue and it will become available in one of our next releases.
Meanwhile, you can skip compression or test the version 2 application package without passing in the image store connection string.
Apologies for the inconvenience!
I used to be able to do upgrade, and it suddenly wont work, not to cloud and not locally.
And there is no error message, so I have no clue what to do.
Publishing a new application works fine.
There seems to be something corrupt with the solution, but I have no idea where I should be looking for this.
In a brand new project, publishing and upgrading a stateful service from template, works without problem.
Things I have done:
Cleaned solution.
Rebuilt solution.
Deleted Debug folders in bin and obj folders.
Restarted Visual Studio.
Cleared MEF Component Cache.
Restarted machine.
Restarted cluster.
The brand new project is deployed to same cluster and upgrade it is working, so I have not deleted the cluster to deploy a new one.
There is no error being thrown so enclosing the script in a try catch seems pointless.
What else can I do here, what can I do to try find out what is going wrong, any suggestions?
I found out it might be a bug. It is reported here:
https://github.com/Azure/service-fabric-issues/issues/240
Summary: When deployed with compression, further upgrades require config version bump, even though config has not changed.
It seems to me like the latest code that I submitted to WSO2 App cloud is not deployed. I tried to access the jenkins server (https://jenkins.cloud.wso2.com/t/cleancoders/webapps/jenkins/job/draft-trunk-default/) I see there that the latest code is built(upto build 29) but on the App cloud still build 24 is deployed. It seems to like the jenkins builds are not synced and deployed.
I also tried to build and deploy manually but It seems that it is not having an effect.
Please suggest what should be done in order to deploy the latest build.
Thanks in advance.
This is a kind of problem which you can get when your app is not properly deployed in jenkins. (There may be configuration issues). Please do contact cloud#wso2.com for assistance.