gnumed-devel
[Top][All Lists]
Advanced

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

Re: [Gnumed-devel] [Gnumed-bugs] Unhandled exception - inbox with Kirk r


From: Karsten Hilbert
Subject: Re: [Gnumed-devel] [Gnumed-bugs] Unhandled exception - inbox with Kirk results could not find patient Kirk in database
Date: Tue, 31 May 2011 13:04:05 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Mon, May 30, 2011 at 08:29:44AM -0700, Jim Busser wrote:

> This was odd.

Indeed.

> I had started by trying to open an encounter history,
> except I had just logged into GNUmed and had not yet
> activated any patient, and so got the expected admonishment.
> 
> So, within the inbox, I clicked (I think) the first record
> and was warned some problem about not finding Kirk in the
> database.

That is, already, the odd part. The log shows that you
successfully logged in as "any-doc". Later on, when trying
to establish a new connection for writing, PostgreSQL
refuses access for the very same credentials.

The only logical explanation would be that something or
someone changed the any-doc credentials between establishing
two consecutive write connections such as - concurrently -
using another PostgreSQL tool.

In case this has most definitely not been the case and
should you be able to reproduce this behaviour then I would
be *extremely* interested in how.

> I then activated (I think) the second inbox item, also
> linked to Kirk, and I was brought to a list of documents but
> without Kirk in the dialog.

That's all followup problems.

We've had a somewhat similar sounding report (unable to
activate a virtual inbox message, which seems quite
impossible since the the virtual message only exists when it
exists) recently so I wonder whether that was actually
triggered by the same behaviour you experienced and the
failure to activate the message was actually just follow up
as well. We did not have a usable log in said other case,
unfortunately.

Karsten
-- 
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346



reply via email to

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