@afabiani I have tried the conifg.yaml file you suggested and I am getting the same error.
If i understand the file structure properly, I believe it is a case where the configurations for those specific criteria I mentioned where not configured, unless its referred to as standard layout @afabiani
Hi everyone. Does anyone knows how to change document permission on batch update? I will have more than 6000 documents, and I need to assign privileges to all documents to Registered members only. Is there a command to run in container or maybe a SQL update directly on table in PostGIS? Thank you in advance.
I find it in Django admin... Documents > Metadata Batch edit
Hi, I am still new to django/geonode-project. If there are new updates to the geonode core codebase, how would someone update their own codebase?
Is this the proper way for a docker setup assuming the installation setup mentioned in the docs:
geonode@ubuntu:/opt/geonode_custom/geonode-project$ git pull geonode@ubuntu:/opt/geonode_custom/my_geonode$ docker-compose -f docker-compose.yml build --no-cache
I am trying to do the same thing. We had a fix for issue 7306 GeoNode/geonode#7306. I ran the commands according to https://docs.geonode.org/en/master/install/basic/index.html#update-geonode-core-to-the-latest-commit, and still having the issues with OGC Metadata Reference. Git status tells that Your branch is up to date with 'origin/master'. But the OGC reference metadata still there even after running makemigrations, migrate, collectstatic and restarting all containers.
Hi, after updating geonode to 3.2.1 (from git/pre-3.2.0), I'm getting a lot of these errors when uploading a layer:
[geoserver.notification] - channel is already closed due to channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'geonode' in vhost '/': received 'false' but current is 'true', class-id=40, method-id=10)
com.rabbitmq.client.AlreadyClosedException: channel is already closed due to channel error; protocol method: #method<channel.close>(reply-code=406, reply-text=PRECONDITION_FAILED - inequivalent arg 'durable' for exchange 'geonode' in vhost '/': received 'false' but current is 'true', class-id=40, method-id=10)
-e ./geonode/and commented out
GeoNode==3.2.1), then removed the dependency_link pointing to the Geonode Core repository from setup.py. After rebuilding the Docker containers, uploading data, and testing the backup, it worked!
2021-08-17 13:36:05,658 WARN [geoserver.geofence] - No source IP address found 2021-08-17 13:36:06,108 WARN [geoserver.geofence] - Error retrieving source address with Spring Request: No thread-bound request found: Are you referring to request attributes outside of an actual web request, or processing a request outside of the originally receiving thread? If you are actually operating within a web request and still receive this message, your code is probably running outside of DispatcherServlet: In this case, use RequestContextListener or RequestContextFilter to expose the current request. 2021-08-17 13:36:06,108 WARN [geoserver.geofence] - No source IP address foundmessage in my /geoserver_data/data/logs/geoserver.log
issuer=C = US, O = Let's Encrypt, CN = R3 --- No client certificate CA names sent Peer signing digest: SHA256 Peer signature type: RSA-PSS Server Temp Key: X25519, 253 bits --- SSL handshake has read 4687 bytes and written 404 bytes Verification: OK --- New, TLSv1.2, Cipher is ECDHE-RSA-AES256-GCM-SHA384 Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 Cipher : ECDHE-RSA-AES256-GCM-SHA384
Protocols enabled TLS1.2,TLS1.1,TLS1.0 Protocols not enabled SSLv3,SSLv2