I am having issues while restarting YARN service. It keeps failing with errors shown in the logs below. YARN was working fine until last week and then the below error messages started to pop up all of a sudden.
Tried restarting YARN/JOB history server. Nothing worked. Kindly help to alleviate this issue.
Thanks,
Vinoth
Error starting JobHistoryServer
java.lang.IllegalAccessError: tried to access class org.apache.hadoop.mapred.JobACLsManager from class org.apache.hadoop.mapreduce.v2.hs.HistoryFileManager
at org.apache.hadoop.mapreduce.v2.hs.HistoryFileManager.serviceInit(HistoryFileManager.java:503)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.mapreduce.v2.hs.JobHistory.serviceInit(JobHistory.java:94)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107)
at org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer.serviceInit(JobHistoryServer.java:145)
at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163)
at org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer.launchJobHistoryServer(JobHistoryServer.java:222)
at org.apache.hadoop.mapreduce.v2.hs.JobHistoryServer.main(JobHistoryServer.java:232)
Are you working in a pseudo environment?
Also not clear what command you are using to restart.
You can try the below command to restart :
sudo service hadoop-master stop
sudo service hadoop-master start
-Senthil
Related
The cloudrun debug in cloud shell was working. It is no longer working for me with the following output.
I have 1) rebooted the VM and 2) I have tried another project that was also working previously.
I suspect something has changed in my environment
Starting to debug the app using configuration 'Cloud Run: Run/Debug
Locally' from .vscode/launch.json... To view more detailed logs, go to
Output channel : "Cloud Run: Run/Debug Locally - Detailed" Dependency
check started Dependency check succeeded Unpausing minikube flag needs
an argument: --status-check See 'skaffold debug --help' for usage.
Exited with code 127. Cleaning up... Finished clean up.
This bug was introduced in the v1.17.1 release of Cloud Code for VS Code, due to a change in v1.37.0 of Skaffold related to the --status-check parameter. This bug was addressed in v1.17.2 of Cloud Code for VS Code, and upgrading to this version (or later) should fix this issue.
When I try to run my localhost using yarn dev it shows this error:
yarn run v1.22.4 $ next -p 7777 ready - started server on
0.0.0.0:7777, url: http://localhost:7777 TypeError: _jestWorker.Worker is not a constructor
at Object.loadWebpackHook (D:\isc-web\isc-front\node_modules\next\dist\server\config-utils.js:67:20)
at Object.loadConfig [as default] (D:\isc-web\isc-front\node_modules\next\dist\server\config.js:332:29)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async NextServer.loadConfig (D:\isc-web\isc-front\node_modules\next\dist\server\next.js:112:22)
error Command failed with exit code 1. info Visit
https://yarnpkg.com/en/docs/cli/run for documentation about this
command.
It was all working fine before I did npm install --save-dev babel-plugin-styled-components even though I canceled the changes by using git checkout -- . but still got the same problem
If you cancelled dependency changes with git checkout your node_modules may still have the old dependencies installed. Try running npm i again to see if getting updated dependencies resolves the issue.
I can't tell much from this error message and I don't know how far along your project is... Have you seen the official Next.js + styled-components example? https://github.com/vercel/next.js/tree/canary/examples/with-styled-components
Perhaps if you try setting up the library this way instead?
I'm trying to install aodh. I am following this tutorial - https://docs.openstack.org/aodh/stein/install/install-ubuntu.html
When I run this command
aodh alarm list
I'm getting following error.
<html>
<head>
<title>503 Service Unavailable</title>
</head>
<body>
<h1>503 Service Unavailable</h1>
The server is currently unavailable. Please try again at a later time.<br /><br />
The Keystone service is temporarily unavailable.
</body>
</html> (HTTP 503) (Request-ID: req-9f8035a5-e324-4e2f-b3f0-037b68f88d1a)
Even though the error says keystone is unavailable, I highly suspect that already there was some problem with aodh installation.
From the aodh link above, I in the final step, it says:
Restart the Alarming services:
# service aodh-api restart
# service aodh-evaluator restart
# service aodh-notifier restart
# service aodh-listener restart
When I tried this
service aodh-api restart
I got following error
Failed to restart aodh-api.service: Unit aodh-api.service not found.
Moreover in step 2 of above link
Source the admin credentials to gain access to admin-only CLI commands:
$ . admin-openrc
Since, I was unable to find admin-openrc, I skipped that step.
So, I am thinking probably aodh installation didn't go well. Hence the aforementioned error in 'aodh alarm list' command.
Other commands like 'nova list' etc are running fine
Can someone please help in figuring out, what could be going wrong?
Install aodh component as plugin during devstack installation.
https://ask.openstack.org/en/question/116895/how-to-configure-devstack-with-ceilometer-gnocchi-and-aodh-components/
Recently, I encountered this problem, which has been answered on the official website.
https://docs.openstack.org/aodh/latest/contributor/install/index.html
Default, API is provided by apache2 wsgi.
But in my environment, this method can not successfully.
Another method, remove aodh apache2 wsgi, and create aodh-api service.
this method success.
Please help me with Redmine. I had a working Redmine at FreeBSD 11.2-RELEASE-p4 with Nginx and Passenger. But after some latest updates, my Redmine is not working properly.
I have an error in passenger.log:
[ E 2018-10-09 16:10:01.0750 42785/Tb
age/Cor/App/Implementation.cpp:221 ]: Could not spawn process for
application /usr/local/www/redmine: The application encountered the
following error: undefined method `active_record' for
(NoMethodError) Error ID: 8412e2de Error details saved to:
/tmp/passenger-error-wIhbfb.html
What can I do with these errors?
You should try to install the gems required, just go to where the redmine code is and type
bundle install
Restart nginx and see if keep saying the same error.
Fresh install of Meteor 0.5.0 on Windows Vista. I don't get the basic examples working. No success after creating the empty'ish hello app either. The shell is running as admin. Meteor recognises that I changed a source file, but then nothing. It doesn't matter where in the filesystem i try this. Always getting
Exited with code: -1073741819:
eg
C:\Users\jawford\Meteor Apps\Examples>meteor create starter3
starter3: created.
To run your new app:
cd starter3
meteor
C:\Users\jawford\Meteor Apps\Examples>cd starter3
C:\Users\jawford\Meteor Apps\Examples\starter3>meteor
[[[[[ C:\Users\jawford\Meteor Apps\Examples\starter3 ]]]]]
Running on: http://localhost:3000/
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
=> Modified -- restarting.
Exited with code: -1073741819
Exited with code: -1073741819
Exited with code: -1073741819
Your application is crashing. Waiting for file change.
^CTerminate batch job (Y/N)? y
C:\Users\jawford\Meteor Apps\Examples\starter3>
If you run into this problem using Windows 8, you will need to change compatibility mode for the node executable.
Go to the folder where you installed Meteor
Open properties for bin/node.exe
Set compatibility mode for Windows 7
You should now be able to start the application as you did earlier.
This has to do with Fibers not loading correctly. You can attempt to run app/meteor/meteor.js with bin/node, both are in the Meteor directory in Program Files. This could maybe give you more details why it is crashing. It might also be handy to run the tests in the lib/node_modules/fibers folder which might point out why Fibers is misbehaving.
The exit code -1073741819 corresponds to C0000005 which indicates an access violation.
Many users find that setting compatibility mode to "Windows 7" solves that problem, but it doesn't always and there is some evidence that it also occurs on Windows 7.
Investigating a later issue on win Meteor 0.5.9, I discovered a problem with fibers on windows that may explain this issue, and I have a tentative fix.
Please see: https://github.com/TomWij/meteor/issues/66#issuecomment-15994548 for further details.