health-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Health-dev] Problems logging into a newly created instance [Was: He


From: Luis Falcon
Subject: Re: [Health-dev] Problems logging into a newly created instance [Was: Health-dev Digest, Vol 97, Issue 17]
Date: Thu, 19 Sep 2019 10:19:09 +0100

Hi Cornelius !
On Thu, 19 Sep 2019 03:02:22 +0000
Cornelius Lee <address@hidden> wrote:

> Good morning Luis,
> 
> Thank you for the suggestion.
> 
> I have taken a look at the link and have ensured that all the steps
> are performed correctly.
> 
> However, I am still unable to log into the health DB from the
> Gnuhealth Client.
> 
> Strangely enough, I am able to log into the health DB via the
> command-line as well. The following shows this.
> 
> gnuhealth@emr:~ $ psql -U gnuhealth -d health
> psql (10.10 (Ubuntu 10.10-0ubuntu0.18.04.1))
> Type "help" for help.
> 
> health=> \du  
>                                    List of roles
>  Role name |                         Attributes
>   | Member of
> -----------+------------------------------------------------------------+-----------
> gnuhealth | Create DB
>  | {} postgres  | Superuser, Create role, Create DB, Replication,
> Bypass RLS | {}
> 
> health=> \l  
>                                    List of databases
>     Name    |   Owner   | Encoding |   Collate   |    Ctype    |
> Access privileges
> ------------+-----------+----------+-------------+-------------+-----------------------
> federation | gnuhealth | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
> health     | gnuhealth | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
> postgres   | postgres  | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
> template0  | postgres  | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
> =c/postgres          + |           |          |             |
>     | postgres=CTc/postgres template1  | postgres  | UTF8     |
> en_US.UTF-8 | en_US.UTF-8 | =c/postgres          + |           |
>     |             |             | postgres=CTc/postgres (5 rows)
> 
> health=> \q  
> 
> 
> 
> Additionally,  where I suspect the problem lies is in the following
> step:
> 
> python3 ./trytond-admin --all --database=health
> 
> which is documented in the following:
> 
> https://en.wikibooks.org/wiki/GNU_Health/Installation#Initialize_the_database_instance
> 
> The difference I have noticed between the official stable version of
> gnuhealth and the snapshot one is, that after the above-mentioned
> command is executed, the following did not appear. ie.
> 
> "admin" password for "health":
> "admin" password confirmation:
> 
> Nothing appeared.(with the snapshot you have released.)
> Could this be the cause of me being unable to log into the health DB
> via the tryton-based Gnuhealth Client only?

Yes. If you don't get the prompt for changing the admin passwd during
the initialization, something went wrong in the process of DB creation,
and that DB is not usable.

Try creating a new one from scratch.

PS: Check the topic ;-)

Best
Luis


> 
> Hope this helps.
> 
> Regards,
> Cornelius
> 
> 
> ________________________________
> From: Health-dev <health-dev-bounces+cornelius=address@hidden>
> on behalf of address@hidden <address@hidden>
> Sent: Thursday, September 19, 2019 12:00 AM To: address@hidden
> <address@hidden> Subject: Health-dev Digest, Vol 97, Issue 17
> 
> Send Health-dev mailing list submissions to
>         address@hidden
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://lists.gnu.org/mailman/listinfo/health-dev
> or, via email, send a message with subject or body 'help' to
>         address@hidden
> 
> You can reach the person managing the list at
>         address@hidden
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Health-dev digest..."
> 
> 
> Today's Topics:
> 
>    1. Re: Development snapshot for upcoming 3.6 series [Was:Re:
>       Health-dev Digest, Vol 97, Issue 3] (Cornelius Lee)
>    2. Re: Development snapshot for upcoming 3.6 series [Was:Re:
>       Health-dev Digest, Vol 97, Issue 3] (Luis Falcon)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Wed, 18 Sep 2019 09:44:48 +0000
> From: Cornelius Lee <address@hidden>
> To: Luis Falcon <address@hidden>
> Cc: "address@hidden" <address@hidden>
> Subject: Re: [Health-dev] Development snapshot for upcoming 3.6 series
>         [Was:Re: Health-dev Digest, Vol 97, Issue 3]
> Message-ID:
>         <address@hidden>
> 
> Content-Type: text/plain; charset="iso-8859-1"
> 
> Good morning Luis,
> 
> Thanks for the advice.
> 
> I will try that and report back as soon as I can.
> 
> 
> Regards,
> Cornelius
> 
> 
> ________________________________
> From: Luis Falcon <address@hidden>
> Sent: Wednesday, September 18, 2019 5:36 PM
> To: Cornelius Lee <address@hidden>
> Cc: address@hidden <address@hidden>
> Subject: Re: Development snapshot for upcoming 3.6 series [Was:Re:
> [Health-dev] Health-dev Digest, Vol 97, Issue 3]
> 
> Good morning Cornelius !
> 
> On Wed, 18 Sep 2019 02:50:18 +0000
> Cornelius Lee <address@hidden> wrote:
> 
> > From Gnuhealth Client, at the password window, I am unable to get
> > pass the password authentication window, even with the correct
> > password entered. See attached. I don't think I am able to find any
> > errors as nothing much is displayed after entering the correct
> > password. However, I am able to connect to the healthDB externally
> > using an 3rd-party app, such as DBeaver.
> >  
> 
> You might need to configure the PG authentication method.
> 
> Take a look at :
> 
> https://en.wikibooks.org/wiki/GNU_Health/Installation#Verify_PostgreSQL_authentication_method
> 
> After bouncing the server check how it goes.
> 
> Bests
> Luis
> 
> 
> 
> --
> Dr. Luis Falcon, M.D.
> President, GNU Solidario
> GNU Health: Freedom and Equity in Healthcare
> www.gnuhealth.org<http://www.gnuhealth.org>
> GPG Fingerprint :ACBF C80F C891 631C 68AA  8DC8 C015 E1AE 0098 9199
> 
> Join us at GNU Health Con 2019 https://www.gnuhealthcon.org
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> <https://lists.gnu.org/archive/html/health-dev/attachments/20190918/c76be7a4/attachment.html>
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 18 Sep 2019 11:40:18 +0100
> From: Luis Falcon <address@hidden>
> To: Cornelius Lee <address@hidden>
> Cc: address@hidden
> Subject: Re: [Health-dev] Development snapshot for upcoming 3.6 series
>         [Was:Re: Health-dev Digest, Vol 97, Issue 3]
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=US-ASCII
> 
> Morning Cornelius !
> 
> On Wed, 18 Sep 2019 03:51:34 +0000
> Cornelius Lee <address@hidden> wrote:
> 
> > Good morning Luis,
> >
> > I have tried the Federation Resource Locator but have not been able
> > to retrieve information from the peoples table in the federation DB.
> >
> > Attached is the screenshot of a search query.  
> 
> Thanks for the feedback, and thank you for testing the FRL plugin !
> 
> Did you check the connection settings ?
> 
> Health -> Configuration -> Federation -> Node Configuration
> 
> Looking at your screenshot, you have entered the federation ID in both
> fields. The first field, the resource, is to be left with the default
> value (people).
> 
> Please send the link of the snapshot, not the snapshot itself in the
> mail . Check
> https://en.wikibooks.org/wiki/GNU_Health/FAQ#Can_I_include_screenshots_in_my_mails_?
> 
> PS: Thanks for updating the Wikibook !
> 
> Bests
> Luis
> 
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Health-dev mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/health-dev
> 
> 
> ------------------------------
> 
> End of Health-dev Digest, Vol 97, Issue 17
> ******************************************



-- 
Dr. Luis Falcon, M.D.
President, GNU Solidario
GNU Health: Freedom and Equity in Healthcare
www.gnuhealth.org
GPG Fingerprint :ACBF C80F C891 631C 68AA  8DC8 C015 E1AE 0098 9199
 
Join us at GNU Health Con 2019 https://www.gnuhealthcon.org



reply via email to

[Prev in Thread] Current Thread [Next in Thread]