Validating daisy 202 - I don't understand why the option --data is required for cli daisy202-validator

[xpilgrim]

Hi,

for several years, I'm validated dtb's with this cmd:
/opt/daisy-pipeline2-cli/dp2 daisy202-validator --ncc /home/myuser/mydtb/ncc.html --output validate

With the go cli pipeline 2-1.14.4_debian.deb the option --ncc changed to --source, it's OK.

But why is -d,--data DATA required?

This is for me a little bit confusing. I'don't want to convert a dtb, I wish only, like the script name is suggesting, validate a 2.02 dtb.

How can I achieve only validating with pipeline2-1.15.1_debian.deb and daisy202-validator?

[bertfrees]

--data is an option that is always required when the server is not in "local file system mode". Since some time, local FS mode is not the default anymore. To enable this mode, you need to edit the file /etc/default/daisy-pipeline.

[tigexplorer]

I've changed in
/opt/daisy-pipeline2/etc/pipeline.properties
the item
#org.daisy.pipeline.ws.localfs=false to org.daisy.pipeline.ws.localfs=true
and restarted the service.

Now I get this error:

/opt/daisy-pipeline2-cli/dp2 daisy202-validator --source /home/me/test1/ncc.html --output /home/me/validate
Error:
	Job request is not valid

The dtb plays well with a software player.

What am I doing wrong?

I'm on

• ubuntu 24.4
• temurin-21-jdk
• pipeline2-1.15.1_debian.deb
• cli-2.3.0-linux_386.deb

[tigexplorer]

Where can I get debug information?

Attached is my pipeline.properties (txt).

The /tmp is writeable an there are a lot of pipeline-104... dirs.

The same dtb is successfully validated with

/opt/daisy-pipeline2-cli/dp2 daisy202-validator --ncc /home/me/test1/ncc.html --output /home/me/validate

on

• ubuntu 22.4
• temurin-11-jdk
• pipeline2-1.14.4_debian.deb
• cli-2.1.1-linux_386.deb

I would very thankful, to get the new system to work.

pipeline.properties.txt

[bertfrees]

I'm going to close this issue as the original question has been answered, and the second question is covered by #843.

You already figured out where you can get debug information (namely in /var/log/daisy-pipeline2/daisy-pipeline.log).

Sorry for the late response, by the way.