How make flink application on yarn killed or failed
itself when flink's inner jobs failed? The application is still running no matter how many jobs failed, as a result, the problems can't be found immediately.
Do you have any idea?
You can always kill it as any other regular yarn application:
yarn application -kill <applicationId>
More e.g. here: https://hadoop.apache.org/docs/r2.7.3/hadoop-yarn/hadoop-yarn-site/YarnCommands.html
Related
It happened after restart of a node in cluster. It complains about incompatible_feature_flags and stops. The doc says that once a feature flag enabled it is impossible to disable. The only other running node in cluster has that flag (user_limit) disabled and once this newly started node completes syncing tables from peer it says in the log that
Application mnesia exited with reason: stopped
BOOT FAILED
===========
Error during startup: {error,
{incompatible_feature_flags,
{not_active,
"All replicas on diskfull nodes are not active yet",
rabbit_user,
[rabbit#rabbitmq3]}}}
I also tried by killing all process relating to rabbit server (including erlang one) and editing rabbit#rabbitmq1-feature_flags before start, but it gets overridden and no success.
I prefer not to enable user_limit feature flag on the running node and remove it on this node whatever it takes. How can I reset this node (for example by removing mnesia directory or else) to forget about its already enabled flag and then join it to the cluster again.
PS: rabbit#rabbitmq3 is also another node in cluster that is down and causing no harm.
I do not know about other circumstances but in my case the culprit was the other down node (rabbit#rabbitmq3). I dont know how but although the rabbit#rabbitmq3-feature_flags said that user_limit is not enabled, after I ran rabbitmqctl forget_cluster_node rabbit#rabbitmq3 on the running node and start the other node it went successfully and became up and cluster is ok too.
If you are using brew run rabbit and don't care about your state, then run the following commands:
brew services stop rabbitmq
brew uninstall rabbitmq
rm -rf /usr/local/var/lib/rabbitmq
rm -rf /usr/local/var/log/rabbitmq
rm -rf /usr/local/etc/rabbitmq
brew install rabbitmq
brew services start rabbitmq
I'm quite new to gitlab CI and have setup my server at DigitalOcean with gitlab-runnner. When I start the gitlab-runner by the command sudo gitlab-runner start, it runs fine and I confirm it with gitlab-runner status. But, the job fails immediately as per this screenshot
However, when I run gitlab-runner --debug run, the job runs perfectly fine.
I want to run gitlab-runner as a background service but its not running my jobs.
I found a solution to this issue from gitlab. For me, the solution was to comment out the clear console command from .bash_logout file in the gitlab-runner home folder.
More information about this issue can be taken from a bug logged at gitlab.
https://gitlab.com/gitlab-org/gitlab-runner/-/issues/4449
This question already has answers here:
react-native :app:installDebug FAILED
(35 answers)
Closed 9 days ago.
There are quite a few online posts about the error. My situation is that I can make the connection sometimes but failed most of times. Here is the error when failing:
PS C:\d\code\js\chatapp> react-native run-android
JS server already running.
Building and installing the app on the device (cd android && gradlew.bat installDebug)...
Starting a Gradle Daemon, 1 incompatible Daemon could not be reused, use --status for details
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:installDebug'.
> com.android.builder.testing.api.DeviceException: No connected devices!
* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
* Get more help at https://help.gradle.org
BUILD FAILED in 15s
27 actionable tasks: 1 executed, 26 up-to-date
Could not install the app on the device, read the error above for details.
Make sure you have an Android emulator running or a device connected and have
set up your Android development environment:
https://facebook.github.io/react-native/docs/getting-started.html
Here is the message when success:
PS C:\d\code\js\chatapp> react-native run-android
JS server already running.
Building and installing the app on the device (cd android && gradlew.bat installDebug)...
> Task :app:installDebug
Installing APK 'app-debug.apk' on 'MHA-L29 - 8.0.0' for app:debug
Installed on 1 device.
BUILD SUCCESSFUL in 6s
27 actionable tasks: 1 executed, 26 up-to-date
'adb' is not recognized as an internal or external command,
operable program or batch file.
Starting the app (c:\AppData\Local\Android\Sdk/platform-tools/adb shell am start -n com.chatapp/com.chatapp.MainActivity...
Starting: Intent { cmp=com.chatapp/.MainActivity }
I don't have good explanation why sometime it did work and other time it did not. Before each react-native run andrioid, USB Debugging is enabled on Mate 9.
This would also happen to me when the phone I had connected had a locked screen. Make sure the phone is 'active' when you're trying to run. Before you run react-native run-android you can use "adb devices" command to list all connected devices. Make sure there is only one at time (no emulator running as well).
Last thing I can recommend is update React Native. They are doing a great job improving with each version and it might happen you will never see this error again in the newest version. Good luck!
I had a similar issue and just posted a solution that worked for me here - https://stackoverflow.com/a/67566428/10392546
I ran into a similar issue, not sure if you get it fixed, but I came accross this post when looking for solutions and the above solution didn't work for me.
A solution I did find out about was to install android-emulator-m1-preview from google, launch that instead of launching the emulator from inside Android Studio. Its almost annoying how simple of an issue it turned out to be to fix.
Seeing build successful after 12+ hours of trying different solutions is really nice.
I have this issue with my project. I have tried many ways to solve that and I have so many guidelines in stackoverflow, github, blog articles. But there was a mistake I made within the process. So make sure you are do things withing the debugging period.
runcd android && ./gradlew clean && ./gradlew :app:bundleRelease
make sure in each action wipe data in emulator
If you are trying with the external device make sure it is online or unlock the screen.
Try uninstalling the package from your phone. Sometimes this data is cached in your phone memory. You can use the following commands.
List adb devices connected to your computer. Head over to the terminal in your the project root directory and run adb devices. This will list all the devices attached.
Your result will look something like this;
$ adb devices
List of devices attached
047292599G105335 device
Then run adb -s <your_device_key> uninstall <your_package_name>.
<your_device_key> in this case is is 047292599G105335 and the package name looks something like com.appname, all without the square brackets.
So in my case it looked like adb -s 047292599G105335 uninstall com.appname
Now run your project again react-native run-android
I need to create node_modules in the root app when deploy new version using Octopus
How can I create a run script using a new octopus step? I try:
npm install
But I get error when execute the script step
'The remote script failed with exit code 1'
Any ideas?
Your build system should be handling that for you. The node_modules directory should then be included in your application package, but ideally, this should also be bundled to reduce the number of files that your application is dependant on.
If you do need to run this as part of a deployment, then you would need NodeJS and npm installed on the server that is executing the deployment step (either the Octopus server itself or a worker instance if using workers).
For more information check out this blog post
I have an interesting issue, I have a setup or rails project and the deployment/upgrades works absolutely fine when running as a dedicated user (deploy) who is used to setup everything.
I am using codeDeploy to manage the deployments and it uses root user to do the deployment on AWS, but during the deployment it fails on running the same script because it's not able to find npm command
cd client && npm run build:client
sh: 1: npm: not found
rake aborted!
Command failed with status (127): [cd client && npm run build:client...]
If i run it manually to check that i also get nothing
root#ip-172-31-4-141:/home/ubuntu# su deploy -c "which npm"
root#ip-172-31-4-141:/home/ubuntu#
NPM is available via the deploy user but I am struggling to understand why it's not available via the root user
deploy#ip-172-31-4-141:/home/ubuntu$ which npm
/home/deploy/.nvm/versions/node/v7.8.0/bin/npm
Any help to get this resolved would be great.
Thanks,
The issue here was that AWS CodeDeploy when starts deployment loads only a minimum env; to load all the env variables I have exported the env and then in the deploy phase source that file, which resolves my issue