dhis2-devs team mailing list archive

[Simen Skogly Russnes <simen.s.russnes@xxxxxxxxx>]

Hi,

I helped solve this problem for someone else yesterday. It seems that you
need to remove the entry in the systemsetting table of the psql database
for SMS Config. I think it was called keySmsConfig, so a simple DELETE FROM
systemsetting WHERE name='keySmsConfig'; should do.

On Wed, Jan 20, 2016 at 11:14 AM, Steven Uggowitzer <whotopia@xxxxxxxxx>
wrote:

> We've been trying to upgrade a working 2.21 instance to 2.22.   Noting the
> new dhis2.conf file, we set this up, then upgraded war.
>
> Problems observed as follows:
>
>    1. The instance had a working ClickATell configuration.   Until I
>    removed all SMS configuration info DHIS would not start and I'd get errors
>    like:
>    [image: Inline image 1]
>    So I guess solution is to remove existing SMS configs, but I would
>    suggest some kind of internal upgrade
>    2. So fixing (1) above, I tried again, and this time oddly Tomcat
>    started listening to tcp6 instead of IPv4.   I've never seen that before,
>    even in my home environment which has IPv6.  It wasn't doing this when
>    running 2.21.  Anyway I added -Djava.net.preferIPv4Stack=true
>    -Djava.net.preferIPv4Addresses   to the startup for Tomcat and that seemed
>    to fix that issue.
>    3. The whole 2.22 system starts up properly with no errors or warning.
>    However now there is no web output at all.   Logs are created but HTTP
>    session returns nothing and closes.   I tried debugging by directly
>    telnetting to localhost:8081 where this particular service runs  GET /
>    returns nothing and the session closes.
>
> For now we have rollled back to 2.21.    Any suggestions???
>
> Thanks
> Steven
>
>
>
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dhis2-devs
> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dhis2-devs
> More help   : https://help.launchpad.net/ListHelp
>
>