[GeoNode-users] Installation Problems with version 2.6 on Ubuntu 16.04

[Cliff Patterson]

No previous version installed. It was installed on a fresh OS.

On Jun 19, 2017 4:43 PM, "Israel López" <asralf at gmail.com> wrote:

Hi, did you have a previous version of genode installed???

I'm testing Geonode 2.6 too, but on Develoment mode, I had similar issues,
but "log-in" problem I solved running the create superuser command again.

The issue that remains is this one:

base.ResourceBase.tkeywords: (fields.W340) null has no effect on
ManyToManyField.

I don't understand it, but Geonode is running and working, if somebody
could explain me
how to fix it I will appreciate it.

Greetings.

2017-06-19 11:29 GMT-05:00 Cliff Patterson <cliffpatterson at gmail.com>:

> I finally reinstalled on a clean Ubuntu 16.04.2 (64 bit) VPS with 4GB of
> ram and still having the same issues:
>
>    1. Unable to log in with superuser credentials
>    2. unable to fully update IP. The system hangs at "Inspecting the
>    available layers in GeoServer ..."
>    3. Getting the following warning during install and when running
>    createssuperuser:
>
> WARNINGS:
> ?: (1_8.W001) The standalone TEMPLATE_* settings were deprecated in Django
> 1.8 and the TEMPLATES dictionary takes precedence. You must put the values
> of the following settings into your default TEMPLATES dict: TEMPLATE_DIRS.
> base.ResourceBase.tkeywords: (fields.W340) null has no effect on
> ManyToManyField.
>
> Bottom line, even on a 4GB machine, I cannot get Geonode working. Have the
> installation instructions changed or am I missing some critical step? I'm
> using these: http://geonode.org/blog/2017/05/17/geonode-2.6-released/
>
> Big thanks!
> Cliff
>
>
> On Fri, Jun 9, 2017 at 7:25 AM, Simone Dalmasso <simone.dalmasso at gmail.com
> > wrote:
>
>> Hi, well 2 GB are probably not enough. 4GB are the minimum I think. You
>> shopuld be able to find geoserver with locate geoserver, it is uncompressed
>> in /usr/share if I'm no wrong.
>>
>> 2017-06-09 13:03 GMT+02:00 Cliff Patterson <cliffpatterson at gmail.com>:
>>
>>> Thanks for the reply!
>>>
>>> I didn't see any errors (except for template warnings) during
>>> installation. I even saw that geonode-geoserver was installed but I can't
>>> find it post installation.
>>>
>>> I spun it up on a VM with 4 cores and 2GB of ram on Digital Ocean. Is
>>> this enough power for GeoNode?
>>>
>>> Thanks again for your help!
>>>
>>> Cheers,
>>> Cliff
>>>
>>> On Jun 9, 2017 3:17 AM, "Simone Dalmasso" <simone.dalmasso at gmail.com>
>>> wrote:
>>>
>>>> Hi, yes definitely geoserver needs to be there and the package should
>>>> install it. Make sure your machine is powerful enough, also during the
>>>> installation you should have gotten some errors.
>>>>
>>>> 2017-06-08 18:22 GMT+02:00 Cliff Patterson <cliffpatterson at gmail.com>:
>>>>
>>>>> PS: and I am unable to authenticate via the geonode website.
>>>>>
>>>>> On Thu, Jun 8, 2017 at 12:20 PM, Cliff Patterson <
>>>>> cliffpatterson at gmail.com> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> I decided to give Geonode 2.6 a go and installed it on a fresh VM
>>>>>> running Ubuntu 16.04.2 x64. I installed it with the following commands:
>>>>>>
>>>>>> sudo add-apt-repository ppa:geonode/stable
>>>>>> sudo apt-get update
>>>>>> sudo apt-get install geonode
>>>>>> geonode createsuperuser
>>>>>> sudo geonode-updateip 67.207.87.119
>>>>>>
>>>>>> When creating the super user, I get the following warning:
>>>>>>
>>>>>> geonode createsuperuser
>>>>>> System check identified some issues:
>>>>>>
>>>>>> WARNINGS:
>>>>>> ?: (1_8.W001) The standalone TEMPLATE_* settings were deprecated in
>>>>>> Django 1.8 and the TEMPLATES dictionary takes precedence. You must put the
>>>>>> values of the following settings into your default TEMPLATES dict:
>>>>>> TEMPLATE_DIRS.
>>>>>> base.ResourceBase.tkeywords: (fields.W340) null has no effect on
>>>>>> ManyToManyField.
>>>>>> Username: test
>>>>>> Email address:
>>>>>> Password:
>>>>>> Password (again):
>>>>>> Superuser created successfully.
>>>>>>
>>>>>> When running sudo geonode-updateip 67.207.87.119, the following
>>>>>> happens:
>>>>>>
>>>>>> 1) Hangs on "Inspecting the available layers in GeoServer ..."
>>>>>> 2) Geonode does get up and running at 67.207.87.119 but no ability to
>>>>>> login
>>>>>>
>>>>>> sudo geonode-updateip 67.207.87.119
>>>>>> Replacing SITEURL value with '67.207.87.119' in
>>>>>> /etc/geonode/local_settings.py ... done.
>>>>>> Adding entry for '67.207.87.119' in /usr/share/geoserver/data/printing/config.yaml
>>>>>> ... done.
>>>>>> Adding ALLOWED_HOSTS with in /etc/geonode/local_settings.py ... done.
>>>>>> Setting up oauth
>>>>>> Inspecting the available layers in GeoServer ...
>>>>>>
>>>>>> Am I missing something in the instructions? Do we need to install
>>>>>> Geoserver on Tomcat7 first, then Geonode? As far as I can see, Geoserver
>>>>>> has not been installed, which I thought was part of the geonode
>>>>>> installation, but I could be wrong.
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> geonode-users mailing list
>>>>> geonode-users at lists.osgeo.org
>>>>> https://lists.osgeo.org/mailman/listinfo/geonode-users
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Simone
>>>>
>>>
>>
>>
>> --
>> Simone
>>
>
>
> _______________________________________________
> geonode-users mailing list
> geonode-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/geonode-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geonode-users/attachments/20170619/36496a91/attachment-0001.html>