[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-30 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















That folder contains only:

(...)
-rw-r--r--   1 tomcat tomcat 3587099 Apr 30 10:54 sc-4.3-linux.tar.gz
drwxr-xr-x   5 tomcat tomcat4096 Dec 19 17:13 sc-4.3.6-linux
(...)


I will delete those manually - as I noticed that the plugin will then generate the sc-4.3.8-linux it needs.
Will you please fix this problem as well?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-30 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















I updated to 1.128.
I get this error now:

Starting Sauce Connect on master node using identifier: default
Launching Sauce Connect on ip-10-197-79-50
FATAL: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory
com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectException: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:358)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279)
	at hudson.model.Build$BuildExecution.doRun(Build.java:156)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
	at hudson.model.Run.execute(Run.java:1744)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:374)
Caused by: java.io.IOException: Cannot run program "/usr/share/tomcat7/sc-4.3.8-linux/bin/sc" (in directory "/usr/share/tomcat7/sc-4.3.8-linux"): error=2, No such file or directory
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:286)
	... 8 more
Caused by: java.io.IOException: error=2, No such file or directory
	at java.lang.UNIXProcess.forkAndExec(Native Method)
	at java.lang.UNIXProcess.init(UNIXProcess.java:135)
	at java.lang.ProcessImpl.start(ProcessImpl.java:130)
	at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
	... 9 more




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-30 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Yes, the job ran (sauce connect worked although job failed due to a test) and produced those 4.3.8 folders:

(...)
-rw-r--r--   1 tomcat tomcat 3596050 Apr 30 12:17 sc-4.3-linux.tar.gz
drwxr-xr-x   5 tomcat tomcat4096 Apr 30 12:17 sc-4.3.8-linux
(...)




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-30 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















I will. Currently some other job is running, so I'm waiting for it to run again.
But the thing above is not new - I also mentioned it in case description. So you didn't introduce it now.
If it behaves as in the past the /usr/share/tomcat7/sc-4.3.8-linux will appear when next sauce-using job runs.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-30 Thread piar...@gmail.com (JIRA)














































Ross Rowe
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Okay, I'm not sure why this error is occuring, as I didn't change the code which launches Sauce Connect in this version. The code should be attempting to extract the .tar.gz file from the Sauce plugin, and expand the contents into the /usr/share/tomcat7/sc-4.3.8-linux directory.

After removing the files in the directory, can you clarify whether the /usr/share/tomcat7/sc-4.3.8-linux directory exists?  You can also specify a different working directory for Sauce Connect via the 'Manage Jenkins' - 'Configure System' page



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-29 Thread piar...@gmail.com (JIRA)














































Ross Rowe
 started work on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















Change By:


Ross Rowe
(29/Apr/15 11:14 AM)




Status:


Open
InProgress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-29 Thread piar...@gmail.com (JIRA)














































Ross Rowe
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Okay, I've just released version 1.128 which should ensure that all open tunnels are closed, when you get a chance could you try this version out? 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-29 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Thank you.
I will update and let you know in case I still see it (hopefully not).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-29 Thread costescuand...@skymail.ro (JIRA)












































 
Andrei Costescu
 edited a comment on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















Thank you.
I will update and let you know in case I still see it (hopefully not).

How long does it take for me to see the new version? (still 1.127 is latest on plugin wiki page and in Jenkins config)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-29 Thread costescuand...@skymail.ro (JIRA)












































 
Andrei Costescu
 edited a comment on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















Thank you.
I will update and let you know in case I still see it (hopefully not).

How long does it take for me to see the new version? (still 1.127 is latest on plugin wiki page and in Jenkins config)
I think the plugin's build itself is failing. Maybe that's why Jenkins doesn't show the update.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-25 Thread piar...@gmail.com (JIRA)














































Ross Rowe
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Thanks for letting me know, I've developed an update to the plugin which should ensure that all opened tunnels are closed when the 'can't lock pidfile' error is generated, I'm just doing some testing of this and I'll let you know when it's ready.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-24 Thread costescuand...@skymail.ro (JIRA)












































 
Andrei Costescu
 edited a comment on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















Meanwhile I found out why my two jobs were starting at the same time: https://issues.jenkins-ci.org/browse/JENKINS-28084
It seems Jenkins core had a problem that affected the Throttle Concurrent Builds plugin.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-24 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Meanwhile I found out why my two jobs were starting at the same time: https://issues.jenkins-ci.org/browse/JENKINS-28084



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-17 Thread piar...@gmail.com (JIRA)















































Ross Rowe
 assigned  JENKINS-27884 to Ross Rowe



Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















Change By:


Ross Rowe
(17/Apr/15 7:55 AM)




Assignee:


KohsukeKawaguchi
RossRowe



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-17 Thread piar...@gmail.com (JIRA)














































Ross Rowe
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Thanks for letting us know, for the 'use latest browser' error, can you tell me what browser you had selected?  The v1.125 version of the plugin does attempt to resolve the 'can't lock pidfile' error, and the sc process tends to take a while to close.  It might be worth trying v1.125 again and taking a look at the errors that are written to the sc.log file.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-17 Thread piar...@gmail.com (JIRA)














































Ross Rowe
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Okay, thanks for letting me know, and apologies for missing the bit about the use latest version...I'll try to add some functionality to the plugin to forcibly close any rogue sc processes, and I'll let you know when I have a new version available.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-17 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















I had no browser selected. Explained in description why.

Indeed the above were from version 1.113 where it also happened once immediately after downgrade (probably because of a 'sc defunct' process).
Anyway here it is from when I had it running with 1.125, then it started to fail again:

At 16:34 there was a successful run of the job.
At 18:34 the tests failed because of a problem with our app. server not starting and thus the unit tests could not connect to it; unit tests connect of 2 min timed out and the job failed.
At 19:14:35 I now see two jobs started simultaneously (one by a timer the other by a colleague manually starting it in the same second)! One succeeded and one failed with that error in console "Process count non-zero, but no active tunnels found - Process count reset to zero - FATAL: Unable to start Sauce Connect, please see the Sauce Connect log"
That should have been possible as the 2 jobs are configured to be mutually exclusive (using another plugin for that) and never saw them run at the same time before even if I started them both manually one after the other.
But anyway it still shouldn't make sauce plugin non-functional for all future jobs... All future jobs failed until I downgraded and killed processes.


20150410 163455.234 [01966] Sauce Connect 4.3.8, build 1671 0fa40e2
20150410 163455.235 [01966] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt.
20150410 163455.235 [01966] *** WARNING: open file limit 4096 is too low!
20150410 163455.235 [01966] *** Sauce Labs recommends setting it to at least 8000.
20150410 163455.235 [01966] Trying to autodetect proxy settings
20150410 163455.235 [01966] Starting up; pid 1966
20150410 163455.235 [01966] Command line arguments: /usr/share/tomcat7/sc-4.3.8-linux/bin/sc -u *** -k  -P 4445
20150410 163455.236 [01966] Using no proxy for connecting to Sauce Labs REST API.
20150410 163455.237 [01966] Resolving saucelabs.com to 162.222.73.28 took 1 ms.
20150410 163456.140 [01966] PROXY *** scproxy started ***
20150410 163456.141 [01966] PROXY found DNS server 172.16.0.23
20150410 163456.190 [01966] Started scproxy on port 46880.
20150410 163456.190 [01966] Please wait for 'you may start your tests' to start your tests.
20150410 163456.190 [01966] Starting secure remote tunnel VM...
20150410 163502.660 [01966] Secure remote tunnel VM provisioned.
20150410 163502.660 [01966] Tunnel ID: fa3516d6947745628480895860b3bb18
20150410 163503.576 [01966] Secure remote tunnel VM is now: booting
20150410 163513.145 [01966] Secure remote tunnel VM is now: running
20150410 163513.145 [01966] Remote tunnel host is: maki77078.miso.saucelabs.com
20150410 163513.145 [01966] Using no proxy for connecting to tunnel VM.
20150410 163513.166 [01966] Resolving maki77078.miso.saucelabs.com to 162.222.77.78 took 21 ms.
20150410 163513.166 [01966] Starting Selenium listener...
20150410 163513.167 [01966] Establishing secure TLS connection to tunnel...
20150410 163513.167 [01966] [EVDNS] Added nameserver 172.16.0.23:53 as 0x7f44b0004c70
20150410 163513.168 [01966] Selenium listener started on port 4445.
20150410 163513.363 [01966] MAIN connecting to KGP server 162.222.77.78 took 195 ms
20150410 163513.365 [01966] MAIN warning, failed to set KGP bufferevent priority to 0
20150410 163516.378 [01966] Sauce Connect is up, you may start your tests.
20150410 163516.378 [01966] Connection established.
20150410 163724.106 [01966] PROXY resolved 'localhost' to '127.0.0.1'
(...) many many PROXY lines when running tests (...)
20150410 164056.602 [01966] PROXY 127.0.0.1:48955 - 200 localhost:8089 (196 bytes)
20150410 164101.193 [01966] Cleaning up.
20150410 164102.171 [01966] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy
20150410 164102.171 [01966] Overlapping domain: sauce-connect.proxy, shutting down tunnel fa3516d6947745628480895860b3bb18.
20150410 164109.020 [01966] KGP warning: no keepalive ack for  5s
20150410 164109.424 [01966] Goodbye.


20150410 183415.744 [09736] Sauce Connect 4.3.8, build 1671 0fa40e2
20150410 183415.745 [09736] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt.
20150410 183415.745 [09736] *** WARNING: open file limit 4096 is too low!
20150410 183415.745 [09736] *** Sauce Labs recommends setting it to at least 8000.
20150410 183415.745 [09736] Trying to autodetect proxy settings
20150410 

[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-17 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Np. I'm glad you are looking at it .



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-17 Thread costescuand...@skymail.ro (JIRA)












































 
Andrei Costescu
 edited a comment on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















I had no browser selected. Explained in description why.

Indeed the above were from version 1.113 where it also happened once immediately after downgrade (probably because of a 'sc defunct' process).
Anyway here it is from when I had it running with 1.125, then it started to fail again:

At 16:34 there was a successful run of the job.
At 18:34 the tests failed because of a problem with our app. server not starting and thus the unit tests could not connect to it; unit tests connect of 2 min timed out and the job failed.
At 19:14:35 I now see two jobs started simultaneously (one by a timer the other by a colleague manually starting it in the same second)! One succeeded and one failed with that error in console "Process count non-zero, but no active tunnels found - Process count reset to zero - FATAL: Unable to start Sauce Connect, please see the Sauce Connect log"
That should not have been possible as the 2 jobs are configured to be mutually exclusive (using another plugin for that) and never saw them run at the same time before even if I started them both manually one after the other.
But anyway it still shouldn't make sauce plugin non-functional for all future jobs... All future jobs failed until I downgraded and killed processes.


20150410 163455.234 [01966] Sauce Connect 4.3.8, build 1671 0fa40e2
20150410 163455.235 [01966] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt.
20150410 163455.235 [01966] *** WARNING: open file limit 4096 is too low!
20150410 163455.235 [01966] *** Sauce Labs recommends setting it to at least 8000.
20150410 163455.235 [01966] Trying to autodetect proxy settings
20150410 163455.235 [01966] Starting up; pid 1966
20150410 163455.235 [01966] Command line arguments: /usr/share/tomcat7/sc-4.3.8-linux/bin/sc -u *** -k  -P 4445
20150410 163455.236 [01966] Using no proxy for connecting to Sauce Labs REST API.
20150410 163455.237 [01966] Resolving saucelabs.com to 162.222.73.28 took 1 ms.
20150410 163456.140 [01966] PROXY *** scproxy started ***
20150410 163456.141 [01966] PROXY found DNS server 172.16.0.23
20150410 163456.190 [01966] Started scproxy on port 46880.
20150410 163456.190 [01966] Please wait for 'you may start your tests' to start your tests.
20150410 163456.190 [01966] Starting secure remote tunnel VM...
20150410 163502.660 [01966] Secure remote tunnel VM provisioned.
20150410 163502.660 [01966] Tunnel ID: fa3516d6947745628480895860b3bb18
20150410 163503.576 [01966] Secure remote tunnel VM is now: booting
20150410 163513.145 [01966] Secure remote tunnel VM is now: running
20150410 163513.145 [01966] Remote tunnel host is: maki77078.miso.saucelabs.com
20150410 163513.145 [01966] Using no proxy for connecting to tunnel VM.
20150410 163513.166 [01966] Resolving maki77078.miso.saucelabs.com to 162.222.77.78 took 21 ms.
20150410 163513.166 [01966] Starting Selenium listener...
20150410 163513.167 [01966] Establishing secure TLS connection to tunnel...
20150410 163513.167 [01966] [EVDNS] Added nameserver 172.16.0.23:53 as 0x7f44b0004c70
20150410 163513.168 [01966] Selenium listener started on port 4445.
20150410 163513.363 [01966] MAIN connecting to KGP server 162.222.77.78 took 195 ms
20150410 163513.365 [01966] MAIN warning, failed to set KGP bufferevent priority to 0
20150410 163516.378 [01966] Sauce Connect is up, you may start your tests.
20150410 163516.378 [01966] Connection established.
20150410 163724.106 [01966] PROXY resolved 'localhost' to '127.0.0.1'
(...) many many PROXY lines when running tests (...)
20150410 164056.602 [01966] PROXY 127.0.0.1:48955 - 200 localhost:8089 (196 bytes)
20150410 164101.193 [01966] Cleaning up.
20150410 164102.171 [01966] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy
20150410 164102.171 [01966] Overlapping domain: sauce-connect.proxy, shutting down tunnel fa3516d6947745628480895860b3bb18.
20150410 164109.020 [01966] KGP warning: no keepalive ack for  5s
20150410 164109.424 [01966] Goodbye.


20150410 183415.744 [09736] Sauce Connect 4.3.8, build 1671 0fa40e2
20150410 183415.745 [09736] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt.
20150410 183415.745 [09736] *** WARNING: open file limit 4096 is too low!
20150410 183415.745 [09736] *** Sauce Labs recommends setting it to at least 8000.
20150410 183415.745 [09736] Trying to autodetect proxy settings

[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-16 Thread costescuand...@skymail.ro (JIRA)












































 
Andrei Costescu
 edited a comment on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















Each time I kill the hanging processes, first job succeeds then the following ones fail and 'sc' processes linger around.
I restarted the server completely, then asked 3 sauce jobs to run (which ended up in the build queue waiting to finish one by one).

Even though only the first job was running there were two 'sc' processes running. Second and third job failed as above and now Jenkins is stale - but 'sc' processes still linger around.

Starting Sauce Connect on master node using identifier: default
Launching Sauce Connect on ***
Process count non-zero, but no active tunnels found
Process count reset to zero
FATAL: Unable to start Sauce Connect, please see the Sauce Connect log
com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:308)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279)
	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
(...)




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-16 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 updated  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125
















Change By:


Andrei Costescu
(16/Apr/15 9:00 AM)




Priority:


Minor
Major



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-16 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















/tmp/sc.log confirms what I though

This is the content when a job that doesn't leave hanging sc processes ends:

(...)
20150415 221730.677 [19514] PROXY 127.0.0.1:33135 - 200 localhost:8081 (196 bytes)
20150415 221736.064 [19514] Cleaning up.
20150415 221741.999 [19514] Checking domain overlap for my domain sauce-connect.proxy, other tunnel domain sauce-connect.proxy
20150415 221741.999 [19514] Overlapping domain: sauce-connect.proxy, shutting down tunnel e66ea3aead4a4656b725fd4b99ccc66c.
20150415 221746.686 [19514] Goodbye.
(...)



This is the content when a job that does leave hanging sc processes ends (any following job using sauce plugin will fail):

(...)
20150416 113808.029 [00744] PROXY 127.0.0.1:51525 - 200 localhost:8081 (196 bytes)
20150416 113816.646 [00744] Cleaning up.
(...)


So I think that is what causes the whole problem - no Goodbye..

The following jobs will fail with:

(...)
20150416 121716.618 [07153] Sauce Connect 4.3.6, build 1628 8a5c837
20150416 121716.618 [07153] Using CA certificate bundle /etc/ssl/certs/ca-bundle.crt.
20150416 121716.618 [07153] Warning, open file limit 4096 is too low.
20150416 121716.618 [07153] Sauce Labs recommends setting it to at least 8000.
20150416 121716.618 [07153] Trying to autodetect proxy settings
20150416 121716.618 [07153] can't lock pidfile /tmp/sc_client.pid. Please check if Sauce Connect is already running.
20150416 121716.618 [07153] Error creating pidfile /tmp/sc_client.pid.
(...)


All jobs that pass show in console the same (so both the job that leaves processes behind and the one that is ok):

(...)
Shutting down Sauce Connect
Decremented process count for ***, now 0
Flushing Sauce Connect Input Stream
Flushing Sauce Connect Error Stream
Closing Sauce Connect process
Sauce Connect stopped for: ***
(...)


We fixed meanwhile the open file limit warning and we will try to run Jenkins with newer java version (1.6.x was used before).
Although those are probably not the causes.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-15 Thread costescuand...@skymail.ro (JIRA)














































Andrei Costescu
 commented on  JENKINS-27884


Doesnt work with: Jenkins1.608 with Sauce on demand plugin 1.125















Each time I kill the hanging processes, first job succeeds then the following ones fail and 'sc' progesses linger around.
I restarted the server completely, then asked 3 sauce jobs to run (which ended up in the build queue waiting to finish one by one).

Even though only the first job was running there were two 'sc' processes running. Second and third job failed as above and now Jenkins is stale - but 'sc' processes still linger around.

Starting Sauce Connect on master node using identifier: default
Launching Sauce Connect on ***
Process count non-zero, but no active tunnels found
Process count reset to zero
FATAL: Unable to start Sauce Connect, please see the Sauce Connect log
com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:308)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279)
	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
(...)




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.