I am trying to upgrade my Jenkins on a Solaris SPARC machine. I have been using Jenkins version 1.528 and the java version is "1.6.0_65".
I tried to install 1.565.1 on this server, I was able to start it using "java -jar jenkins.war --httpPort=8086"
Aug 13, 2014 2:52:16 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started SelectChannelConnector#0.0.0.0:8086
Aug 13, 2014 2:52:16 PM winstone.Logger logInternal
INFO: Winstone Servlet Engine v2.0 running: controlPort=disabled
Aug 13, 2014 2:52:18 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started initialization
Aug 13, 2014 2:52:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Listed all plugins
Aug 13, 2014 2:52:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Prepared all plugins
Aug 13, 2014 2:52:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Started all plugins
Aug 13, 2014 2:52:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Augmented all extensions
Aug 13, 2014 2:52:19 PM jenkins.InitReactorRunner$1 onAttained
INFO: Loaded all jobs
Aug 13, 2014 2:52:37 PM org.jenkinsci.main.modules.sshd.SSHD start
INFO: Started SSHD at port 54927
Aug 13, 2014 2:52:37 PM jenkins.InitReactorRunner$1 onAttained
INFO: Completed initialization
Aug 13, 2014 2:52:37 PM hudson.TcpSlaveAgentListener <init>
INFO: JNLP slave agent listener started on TCP port 54928
Aug 13, 2014 2:52:37 PM hudson.WebAppMain$3 run
INFO: Jenkins is fully up and running
but the homepage never loads on browser. I see there is something listening on the port but the connnetion is in CLOSE_WAIT status.
bash-3.2$ lsof -i |grep 8086
java 26329 acs 7u IPv4 0x3018556b840 0t0 TCP *:8086 (LISTEN)
java 26329 acs 105u IPv4 0x30278e93900 0t0 TCP server:8086->user-machine:54670 (ESTABLISHED)
java 26329 acs 750u IPv4 0x300b9af9900 0t0 TCP server:8086->user-machine:54671 (CLOSE_WAIT)
java 26329 acs 751u IPv4 0x301ab4f0080 0t0 TCP server:8086->user-machine:54672 (CLOSE_WAIT)
I tried other version 1.532 and it worked but it did not work for 1.534
I tried the same version 1.565.3 on a Linux server and it worked there, It had java version "1.7.0_45". Has anyone else faced this issue?
We have got the same problem on Solaris 11.1.
SunOS XXXXX 5.11 11.1 sun4v sparc sun4v
We are so far using 5.32.1 stable working. 5.80.3 not working.
There is no respond on wget. We are using default port 8080 and neither on wget nor on browser a connection can be established.
This issue is not fixed, I have opened a JIRA ticket on Jenkins forum
JENKINS-24357
There are a few related tickets as well
Related
I am trying to deploy a jenkins war file. I executed the following command
java -jar jenkins.war
Below is the log file.
PS C:\Sites> java -jar jenkins.war Running from: C:\Sites\jenkins.war
webroot: $user.home/.jenkins Sep 03, 2014 6:09:15 PM winstone.Logger
logInternal INFO: Beginning extraction from war file Sep 03, 2014
6:09:28 PM org.eclipse.jetty.util.log.JavaUtilLog info INFO:
jetty-8.y.z-SNAPSHOT Sep 03, 2014 6:09:35 PM
org.eclipse.jetty.util.log.JavaUtilLog info INFO: NO JSP Support for ,
did not find org.apache.jasper.servlet.JspServlet Jenkins home
directory: C:\Users\Mathew.jenkins found at: $user.home/.jenkins
Sep 03, 2014 6:09:46 PM org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Started SelectChannelConnector#0.0.0.0:8080 Sep 03, 2014 6:09:46
PM winstone.Logger logInternal INFO: Winstone Servlet Engine v2.0
running: controlPort=disabled Sep 03, 2014 6:09:46 PM
jenkins.InitReactorRunner$1 onAttained INFO: Started initialization
Sep 03, 2014 6:10:26 PM jenkins.InitReactorRunner$1 onAttained INFO:
Listed all plugins Sep 03, 2014 6:10:26 PM jenkins.InitReactorRunner$1
onAttained INFO: Prepared all plugins Sep 03, 2014 6:10:26 PM
jenkins.InitReactorRunner$1 onAttained INFO: Started all plugins Sep
03, 2014 6:10:26 PM jenkins.InitReactorRunner$1 onAttained INFO:
Augmented all extensions Sep 03, 2014 6:10:26 PM
jenkins.InitReactorRunner$1 onAttained INFO: Loaded all jobs Sep 03,
2014 6:10:42 PM org.jenkinsci.main.modules.sshd.SSHD start INFO:
Started SSHD at port 55062 Sep 03, 2014 6:10:45 PM
jenkins.InitReactorRunner$1 onAttained INFO: Completed initialization
Sep 03, 2014 6:10:45 PM hudson.WebAppMain$3 run INFO: Jenkins is fully
up and running Sep 03, 2014 6:11:48 PM
hudson.model.DownloadService$Downloadable load INFO: Obtained the
updated data file for hudson.tasks.Maven.MavenInstaller Sep 03, 2014
6:11:51 PM hudson.model.DownloadService$Downloadable load INFO:
Obtained the updated data file for hudson.tasks.Ant.AntInstaller Sep
03, 2014 6:11:52 PM hudson.model.DownloadService$Downloadable load
INFO: Obtained the updated data file for hudson.tools.JDKInstaller Sep
03, 2014 6:12:11 PM hudson.model.UpdateSite updateData INFO: Obtained
the latest update center data file for UpdateSource default
Can anyone tell me what does the command java-jar jenkins.war do?
WHere did it deploy my war file?
Which web server does it use and how does localhost:8080 point to jenkins application?
Q. Can anyone tell me what does the command java -jar jenkins.war do?
java -jar expects a jar file name, in this case, jenkins.war.
An executable Java program can be packaged in a JAR file, along with any libraries the program uses. Executable JAR files have the manifest specifying the entry point class with Main-Class: myPrograms.MyClass and an explicit Class-Path (and the -cp argument is ignored). Some operating systems can run these directly when clicked. The typical invocation is "java -jar foo.jar" from a command line
Reference: http://en.wikipedia.org/wiki/JAR_(file_format)
Q. Where did it deploy my war file?
In case it is a RHEL/CentOS installation, your war is deployed at /var/lib/jenkins
You can find out the location by reading the file /etc/init.d/jenkins. You will find a variable named JENKINS_CONFIG
JENKINS_CONFIG=/etc/sysconfig/jenkins
Q. Which web server does it use and how does localhost:8080 point to jenkins application?
In case it is a RHEL/CentOS installation, you will generally find the file here: /etc/sysconfig/jenkins. In this file, you define port on which Jenkins runs.
1) It executes the java arvhive jenkins.war (see http://docs.oracle.com/javase/7/docs/technotes/tools/windows/jar.html)
2) From the output you posted yourself:
Running from: C:\Sites\jenkins.war webroot: $user.home/.jenkins
the user.home variable may refer to your ~ directory on Linux, or your Document and Settings on windows. See http://docs.oracle.com/javase/tutorial/essential/environment/sysprop.html
3) From the output you posted yourself:
jetty-8.y.z-SNAPSHOT
INFO: Started SelectChannelConnector#0.0.0.0:8080
See http://www.eclipse.org/jetty/. This is a web server that register a listener on port 8080.
it uses the Manifest.mf inside, if you open the war, you would understand how it runs
The Main class uses winstone http://winstone.sourceforge.net/
I would recommend to use glassfish, jetty or tomcat - for better control on configuration
there is a bug open for that
https://issues.jenkins-ci.org/browse/JENKINS-18366
Also see various container notes
https://wiki.jenkins-ci.org/display/JENKINS/Containers
I have installed Tomcat 7 with Java 7 on a debian box. It has 512 MB of RAM. I run tomcat out of the box, I have installed nothing, and it is consistently shutting down by itself. I am not even browsing the Tomcat landing page.
As you can see, it is running perfectly normal and then all of a sudden it stops:
Jul 21, 2013 6:11:20 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Jul 21, 2013 6:11:20 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 1063 ms
Jul 21, 2013 8:22:35 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["http-bio-8080"]
Jul 21, 2013 8:22:35 AM org.apache.coyote.AbstractProtocol pause
INFO: Pausing ProtocolHandler ["ajp-bio-8009"]
Jul 21, 2013 8:22:35 AM org.apache.catalina.core.StandardService stopInternal
It just mysteriously stops. What can it be? I know the Tomcat distribution and the Java distribution are good because I downloaded them from the Tomcat site and Oracle, and FTP'd them over to my server.
There are no other errors in any other tomcat log files. Is is a permissions thing? Memory issue? Appreciate your help.
I think a memory issue would show up in the log. I would simply reinstall Tomcat and check if it's still buggy.
I am using Mac OS X 10.7.4, app engine sdk 1.7.0, eclipse juno and Java as programming language. The problem is that App runs perfectly well when deployed on appspot but does not work on localhost. When run as web application on port 8888 or any other port (if change it from the configuration), the log represents server is running but when I hit the URL, nothing happens and after some time connection times out. When, debugged it gives the error: Cannot connect to VM. Logs from console for both run and debugged are shown below, kindly help me, I have searched all over the 'net but could not find the solution.
Log when Debugged:
ERROR: transport error 202: handshake failed - connection prematurally closed
ERROR: JDWP: Failed to initialize transport via localhost:49741, trying localhost via 127.0.0.1:49741
ERROR: transport error 202: recv failed during handshake: Connection reset by peer
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Log when run:
2012-07-17 19:07:42.504 java[417:407] [Java CocoaComponent compatibility mode]: Enabled
2012-07-17 19:07:42.505 java[417:407] [Java CocoaComponent compatibility mode]: Setting timeout for SWT to 0.100000
Jul 17, 2012 2:07:49 PM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Jul 17, 2012 2:07:50 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed /Volumes/DATA 1/Google App Engine/Java/HelloWorld/war/WEB-INF/appengine-web.xml
Jul 17, 2012 2:07:50 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed /Volumes/DATA 1/Google App Engine/Java/HelloWorld/war/WEB-INF/web.xml
Jul 17, 2012 7:07:52 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at localhost:8888/
Jul 17, 2012 7:07:52 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at localhost:8888/_ah/admin
Log when Run from command line:
Jul 21, 2012 3:23:19 PM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Jul 21, 2012 3:23:19 PM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed /Volumes/DATA 1/Softwares/appengine-java-sdk-1.7.0/demos
/guestbook/war/WEB-INF/appengine-web.xml
Jul 21, 2012 3:23:19 PM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed /Volumes/DATA 1/Softwares/appengine-java-sdk-1.7.0/demos/guestbook/war/WEB-INF/web.xml
Jul 21, 2012 8:23:22 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at http://localhost:8080/
Jul 21, 2012 8:23:23 PM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at http://localhost:8080/_ah/admin
Check the following:
1) If the application has actually started. Enter "ps ax | grep java" in terminal
2) If the application has bound to the port. Install nmap (not sure how to do it on mac) and run it with "nmap localhost". You will see a list of ports and protocols used. If you don't see 8888 with http then something is wrong.
Have you tried running it from the command line? It looks like you're trying to start it in the debugger as well.. no? Try running from the command line, make sure that works. Then try running it from eclipse with "Run" not "Debug" and make sure that works before trying the debugger. Appengine is a little bit particular...
i downloaded the google app engine plugin for eclipse and i opened a new web project.
but when i try to run this project (untouched) the eclipse say:
"The server is running at http://localhost:8888/"
so i opened the browser and i get 101 error
"The connection to localhost was interrupted."
what i did wrong?
here is what the console present:
Dec 21, 2011 12:10:03 AM com.google.apphosting.utils.jetty.JettyLogger info
INFO: Logging to JettyLogger(null) via com.google.apphosting.utils.jetty.JettyLogger
Dec 21, 2011 12:10:03 AM com.google.apphosting.utils.config.AppEngineWebXmlReader readAppEngineWebXml
INFO: Successfully processed C:\Users\sl300\Synca\try2\war\WEB-INF/appengine-web.xml
Dec 21, 2011 12:10:03 AM com.google.apphosting.utils.config.AbstractConfigXmlReader readConfigXml
INFO: Successfully processed C:\Users\sl300\Synca\try2\war\WEB-INF/web.xml
Dec 21, 2011 2:10:04 AM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The server is running at http://localhost:8888/
Dec 21, 2011 2:10:04 AM com.google.appengine.tools.development.DevAppServerImpl start
INFO: The admin console is running at http://localhost:8888/_ah/admin
(little details: i have windows vista, eclipse Helios Service Release 2.
i tried with jre6 or jre7 )
This can occur because of your 'Hosts File Configuration' or 'Proxy settings' or 'Anti-Virus software on your system' or if you are using web-debugging/http-logging tools like Fiddler or TCPMon. Correct the configuration if it is not properly set and try it again.
I downloaded Apache Tomcat 7.x. When I add this Tomcat in Eclipse I get this error:
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:05 PM org.apache.catalina.core.AprLifecycleListener init
SEVERE: An incompatible version 1.1.12 of the APR based Apache Tomcat Native library is installed, while Tomcat requires version 1.1.17
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler init
INFO: Initializing ProtocolHandler ["ajp-bio-8009"]
Jan 25, 2011 3:21:08 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 3054 ms
Jan 25, 2011 3:21:08 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
Jan 25, 2011 3:21:08 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.6
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["http-bio-8080"]
Jan 25, 2011 3:21:08 PM org.apache.coyote.AbstractProtocolHandler start
INFO: Starting ProtocolHandler ["ajp-bio-8009"]
Jan 25, 2011 3:21:08 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 251 ms
How can I solve this problem?
When I open the localhost:8080/manager/html it shows the following error:
HTTP Status 404 - /manager/html
type Status report
message /manager/html
description The requested resource (/manager/html) is not available.
Apache Tomcat/7.0.6
The first error certainly sounds like a version mismatch. The APR library is a library linked in at runtime based on your path (which itself can be based on where you execute Tomcat from). It sounds like you have the APR library for Tomcat 6. It's possible that Eclipse is providing this APR library.
Tomcat ships with an APR library but in order to ease installation Tomcat doesn't automatically modify the path to point at the APR library. The Eclipse Tomcat integration may (I'm not sure on this one, haven't used the integration before) include the APR libraries to make it easier to use Tomcat.
Check and make sure that Eclipse isn't configured to use an earlier version of Tomcat and if it is, either upgrade Eclipse to Tomcat 7 or downgrade Tomcat to the version specified in Eclipse.
If you can't figure it out then you don't necessarily have to worry about it at the moment. Tomcat should work anyways without the APR libraries. The only benefit you will get from the APR libraries is increased performance and since this is probably the start of your project that doesn't have to be worked out right away.
The second issue, the /manager/ page, could be Tomcat configuration. Tomcat won't actually display the manager page (and it will give you that error) unless users have been configured with manager permissions.
Try going to just / (i.e. http://localhost:8080), that page should load regardless of user configuration.
In my case I had inadvertently installed the APR library when I install once Tomcat locally on my Linux using the package manager. On Debian/Ubuntu this installed the APR package for a different Tomcat version (the one bundled with your distribution) which caused this error.
After simply
sudo apt-get purge libtcnative-1
The error was gone.