Bug #2607
Bug #2613: [yacy] Signature no longer trusted.
[yacy]: Option flag error on systemctl start
90%
Description
My system: Parabola x86_64.
The program gives an error. The option flag seems to be missing a part.
The error is:
Jan 20 20:18:05 terracap yacy[4990]: Unrecognized option: - Jan 20 20:18:05 terracap yacy[4990]: Error: Could not create the Java Virtual Machine. Jan 20 20:18:05 terracap yacy[4990]: Error: A fatal exception has occurred. Program will exit. Jan 20 20:18:05 terracap systemd[1]: yacy.service: Main process exited, code=exited, status=1/FAILURE -- Subject: Unit process exited
Expected behavior is the program will start without an error.
I start it with "systemctl start yacy" to get the error.
History
Updated by bill-auger over 4 years ago
off-hand, my guess is that the 'yacy' program is expecting a specific version of java - i would try it with each of the other java versions
$ pacman -Si yacy | grep Depends
Depends on : java-environment
$ pacman -Ss java-environment
...
extra/jdk-openjdk 13.0.1.u9-1
OpenJDK Java 13 development kit
extra/jdk10-openjdk 10.0.2.u13-2
OpenJDK Java 10 development kit
extra/jdk11-openjdk 11.0.5.u10-1
OpenJDK Java 11 development kit
extra/jdk7-openjdk 7.u231_2.6.19-1
OpenJDK Java 7 development kit
extra/jdk8-openjdk 8.u232-1
OpenJDK Java 8 development kit
Updated by ani over 4 years ago
I tested every other Java version there is and the same error pops up regardless. How do I show this in a logfile so you can see what I did?
Updated by bill-auger over 4 years ago
im not sure what you are asking - you already did show the error
- the important thing missing was the command that you typed -
im guessing that was `systemctl start ` - any way you can get
the text into a file, you can attach it to this ticket
a_command > afile or a_command 2> afile
then press the "browse" button on this ticket and find 'afile'
Updated by ani over 4 years ago
I'm asking because "journalctl -xe" gives output in a seperate buffer and thus I cannot pipe that into a file. However the error messages are all the same as the original one, for each and every OpenJDK version that I tried.
archlinux-java status Available Java environments: java-10-openjdk java-11-openjdk java-13-openjdk java-7-openjdk (default) java-8-openjdk
And "sudo archlinux-java set <ENVIRONMENT>" is what I did for every item listed. Then "sudo systemctl start yacy" which brings no output and lists that error in journalctl.
Updated by bill-auger over 4 years ago
journalctl will print to a file just as i described
$ journalctl --unit=SOME.service --since=today > journalctl.log
probably youve given enough detail already though - the problem
is not obvious; so someone will need to trouble-shoot it
Updated by freemor about 4 years ago
- Parent task set to #2613
- Priority changed from bug to broken
- Assignee set to freemor
- Status changed from unconfirmed to confirmed
Set related and parent to #2613. People can follow the goings on there
Updated by freemor about 4 years ago
- % Done changed from 0 to 100
- Status changed from confirmed to fixed
Updated by ani about 4 years ago
Even after this last upgrade I still get the same error as before. Version 1.922-1 is current on my system.
Updated by freemor about 4 years ago
- % Done changed from 100 to 90
Can you please run /opt/yacy/yacy manually and see what the output from that is it may be more dagnostic then the output from systemd
does /usr/lib/jvm/java-8-openjdk/bin/java exist on your system?
Updated by ani about 4 years ago
Running /opt/yacy/yacy creates no output. The file you requested exists.
Updated by ani about 4 years ago
I ran the latest command you requested and the output is:
Starting YaCy Daemon Unrecognized option: - Error: Could not create the Java Virtual Machine. Error: A fatal exception has occurred. Program will exit.