The peer must go online to get a peer address.

Discussion in English language.
You can start and continue with posts in english language in all other forums as well, but if you are looking for a forum to start a discussion in english, this is the right choice.

The peer must go online to get a peer address.

Beitragvon xioc752 » Do Okt 30, 2014 10:40 am

on two Robinson servers, cloud based
we applied update

then, after making no other changes we got displayed
The peer must go online to get a peer address.

This was caused exclusively by the update.
Repeated on the 2nd server.
Same effects, same update applied - within minutes of each other.

How do we get past this, please?
A) Admin window displays normally...most things are OK
B) Data and available space sizes appear normal.

1) No Search Results data is displayed when searches are made
Only the Top of Page Framework displays with the search button clickable, but with NO RESULTS
2) Admin Http 500 Error screens in html display for

Search results Page Header display but no crawl results display.
How do we get around this blockage...Work Around, Patch or Rollback.
Ideally we wish to move forward repair and continue daily updates, of course.
The functions & security features in this engine are very important to us
Many Thanks!
Beiträge: 68
Registriert: Mo Jul 28, 2014 5:01 pm

Re: The peer must go online to get a peer address.

Beitragvon Orbiter » Mi Nov 12, 2014 10:47 am

there was a small IPv6 problem which may have caused robinson peers to be unable to show local search results. This has been fixed about 9 days ago.
Beiträge: 5797
Registriert: Di Jun 26, 2007 10:58 pm
Wohnort: Frankfurt am Main

Re: The peer must go online to get a peer address.

Beitragvon xioc752 » Do Nov 20, 2014 10:45 pm

Thank you very kindly for the replies!
I have updated both servers to version 1.81/9168
Ubuntu is updated to the latest available versions, as of this date.
Both are cloud servers with identical installations of YaCy (Robinson, reading each other but not writing to each other) and different data sets, of course.

1) on the fast server, the results now show and it is online. Great! Thanks.

But this still shows "The peer must go online to get a peer address."
Despite many RSS feeds scheduled, the server does not crawl at all and results remain the same.
Interestingly in System Status on page Status.html?noforward=
Host: []:8090
peer address not assigned
Transparent off URL off
Remote: not used

Is this significant? How to manually correct this in a file, somewhere, please? Thanks.

2)The fast server displays web results but in admin if one selects ConfigPortal.html
the following displays in the www page:

Problem accessing /ConfigPortal.html. Reason:

Server Error
Caused by:

javax.servlet.ServletException: /usr/share/yacy/htroot/ConfigPortal.html
at net.yacy.http.servlets.YaCyDefaultServlet.handleTemplate(
at net.yacy.http.servlets.YaCyDefaultServlet.doGet(
at javax.servlet.http.HttpServlet.service(
at javax.servlet.http.HttpServlet.service(
at org.eclipse.jetty.servlet.ServletHolder.handle(
at org.eclipse.jetty.servlet.ServletHandler.doHandle(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.session.SessionHandler.doHandle(
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(
at org.eclipse.jetty.servlet.ServletHandler.doScope(
at org.eclipse.jetty.server.session.SessionHandler.doScope(
at org.eclipse.jetty.server.handler.ContextHandler.doScope(
at org.eclipse.jetty.server.handler.ScopedHandler.handle(
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at net.yacy.http.CrashProtectionHandler.handle(
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(
at org.eclipse.jetty.server.Server.handle(
at org.eclipse.jetty.server.HttpChannel.handle(
at org.eclipse.jetty.server.HttpConnection.onFillable(
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(
at org.eclipse.jetty.util.thread.QueuedThreadPool$

YaCy 1.81 - powered by Jetty -

How to fix this manually, please? Many thanks!

3) The slow server has a more complicated problem, apparently, and is not displaying the admin or results pages.
Calling up the server page,at Status.html, generates this www page response:

Problem accessing /Status.html. Reason:

proxy use not allowed (see Advanced Settings -> HTTP Networking -> Transparent Proxy; switched off).
Powered by Jetty://

How to correct this manually, please? Many thanks!
We are very grateful for the regular updates and advice :)
Beiträge: 68
Registriert: Mo Jul 28, 2014 5:01 pm

Zurück zu English

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 2 Gäste