Package Details: yacy 1.92-2

Git Clone URL: https://aur.archlinux.org/yacy.git (read-only)
Package Base: yacy
Description: Peer to peer search engine
Upstream URL: http://www.yacy.net/
Licenses: GPL2
Submitter: flori
Maintainer: funilrys
Last Packager: funilrys
Votes: 89
Popularity: 0.009827
First Submitted: 2007-02-06 17:59
Last Updated: 2017-02-07 11:32

Latest Comments

1 2 3 4 5 6 ... Next › Last »

k2s commented on 2018-08-19 07:35

to fix Unrecognized VM option 'CMSIncrementalMode' simply edit /etc/yacy/yacy and remove CMSIncrementalMode from start arguments.

DoMiNeLa10 commented on 2018-06-06 17:33

The wrapper script fails with jre10-openjdk because of deprecated java flags.

Relevant installed Java packages:

local/java-environment-common 3-1
    Common files for Java Development Kits
local/java-runtime-common 3-1
    Common files for Java Runtime Environments
local/jdk10-openjdk 10.0.1.u10-1
    OpenJDK Java 10 development kit
local/jre10-openjdk 10.0.1.u10-1
    OpenJDK Java 10 full runtime environment
local/jre10-openjdk-headless 10.0.1.u10-1
    OpenJDK Java 10 headless runtime environment

Systemd unit log:

Jun 06 19:12:26 host systemd[1]: Started YaCy P2P Web Search.
Jun 06 19:12:26 host yacy[9308]: Starting YaCy Daemon
Jun 06 19:12:26 host yacy[9308]: OpenJDK 64-Bit Server VM warning: Ignoring option MaxPermSize; support was removed in 8.0
Jun 06 19:12:26 host yacy[9308]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Jun 06 19:12:26 host yacy[9308]: Unrecognized VM option 'CMSIncrementalMode'
Jun 06 19:12:26 host yacy[9308]: Error: Could not create the Java Virtual Machine.
Jun 06 19:12:26 host yacy[9308]: Error: A fatal exception has occurred. Program will exit.
Jun 06 19:12:26 host systemd[1]: yacy.service: Main process exited, code=exited, status=1/FAILURE
Jun 06 19:12:26 host systemd[1]: yacy.service: Failed with result 'exit-code'.

Self-Perfection commented on 2017-08-16 18:40

For now you can open http://127.0.0.1:8090/ConfigProperties_p.html
and set browserPopUpTrigger:false as a workaround.

But I believe *.service file should override this option somehow and disable browser start for daemon process. But is seems currently there is no way to achieve this.

I've created bugreport in upstream regarding this issue https://github.com/yacy/yacy_search_server/issues/125

Self-Perfection commented on 2017-08-16 17:04

Looks like YaCy tries to launch web browser on start and may succeed even when starting as systemd controlled daemon if there is installed cli browser:

$ COLUMNS=80 systemd-cgls --no-pager --unit yacy.service
Unit yacy.service (/system.slice/yacy.service):
├─30858 /bin/sh /opt/yacy/yacy start
├─30876 /usr/sbin/java -Xms1024m -Xmx1024m -server -Xss256k -XX:MaxPermSize=2...
├─31004 /bin/sh /usr/sbin/xdg-open http://localhost:8090/index.html
└─31033 lynx http://localhost:8090/index.html

Too bad no one sees this running lynx :-D

Running useless process is definitely a bug, though I have not figured whether it upstream or packaging bug.

funilrys commented on 2017-06-28 20:43

@noogar I really can't explain your problem with the service ... I reinstalled using `pacaur -S yacy` and didn't have such problem ... In between, the warning are normal !

uzerus commented on 2017-04-07 12:10

maybe updated, but after reinstallation (cos want fresh configs, old has crashed for unknown reason) it do not ask what java version i want use to, and there IS NO SERVICE named yacy (eg. yacy.service)

look at build log https://pastebin.com/dV8kZJhe

removing all dependencies and build again does not fix it, maybe some files exist of old yacy instance?

funilrys commented on 2017-02-07 11:34

Updated !
For fast contact :
https://gitter.im/funilrys_/PKGBUILD
https://gitter.im/funilrys_/yacy

GI_Jack commented on 2016-10-18 22:08

PKGBUILD for 1.90
http://pastebin.com/L90C8t43

flacks commented on 2016-09-10 06:25

Version 1.90 is the latest version as of this writing.

ale1ster commented on 2016-01-30 14:52

I think it's the second hash that is not correct ('7cf5...').
For me it worked by deleting it from the PKGBUIlD and continuing the build...