exist-open — Open discussion

[Exist-open] [ANN] eXist-db 4.10.0, 5.4.1, and 6.0.1 released

[Adam R. <ad...@ex...>]

Dear eXist-db users,

Happy Valentines Day!

We have recently published new eXist-db releases for you. The versions include:

* 6.0.1 which is much the same as 5.4.1 but with two small API breaking changes.

* 5.4.1 which is a small bug fixed version of the recent 5.4.0 release.

* 4.9.0 and 4.10.0 as updates for those still using the legacy 4.x.x line.

You can find all the versions, associated release notes and downloads
here: https://github.com/exist-db/exist/releases

Kind regards. Adam.

-- 
Adam Retter

eXist Core Developer
{ United Kingdom }
ad...@ex...

Re: [Exist-open] eXist 6.0.0 with OxygenXML

[Josef W. UL <jwe...@hi...>]

Hi Marc

This is what I did, I didn't notice my mail client didn't add the 
mailing list (I think I clicked on "reply all"). This time it should be 
there.

Thank you for your reply! I did indeed use my old connection from 
eXist-db 5.3.x. I will correct that and see what's happening.

Josef

On 09.02.22 14:02, Marc de Graauw wrote:
> Hi Josef,
>
> I don't see your message appearing on the mailing list, maybe you sent 
> it to just me.
>
> Anyway, I did have some Ace* errors with eXist 6 too, but in my case 
> those were caused by me not having made a new eXist-db connection in 
> the Oxygen data sources with the eXist 6 libraries - I still had an 
> older eXist 5 connection which I used. Hope this is not what's 
> happening in your case too.
>
> Marc
>
> On Wed, 9 Feb 2022 at 08:58, Josef Wetzel UL 
> <jwe...@hi...> wrote:
>
>     Hi Marc, Hi everybody
>
>     On eXist-db 6.0.0 and Oxygen:
>     I work with Oxygen Editor 23.1 and connect it to eXist-db-6.0.0 via
>     Database Soruce -> eXist-db as described in Oxygen help.
>
>     In the beginning everything worked as expected. But then I came
>     across a
>     problem:
>
>     When I wanted to browse a certain collection in my eXist-db in
>     Oxygen, I
>     received an error message saying something like "aceAccess ...".
>     Oxygen
>     refused to show the contents of this collection.
>     I then realised, that I had some documents in this collection, which
>     where protected not only by the common flags rwx for owner, group and
>     others but also by an ACL. This ACL triggered the error. I removed
>     the
>     ACL and everything worked fine. In this case I can rethink the
>     document
>     protection to work without ACL, but this might be a problem when
>     using
>     Oxygen with eXist-db-6.0.0.
>
>     Josef
>
>     On 01.02.22 17:05, Marc de Graauw wrote:
>     > I've been trying eXist 6.0.0 on my local machine, OxygenXML
>     seems to
>     > work fine - I can create, delete, execute. The blog mentions
>     > incompatibilities - any hints as to what kind of trouble I
>     should be
>     > looking for?
>     >
>     > Marc
>     >
>     >
>     > _______________________________________________
>     > Exist-open mailing list
>     > Exi...@li...
>     > https://lists.sourceforge.net/lists/listinfo/exist-open
>
>
>
>
> -- 
>
> Groeten,
>
> Marc

[Exist-open] [exist-open] off-topic announcement: Fore replaces betterFORM

[Joern T. <joe...@gm...>]

Sorry for this slightly off-topic posting:

For those who have used betterFORM in eXist-db and those who have to edit
some structured XML please read on.

There's a new pre-release of Fore (1.0.0-2) available at
https://github.com/Jinntec/Fore/releases/tag/v1.0.0-2

We have successfully ported a complex betterFORM XForms page with about
1.500 lines of code (reduced to about 900 lines afterwards), using about 20
data instances and deeply nested repeats to Fore. Unfortunately betterFORM
is not compatible with latest eXist-db releases any more but Fore is here
as a replacement. It's now pure client-side and requires no  setup.

However we plan a fore-exist module to make it even easier to use it within
your eXist-db apps and and provide a generic server-side validation
facility.

If you like it, I would appreciate a github star.

If you find things not being covered I'm open for feature requests and
discussions.

Thanks for listening,

Joern

Re: [Exist-open] Status of eXist-db 5.3.1, 5.4, 6.0?

[Craig A. B. <cra...@ma...>]

> On Jan 28, 2022, at 4:12 AM, Jo Calder <Jo....@ha...> wrote:
> 
> Hi all,
> 
> I see that there's new eXist-db (6.0 reached via http://exist-db.org/exist/apps/homepage/index.html#downloads, and clicking on the 5.3.1 link).   Did I miss the announcement for 6.0?  
> 
> The new drop happened just as I was preparing a release.  It would be really useful to know whether any regressions were detected in 5.3.1 (relative to 5.2) which are corrected in 5.4/6.0.  Can anyone supply that info?  

According to the publicly-available community call meeting minutes from Monday:

<https://docs.google.com/document/d/1eycQBp0CR9_B4fcGPt-1et4Ymgt4Fpzj5YcKhZp3Ln4/edit#heading=h.ei4sqy3ojpkl>

The announcements for 5.4.0 and 6.0.0 were held back because of a problem discovered with Monex in those releases.  That problem seems to have been addressed:

<https://github.com/eXist-db/exist/pull/4215>

and releases of 5.4.1 and 6.0.1 that include it should be out soon.  The fix is in eXist itself and can't be fixed by upgrading Monex.

The small team of volunteers that produces these releases is understandably a bit behind on their paperwork and has some work to get the issue tracker caught up with reality, but I would expect master tickets for the upcoming releases to appear soon on the milestones page:

<https://github.com/eXist-db/exist/milestones>


________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

[Exist-open] eXist 6.0.0 with OxygenXML

[Marc de G. <mar...@gm...>]

I've been trying eXist 6.0.0 on my local machine, OxygenXML seems to work
fine - I can create, delete, execute. The blog mentions incompatibilities -
any hints as to what kind of trouble I should be looking for?

Marc

Re: [Exist-open] Status of eXist-db 5.3.1, 5.4, 6.0?

[Martin M. <mar...@no...>]

I’m not quite sure how to read the caveats about eXist 6.0.  I think they mean that if you are using oXygen with eXist you’re better off sticking with 5.4. Is that correct?  Or are the security concerns of such rarefied quality that it doesn’t matter a whole lot.

Re: [Exist-open] Status of eXist-db 5.3.1, 5.4, 6.0?

[Eduard D. <ed...@fr...>]

https://exist-db.org/exist/apps/wiki/blogs/eXist//eXistdb540
https://exist-db.org/exist/apps/wiki/blogs/eXist//eXistdb600 id="-x-evo-selection-start-marker">

-----Original Message-----
From: Jo Calder <Jo....@ha...>
To: exi...@li...
Subject: [Exist-open] Status of eXist-db 5.3.1, 5.4, 6.0?
Date: Fri, 28 Jan 2022 10:12:16 +0000

Hi all,
I see that there's new eXist-db (6.0 reached via 
http://exist-db.org/exist/apps/homepage/index.html#downloads, and
clicking on the 5.3.1 link).   Did I miss the announcement for 6.0?  

The new drop happened just as I was preparing a release.  It would be
really useful to know whether any regressions were detected in 5.3.1
(relative to 5.2) which are corrected in 5.4/6.0.  Can anyone supply
that info?  

With thanks, -- Jo

_______________________________________________Exist-open mailing 
lis...@li...
https://lists.sourceforge.net/lists/listinfo/exist-open

-- 
Eduard Drenth, Software Architekt

ed...@fr...

Doelestrjitte 8
8911 DX  Ljouwert
+31 58 234 30 47
+31 62 094 34 28 (privé)

skype: eduarddrenth
https://github.com/eduarddrenth
frisian.eu
gpg: https://pgp.surfnet.nl/pks/lookup?search=eduarddrenth


Op freed bin ik thús/wurkje ik minder

[Exist-open] Status of eXist-db 5.3.1, 5.4, 6.0?

[Jo C. <Jo....@ha...>]

Hi all,

I see that there's new eXist-db (6.0 reached via
http://exist-db.org/exist/apps/homepage/index.html#downloads, and clicking
on the 5.3.1 link).   Did I miss the announcement for 6.0?

The new drop happened just as I was preparing a release.  It would be
really useful to know whether any regressions were detected in 5.3.1
(relative to 5.2) which are corrected in 5.4/6.0.  Can anyone supply that
info?

With thanks, -- Jo

[Exist-open] baffled by password problems

[Martin M. <mar...@no...>]

I have run exist 5.3.1 on my Mac mini with Montero. I uninstalled it and also removed the org.exist directory because  some TEI Publisher icons wouldn’t go away even after I delete the apps vi the Java admin client.

Then I reinstalled eXist from scratch.  But the new installation refuses to register passwords. In the documentation there is an icon that suggests that in the first request for setting an admin password there is a screen  that asks you to confirm the password. That screen doesn’t show, but unless my memory tricks me it wasn’t there on the earlier installation, but it accepted the initial admin passs word without confirmation and let me create another user with a password.

I repeated the procedure several times to no avail. So now I’m in a situation where on an otherwise functional Mac I can’t install eXist.

I’ll be grateful for any advice

Re: [Exist-open] Instrumenting XQL for millisecond time

[Len S. <le...@wi...>]

Yes, Monex tracing works great.

--len

On Jan 20, 2022, at 5:57 AM, Dannes Wessels <di...@ex...<mailto:di...@ex...>> wrote:

Hi,

Did you have a look at the tracing function of monex?

The function you mention requires to return the same time, according to the w3c spec.

Regards

Dannes

Sent from my iPhone

On 16 Jan 2022, at 22:34, Len Schultz <le...@wi...<mailto:le...@wi...>> wrote:

 I’m trying to instrument my XQL so I can see how long functions take to execute.

I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don’t see something similar in eXist.  But even that may not work for XQL being an OOO functional language.

What’s the best way to profile the latency of functions?

--len

_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Instrumenting XQL for millisecond time

[Dannes W. <di...@ex...>]

Hi,

Did you have a look at the tracing function of monex?

The function you mention requires to return the same time, according to the w3c spec.

Regards

Dannes

Sent from my iPhone

> On 16 Jan 2022, at 22:34, Len Schultz <le...@wi...> wrote:
> 
>  I’m trying to instrument my XQL so I can see how long functions take to execute.
> 
> I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don’t see something similar in eXist.  But even that may not work for XQL being an OOO functional language.
> 
> What’s the best way to profile the latency of functions?
> 
> --len
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Exchange JETTY version in eXist 5

[Omar S. <Oma...@oe...>]

Hello,

Am 17.01.2022 um 09:25 schrieb Jens Tischler via Exist-open:
>
> Does anyone know how to switch JETTY to a higher version in eXist 5 
> (5.1.1)? Exchanging the JARs seems not to be sufficient. d regards
> Jens
>
I have good experience in rebuilding exist-db with just some 
dependencies updated. Especially log4j and jetty works well.

Best regards

-- 
Mag. Ing. Omar Siam
Austrian Center for Digital Humanities and Cultural Heritage
Österreichische Akademie der Wissenschaften | Austrian Academy of Sciences
Stellvertretende Behindertenvertrauensperson | Deputy representative for disabled persons
Wohllebengasse 12-14, 1040 Wien, Österreich | Vienna, Austria
T: +43 1 51581-7295
oma...@oe... | www.oeaw.ac.at/acdh

[Exist-open] Exchange JETTY version in eXist 5

[Jens T. <tis...@do...>]

Hello,

this is Jens from DOSCO.

Does anyone know how to switch JETTY to a higher version in eXist 5 
(5.1.1)? Exchanging the JARs seems not to be sufficient.

Background: Our customer recognized some security issues with the 
built-in JETTY 9.4.24.

Thanks and regards
Jens

-- 
__________________________________________________________________________
<> DOSCO Document Systems Consulting GmbH
Jens Tischler

phone +49 162 4664334
      (+49 6221 1486 25)
mail  tis...@do...
web   http://www.dosco.de

       DOSCO Document Systems Consulting GmbH
       Mannheimer Strasse 1
       69115 Heidelberg, GERMANY

       Handelsregister:  Mannheim HRB 335122
       Geschäftsführung: Robert Erfle

Re: [Exist-open] Instrumenting XQL for millisecond time

[Len S. <le...@wi...>]

Sava,

Can you please share link to the eXist profiler?

--len

On Jan 16, 2022, at 1:37 PM, sju...@mr...<mailto:sju...@mr...> wrote:


Hi Len,

we utilize eXist profiler for this purpose.

Cheers,

Sava

On 2022-01-16 12:00, Len Schultz wrote:

I'm trying to instrument my XQL so I can see how long functions take to execute.

I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don't see something similar in eXist.  But even that may not work for XQL being an OOO functional language.

What's the best way to profile the latency of functions?

--len

_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Instrumenting XQL for millisecond time

[Len S. <le...@wi...>]

Thanks.  I didn’t know about this.  It helps a lot.

--len

On Jan 16, 2022, at 1:55 PM, sju...@mr...<mailto:sju...@mr...> wrote:


It is part of the eXist install

http://localhost:8080/exist/apps/monex/index.html

Cheers,

Sava



On 2022-01-16 13:47, Len Schultz wrote:

Sava,

Can you please share link to the eXist profiler?

--len

On Jan 16, 2022, at 1:37 PM, sju...@mr...<mailto:sju...@mr...> wrote:

Hi Len,

we utilize eXist profiler for this purpose.

Cheers,

Sava

On 2022-01-16 12:00, Len Schultz wrote:

I'm trying to instrument my XQL so I can see how long functions take to execute.

I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don't see something similar in eXist.  But even that may not work for XQL being an OOO functional language.

What's the best way to profile the latency of functions?

--len

_______________________________________________
Exist-open mailing list
Exi...@li...<mailto:Exi...@li...>
https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Instrumenting XQL for millisecond time

[Craig B. <cra...@ma...>]

Profiler certainly works for some use cases.  If there is a particular beast of a function that routinely causes performance problems, I will often do something like this to keep an eye on just how bad it is:

    let $start-time := util:system-time()
. . .
    let $seconds := (util:system-time() - $start-time) div xs:dayTimeDuration("PT1S")
    let $x := console:log("Completed in " || $seconds || "s.")

> On Jan 16, 2022, at 3:37 PM, sju...@mr... wrote:
> 
> Hi Len,
> 
> we utilize eXist profiler for this purpose.
> 
> Cheers,
> 
> Sava
> 
> On 2022-01-16 12:00, Len Schultz wrote:
> 
>> I'm trying to instrument my XQL so I can see how long functions take to execute.
>>  
>> I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don't see something similar in eXist.  But even that may not work for XQL being an OOO functional language.
>>  
>> What's the best way to profile the latency of functions?
>> 
>> --len
>> 
>> _______________________________________________
>> Exist-open mailing list
>> Exi...@li...
>> https://lists.sourceforge.net/lists/listinfo/exist-open
>  
>  
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

________________________________________
Craig A. Berry

"... getting out of a sonnet is much more
 difficult than getting in."
                 Brad Leithauser

Re: [Exist-open] Instrumenting XQL for millisecond time

[Jean-Paul R. <re...@gm...>]

 util:system-time() does what you need.



On Sun, Jan 16, 2022 at 10:34 PM Len Schultz <le...@wi...> wrote:

> I’m trying to instrument my XQL so I can see how long functions take to
> execute.
>
> I tried current-dateTime(), but that returns the same millisecond
> timestamp at all points of the code, apparently being the time the XQL
> started.  Is there a way to do this?  Marklogic seems to have
> xdmp:elapsed-time(), but I don’t see something similar in eXist.  But even
> that may not work for XQL being an OOO functional language.
>
> What’s the best way to profile the latency of functions?
>
> --len
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

Re: [Exist-open] Instrumenting XQL for millisecond time

[<sju...@mr...>]

 

Hi Len, 

we utilize eXist profiler for this purpose. 

Cheers, 

Sava 

On 2022-01-16 12:00, Len Schultz wrote: 

> I'm trying to instrument my XQL so I can see how long functions take to execute. 
> 
> I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don't see something similar in eXist.  But even that may not work for XQL being an OOO functional language. 
> 
> What's the best way to profile the latency of functions? 
> 
> --len 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

  

Re: [Exist-open] Instrumenting XQL for millisecond time

[<sju...@mr...>]

 

It is part of the eXist install 

http://localhost:8080/exist/apps/monex/index.html 

Cheers, 

Sava 

On 2022-01-16 13:47, Len Schultz wrote: 

> Sava, 
> 
> Can you please share link to the eXist profiler?  
> 
> --len 
> 
> On Jan 16, 2022, at 1:37 PM, sju...@mr... wrote: 
> 
> Hi Len, 
> 
> we utilize eXist profiler for this purpose. 
> 
> Cheers, 
> 
> Sava 
> 
> On 2022-01-16 12:00, Len Schultz wrote: I'm trying to instrument my XQL so I can see how long functions take to execute. 
> 
> I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don't see something similar in eXist.  But even that may not work for XQL being an OOO functional language. 
> 
> What's the best way to profile the latency of functions? 
> 
> --len 
> 
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

  

[Exist-open] Instrumenting XQL for millisecond time

[Len S. <le...@wi...>]

I’m trying to instrument my XQL so I can see how long functions take to execute.

I tried current-dateTime(), but that returns the same millisecond timestamp at all points of the code, apparently being the time the XQL started.  Is there a way to do this?  Marklogic seems to have xdmp:elapsed-time(), but I don’t see something similar in eXist.  But even that may not work for XQL being an OOO functional language.

What’s the best way to profile the latency of functions?

--len

Re: [Exist-open] Securing my exist-db

[Pietro L. <pie...@gm...>]

Dear Nick,
I also use the systemd solution and since I learned that from exist, I use that for everything I can in the same way.
The location of exist and the data directory is owned by the user named in the systemd configuration. 
all best

Pietro Maria Liuzzo (egli/lui,he/him,er/ihn)
cel (DE): +49 (0) 176 61 000 606
Skype: pietro.liuzzo (Quingentole)
ORCID: https://orcid.org/0000-0001-5714-4011
Academia: https://uni-hamburg.academia.edu/PietroMariaLiuzzo






> Il giorno 12 gen 2022, alle ore 22:00, Øyvind Gjesdal <oyv...@gm...> ha scritto:
> 
> Hi Nick, 
> 
> I think this is supposed to happen, and is part of the nologin you added. The section under https://exist-db.org/exist/apps/doc/advanced-installation#linux <https://exist-db.org/exist/apps/doc/advanced-installation#linux> also seems to follow the production good practice guide for creating a user, and it also shows how to set up a systemd service which runs the application as that exist-user. I think you can probably also start the service manually for testing by running "sudo -u exist-user $EXIST_HOME/bin/startup.sh".
> 
> Best regards,
> Øyvind Gjesdal
> 
> ons. 12. jan. 2022 kl. 19:32 skrev Nick Sincaglia <nsi...@nu... <mailto:nsi...@nu...>>:
> I am in the process of setting up a brand new server with eXist-db running on it. I am paying particular attention in trying to make this server as secure as possible. I am not a linux administrator by training but I know decent amount to be able to follow directions. 
> 
> The eXist-db website has a best practices page for setting up eXist-db here:
> https://exist-db.org/exist/apps/doc/production_good_practice.xml <https://exist-db.org/exist/apps/doc/production_good_practice.xml>
> 
> Under the "Operating System Permissions" section it states the following:
> "Typically we would recommend creating an exist user account and exist user group with no login privileges (no shell and empty password), changing the permissions of the eXist-db installation to be owned by that user and group. Then run eXist-db using those credentials."
> 
> I am using AWS Linux and I am able to SSH into the server as "ec2-user". I created a new user "exist-user" using the "adduser" command. I then tried to remove login privileges by typing the command:
> >sudo usermod exist-user -s /sbin/nologin
> 
> This successfully removed login privileges for 'exist-user', however, when I try to switch my ec2-user to exist-user I get the notification "This account is currently not available."
> 
> I believe I must be misunderstanding the what the best practices recommendation is trying to tell me. What do I need to do to create a user "with no login privileges (no shell and empty password)"? Can someone explain?
> 
> Nick
> 
>  -- 
> Nick Sincaglia 
> President/Founder
> NueMeta, LLC
> Digital Media & Technology
> Phone: +1-630-303-7035
> nsi...@nu... <mailto:nsi...@nu...> 
> http://www.nuemeta.com <http://www.nuemeta.com/>
> Skype: nsincaglia
> _______________________________________________
> Exist-open mailing list
> Exi...@li... <mailto:Exi...@li...>
> https://lists.sourceforge.net/lists/listinfo/exist-open <https://lists.sourceforge.net/lists/listinfo/exist-open>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open

Re: [Exist-open] Securing my exist-db

[Øyvind G. <oyv...@gm...>]

Hi Nick,

I think this is supposed to happen, and is part of the nologin you added.
The section under
https://exist-db.org/exist/apps/doc/advanced-installation#linux also seems
to follow the production good practice guide for creating a user, and it
also shows how to set up a systemd service which runs the application as
that exist-user. I think you can probably also start the service manually
for testing by running "sudo -u exist-user $EXIST_HOME/bin/startup.sh".

Best regards,
Øyvind Gjesdal

ons. 12. jan. 2022 kl. 19:32 skrev Nick Sincaglia <nsi...@nu...>:

> I am in the process of setting up a brand new server with eXist-db running
> on it. I am paying particular attention in trying to make this server as
> secure as possible. I am not a linux administrator by training but I know
> decent amount to be able to follow directions.
>
> The eXist-db website has a best practices page for setting up eXist-db
> here:
> https://exist-db.org/exist/apps/doc/production_good_practice.xml
>
> Under the "Operating System Permissions" section it states the following:
> "*Typically we would recommend creating an exist user account and exist
> user group with no login privileges (no shell and empty password), changing
> the permissions of the eXist-db installation to be owned by that user and
> group. Then run eXist-db using those credentials.*"
>
> I am using AWS Linux and I am able to SSH into the server as "ec2-user". I
> created a new user "exist-user" using the "adduser" command. I then tried
> to remove login privileges by typing the command:
> >sudo usermod exist-user -s /sbin/nologin
>
> This successfully removed login privileges for 'exist-user', however,
> when I try to switch my ec2-user to exist-user I get the notification "This
> account is currently not available."
>
> I believe I must be misunderstanding the what the best practices
> recommendation is trying to tell me. What do I need to do to create a user *"with
> no login privileges (no shell and empty password)"? *Can someone explain?
>
> Nick
>
> --
> Nick Sincaglia
> President/Founder
> NueMeta, LLC
> Digital Media & Technology
> Phone: +1-6...@nu... http://www.nuemeta.com
> Skype: nsincaglia
>
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>

[Exist-open] Securing my exist-db

[Nick S. <nsi...@nu...>]

I am in the process of setting up a brand new server with eXist-db 
running on it. I am paying particular attention in trying to make this 
server as secure as possible. I am not a linux administrator by training 
but I know decent amount to be able to follow directions.

The eXist-db website has a best practices page for setting up eXist-db here:
https://exist-db.org/exist/apps/doc/production_good_practice.xml

Under the "Operating System Permissions" section it states the following:
"/Typically we would recommend creating an exist user account and exist 
user group with no login privileges (no shell and empty password), 
changing the permissions of the eXist-db installation to be owned by 
that user and group. Then run eXist-db using those credentials./"

I am using AWS Linux and I am able to SSH into the server as "ec2-user". 
I created a new user "exist-user" using the "adduser" command. I then 
tried to remove login privileges by typing the command:
 >sudo usermod exist-user -s /sbin/nologin

This successfully removed login privileges for 'exist-user', however, 
when I try to switch my ec2-user to exist-user I get the notification 
"This account is currently not available."

I believe I must be misunderstanding the what the best practices 
recommendation is trying to tell me. What do I need to do to create a 
user /"with no login privileges (no shell and empty password)"? /Can 
someone explain?

Nick

-- 
Nick Sincaglia
President/Founder
NueMeta, LLC
Digital Media & Technology
Phone: +1-630-303-7035
nsi...@nu...  
http://www.nuemeta.com
Skype: nsincaglia

Re: [Exist-open] Error in locally built Docker 5.3.1 image

[Loren C. <lor...@gm...>]

Hello Dannes,

I removed java 11 from my system and set the java version to 8.

Loren

> On Dec 23, 2021, at 9:27 AM, Dannes Wessels <da...@ex...> wrote:
> 
> Hi Loren,
> 
> This is a known issue/feature, not specific to eXist-db;
> 
> Something ‘ugly’ happened in the Java11 compiler regarding java.nio.ByteBuffer so if you compile eXist-db with Java11, you can not run it on Java8.
> 
> I mentioned it on the Monday teleconf actually.
> 
> There are quite many references on internet, see here <https://duckduckgo.com/?q=java.nio.ByteBuffer.clear()+java+8&t=osx&ia=web>.
> 
> On SO there is a workaround mentioned <https://stackoverflow.com/a/61267496>, but I never dared to apply it, as I did not trust it to modify so low level code. I think I remember I retracted my PR for that.
> 
> cheers
> 
> Dannes
> 
> 
>> On 21 Dec 2021, at 18:06 , Loren Cahlander <lor...@gm... <mailto:lor...@gm...>> wrote:
>> 
>> java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer; 
>> org.exist.EXistException: java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer;
>>        at org.exist.storage.BrokerPool.initialize(BrokerPool.java:465) ~[exist.uber.jar:5.3.1]
>>        at org.exist.storage.BrokerPools.configure(BrokerPools.java:177) [exist.uber.jar:5.3.1]
>>        at org.exist.storage.BrokerPools.configure(BrokerPools.java:112) [exist.uber.jar:5.3.1]
>>        at org.exist.jetty.JettyStart.run(JettyStart.java:216) [exist.uber.jar:5.3.1]
>>        at org.exist.jetty.JettyStart.main(JettyStart.java:103) [exist.uber.jar:5.3.1]
> 

Re: [Exist-open] Error in locally built Docker 5.3.1 image

[Dannes W. <da...@ex...>]

Hi Loren,

This is a known issue/feature, not specific to eXist-db;

Something ‘ugly’ happened in the Java11 compiler regarding java.nio.ByteBuffer so if you compile eXist-db with Java11, you can not run it on Java8.

I mentioned it on the Monday teleconf actually.

There are quite many references on internet, see here <https://duckduckgo.com/?q=java.nio.ByteBuffer.clear()+java+8&t=osx&ia=web>.

On SO there is a workaround mentioned <https://stackoverflow.com/a/61267496>, but I never dared to apply it, as I did not trust it to modify so low level code. I think I remember I retracted my PR for that.

cheers

Dannes


> On 21 Dec 2021, at 18:06 , Loren Cahlander <lor...@gm...> wrote:
> 
> java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer; 
> org.exist.EXistException: java.lang.NoSuchMethodError: java.nio.ByteBuffer.clear()Ljava/nio/ByteBuffer;
>        at org.exist.storage.BrokerPool.initialize(BrokerPool.java:465) ~[exist.uber.jar:5.3.1]
>        at org.exist.storage.BrokerPools.configure(BrokerPools.java:177) [exist.uber.jar:5.3.1]
>        at org.exist.storage.BrokerPools.configure(BrokerPools.java:112) [exist.uber.jar:5.3.1]
>        at org.exist.jetty.JettyStart.run(JettyStart.java:216) [exist.uber.jar:5.3.1]
>        at org.exist.jetty.JettyStart.main(JettyStart.java:103) [exist.uber.jar:5.3.1]