[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
kutzi commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Did you look into http://stackoverflow.com/questions/9330367/how-to-configure-jenkins-to-run-on-port-80 ? 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Thank you, but mine is a RHEL/CentOS flavor, and it is referencing the same process that is failing for me just in the Ubuntu OS. 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober edited a comment on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Thank you, and reading the page this is a similar issue. But mine is a RHEL/CentOS flavor, and it is referencing the same process that is failing for me in the Ubuntu OS. and references a fix that I do not know if there is a authbind system in RHEL/CentOS? 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
kutzi commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Yes, I've seen that you're using a different Linux flavor, but I think the general problem is the same. And furthermore I wanted to point out that this looks like a general Linux issue - i.e. that you cannot bind to a port 1024 with a non-root user - and not a Jenkins issue per se. If you search on the web you'll surely find several pages which describe how to solve this in general for RHEL. 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. I understand what you are saying about binding to the port it just like the Apache user for httpd and port 80, but this issue also manifest when I try to make this a headless system and change the port to -1 That is what lead me to this as an issue with the Jenkins system and not a port binding issue. 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Per the docs and the notes this setting should be modifiable, and the system should use the non-privileged user that is set it the /etc/sysconfig/jenkins 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober commented on JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. I need at least some sort of work around, or some kind of temporary fix. 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober updated JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Change By: C. Alex Reober (04/Mar/13 4:57 PM) Component/s: core Component/s: multi-slave-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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
rsandell assigned JENKINS-17008 to Unassigned Config changes stop Jenkins from running on next restart, stop/start, reboot. Change By: rsandell (05/Mar/13 7:10 AM) Assignee: rsandell 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/groups/opt_out.
[JIRA] (JENKINS-17008) Config changes stop Jenkins from running on next restart, stop/start, reboot.
C. Alex Reober created JENKINS-17008 Config changes stop Jenkins from running on next restart, stop/start, reboot. Issue Type: Bug Affects Versions: current Assignee: rsandell Components: multi-slave-config Created: 28/Feb/13 5:55 PM Description: Install Jenkins via RPM per instructions. (There is nothing else running on the system, i.e. httpd, etc.) Edit /etc/sysconfig/jenkins Change JENKINS_PORT from JENKINS_PORT="8080" to JENKINS_PORT="80" or any other setting (i.e. -1) Restart jenkins using service jenkins restart Get Starting Jenkins [ OK ] check status service jenkins status Get jenkins dead but pid file exists No information in logs of what, when, or why. Due Date: 08/Mar/13 12:00 AM Environment: AWS: AWS Linux 3.2.12-3.2.4.amzn1.x86_64 AMI: ami-f619c29f Zone: us-east-1d Project: Jenkins Labels: jenkins configuration Priority: Major Reporter: C. Alex Reober 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/groups/opt_out.
