Re: Problem updating to 4.2.7

Hi David, No problem. As the mailing list doesn't accept attachment, feel free to send to me directly. Thanks Regards JB On 30/10/2019 01:19, David Leangen wrote: Thanks JB, I’ll try to comb through the lists to figure out precisely what you mean by “a simple test”. Apologies for my

Re: Problem updating to 4.2.7

Thanks JB, I’ll try to comb through the lists to figure out precisely what you mean by “a simple test”. Apologies for my ignorance…  I’ll get back to you soon. Cheers, =David > On Oct 30, 2019, at 2:10, Jean-Baptiste Onofré wrote: > > Hi, > > the easy path would be the features XML

Re: Problem updating to 4.2.7

Hi, the easy path would be the features XML with a zip of your resources repository. A simple test should be enough. Thanks a lot ! Regards JB On 29/10/2019 11:13, David Leangen wrote: Hi JB, Sure! What would be the best way of doing that? I could give you a reference to my docker

Re: Problem updating to 4.2.7

Hi JB, Sure! What would be the best way of doing that? I could give you a reference to my docker image, config changes, and repo and you run it? Or give you access to a running server instance? Or something else? Cheers, =David > On Oct 29, 2019, at 17:45, Jean-Baptiste Onofré wrote:

Re: Problem updating to 4.2.7

Hi David, do you think you can have a simple test case you can send to me ? It would help to identify the issues between 4.2.0 and 4.2.1. Thanks, Regards JB On 29/10/2019 09:29, David Leangen wrote: 4.2.1 was a no-go. The same problem occurred as with 4.2.7. So it appears that the

Re: Problem updating to 4.2.7

4.2.1 was a no-go. The same problem occurred as with 4.2.7. So it appears that the problematic change got introduced sometime between 4.2.0 and 4.2.1. For now, I will try to get my system up and running in 4.2.0 if I can figure out the resolution problems, but it would still be great to

Re: Problem updating to 4.2.7

Hi, FYI it looks like 4.2.0 worked. I am having trouble with resolution of my bundles now, but at least the problem I was seeing in 4.2.7 is not there. I will give it a try with 4.2.1 next. Cheers, =David > On Oct 28, 2019, at 20:14, David Leangen wrote: > > > The owner of the file (as

Re: Problem updating to 4.2.7

The owner of the file (as well as the directory) is karaf.karaf. From /etc/passwd: karaf:x:1001:1001::/home/karaf:/bin/bash From /etc/group: karaf:x:1001: The owner of the docker process in which karaf is running is root. So I don’t think it’s a permissions problem. The etc directory is

Re: Problem updating to 4.2.7

Hmmm, does the user running Karaf has permission to read the file/folder ? Regards JB On 28/10/2019 08:11, David Leangen wrote: You amaze me! How are you so fast? Anyway… Again you’ll have to excuse my ignorance, but… [root@deimos features]# pwd /home/karaf/features [root@deimos

Re: Problem updating to 4.2.7

Hi, You can do: feature:repo-add file:/path/to/your/features.xml Then feature:install -v -t enroute Regards JB On 28/10/2019 07:56, David Leangen wrote: Hi, Excuse my ignorance… But given this feature file: http://karaf.apache.org/xmlns/features/v1.4.0;>   

Re: Problem updating to 4.2.7

Hi, Excuse my ignorance… But given this feature file: >name="enRoute Distribution Features" > xmlns="http://karaf.apache.org/xmlns/features/v1.4.0 > "> > > >

Re: Problem updating to 4.2.7

Hi, And I worked in 4.2.0 / 4.2.0-SNAPSHOT ? That's weird. Can you try a feature:install -v -t install of going via the deploy folder ? Regards JB On 28/10/2019 06:28, David Leangen wrote: Thanks JB! Unfortunately, exactly the same problem occurs with 4.2.3. Should I try a different

Re: Problem updating to 4.2.7

Thanks JB! Unfortunately, exactly the same problem occurs with 4.2.3. Should I try a different version? Which one do you suggest? Cheers, =David > On Oct 26, 2019, at 16:43, Jean-Baptiste Onofré wrote: > > Hi David, > > No problem, please let me know. > Don't hesitate to ping me when

Re: Problem updating to 4.2.7

Hi David, No problem, please let me know. Don't hesitate to ping me when you can, we will figure it out together. Regards JB On 26/10/2019 08:19, David Leangen wrote: Hi JB, Thank you for your amazingly fast reply! Ok, I will try these out, but unfortunately it won’t be today. I’ll let

Re: Problem updating to 4.2.7

Hi JB, Thank you for your amazingly fast reply! Ok, I will try these out, but unfortunately it won’t be today. I’ll let you know. Cheers, =David > On Oct 26, 2019, at 15:10, Jean-Baptiste Onofré wrote: > > Hi David, > > Does Karaf stop or restart ? > > About what you said, it seems to

Re: Problem updating to 4.2.7

Hi David, Does Karaf stop or restart ? About what you said, it seems to restart. It's maybe not the whole container but just the shell console, due to a refresh. Can you try feature:install -t -v to see what's going on ? Did you test on intermediate version like 4.2.3 ? And eventually do

Problem updating to 4.2.7

Hi! I am trying to update my Karaf to 4.2.7. I was using a snapshot of 4.2.0. Using the default configuration, the container starts up just fine. However, when I attempt to deploy a feature (by placing the file in the deploy directory), the container dies, and then goes into a bad cycle where