Hello JB,
Linux 5.13.19-2-MANJARO on ext4
Br,
Matthias
Am Mo., 27. Sept. 2021 um 14:50 Uhr schrieb Jean-Baptiste Onofré
<[email protected] <mailto:[email protected]>>:
Hi Matthias,
what's your OS and environment ?
It seems to work fine to me: I added a new fileinstall factory pid and
it's deploying from there.
Regards
JB
On 27/09/2021 14:38, Matthias Leinweber wrote:
> I also tried to add a config file
(org.apache.felix.fileinstall-foo.cfg)
> into the etc folder before first startup, But also no success.
>
> Br,
> Matthias
>
> Am Fr., 24. Sept. 2021 um 10:28 Uhr schrieb Jean-Baptiste Onofré
> <[email protected] <mailto:[email protected]> <mailto:[email protected]
<mailto:[email protected]>>>:
>
> I think you have a race condition: fileinstall is installed by
> startup.properties, and you provide the config via features
core which
> come later in the bootstrap.
>
> Let me try a startup like this and get back to you.
> I keep you posted.
>
> Regards
> JB
>
> On 24/09/2021 09:27, Matthias Leinweber wrote:
> > Hello,
> >
> > Does not work for us. In our assembly we add a boot feature
> containing:
> >
> > <config name="org.apache.felix.fileinstall-camel">
> > felix.fileinstall.dir = ${env:CAMEL_PATH:-/deploy/}
> > felix.fileinstall.filter = .*\\.(xml|cfg|groovy)
> > felix.fileinstall.poll = 1000
> > felix.fileinstall.start.level = 80
> > felix.fileinstall.active.level = 80
> > felix.fileinstall.log.level = 3
> > </config>
> >
> > The content of this fileinstaller does not get processed
on the
> first
> > system start. After restart it's fine, but not a viable
option. I
> tired
> > start+active @ 60,80,100 + start@100 active@80. As well as
> disable nio2.
> > In all cases I need to touch a file to make it working.
> >
> > br,
> > Matthias
> >
> > Am Do., 23. Sept. 2021 um 21:05 Uhr schrieb Paul Fraser
> > <[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
> <mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>>:
> >
> > Yes, running without clean works OK in my case.
> >
> > Paul Fraser
> >
> > On 23/9/21 6:45 pm, Jean-Baptiste Onofré wrote:
> > > I guess it works fine without the clean arg right ?
> > >
> > > Regards
> > > JB
> > >
> > > On 22/09/2021 13:15, Jesse White wrote:
> > >> We're hitting a similar problem with the deploy/
folder
> and can
> > >> reproduce with a vanilla distribution of Karaf 4.3.3.
> > >>
> > >> On Mac OS w/ JDK 11:
> > >>
> > >> tar zxvf apache-karaf-4.3.3.tar.gz &&
> cd apache-karaf-4.3.3
> > >> cp /tmp/confd-telemetry-feature.xml deploy/
> > >> ./bin/karaf clean
> > >>
> > >> karaf@root()> feature:info confd-telemetry-auto
> > >> Feature not found
> > >>
> > >> Similar test with Karaf 4.3.2 shows:
> > >>
> > >> karaf@root()> feature:info confd-telemetry-auto
> > >> Feature confd-telemetry-auto 1.0.0
> > >> Feature configuration:
> > >>
> org.opennms.features.telemetry.listeners-single-port-flows
> > >>
org.opennms.features.telemetry.listeners-JTI-Listener
> > >>
org.opennms.features.telemetry.listeners-NXOS-Listener
> > >> ...
> > >>
> > >> Here's a reference to the feature file in question:
> > >>
> https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>
>
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>>
> >
>
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>
>
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>>>
> > >>
> >
>
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>
>
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>>
> >
>
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>
>
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b
<https://gist.github.com/j-white/1574f34cb94dc2d9166ae9805bd4ba3b>>>>
> > >>
> > >> Thanks for all the effort in maintaining the
distribution
> - looking
> > >> forward to getting R7 up and running with JDK 17!
> > >>
> > >> Best,
> > >> Jesse
> > >>
> >
>
------------------------------------------------------------------------
> > >> *From:* Jean-Baptiste Onofre <[email protected]
<mailto:[email protected]>
> <mailto:[email protected] <mailto:[email protected]>>
> > <mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>>
> > >> *Sent:* Tuesday, September 21, 2021 9:39 AM
> > >> *To:* [email protected]
<mailto:[email protected]>
> <mailto:[email protected] <mailto:[email protected]>>
<mailto:[email protected] <mailto:[email protected]>
> <mailto:[email protected] <mailto:[email protected]>>>
> > <[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
> <mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>>
> > >> *Subject:* Re: FileInstaller with 4.3.3
> > >> WARNING: This email originated outside of NantHealth.
> > >> DO NOT CLICK links or attachments unless you
recognize the
> > sender and
> > >> are expecting this email.
> > >> ________________________________
> > >>
> > >> Yes, I tried both, no clean, clean as argument,
clean in
> > >> config.properties.
> > >>
> > >> All works fine.
> > >>
> > >> Can you share some details about your test case and
> environment
> > >> (especially if you are on Windows or Unix) ?
> > >>
> > >> Regards
> > >> JB
> > >>
> > >>> Le 21 sept. 2021 à 15:00, Matthias Leinweber
> > >>> <[email protected]
<mailto:[email protected]>
> <mailto:[email protected]
<mailto:[email protected]>>
> > <mailto:[email protected]
<mailto:[email protected]>
> <mailto:[email protected]
<mailto:[email protected]>>>> a écrit :
> > >>>
> > >>> For me it's a custom dist. Did you do a clean start?
> > >>>
> > >>> Am Di., 21. Sept. 2021 um 14:28 Uhr schrieb
> Jean-Baptiste Onofre
> > >>> <[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
> <mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>>:
> > >>> Hi,
> > >>>
> > >>> I did several test and it works fine for me.
> > >>>
> > >>> Here’s the very simplest test:
> > >>>
> > >>> - Starting from Karaf 4.3.3 vanilla
> > >>> - I put commons-lang-2.6.jar in the deploy folder
(while
> Karaf is
> > >>> stopped)
> > >>> - then, I’m starting Karaf with bin/karaf
> > >>> - When I checked the bundle:list:
> > >>>
> > >>> 54 │ Active │ 10 │ 2.6.7 │ OPS4J
Pax Url
> - wrap:
> > >>> 55 │ Active │ 80 │ 2.6 │
Commons Lang
> > >>>
> > >>> So, you can see commons-lang installed and active,
> meaning the
> > >>> deployers deployed it from the deploy folder.
> > >>>
> > >>> It works for me.
> > >>>
> > >>> Can you elaborate a bit your test case ?
> > >>> Is it a custom distribution ?
> > >>>
> > >>> Regards
> > >>> JB
> > >>>
> > >>> > Le 20 sept. 2021 à 08:29, Paul Fraser
> <[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
> > <mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>> a écrit :
> > >>> >
> > >>> > Hi JB,
> > >>> >
> > >>> > Any result on this check?
> > >>> >
> > >>> > Paul Fraser
> > >>> >
> > >>> > On 17/9/21 9:55 pm, JB Onofré wrote:
> > >>> >> I checked etc I will check deploy now.
> > >>> >>
> > >>> >> Regards
> > >>> >> JB
> > >>> >>
> > >>> >>> Le 17 sept. 2021 à 12:29, Paul Fraser
> <[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>
> > <mailto:[email protected] <mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>>> a écrit :
> > >>> >>>
> > >>> >>> Hi JB,
> > >>> >>>
> > >>> >>> In my case the problem occurs using the
deploy folder.
> > >>> >>>
> > >>> >>> Exact same code in 4.3.2 works, 4.3.3 does not
> install the
> > >>> deploy folder files.
> > >>> >>>
> > >>> >>> Paul
> > >>> >>>
> > >>> >>>> On 17/9/21 7:04 pm, Jean-Baptiste Onofré wrote:
> > >>> >>>> Hi,
> > >>> >>>>
> > >>> >>>> did you updated the etc location in
> etc/config.properties (in
> > >>> the felix.fileinstall.dir property) ?
> > >>> >>>>
> > >>> >>>> I just tried and it works fine for me. Here's my
> test case:
> > >>> >>>>
> > >>> >>>> 1. I created etc/my.config.cfg containing
foo=bar
> > >>> >>>> 2. I'm starting karaf
> > >>> >>>> 3. I can see the config loaded:
> > >>> >>>>
> > >>> >>>> karaf@root()> config:list
"(service.pid=my.config)"
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>
> >
----------------------------------------------------------------
> > >>> >>>> Pid: my.config
> > >>> >>>> BundleLocation: ?
> > >>> >>>> Properties:
> > >>> >>>> felix.fileinstall.filename =
> > >>>
> >
>
file:/home/jbonofre/Workspace/karaf/assemblies/apache-karaf/target/apache-karaf-4.3.4-SNAPSHOT/etc/my.config.cfg
> > >>> >>>> foo = bar
> > >>> >>>> service.pid = my.config
> > >>> >>>>
> > >>> >>>> Can you share your test case ?
> > >>> >>>>
> > >>> >>>> Regards
> > >>> >>>> JB
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>
> > >>> >>>>> On 16/09/2021 14:31, Matthias Leinweber wrote:
> > >>> >>>>> Hello,
> > >>> >>>>>
> > >>> >>>>> I am having a strange issue after I updated my
> assembly to
> > >>> 4.3.3. I am using a custom file installer
location which
> I deploy
> > >>> with a feature.
> > >>> >>>>>
> > >>> >>>>> The strange thing is that the folder is not
processed
> > >>> automatically at startup, but if I touch a single
file
> in the
> > folder
> > >>> all others files get processed as well.
> > >>> >>>>>
> > >>> >>>>> Any ideas?
> > >>> >>>>>
> > >>> >>>>> br,
> > >>> >>>>> Matthias
> > >>>
> > >>>
> > >>>
> > >>>
> > >>
> > >>
> > >> CONFIDENTIALITY NOTICE
> > >> This e-mail message and any attachments are
> only for
> > the use
> > >> of the intended recipient and may contain
> information
> > that is
> > >> privileged, confidential or exempt from
> disclosure under
> > >> applicable law. If you are not the intended
> recipient, any
> > >> disclosure, distribution or other use of
this
> e-mail
> > message
> > >> or attachments is prohibited. If you
have received
> > this e-mail
> > >> message in error, please delete and
notify the
> sender
> > >> immediately. Thank you.
> > >>
> >
> >
> >
> >
>
>
>
