Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#911 closed defect (worksforme)

Z3950 Server not working correctly? Can't find collection (default or otherwise)?

Reported by: simonp Owned by: geonetwork-devel@…
Priority: major Milestone: v2.8.0
Component: General Version:
Keywords: Cc:

Description

Reported by MurrayH

Change History (2)

comment:1 Changed 9 years ago by simonp

Resolution: worksforme
Status: newclosed

It does work from yaz-client (don't think the isite client is working):

eg. from yaz-client with sample data for iso19139 loaded:

open localhost:6668/geonetwork-local f @attr 1=4 africa

Sometimes queries are not logged to search stats though - this should be opened on a different ticket though.

comment:2 Changed 9 years ago by murrayh

I get the same errors with yaz-client (as I do with zclient). My GeoNetwork instance has 27 iso19139.anzlic records. Looks like I need to dig deeper.

$ yaz-client.exe Z> open cdcvd-asrdcap1:2200/geonetwork-local f @attr 1=4 forecast Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 174 Name : GeoNetwork JZKit generic server / JZKit Meta Search Service Version: 3.r260.geonetwork.patch.1 Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets Z> find forecast Sent searchRequest. Received SearchResponse?. Search was a bloomin' failure. Number of hits: 0, setno 1 Result Set Status: none records returned: 0 Diagnostic message(s) from database:

[235] Database does not exist -- v2 addinfo 'Unknown Collection geonetwork-local'

Z>

$ yaz-client.exe Z> open cdcvd-asrdcap1:2200/geonetwork Connecting...OK. Sent initrequest. Connection accepted by v3 target. ID : 174 Name : GeoNetwork JZKit generic server / JZKit Meta Search Service Version: 3.r260.geonetwork.patch.1 Options: search present delSet triggerResourceCtrl scan sort extendedServices namedResultSets Z> find forecast Sent searchRequest. Received SearchResponse?. Search was a bloomin' failure. Number of hits: 0, setno 1 Result Set Status: none records returned: 0 Diagnostic message(s) from database:

[2] Temporary system error -- v2 addinfo 'Unable to rewrite node. Semantic action was set to strict, and t

here appears to be no valid alternatives for node null Single Term : forecast attrs : {}'

Note: See TracTickets for help on using tickets.