Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52865

Jenkins has error code 268435458.

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Minor
    • Resolution: Unresolved
    • core

    Description

      Hello all.

      I have a problem when I use Jenkins to call Trace32 software. Sometime, Jenkins cannot launch the Trace32 software and he is suspended. I have to click button to stop job. Then I see in the console the error message:

      "Executing debugger... ERROR: Build step failed with exceptionExecuting debugger... ERROR: Build step failed with exceptionorg.jvnet.winp.WinpException: Process with pid=12108 is not a 32bit process (or it is not running). Cannot query it from a 32bit library error=268435458 at envvar-cmdline.cpp:183 at org.jvnet.winp.Native.getCmdLine(Native Method) at org.jvnet.winp.WinProcess.parseCmdLine(WinProcess.java:132) at org.jvnet.winp.WinProcess.getCommandLine(WinProcess.java:107) at hudson.util.ProcessTree$WindowsOSProcess.getArguments(ProcessTree.java:522) at hudson.plugins.msbuild.MsBuildKillingVeto.vetoProcessKilling(MsBuildKillingVeto.java:56) at hudson.util.ProcessTree$OSProcess$CheckVetoes.call(ProcessTree.java:337) at hudson.util.ProcessTree$OSProcess$CheckVetoes.call(ProcessTree.java:327) at hudson.remoting.LocalChannel.call(LocalChannel.java:45) at hudson.util.ProcessTree$OSProcess.getVeto(ProcessTree.java:263) at hudson.util.ProcessTree$WindowsOSProcess.killRecursively(ProcessTree.java:500) at hudson.util.ProcessTree.killAll(ProcessTree.java:157) at hudson.Proc$LocalProc.destroy(Proc.java:384) at hudson.Proc$LocalProc.join(Proc.java:357) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:155) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:109) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'Execute shell' marked build as failure"

       

      I see that the error code: 268435458. But I cannot figure out anything about it from google. Could you help me to find the root cause and solution for it.

      Attachments

        Issue Links

          Activity

            namkd Nam Khuc created issue -
            oleg_nenashev Oleg Nenashev added a comment -

            Most likely you are running with 32-bit JVM on a 64-bit operating system. Please verify that.

            oleg_nenashev Oleg Nenashev added a comment - Most likely you are running with 32-bit JVM on a 64-bit operating system. Please verify that.
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Assignee Oleg Nenashev [ oleg_nenashev ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels winp
            namkd Nam Khuc added a comment -

            My computer is windows10 64bit and my Jenkins is 32 bit version. My Trace32 software is 64-bit also. Maybe it is root cause?

            namkd Nam Khuc added a comment - My computer is windows10 64bit and my Jenkins is 32 bit version. My Trace32 software is 64-bit also. Maybe it is root cause?
            namkd Nam Khuc added a comment -

            I had checked my Java, it is 64 bit version. Maybe I need to install Jenkins 64bit version?

            namkd Nam Khuc added a comment - I had checked my Java, it is 64 bit version. Maybe I need to install Jenkins 64bit version?
            oleg_nenashev Oleg Nenashev added a comment -

            Yes, this is the root cause: https://github.com/kohsuke/winp#platform-support

            On 64-bit machines you should be running with 64-bit Java. The main problem is that we offer only the 32-bit package in jenkins.io/download, so it is not quite uncommon. I have created JENKINS-52868 so that we have a tracking issue for packaging

            So a resolution for you will be to update Java to 64bit.

            oleg_nenashev Oleg Nenashev added a comment - Yes, this is the root cause: https://github.com/kohsuke/winp#platform-support On 64-bit machines you should be running with 64-bit Java. The main problem is that we offer only the 32-bit package in jenkins.io/download, so it is not quite uncommon. I have created JENKINS-52868 so that we have a tracking issue for packaging So a resolution for you will be to update Java to 64bit.
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue relates to JENKINS-52868 [ JENKINS-52868 ]
            namkd Nam Khuc added a comment - - edited

            Oh,I had checked my Java and it is 64 bit version (because Java is installed into "Program Files" folder). But my Jenkins is 32 bit version (because Jenkins is installed into "Program Files (x86)" folder). 

            So the solution that, I should update Jenkins to 64 bit version, right? (Because, I saw that, you said ".... update Java to 64bit.").

            namkd Nam Khuc added a comment - - edited Oh,I had checked my Java and it is 64 bit version (because Java is installed into "Program Files" folder). But my Jenkins is 32 bit version (because Jenkins is installed into "Program Files (x86)" folder).  So the solution that, I should update Jenkins to 64 bit version, right? (Because, I saw that, you said ".... update Java to 64bit.").
            oleg_nenashev Oleg Nenashev added a comment -

            Jenkins itself is a Java application, which supports both 32 and 64 bits. Please check jenkins.xml in the Root, most likely it references the Java version embedded in the Jenkins package.

             

            oleg_nenashev Oleg Nenashev added a comment - Jenkins itself is a Java application, which supports both 32 and 64 bits. Please check jenkins.xml in the Root, most likely it references the Java version embedded in the Jenkins package.  
            namkd Nam Khuc made changes -
            Attachment jenkins.xml [ 43598 ]
            namkd Nam Khuc made changes -
            Attachment jenkins.xml [ 43599 ]
            namkd Nam Khuc added a comment -

            I saw in my jenkins.xml file. But I don't see any information about Jave version.

            This is content in my jenkins.xml

             

             

            <!--
            The MIT License

            Copyright (c) 2004-2017, Sun Microsystems, Inc., Kohsuke Kawaguchi, Oleg Nenashev, and other Jenkins contributors

            Permission is hereby granted, free of charge, to any person obtaining a copy
            of this software and associated documentation files (the "Software"), to deal
            in the Software without restriction, including without limitation the rights
            to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
            copies of the Software, and to permit persons to whom the Software is
            furnished to do so, subject to the following conditions:

            The above copyright notice and this permission notice shall be included in
            all copies or substantial portions of the Software.

            THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
            IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
            FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
            AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
            LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
            OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
            THE SOFTWARE.
            -->

            <!--
            Windows service definition for Jenkins.

            To uninstall, run "jenkins.exe stop" to stop the service, then "jenkins.exe uninstall" to uninstall the service.
            Both commands don't produce any output if the execution is successful.
            -->
            <service>
            <id>Jenkins</id>
            <name>Jenkins</name>
            <description>This service runs Jenkins automation server.</description>
            <env name="JENKINS_HOME" value="D:\NamKD\Jenkins_Home"/>
            <!--
            if you'd like to run Jenkins with a specific version of Java, specify a full path to java.exe.
            The following value assumes that you have java in your PATH.
            -->
            <executable>%BASE%\jre\bin\java</executable>
            <arguments>-Xrs -Djava.awt.headless=true -Dmail.smtp.starttls.enable=true -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080 --webroot="%BASE%\war"</arguments>
            <!--
            interactive flag causes the empty black Java window to be displayed.
            I'm still debugging this.
            <interactive />
            -->
            <logmode>rotate</logmode>

            <onfailure action="restart" />

            <!--
            In the case WinSW gets terminated and leaks the process, we want to abort
            these runaway JAR processes on startup to prevent corruption of JENKINS_HOME.
            So this extension is enabled by default.
            -->
            <extensions>
            <!-- This is a sample configuration for the RunawayProcessKiller extension. -->
            <extension enabled="true"
            className="winsw.Plugins.RunawayProcessKiller.RunawayProcessKillerExtension"
            id="killOnStartup">
            <pidfile>%BASE%\jenkins.pid</pidfile>
            <stopTimeout>10000</stopTimeout>
            <stopParentFirst>false</stopParentFirst>
            </extension>
            </extensions>

            <!-- See the referenced examples for more options -->

            </service>

            namkd Nam Khuc added a comment - I saw in my jenkins.xml file. But I don't see any information about Jave version. This is content in my jenkins.xml     <!-- The MIT License Copyright (c) 2004-2017, Sun Microsystems, Inc., Kohsuke Kawaguchi, Oleg Nenashev, and other Jenkins contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. --> <!-- Windows service definition for Jenkins. To uninstall, run "jenkins.exe stop" to stop the service, then "jenkins.exe uninstall" to uninstall the service. Both commands don't produce any output if the execution is successful. --> <service> <id>Jenkins</id> <name>Jenkins</name> <description>This service runs Jenkins automation server.</description> <env name="JENKINS_HOME" value="D:\NamKD\Jenkins_Home"/> <!-- if you'd like to run Jenkins with a specific version of Java, specify a full path to java.exe. The following value assumes that you have java in your PATH. --> <executable>%BASE%\jre\bin\java</executable> <arguments>-Xrs -Djava.awt.headless=true -Dmail.smtp.starttls.enable=true -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080 --webroot="%BASE%\war"</arguments> <!-- interactive flag causes the empty black Java window to be displayed. I'm still debugging this. <interactive /> --> <logmode>rotate</logmode> <onfailure action="restart" /> <!-- In the case WinSW gets terminated and leaks the process, we want to abort these runaway JAR processes on startup to prevent corruption of JENKINS_HOME. So this extension is enabled by default. --> <extensions> <!-- This is a sample configuration for the RunawayProcessKiller extension. --> <extension enabled="true" className="winsw.Plugins.RunawayProcessKiller.RunawayProcessKillerExtension" id="killOnStartup"> <pidfile>%BASE%\jenkins.pid</pidfile> <stopTimeout>10000</stopTimeout> <stopParentFirst>false</stopParentFirst> </extension> </extensions> <!-- See the referenced examples for more options --> </service>
            oleg_nenashev Oleg Nenashev added a comment -

            namkd "%BASE%\jre\bin\java " - it points to the bundled java. You can just replace it by the path to your Java executable

            oleg_nenashev Oleg Nenashev added a comment - namkd "%BASE%\jre\bin\java " - it points to the bundled java. You can just replace it by the path to your Java executable
            namkd Nam Khuc added a comment -

            I had open cmd in this path and use command:  java -XshowSettings:all to check this jave is 32 or 64 bit. This is result sun.arch.data.model = 64. I think the Java version embedded in my Jenkins is 64 bit.

            But, I also try to run Jenkins with my Java which is installed in "Program Files" folder and inform you late.

            namkd Nam Khuc added a comment - I had open cmd in this path and use command:   java -XshowSettings:all  to check this jave is 32 or 64 bit. This is result  sun.arch.data.model = 64.  I think the Java version embedded in my Jenkins is 64 bit. But, I also try to run Jenkins with my Java which is installed in "Program Files" folder and inform you late.
            oleg_nenashev Oleg Nenashev added a comment -

            What is "this path"? Note that Windows will still rely on PATH unless you explicitly invoke java.exe, preferable by absolute path

            oleg_nenashev Oleg Nenashev added a comment - What is "this path"? Note that Windows will still rely on PATH unless you explicitly invoke java.exe, preferable by absolute path
            namkd Nam Khuc added a comment -

            I mean that, I go to "C:\Program Files (x86)\Jenkins\jre\bin" and check version of Java in here. Because, I think the %BASE%=C:\Program Files (x86)\Jenkins

            namkd Nam Khuc added a comment - I mean that, I go to "C:\Program Files (x86)\Jenkins\jre\bin" and check version of Java in here. Because, I think the %BASE%=C:\Program Files (x86)\Jenkins
            oleg_nenashev Oleg Nenashev added a comment -

            Yes. But be sure that "C:\Program Files (x86)\Jenkins\jre\bin" contains a 32bit Java. If no, it would be a critical issue in the packaging.

             

            oleg_nenashev Oleg Nenashev added a comment - Yes. But be sure that "C:\Program Files (x86)\Jenkins\jre\bin" contains a 32bit Java. If no, it would be a critical issue in the packaging.  
            namkd Nam Khuc added a comment -

            Thanks for your remind. As I said at last commnet. I checked by  java -XshowSettings:all command and result is sun.arch.data.model = 64. So I think the java version which is embedded in Jenkins is 64 bit.

             

            Maybe it is a issue of packaging!

            namkd Nam Khuc added a comment - Thanks for your remind. As I said at last commnet. I checked by   java -XshowSettings:all  command and result is  sun.arch.data.model = 64.  So I think the java version which is embedded in Jenkins is 64 bit.   Maybe it is a issue of packaging!
            namkd Nam Khuc added a comment -

            Hello Oleg.

             

            Could you pls tell me about status of solution for this issue? I don't see any update for this one!

            thanks

             

            namkd Nam Khuc added a comment - Hello Oleg.   Could you pls tell me about status of solution for this issue? I don't see any update for this one! thanks  
            oleg_nenashev Oleg Nenashev added a comment -

            No progress on my side. I will unassign it for now to make the status explicit

            oleg_nenashev Oleg Nenashev added a comment - No progress on my side. I will unassign it for now to make the status explicit
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]

            People

              Unassigned Unassigned
              namkd Nam Khuc
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated: