Compile Program for MapReduce2 but still get JobTracker Error - hadoop2

I am trying to run a MapReduce 2 job on hadoop but get an error about connecting to port 8021. As far as I know this port is for the JobTracker, which is not used in MR2. This makes me wonder if I am somehow accidentally using MR1. However, extensive web search did not get me anywhere.
I used the new API (org.apache.hadoop.mapreduce.*) and compiled with javac -cp 'yarn classpath' sourcefolder. Does anyone have a clue what I might be doing wrong?

Please check your configuration files and also make sure that your job tracker and task tracker are active. If its having problem connecting to port 8021, it might be used by other applications.

Related

Windows Installer Crashes with 0xC0000409 error but doesn't display anything

I am working with a 64-bit Windows installer on a 64-bit Windows 10 system that has intermittent crashing issues, where it will crash and close without displaying any kind of error message. This occurs when clicking through the installer's UI, it does not actually attempt to install anything. Collecting a crash dump, I saw that it listed the exception as an "unknown error) 0xC000409. When I ran the crash dump through Visual Studio's debugger in order to obtain information, the message said:
Unhandled exception at 0x00007FFCA685C56F (ntdll.dll) in msiexec__PID__9356__Date__11_01_2021__Time_01_46_34PM__594__Second_Chance_Exception_C0000409.dmp: RangeChecks instrumentation code detected an out of range array access.
The stack trace collected from the crash dump says the following:
ntdll!LdrpICallHandler+f
ntdll!RtlpExecuteHandlerForException+f
ntdll!RtlDispatchException+244
ntdll!KiUserExceptionDispatch+2e
ntdll!LdrpDispatchUserCallTarget+e
msi!CMsiRecord::Release+12e
msihnd!CMsiHandler::CreateControls+18e
msihnd!CMsiHandler::CreateNewDialog+6ba
msihnd!CMsiHandler::RunWizard+564
msihnd!CMsiHandler::DoAction+6e6
msi!MsiUIMessageContext::ProcessMessage+1816
msi!MsiUIMessageContext::RunInstall+1ed
msi!RunEngine+1c9
msi!MsiInstallProductW+11f
msiexec!DoInstallPackage+20e
msiexec!ServerMain+1009
msiexec!WinMain+36
msiexec!__mainCRTStartup+1a0
kernel32!BaseThreadInitThunk+14
ntdll!RtlUserThreadStart+21
As far as I am aware, there were no major changes made to the installer recently. It just suddenly started getting reported that the installer was crashing, and this was the information that I was able to compile so far. My question is if there's any way to troubleshoot the installer during runtime so that I can get to the bottom of this, or are there any potential fixes I can explore applying? I've done lots of googling on this error and I haven't been able to find a related result yet.
I have also attempted to use ProcMon to see if a file is being blocked but have yet to find anything. I attempted to attach debuggers to the installer to produce a runtime failure, but because it appears to be going into Microsoft code, I can't get a look at the source or the information that it's working with.
I attempted to gather Windows Installer logs, but the log just cuts off at the moment of crashing without displaying any useful exception information. As best as I can gather, the crash occurs when the installer tries to create a dialog.
UPDATE: Some questions:
1) Do you have any custom actions in the setup GUI?
2) Is this a GUI-set from WiX or is it your own, custom GUI?
3) These machines are not Windows 11 are they?
4) Are you installing on a very clean virtual? The below entry in the stack trace makes me wonder if the Visual C/C++ Runtime is installed on the box in the appropriate version?:
msiexec!__mainCRTStartup+1a0
This would seem to refer to "The C runtime Library (CRT)". Please check if it is installed: Microsoft Visual C++ Redistributable Latest Supported Downloads.
Logging
Verbose logging with extra debugging information (very slow) - Comprehensive answer on logging:
msiexec.exe /i C:\Path\Your.msi /L*vx! C:\Your.log
Quick Parameter Explanation:
/i = run install sequence
/L*vx! C:\Your.log = verbose debug logging at specified path
The x adds extra debugging information, and the ! disables the log buffer. This means there is no lost log if there are any crashes.
Silent Installation
I am wondering if the crash comes from the setup GUI alone. If this is the case you might be able to install the setup silently successfully (since this bypasses the GUI entirely). Please try this? If this fails too, perhaps it is the Visual C/C++ runtime that is missing? Or likely something else. Logging is essential as explained above.
msiexec.exe /i c:\setup.msi /QN /L*V "C:\Temp\msilog.log"
Quick Parameter Explanation:
/L*V "C:\Temp\msilog.log"= verbose logging
/QN = run completely silently
/i = run install sequence
You can throw in the exclamation mark for continuous logging (no log buffer) here as well, but that will slow the installation down a lot.
Links:
Answer on silent installation here
Comprehensive answer on MSI logging
https://www.advancedinstaller.com/user-guide/read-log.html

Red Folder in intelliJ after running springboot:run

Hi guys im having an issue with my intellij react project, ive already connected to the MySQL DB from intelliJ..
After running springboot:run, it installs all dependencies for the app after all is done i get a target folder thats red and a package-lock.json thats also red what does this mean?
Im new to react so im trying to run this app locally but when i run the project i get this error:
"Error starting ApplicationContext. To display the auto-configuration report re-run your application with 'debug' enabled.
2018-06-22 13:23:20.295 ERROR 6796 --- [ restartedMain] o.s.boot.SpringApplication : Application startup failed"
Project has already been built by previous Dev im just trying to get it ti run locally now.
what could i be doing wrong?
Spring-boot is one of the wonderful thing to get started to fast, it
does many things automatically. At the same time, missing
configuration will lead to this kind of errors.
Please double check application.yaml/.properties and pom.xml for more details.
This error is thrown when dependencies are not resolved correctly and mis-configuration of dependencies.
If it is a Maven project, right click on project folder and do 'Maven -> Re-Import'. It will fetch the missing maven dependencies.
Also, whatever is mentioned as part of the dependencies should have proper configurations. Let's say for example, you're mentioning mysql as dependency and doesn't provide connection/username/password details then this error occurs.
Please provide more details/error-trace log to provide more accurate answer.
Hope it helps!!

Debug JRuby rack runtime error in tomcat

We recently upgraded an old rails app from rails 3 to 4.2, along with many other gem updates. Now I can't get my rails app to load any pages. We were on JRuby 9.1.0.0 but upgraded to 9.1.8.0. However, I'm hitting the same problem on both versions.
Once we start tomcat with our latest .war, it runs all the way until I see the INFO: Server startup in 1234ms message. I've added some debug statements in my rails environment / initializers files to follow it through and it is hitting each of them. So once I see the startup message from tomcat, I figured it would be okay. However, it immediately spits out the following message quite a few times:
DEBUG: resetting rack response due exception
Every time I load a URL, it also shows that message in my logs.
I see that it's from this jruby-rack class but I have no idea how to debug or troubleshoot this further.
I assume that something in my configuration is causing a problem or that a class/module is somehow short-circuiting it but I'm not sure how to identify which one it is or isolate the issue.
Does anybody know of a way to get some more verbose logs or ways to figure out where the problem is happening?
Happy to post any config/gemfiles etc if it will help.
After receiving some great help from the #jruby IRC channel, they mentioned the error message was missing the specific exception message. I was using the latest version, v1.1.21 so I just made a hack-build that added some logging to identify my problem further. Turns out it was a runtime error because of some missing config.
I made an issue with jruby-rack and a PR which will hopefully make its way into the next release!

CLSQL on CentOS installation

I want to connect to MySQL from SBCL using CLSQL. I loaded CLSQL using quicklisp (ql:quickload 'clsql). However, when calling (clsql:connect '(...) :database-type :mysql), it said:
Couldn't load foreign libraries "libmysqlclient", "libmysql". (searched CLSQL-SYS:FOREIGN-LIBRARY-SEARCH-PATHS).
I'm on CentOS, and basically what I want to do is
Install mysql client development headers with yum, so UFFI can find it (which I failed to do)
after installing, be able to connect to local MySQL server (I think after 1. is done, it could be working automatically).
I'm currently using:
CentOS 5.7 Final (32 bit)
SBCL 1.0.55
Quicklisp beta
yum repositories: base, epel, extras, updates
I didn't just ask about how to install MySQL development headers on CentOS, because that would solve only part of my problem, I would still need to know what's missing from my machine. I also didn't try to build libmysqlclient/libmysql from source, because I don't know whether clsql would be able then to find it or not. I think not.
I'm really sorry if my question somehow misses the point, but extensive googling didn't yield any results. If anyone told me they couldn't install mysql client development headers on CentOS, I would laugh at them and tell them to use yum search, but I couldn't find it neither with yum neither online.
I know the solution for ubuntu (and debian), because there is a cl-sql package and I can easily find mysql headers there too, but I need it on CentOS.
Thanks in advance.
Somehow, when you try something long enough, it will get done ;)
Here's what I did if anyone needs an answer and stumbles upon this question:
(ql:quickload 'clsql)
;tell clsql where to search for mysql libs
(push #P"/usr/lib/mysql" CLSQL-SYS:*FOREIGN-LIBRARY-SEARCH-PATHS*)
;add mysql libs to clsql library path [apparent from code :]
(clsql:push-library-path "/usr/lib/mysql/")
;directly tell uffi to load mysqlclient shared library
(uffi:load-foreign-library "/usr/lib/mysql/libmysqlclient.so")
Of course, you can replace "/usr/lib/mysql" with a different path for mysql libraries, if needed.

Glassfish Deploy CommandException Error

I want to deploy my application to glassvish v3 with asadmin deploy command however I get an error:
com.sun.enterprise.admin.cli.CommandException: remote failure: There is no installed container capable of handling this application com.sun.enterprise.deploy.shared.FileArchive#1c2a1c7
What can be the problem?
To me, the problem was coming from the fact that in /domains/domain/applications there was still the application I was trying to deploy again.
Another file access possibility I just ran into:
Service was started as root and the app undeployed/deployed. Then, as the correct limited rights user, undeploy/deploy. On deploy you'll receive this error, as the application files will still exist in he 'domains/yourdomain/applications' directory, and will be owned by root.
+1 to Keeg's comment on the awesome error messages we've all come to expect from Glassfish.
Hey I got the same error.In my case,I'd made a directory named "Web-INF",apparently the name of the folder has to be (mandatory) in upper-case i.e. "WEB-INF".
In short,check for spelling errors.
It solved my issue.So just wanted to share.I'm new to glassfish, so can't really tell you the exact solution.But what worked for me could be a solution for you as well.
Just in case someone else finds this question and the above answer doesn't match your case... Our problem was that the temporary area on the Glassfish server was full. Clearing some space let me redeploy the same application. Thank goodness for excellent error messages.
I had an ear project, where the ear package had different version number configured to maven pom.xml than the rest of the projects it contained. It searched sub-modules from version 1.x and the rest of the project was at 1.y version. I updated every pom to same version and that made the trick.