[ http://jira.magnolia-cms.com/browse/MAGNOLIA-1959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=21847#action_21847 ]
Giancarlo Berner commented on MAGNOLIA-1959: -------------------------------------------- I am experiencing the same issues. But only with a NEW installation. I got 3.5.4, 3.6.1, 3.6.3 and 4.0.1 installed. With 3.6.3 and 4.0, installed after updating to Mac OS X 10.5.6 (9G66), I have this issues, but not with the 3.5.4 and 3.6.1 installation. So that is confusing. Then I followed an advise by Zdenek and "unlocked/locked" the Firewall pane. While the installation of 4.0.1 EE worked fine, I could not start it. After the weird pane thing I could start Magnolia and install the modules. But now I have often images not loaded or weird styles, some garbled stuff. After a few refreshes the page though comes back again. This would speak for the maxfiles being set too low. The good news though is that I am finally getting an error message. I saw the socket error before, so not sure yet what relevance it. I will be trying to figure that out as soon as I get more time. But for those who are interested, here is a snippet of catalina.out: Mar 15, 2009 9:45:04 AM org.apache.coyote.http11.Http11BaseProtocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Mar 15, 2009 9:45:05 AM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Mar 15, 2009 9:45:05 AM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/184 config=null Mar 15, 2009 9:45:05 AM org.apache.catalina.storeconfig.StoreLoader load INFO: Find registry server-registry.xml at classpath resource Mar 15, 2009 9:45:05 AM org.apache.catalina.startup.Catalina start INFO: Server startup in 19739 ms Mar 15, 2009 10:13:07 AM org.apache.catalina.core.StandardServer await WARNING: StandardServer.await: read: java.net.SocketException: Invalid argument at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at java.net.SocketInputStream.read(SocketInputStream.java:182) at org.apache.catalina.core.StandardServer.await(StandardServer.java:402) at org.apache.catalina.startup.Catalina.await(Catalina.java:616) at org.apache.catalina.startup.Catalina.start(Catalina.java:576) 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:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Mar 15, 2009 10:13:07 AM org.apache.catalina.core.StandardServer await WARNING: StandardServer.await: Invalid command '' received Mar 16, 2009 10:33:48 PM org.apache.catalina.core.AprLifecycleListener lifecycleEvent INFO: The Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java Mar 16, 2009 10:33:48 PM org.apache.coyote.http11.Http11BaseProtocol init > Leopard (osx 10.5) issues > ------------------------- > > Key: MAGNOLIA-1959 > URL: http://jira.magnolia-cms.com/browse/MAGNOLIA-1959 > Project: Magnolia > Issue Type: Bug > Affects Versions: 3.5 > Reporter: Gregory Joseph > Assignee: Gregory Joseph > Fix For: 4.1 > > > h3. Leopard's application level firewall : > Leopard's firewall behaves significantly differently than the firewall > shipped with OSX 10.4. The symptoms are that Tomcat seems unreachable > ("kCFErrorDomainCFNetwork:302"), but unfortunately no log message *clearly* > identifies the issue. > It seems the behavior was different prior to OSX 10.5.3, but at least in > 10.5.4 the following seems to work: > - "allow incoming connections" for the Magnolia and Tomcat scripts > ({{magnolia_control.sh}}, {{startup.sh}}, {{shutdown.sh}}, {{catalina.sh}}), > as well as the Java binary (ie > {{/System/Library/Frameworks/JavaVM.framework/Versions/1.5.0/Commands/java}}) > - it seems sometimes necessary to "lock" and "unlock" the firewall settings > pane, so as to force it to take the new settings into account. > - if Magnolia was started, you'll have to kill it (-HUP works and shuts it > down nicely) and restart. > h4. More comments and questions > - somehow, setting the firewall too "allow all" does not seem to help. > - {{sudo launchctl remove com.apple.alf}} should remove the application-level > firewall, but for some reason, this hasn't proved very useful. Will have to > try again. > h4. Log files to watch: > * {{/var/log/system.log}} > * {{/var/log/secure.log}} > * {{/var/log/appfirewall.log}} > h4. Some interesting links: > * http://securosis.com/2007/11/01/investigating-the-leopard-firewall/ > * http://documentation.magnolia.info/administration.html#Knownissues which > links back to here but has a nice little screenshot of Leopard's firewall > configuration gui ;) > h3. "Max.files opened" > There might be some "max.files opened" issues, with settings which are > different from Tiger(10.4), although this hasn't been reported in a while. > There is unfortunately not much we can do about this issue at the moment, as > far as we know. > *Feel free to comment on your own experience below and contribute tips and > tricks !* -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.magnolia-cms.com/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------