[jira] Created: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
Permission denied using setuid on Fedora Core 4 and 5
-----------------------------------------------------

                 Key: JETTY-444
                 URL: http://jira.codehaus.org/browse/JETTY-444
             Project: Jetty
          Issue Type: Bug
          Components: Security and SSL
    Affects Versions: 6.1.6rc0
         Environment: Fedora Core 4 (and 5)
            Reporter: Matt Sheppard


It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.

I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.

I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).

For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.




[root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
2007-10-17 10:44:04.849::INFO: Setting UID=514
2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
java.net.SocketException: Permission denied
        at sun.nio.ch.Net.bind(Native Method)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
        at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
        at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at org.mortbay.jetty.Server.doStart(Server.java:233)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.mortbay.start.Main.invokeMain(Main.java:194)
        at org.mortbay.start.Main.start(Main.java:509)
        at org.mortbay.start.Main.main(Main.java:119)
2007-10-17 10:44:05.208::WARN: failed Server@364641
...


--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

Re: [jira] Created: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

Chris Haynes
Even with SELinux disabled, I think most Linus distros prohibit non-root users from opening sockets < 1024.

I suggest you try a simple Java program to test this - so as to rule in/out Jetty.

Something like this should do it:

public class Test{ public static void main(String[] args)
throws java.io.IOException{new java.net.ServerSocket(80);}}

On my SuSE 10 with no SELinux this throws an exception with 80, but not with 8000.

HTH

Chris Haynes

On Thursday, October 18, 2007 at 6:06:52 AM, Matt Sheppard (JIRA) wrote:
> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------

>                  Key: JETTY-444
>                  URL: http://jira.codehaus.org/browse/JETTY-444
>              Project: Jetty
>           Issue Type: Bug
>           Components: Security and SSL
>     Affects Versions: 6.1.6rc0
>          Environment: Fedora Core 4 (and 5)
>             Reporter: Matt Sheppard


> It's quite possible I'm doing something wrong here, but no one on
> the support list has been able to point out my error.

> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora
> Core 4 (and 5) as described in
> http://docs.codehaus.org/display/JETTY/port80.

> I'm getting a "java.net.SocketException: Permission denied" despite
> starting as root, but removing the setuid configuration file seems
> to fix the problem (though jetty's then running as root).

> For what it's worth I've confirmed the SELinux is disabled, and the
> same setup seems to work as expected on CentOS.





-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110375 ]

Jan Bartel commented on JETTY-444:
----------------------------------

Matt,

Well the good news is that the setuid part is working - you're trying to open the sockets as the non-privileged user instead of the root user you ran the process as :-) The problem is that the opening of the sockets is supposed to happen before the switch to the non-privileged user.

Can you attach your xml config files?

regards
Jan

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Sheppard updated JETTY-444:
--------------------------------

    Attachment: 444-setuid.xml
                444-conf.xml

Thanks Jan...

I've trimmed it down a bit, so I'm not starting jetty with...

/opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/444-setuid.xml /opt/funnelback-matt/web/conf/444-conf.xml

using the two config files attached, and getting the following...


2007-10-22 09:52:06.317::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
2007-10-22 09:52:06.514::INFO:  jetty-6.1.6rc0
2007-10-22 09:52:06.534::INFO:  Setting UID=514
2007-10-22 09:52:06.536::INFO:  jetty-6.1.6rc0
2007-10-22 09:52:06.599::WARN:  failed SelectChannelConnector@0.0.0.0:81
java.net.SocketException: Permission denied
        at sun.nio.ch.Net.bind(Native Method)
        at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
        at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
        at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
        at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at org.mortbay.jetty.Server.doStart(Server.java:233)
        at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
        at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        at java.lang.reflect.Method.invoke(Method.java:597)
        at org.mortbay.start.Main.invokeMain(Main.java:194)
        at org.mortbay.start.Main.start(Main.java:509)
        at org.mortbay.start.Main.main(Main.java:119)
2007-10-22 09:52:06.602::WARN:  failed Server@142bece
(and two more similar exceptions)

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110711 ]

Matt Sheppard commented on JETTY-444:
-------------------------------------

Oops...make that...

...so I'm NOW starting jetty with...


> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110726 ]

Jan Bartel commented on JETTY-444:
----------------------------------

Matt,

You should change your 444-setuid.xml file thus:

 <Set name="startServerAsPrivileged">false</Set>

This will ensure that only the ports are being opened as the superuser, then for the rest of the startup sequence the non-privileged user will be used.

Please test again with the new setting. If that works for you, then I'll close the issue.

regards
Jan

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Assigned: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bartel reassigned JETTY-444:
--------------------------------

    Assignee: Jan Bartel

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>            Assignee: Jan Bartel
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110741 ]

Jan Bartel commented on JETTY-444:
----------------------------------

Uh, one more thing - your 444-conf.xml file does not have id=Server in the first line. This id links up the server instance from the 444-setuid.xml file. Without it, the second config file will create a different server instance. Which could be the major part of your problem :-)

But, try what I suggested anyway, as it is much cleaner to only start the connectors as the super user and then revert to the non-privileged user.

regards
Jan

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>            Assignee: Jan Bartel
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110756 ]

Matt Sheppard commented on JETTY-444:
-------------------------------------

Ahhh, ok...

Just tried the first suggestion and it didn't make a difference (I had previously tried it with both settings as I wasn't really sure what it should do).

The second, however, seems to stop the error from occurring. I'll do a bit more testing and confirm that it's all working as expected.

Thanks, Matt Sheppard

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>            Assignee: Jan Bartel
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Commented: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

    [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110922 ]

Matt Sheppard commented on JETTY-444:
-------------------------------------

Thanks Jan, It's now working well now (thanks to the id="Server" change).

Not sure if it should have worked without, so I'll leave this one for you to close or not as you think best.

Thanks for your help,
Matt Sheppard

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>            Assignee: Jan Bartel
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss
Reply | Threaded
Open this post in threaded view
|

[jira] Closed: (JETTY-444) Permission denied using setuid on Fedora Core 4 and 5

JIRA jira@codehaus.org
In reply to this post by JIRA jira@codehaus.org

     [ http://jira.codehaus.org/browse/JETTY-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Bartel closed JETTY-444.
----------------------------

    Resolution: Won't Fix

Hi Matt,
Yes, the consistency of the id is key to making this work, so I'm closing this as not a bug.

cheers
Jan

> Permission denied using setuid on Fedora Core 4 and 5
> -----------------------------------------------------
>
>                 Key: JETTY-444
>                 URL: http://jira.codehaus.org/browse/JETTY-444
>             Project: Jetty
>          Issue Type: Bug
>          Components: Security and SSL
>    Affects Versions: 6.1.6rc0
>         Environment: Fedora Core 4 (and 5)
>            Reporter: Matt Sheppard
>            Assignee: Jan Bartel
>         Attachments: 444-conf.xml, 444-setuid.xml
>
>
> It's quite possible I'm doing something wrong here, but no one on the support list has been able to point out my error.
> I'm having rouble using setuid to bind to port 81 (or 80) on Fedora Core 4 (and 5) as described in http://docs.codehaus.org/display/JETTY/port80.
> I'm getting a "java.net.SocketException: Permission denied" despite starting as root, but removing the setuid configuration file seems to fix the problem (though jetty's then running as root).
> For what it's worth I've confirmed the SELinux is disabled, and the same setup seems to work as expected on CentOS.
> [root@blue jetty]# /opt/funnelback-matt/linbin/jdk1.6.0_03/bin/java -jar start.jar /opt/funnelback-matt/web/conf/jetty-setuid.xml /opt/funnelback-matt/web/conf/funnelback-jetty-https.xml /opt/funnelback-matt/web/conf/funnelback-jetty-http.xml;
> 2007-10-17 10:44:04.580::INFO: Logging to STDERR via org.mortbay.log.StdErrLog
> 2007-10-17 10:44:04.849::INFO: Setting UID=514
> 2007-10-17 10:44:04.851::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:04.868::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.180::INFO: Started SslSocketConnector@0.0.0.0:8443
> 2007-10-17 10:44:05.180::INFO: jetty-6.1.6rc0
> 2007-10-17 10:44:05.205::WARN: failed SelectChannelConnector@0.0.0.0:81
> java.net.SocketException: Permission denied
>         at sun.nio.ch.Net.bind(Native Method)
>         at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:119)
>         at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:59)
>         at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:204)
>         at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:302)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.jetty.Server.doStart(Server.java:233)
>         at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:40)
>         at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:977)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:597)
>         at org.mortbay.start.Main.invokeMain(Main.java:194)
>         at org.mortbay.start.Main.start(Main.java:509)
>         at org.mortbay.start.Main.main(Main.java:119)
> 2007-10-17 10:44:05.208::WARN: failed Server@364641
> ...

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
jetty-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jetty-discuss