Bamboo fails to start on FreeBSD
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The following error is recorded during start-up
1
2
3
4
5
6
INFO | jvm 1 | 2012/08/16 22:37:06 | 2012-08-16 22:37:06,730 INFO [WrapperSimpleAppMain] [AccessLogFilter] AccessLogFilter initialized. Format is: <user> <url> <starting memory free (kb)> +- <difference in free mem (kb)> <query time (ms)>
INFO | jvm 1 | 2012/08/16 22:37:06 | 2012-08-16 22:37:06.876:WARN:oejuc.AbstractLifeCycle:FAILED org.eclipse.jetty.server.nio.SelectChannelConnector$ConnectorSelectorManager@1cc2c78: java.io.IOException: Function not implemented
INFO | jvm 1 | 2012/08/16 22:37:06 | java.io.IOException: Function not implemented
INFO | jvm 1 | 2012/08/16 22:37:06 | at sun.nio.ch.EPollArrayWrapper.epollCreate(Native Method)
INFO | jvm 1 | 2012/08/16 22:37:06 | at sun.nio.ch.EPollArrayWrapper.<init>(Unknown Source)
INFO | jvm 1 | 2012/08/16 22:37:06 | at sun.nio.ch.EPollSelectorImpl.<init>(Unknown Source)Cause
FreeBSD is unable to handle Java NIO calls.
Resolution
FreeBSD isn't a supported platform. We recommend using *nix variant such as Red Hat, Debian and etc.
If you would still use FreeBSD, there are some workarounds:
install Tomcat and deploy Bamboo WAR.
disable NIO in Jetty in favour of BIO by replacing the
SelectChannelConnectorinjetty.xmlwith aSocketConnector(this XML snippet:http://jira.codehaus.org/browse/JETTY-1441 looks helpful).
Was this helpful?