Opened 6 years ago

Closed 5 years ago

#1188 closed defect (fixed)

geoserver: server errors in cartaro and geonode

Reported by: hamish Owned by: live-demo@…
Priority: minor Milestone: OSGeoLive8.0
Component: OSGeoLive Keywords: geoserver, cartaro, geonode
Cc:

Description

Hi,

a number of errors come back for cartaro and geonode in the build logs, apparently connected to geoserver.

86295:ERROR:  database "cartaro" does not exist
86296:ERROR:  role "cartaro" does not exist
86585:31 Jul 20:23:12 ERROR [geoserver.rest] - No such workspace: cartaro
86586:31 Jul 20:23:12 ERROR [geoserver.rest] - 
86670:31 Jul 20:23:12 ERROR [geoserver.rest] - No such datastore: cartaro,cartaro
86671:31 Jul 20:23:12 ERROR [geoserver.rest] - 
86757:31 Jul 20:23:27 ERROR [geoserver.rest] - No such feature type: cartaro,cartaro,capitals
86758:31 Jul 20:23:27 ERROR [geoserver.rest] - 
86843:org.postgresql.util.PSQLException: ERROR: permission denied for relation geography_columns
86946:WD mail: Error sending e-mail (from admin@example.com to             ESC[31;40mESC[1m[error]ESC[0m
86949:Unable to send e-mail. Contact the site administrator if the problem ESC[31;40mESC[1m[error]ESC[0m
86974:31 Jul 20:23:51 WARN [support.DisposableBeanAdapter] - Invocation of destroy method failed on bean with name 'geoServerLoader': org.springframework.beans.factory.BeanCreationNotAllowed
Exception: Error creating bean with name 'GWCLifeCycleHandler': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a Bean
Factory in a destroy method implementation!)
87663:checking if bus error on unaligned pointers... no
93059:Copying '/usr/lib/python2.7/dist-packages/geoexplorer/static/geoexplorer/externals/ext/resources/images/default/window/icon-error.gif'
93196:Copying '/usr/lib/python2.7/dist-packages/geoexplorer/static/geoexplorer/externals/ext/resources/images/default/form/error-tip-corners.gif'
93261:Copying '/usr/lib/python2.7/dist-packages/geoexplorer/static/geoexplorer/externals/ext/resources/images/gray/window/icon-error.gif'
93766:org.postgresql.util.PSQLException: ERROR: permission denied for relation geography_columns
95424:31 Jul 20:39:48 ERROR [geoserver.ows] - 
95500:31 Jul 20:39:49 ERROR [geoserver.ows] - 
95576:31 Jul 20:39:49 ERROR [geoserver.ows] - 
95652:31 Jul 20:39:49 ERROR [geoserver.ows] - 
96469:31 Jul 20:40:25 ERROR [geoserver.ows] - 
96545:31 Jul 20:40:25 ERROR [geoserver.ows] - 
96868:31 Jul 20:40:41 ERROR [geoserver.ows] - 
96944:31 Jul 20:40:41 ERROR [geoserver.ows] - 
97267:31 Jul 20:40:57 ERROR [geoserver.ows] - 
97343:31 Jul 20:40:57 ERROR [geoserver.ows] - 
97666:31 Jul 20:41:14 ERROR [geoserver.ows] - 
97742:31 Jul 20:41:14 ERROR [geoserver.ows] - 
98065:31 Jul 20:41:32 ERROR [geoserver.ows] - 
98141:31 Jul 20:41:32 ERROR [geoserver.ows] - 
org.geoserver.platform.ServiceException: No service: ( WPS )
98726:31 Jul 20:41:53 ERROR [geoserver.ows] - 
98848:31 Jul 20:41:55 ERROR [geoserver.ows] - 
98948:31 Jul 20:41:55 ERROR [geoserver.ows] - 
99122:31 Jul 20:42:00 ERROR [geoserver.ows] - 
99244:31 Jul 20:42:00 ERROR [geoserver.ows] - 
99344:31 Jul 20:42:00 ERROR [geoserver.ows] - 
99518:31 Jul 20:42:04 ERROR [geoserver.ows] - 
99640:31 Jul 20:42:05 ERROR [geoserver.ows] - 
99740:31 Jul 20:42:05 ERROR [geoserver.ows] - 
99914:31 Jul 20:42:10 ERROR [geoserver.ows] - 
100036:31 Jul 20:42:10 ERROR [geoserver.ows] - 
100136:31 Jul 20:42:10 ERROR [geoserver.ows] - 
100800:31 Jul 20:42:48 ERROR [gce.arcgrid] - 
100951:31 Jul 20:42:49 ERROR [geoserver.ows] - 
101051:31 Jul 20:42:49 ERROR [geoserver.ows] - 
101234:31 Jul 20:43:04 ERROR [gce.arcgrid] - 
101385:31 Jul 20:43:04 ERROR [geoserver.ows] - 
101485:31 Jul 20:43:05 ERROR [geoserver.ows] - 
101668:31 Jul 20:43:13 ERROR [gce.arcgrid] - 
101819:31 Jul 20:43:13 ERROR [geoserver.ows] - 
101919:31 Jul 20:43:14 ERROR [geoserver.ows] - 
102102:31 Jul 20:43:24 ERROR [gce.arcgrid] - 
org.geoserver.ows.ClientStreamAbortedException
102253:31 Jul 20:43:25 ERROR [geoserver.ows] - 
102353:31 Jul 20:43:25 ERROR [geoserver.ows] - 
102525:31 Jul 20:43:28 ERROR [geoserver.ows] - 
102625:31 Jul 20:43:28 ERROR [geoserver.ows] - 
102821:31 Jul 20:43:33 ERROR [geoserver.ows] - 
102921:31 Jul 20:43:33 ERROR [geoserver.ows] - 
103117:31 Jul 20:43:37 ERROR [geoserver.ows] - 
103217:31 Jul 20:43:37 ERROR [geoserver.ows] - 
103413:31 Jul 20:43:41 ERROR [geoserver.ows] - 
103513:31 Jul 20:43:41 ERROR [geoserver.ows] - 
103626:org.postgresql.util.PSQLException: ERROR: permission denied for relation geography_columns
103799:org.postgresql.util.PSQLException: ERROR: permission denied for relation geography_columns
103905:31 Jul 20:43:46 ERROR [geoserver.rest] - No such style: capital
103906:31 Jul 20:43:46 ERROR [geoserver.rest] - 
104032:31 Jul 20:43:47 WARN [support.DisposableBeanAdapter] - Invocation of destroy method failed on bean with name 'geoServerLoader': org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'GWCLifeCycleHandler': Singleton bean creation not allowed while the singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method implementation!)

see the full build log for details.

http://aiolos.survey.ntua.gr/gisvm/dev/

Change history (12)

comment:1 Changed 6 years ago by friedjoff

On installation Cartaro checks if the GeoServer? workspace, datastore and feature types already exist before creating them. That's where the log entries related to Cartaro come from, so nothing to worry about.

comment:2 in reply to:  1 Changed 6 years ago by hamish

Replying to friedjoff:

On installation Cartaro checks if the GeoServer? workspace, datastore and feature types already exist before creating them. That's where the log entries related to Cartaro come from, so nothing to worry about.

is there any way to have them do that without pages and pages of error messages? it makes finding the real errors very hard if there is too much background noise.

thanks, Hamish

comment:3 Changed 6 years ago by kalxas

Priority: normalminor

Hamish, those errors are not to worry about. Regarding a quiet geoserver startup/shutdown, it would be nice to have. Any ideas?

comment:4 in reply to:  3 Changed 6 years ago by hamish

Replying to kalxas:

Hamish, those errors are not to worry about.

having lots of noisy false errors in the build logs makes the real errors harder to spot. so it is best to quieten them if we can.

e.g. real or not?

  ERROR: permission denied for relation geography_columns

thanks, Hamish

comment:5 Changed 6 years ago by kalxas

(In [10592]) trying to make geoserver startup and shutdown silent (refs#1188)

comment:6 in reply to:  5 Changed 6 years ago by hamish

Replying to hamish:

having lots of noisy false errors in the build logs makes the real errors harder to spot. so it is best to quieten them if we can.

Replying to kalxas:

(In [10592]) trying to make geoserver startup and shutdown silent (refs#1188)

I should have added that simply redirecting everything to /dev/null is not good either, because then you end up hiding real/important errors, and so make debugging harder.

it's better to go in and find the exact lines in the scripts being noisy, and add --quiet as needed, or just redirect stdout to /dev/null if that is where the noise is coming from, and leave stderr passing through.

same for the half-megabyte of rasdaman pgsql noise in the build log, but I don't understand why "-q" doesn't work there. Is there a "NOT QUIET;" or so in the db.sql command file or something?

thanks, Hamish

comment:7 Changed 6 years ago by kalxas

Before Cartaro and GeoNode? existed in OSGeoLive, GeoServer? was not launched within the build process and we did not get feedback in the build logs. I think it is ok to redirect the jetty output to /dev/null since we are testing GeoServer? for UAT anyway.

comment:8 Changed 6 years ago by hamish

In the long run, and even short term, we're not doing ourselves any favours by bulk masking errors.

In an individual command is making a known false-positive message, mask that individual command, not the entire script (or better: fix the calling command so the error never happens); it's much better and easier that we catch errors early than hope to catch everything at testing time.

regards, Hamish

comment:9 Changed 6 years ago by kalxas

Milestone: OSGeoLive7.0OSGeoLive7.5

There is not enough time to try to fix such a small detail IMHO. For 7.0 either we keep the full Jetty logs or not...

Regards, Angelos

comment:10 Changed 5 years ago by kalxas

Resolution: wontfix
Status: newclosed

comment:11 Changed 5 years ago by hamish

Milestone: OSGeoLive7.9OSGeoLive8.0
Resolution: wontfix
Status: closedreopened

it pollutes the error logs and so makes real errors hard to see.

please fix.

Hamish

comment:12 Changed 5 years ago by kalxas

Resolution: fixed
Status: reopenedclosed

The GeoServer? startup/shutdown log messages do not appear in 8.0 build logs.

Note: See TracTickets for help on using tickets.