Le 02/06/2011 21:23, Nate Coraor a écrit :
Louise-Amélie Schmitt wrote:
On Thu, 2 Jun 2011 11:48:55 -0400, Nate Coraorn...@bx.psu.edu wrote:
Greg Von Kuster wrote:
Hello Louise,
I've CC'd Nate on this as he may be able to help - although no
guarantees. I'm not expert enough in this area to
Louise-Amélie Schmitt wrote:
Hello everyone
I have an issue when trying to import new datasets or when putting a
dataset into a history. I saw Edward Kirton had the same problem but he
got no answer:
http://lists.bx.psu.edu/pipermail/galaxy-dev/2010-May/002732.html
Here is the error
On Thu, 2 Jun 2011 11:48:55 -0400, Nate Coraor n...@bx.psu.edu wrote:
Greg Von Kuster wrote:
Hello Louise,
I've CC'd Nate on this as he may be able to help - although no
guarantees. I'm not expert enough in this area to know where to look
for
the cause. Perhaps someone in the community
Louise-Amélie Schmitt wrote:
On Thu, 2 Jun 2011 11:48:55 -0400, Nate Coraor n...@bx.psu.edu wrote:
Greg Von Kuster wrote:
Hello Louise,
I've CC'd Nate on this as he may be able to help - although no
guarantees. I'm not expert enough in this area to know where to look
for
the cause.
Ok, now it's the other install that doesn't work anymore.
Looks like a cuckoo's nest, they must be sharing something they
shouldn't, first arrived first served.
But I really don't see what's going wrong:
- They run from distinct galaxy copies
- They use different databases
- They use
Hello again
I tried deleting the compiled templates like Sarah Diehl did for her
user registration issue:
first thank you for your help. I tried reloading everything, cleared
the cache of my browser and tried it on a different computer whose
browser never before was on the Galaxy website. All
On 04/18/2011 11:28 AM, Louise-Amélie Schmitt wrote:
Hello again
I tried deleting the compiled templates like Sarah Diehl did for her
user registration issue:
first thank you for your help. I tried reloading everything, cleared
the cache of my browser and tried it on a different computer
On 04/14/2011 07:36 PM, Greg Von Kuster wrote:
Hello Louise,
I've CC'd Nate on this as he may be able to help - although no guarantees. I'm
not expert enough in this area to know where to look for the cause. Perhaps
someone in the community can help as well.
It is likely that LDAP is
On 04/15/2011 10:56 AM, Louise-Amélie Schmitt wrote:
Hi Hans, thanks for your reply.
- is your PostgreSQL database in sync with the database folder?
I'm sorry I'm not sure I get what you mean, what folder is it?
the folder where you keep the datasets, eg:
your local
Ooops, this is very right, I totally forgot about that. It woud have
become problematic at some point I guess. Thank you for pointing this
out!
I changed it so the new database is associated with brand new
appropriate directories. (and dropped and re-created the db again) But I
keep getting the
I assume when you dropped the old database and recreated the new, empty
database, you made sure the database connection string in universe_wsgi.ini was
correctly set. if so, when you started up Galaxy, it would have created all of
the required tables in the new database, and they would all be
On Apr 14, 2011, at 11:49 AM, Louise-Amélie Schmitt wrote:
Here is the result I got from the debug statements:
galaxy.web.controllers.library_common DEBUG 2011-04-14 17:46:02,286 ###
history: None
This is the problem - when you registered normally, a history would have been
automatically
The thing is, we use LDAP logging so we can't even access the website
without logging in.
Moreover, when I logged in, I arrived on the data analysis page where the
automatic unnamed history was obviously created in the history panel.
I forgot to mention we have issues creating and deleting
Hello Louise,
I've CC'd Nate on this as he may be able to help - although no guarantees. I'm
not expert enough in this area to know where to look for the cause. Perhaps
someone in the community can help as well.
It is likely that LDAP is playing a role in this behavior.
On Apr 14, 2011, at
14 matches
Mail list logo
