Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fresh install Ubuntu 14.04 - Geoserver-geonode problem - latest beta version. #2076

Closed
JamesLeonDufour opened this issue Feb 13, 2015 · 23 comments
Milestone

Comments

@JamesLeonDufour
Copy link

While installing the latest beta version on Ubuntu 14.04, got this error message and didn't manage to fix it .

  • Starting Tomcat servlet engine tomcat7 [fail]
    dpkg: error processing package geoserver-geonode (--configure):
    subprocess installed post-installation script returned error exit status 1
    dpkg: dependency problems prevent configuration of geonode:
    geonode depends on geoserver-geonode | geoserver; however:
    Package geoserver-geonode is not configured yet.
    Package geoserver is not installed.

dpkg: error processing package geonode (--configure):
dependency problems - leaving unconfigured
Setting up python-software-properties (0.92.37.3) ...
No apport report written because the error message indicates its a followup error from a previous failure.
Errors were encountered while processing:
geoserver-geonode
geonode
E: Sub-process /usr/bin/dpkg returned an error code (1)

@simod
Copy link
Member

simod commented Feb 13, 2015

@JamesLeonDufour thanks for reporting this. Is indeed weird, I will test it soon. Can you confirm that you installed GeoNode on a new machine?

@JamesLeonDufour
Copy link
Author

Had the problem when upgrading from a 2.4b11 version, so tried on a new machine and had same problem. Thanks in advance for your feedback.

@JamesLeonDufour
Copy link
Author

@simod Any update, I m a bit stuck right now.. :o(

@simod
Copy link
Member

simod commented Feb 18, 2015

@JamesLeonDufour I installed GeoNode b22 yesterday on a fresh 14.04 machine and I had no issues. Everything went fine. Sorry but I can't replicate this.

@JamesLeonDufour
Copy link
Author

Tried again on a new machine, and got the exact same problem.

Creating config file /etc/logrotate.d/tomcat7 with new version

  • Starting Tomcat servlet engine tomcat7 [ OK ]
    Processing triggers for ureadahead (0.100.0-16) ...
    Setting up geoserver-geonode (2.0+201501230745) ...
  • Stopping Tomcat servlet engine tomcat7 [ OK ]
  • Starting Tomcat servlet engine tomcat7 [fail]
    dpkg: error processing package geoserver-geonode (--configure):
    subprocess installed post-installation script returned error exit status 1
    dpkg: dependency problems prevent configuration of geonode:
    geonode depends on geoserver-geonode | geoserver; however:
    Package geoserver-geonode is not configured yet.
    Package geoserver is not installed.

dpkg: error processing package geonode (--configure):
dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.19-0ubuntu6.5) ...
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for ufw (0.34~rc-0ubuntu2) ...
Processing triggers for python-support (1.0.15) ...
Processing triggers for ca-certificates (20130906ubuntu2) ...
Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....
done.
done.
Errors were encountered while processing:
geoserver-geonode
geonode
E: Sub-process /usr/bin/dpkg returned an error code (1)

Am I missing something in the install ?

$ sudo add-apt-repository ppa:geonode/testing
$ sudo apt-get update
$ sudo apt-get install geonode

Best

@simod
Copy link
Member

simod commented Feb 18, 2015

All correct, do you have any firewalls or something that could prevent connections?

@JamesLeonDufour
Copy link
Author

I dont think so, i never had problems before, I'll check but it s on EC2 AWS amazon.

@davekennewell
Copy link

G'day James,

I'm not sure of the details of your error message, but it does sound like
something on the amazon end.

I had many similar messages using free-tier hardware, where processes would
time out before they had finished, simply because the little freetier cpu
couldn't run fast enough to get the job done.

If it helps, this works for me as of this evening:
Launch an m3.medium instance based on ami-b1eb9e8b

type this (first 3 directly copied from your mail above)
$ sudo add-apt-repository ppa:geonode/testing
$ sudo apt-get update
$ sudo apt-get install geonode
$ geonode createsuperuser
$ sudo geonode-updateip _..**.**_ (using the public IP of your aws
instance)

OK that's exhausted all my knowledge now :)

cheers
Dave

On 18 February 2015 at 21:43, James Léon-Dufour [email protected]
wrote:

I dont think so, i never had problems before, I'll check but it s on EC2
AWS amazon.


Reply to this email directly or view it on GitHub
#2076 (comment).

@simod
Copy link
Member

simod commented Feb 18, 2015

I can confirm that on a t2.micro the installation breaks. As @davekennewell says it could be related to poor performance machine. Thanks for reporting

@JJediny
Copy link
Member

JJediny commented Feb 18, 2015

I can confirm that you need a minimum of an m3.medium... I've done a lot of research the best price point for performance is a c3.xlarge @~42 US cents/hr. Ideally c3.2xlarge at ~60c/hr as this tier includes the most important spec people forget about in throughput on the Internet latency/speed @1gb LAN

@JamesLeonDufour
Copy link
Author

Thanks for the comment, I migrated on another hosting provider and I got another issue :o(

root@vps26298:~# geonode createsuperuser
Username: admin
Traceback (most recent call last):
File "/usr/bin/django-admin", line 5, in
management.execute_from_command_line()
File "/usr/lib/python2.7/dist-packages/django/core/management/init.py", line 399, in execute_from_command_line
utility.execute()
File "/usr/lib/python2.7/dist-packages/django/core/management/init.py", line 392, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 242, in run_from_argv
self.execute(_args, *_options.dict)
File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 285, in execute
output = self.handle(args, _options)
File "/usr/lib/python2.7/dist-packages/django/contrib/auth/management/commands/createsuperuser.py", line 102, in handle
self.UserModel._default_manager.db_manager(database).get_by_natural_key(username)
File "/usr/lib/python2.7/dist-packages/django/contrib/auth/models.py", line 167, in get_by_natural_key
return self.get(
{self.model.USERNAME_FIELD: username})
File "/usr/lib/python2.7/dist-packages/django/db/models/manager.py", line 151, in get
return self.get_queryset().get(_args, **kwargs)
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 301, in get
num = len(clone)
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 77, in len
self._fetch_all()
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 854, in _fetch_all
self._result_cache = list(self.iterator())
File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 220, in iterator
for row in compiler.results_iter():
File "/usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 710, in results_iter
for rows in self.execute_sql(MULTI):
File "/usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", line 780, in execute_sql
cursor = self.connection.cursor()
File "/usr/lib/python2.7/dist-packages/django/db/backends/init.py", line 159, in cursor
cursor = util.CursorWrapper(self._cursor(), self)
File "/usr/lib/python2.7/dist-packages/django/db/backends/init.py", line 129, in _cursor
self.ensure_connection()
File "/usr/lib/python2.7/dist-packages/django/db/backends/init.py", line 124, in ensure_connection
self.connect()
File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 99, in exit
six.reraise(dj_exc_type, dj_exc_value, traceback)
File "/usr/lib/python2.7/dist-packages/django/db/backends/init.py", line 124, in ensure_connection
self.connect()
File "/usr/lib/python2.7/dist-packages/django/db/backends/init.py", line 112, in connect
self.connection = self.get_new_connection(conn_params)
File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 116, in get_new_connection
return Database.connect(**conn_params)
File "/usr/lib/python2.7/dist-packages/psycopg2/init.py", line 179, in connect
connection_factory=connection_factory, async=async)
django.db.utils.OperationalError: FATAL: database "geonode" does not exist

mmmmm

@gubuntu
Copy link

gubuntu commented Mar 6, 2015

original issue here shows the same symptoms as #2092

@ramavanan
Copy link

geonode uninstall procedure please

ubuntu command

@jj0hns0n jj0hns0n modified the milestone: 2.5.x Nov 18, 2015
@francbartoli
Copy link
Member

francbartoli commented Jun 17, 2016

I reproduce this issue during the preparation of a vagrant box. As already reported by @simod the problem is the allocated memory to the virtual machine template used to install geonode. After setting this larger the problem disappears.

Regarding docker:

@gubuntu can you check memory by running this command in your environment (assuming you are using the default machine)?

docker-machine inspect default | grep -i memory

@jj0hns0n does make sense treating this as bug and still open?

@jj0hns0n
Copy link
Member

ref #2593

@jamesmmbugua
Copy link

@JamesLeonDufour refering to your post dated Feb 14, 2015, I am having the same problem trying to install Geonode on a new ubuntu VM. Did you ever get a solution to this?

@ecerrillo
Copy link

@jamesmmbugua similar problem here. Did you manage to solve it?

@francbartoli
Copy link
Member

@jamesmmbugua @ecerrillo what version are you installing? And which ppa are you using?

@ecerrillo
Copy link

@francbartoli I'm trying to install geonode 2.4 on ubuntu 14.04. Ppa is: geonode/stable

I'm following the quick install section: http://docs.geonode.org/en/master/tutorials/install_and_admin/quick_install.html

Thanks!

@francbartoli
Copy link
Member

@ecerrillo what size does your memory have?

@jamesmmbugua
Copy link

jamesmmbugua commented Apr 25, 2017 via email

@UbuntuEvangelist
Copy link

I am having the same problem

@art5bv
Copy link

art5bv commented Mar 6, 2018

Package geoserver-geonode is not configured yet.
Package geoserver is not installed.
Ubuntu 17.10

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests