[INTDIST-56] unable to start karaf offline Created: 12/Jul/16  Updated: 20/Oct/17  Resolved: 04/Aug/16

Status: Resolved
Project: integration-distribution
Component/s: Karaf
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Peter Gubka Assignee: Vratko Polak
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Zip Archive karaf.log.zip    
External issue ID: 6187

 Description   

odl: distribution-karaf-0.5.0-20160706.150806-3364.zip

after unzipping the only chcanges done were :

setting etc/org.apache.karaf.features.cfg
featuresBoot=config,standard,region,package,kar,ssh,management,odl-restconf,odl-bgpcep-pcep-all,odl-bgpcep-bgp-all,odl-bgpcep-bgp,odl-bgpcep-pcep,odl-netconf-connector-all,odl-bgpcep-data-change-counter,odl-bgpcep-bmp

and setting default log to debug.

After several minutes nearly no ports are binded
sudo netstat -npl | grep java
tcp6 0 0 :::34503 :::* LISTEN 31617/java
tcp6 0 0 127.0.0.1:34896 :::* LISTEN 31617/java

snd nothing is happening.

See logs for detauils.



 Comments   
Comment by Peter Gubka [ 12/Jul/16 ]

Attachment karaf.log.zip has been added with description: karaf log

Comment by Jamo Luhrsen [ 22/Jul/16 ]

another example:

[odl@localhost bin]$ ./karaf clean
karaf: JAVA_HOME not set; results may vary
Apache Karaf starting up. Press Enter to open the shell now...
100% [========================================================================]

Karaf started in 4s. Bundle stats: 37 active, 37 total

________ ________ .__ .__ .__ __
_____ \ ______ ____ ____ ______ \ _____ __..| | || ____ | |_/ |
/ |
____ _/ __ \ / \ | |
__ \< | || | | |/ ___| | \ __\
/ | \ |> > ___/| | | ` \/ __
___ || |
| / /_/ > Y \ |
_______ / _/ __ >__| /______ (____ / ___||__/__ /|__| /_|
\/|_| \/ \/ \/ \/\/ /____/ \/

Hit '<tab>' for a list of available commands
and '[cmd] --help' for help on a specific command.
Hit '<ctrl-d>' or type 'system:shutdown' or 'logout' to shutdown OpenDaylight.

opendaylight-user@root>feature:install odl-openflowplugin-all
Error executing command: Error resolving artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.0.2: Could not transfer artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.0.2 from/to central (http://repo1.maven.org/maven2/): repo1.maven.org: unknown error
opendaylight-user@root>

Comment by Vratko Polak [ 26/Jul/16 ]

Confirmed in Recent Boron [0], not present in Beryllium.

[0] https://logs.opendaylight.org/releng/jenkins092/integration-distribution-offline-boron/281/archives/karaf.log.gz

Comment by Ricardo Noriega [ 28/Jul/16 ]

Deploying Boron in an isolated server (no Internet connectivity) gave me these errors, which seem to be caused by the same issue:

Caused by: shaded.org.eclipse.aether.transfer.ArtifactTransferException: Could not transfer artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.0.2 from/to central (http://repo1.maven.org/maven2/): repo1.maven.org: unknown error
at shaded.org.eclipse.aether.connector.basic.ArtifactTransportListener.transferFailed(ArtifactTransportListener.java:43)
at shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:355)
at shaded.org.eclipse.aether.util.concurrency.RunnableErrorForwarder$1.run(RunnableErrorForwarder.java:67)
at shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$DirectExecutor.execute(BasicRepositoryConnector.java:581)
at shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector.get(BasicRepositoryConnector.java:249)
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:520)
at shaded.org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
... 62 more
Caused by: shaded.org.apache.maven.wagon.TransferFailedException: repo1.maven.org: unknown error
at shaded.org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1085)
at shaded.org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:977)
at shaded.org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
at shaded.org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at shaded.org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at shaded.org.eclipse.aether.transport.wagon.WagonTransporter$GetTaskRunner.run(WagonTransporter.java:560)
at shaded.org.eclipse.aether.transport.wagon.WagonTransporter.execute(WagonTransporter.java:427)
at shaded.org.eclipse.aether.transport.wagon.WagonTransporter.get(WagonTransporter.java:404)
at shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$GetTaskRunner.runTask(BasicRepositoryConnector.java:447)
at shaded.org.eclipse.aether.connector.basic.BasicRepositoryConnector$TaskRunner.run(BasicRepositoryConnector.java:350)
... 67 more
Caused by: java.net.UnknownHostException: repo1.maven.org: unknown error
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)[:1.8.0_101]
at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:928)[:1.8.0_101]
at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1323)[:1.8.0_101]
at java.net.InetAddress.getAllByName0(InetAddress.java:1276)[:1.8.0_101]
at java.net.InetAddress.getAllByName(InetAddress.java:1192)[:1.8.0_101]
at java.net.InetAddress.getAllByName(InetAddress.java:1126)[:1.8.0_101]
at shaded.org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:44)
at shaded.org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:101)
at shaded.org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:318)
at shaded.org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
at shaded.org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
at shaded.org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
at shaded.org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
at shaded.org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
at shaded.org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
at shaded.org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
at org.ops4j.pax.url.mvn.internal.wagon.ConfigurableHttpWagon.execute(ConfigurableHttpWagon.java:142)
at shaded.org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:1000)
... 76 more
2016-07-28 13:49:00,780 | ERROR | Event Dispatcher | BootFeaturesInstaller | 20 - org.apache.karaf.features.core - 3.0.6 | Error getting feature for feature string kar
java.io.IOException: Error resolving artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.0.2: Could not transfer artifact org.apache.cxf.karaf:apache-cxf:xml:features:3.0.2 from/to central (http://repo1.maven.org/maven2/): repo1.maven.org: unknown error
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:626)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:570)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:548)
at org.ops4j.pax.url.mvn.internal.AetherBasedResolver.resolve(AetherBasedResolver.java:523)
at org.ops4j.pax.url.mvn.internal.Connection.getInputStream(Connection.java:123)

Comment by Tim Rozet [ 03/Aug/16 ]

What is the ETA for fixing this? We are blocked on OPNFV until this gets resolved.

Comment by Jamo Luhrsen [ 03/Aug/16 ]

(In reply to Timothy Rozet from comment #4)
> What is the ETA for fixing this? We are blocked on OPNFV until this gets
> resolved.

Fix in the works, Tim.
https://git.opendaylight.org/gerrit/#/c/42842/

hopefully it gets merged soon.

Comment by Vratko Polak [ 04/Aug/16 ]

Verified on RelEng Jenkins: https://jenkins.opendaylight.org/releng/view/integration/job/integration-distribution-offline-boron/293/

Comment by Vratko Polak [ 04/Aug/16 ]

Cherry-pick to Beryllium is not merged yet [0], but that version of Karaf does not complain (unless you try to install a feature that really requires apache-cxf).

[0] https://git.opendaylight.org/gerrit/43055

Comment by Stephen Kitt [ 04/Aug/16 ]

(In reply to Vratko Polák from comment #6)
> Verified on RelEng Jenkins:
> https://jenkins.opendaylight.org/releng/view/integration/job/integration-
> distribution-offline-boron/293/

That build used Karaf 3.0.7 (from https://git.opendaylight.org/gerrit/40818); it would be nice to have a 3.0.6 verification too I guess.

Comment by Vratko Polak [ 04/Aug/16 ]

Oh, I forgot patch test also triggers that job. I have scheduled #294.

Comment by Vratko Polak [ 04/Aug/16 ]

I just realized that there are no fixed builds available due to the Nexus upload issue, so I have un-scheduled the run.
Setting back to RESOLVED.

Generated at Wed Feb 07 20:02:39 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.