Re: [galaxy-dev] error and question from using galaxy kickstart
Never mind folks, it was that I had an older version of nginx running with a different config file. After I added the upload module and restarted it, now I could simply go to the UI by just specifying the host name. But...how do I stop/start this still remains unclear. please help if you could. :-) I see that I have so many python processes and postgresql processes: bioinfo+ 101567 101415 0 19:41 ?00:00:04 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/python2 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/uwsgi --virtualenv /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv --ini-paste /media/libraryfiles/bioinfoadmin/bioinfoadmin/config/galaxy.ini --logdate --thunder-lock --master --processes 2 --threads 2 --logto /media/libraryfiles/bioinfoadmin/bioinfoadmin/uwsgi.log --socket 127.0.0.1:4001 --pythonpath lib --stats 127.0.0.1:9191 -b 16384 bioinfo+ 101568 101415 1 19:41 ?00:01:38 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/python ./lib/galaxy/main.py -c /media/libraryfiles/bioinfoadmin/bioinfoadmin/config/galaxy.ini --server-name=handler0 --log-file=/media/libraryfiles/bioinfoadmin/bioinfoadmin/handler0.log bioinfo+ 101569 101415 1 19:41 ?00:01:37 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/python ./lib/galaxy/main.py -c /media/libraryfiles/bioinfoadmin/bioinfoadmin/config/galaxy.ini --server-name=handler1 --log-file=/media/libraryfiles/bioinfoadmin/bioinfoadmin/handler1.log bioinfo+ 101570 101415 1 19:41 ?00:01:38 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/python ./lib/galaxy/main.py -c /media/libraryfiles/bioinfoadmin/bioinfoadmin/config/galaxy.ini --server-name=handler2 --log-file=/media/libraryfiles/bioinfoadmin/bioinfoadmin/handler2.log bioinfo+ 101571 101415 1 19:41 ?00:01:38 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/python ./lib/galaxy/main.py -c /media/libraryfiles/bioinfoadmin/bioinfoadmin/config/galaxy.ini --server-name=handler3 --log-file=/media/libraryfiles/bioinfoadmin/bioinfoadmin/handler3.log bioinfo+ 102477 101567 1 19:41 ?00:01:39 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/python2 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/uwsgi --virtualenv /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv --ini-paste /media/libraryfiles/bioinfoadmin/bioinfoadmin/config/galaxy.ini --logdate --thunder-lock --master --processes 2 --threads 2 --logto /media/libraryfiles/bioinfoadmin/bioinfoadmin/uwsgi.log --socket 127.0.0.1:4001 --pythonpath lib --stats 127.0.0.1:9191 -b 16384 bioinfo+ 102478 101567 1 19:41 ?00:01:39 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/python2 /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/bin/uwsgi --virtualenv /media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv --ini-paste /media/libraryfiles/bioinfoadmin/bioinfoadmin/config/galaxy.ini --logdate --thunder-lock --master --processes 2 --threads 2 --logto /media/libraryfiles/bioinfoadmin/bioinfoadmin/uwsgi.log --socket 127.0.0.1:4001 --pythonpath lib --stats 127.0.0.1:9191 -b 16384 $ ps -ef | grep -i post postgres 102744 1 0 19:41 ?00:00:00 /usr/lib/postgresql/10/bin/postgres -D /var/lib/postgresql/10/main -c config_file=/etc/postgresql/10/main/postgresql.conf postgres 102747 102744 0 19:41 ?00:00:00 postgres: 10/main: checkpointer process postgres 102748 102744 0 19:41 ?00:00:00 postgres: 10/main: writer process postgres 102749 102744 0 19:41 ?00:00:00 postgres: 10/main: wal writer process postgres 102750 102744 0 19:41 ?00:00:00 postgres: 10/main: autovacuum launcher process postgres 102751 102744 0 19:41 ?00:00:00 postgres: 10/main: stats collector process postgres 102752 102744 0 19:41 ?00:00:00 postgres: 10/main: bgworker: logical replication launcher postgres 103679 101415 0 19:42 ?00:00:00 /usr/lib/postgresql/9.5/bin/postmaster -D /var/lib/postgresql/9.5/main -c config_file=/etc/postgresql/9.5/main/postgresql.conf postgres 103689 103679 0 19:42 ?00:00:00 postgres: checkpointer process postgres 103690 103679 0 19:42 ?00:00:00 postgres: writer process postgres 103691 103679 0 19:42 ?00:00:00 postgres: wal writer process postgres 103692 103679 0 19:42 ?00:00:00 postgres: autovacuum launcher process postgres 103693 103679 0 19:42 ?00:00:01 postgres: stats collector process postgres 103694 103679 0 19:42 ?00:00:04 postgres: bioinfoadmin galaxy 127.0.0.1(36144) idle postgres 103695 103679 0 19:42 ?00:00:04 postgres: bioinfoadmin galaxy 127.0.0.1(36146) idle postgres 103696 103679 0 19:42 ?00:00:04 postgres: bioinfoadmin galaxy 127.0.0.1(36148) idle postgres 103697 103679 0 19:42 ?00:00:04 postgres: bioinfoadmin galaxy 127.0.0.1(36150) idle postgres 103698 103679 0 19:42 ?00:00:11 postgres: bioinfoadmin galaxy 127.0.0.1(36152) idle postgres 103699 103679 0 19:42 ?00:00:11
[galaxy-dev] error and question from using galaxy kickstart
Hi Folks, So I managed to ran through the ansible. What I did was to remove certain steps. For example, I don't need slurm-drmaa and docker, then I skipped the update cache. After these minor changes, it finished successfully(?) with an error message it ignored. Then I tried to access the UI, but nothing worked. I pasted it below for your reference. If anyone has seen this before, please help. :-) Sorry for the beginner question, so once the ansible playbook ran through...seems the galaxy and the postgresql etc were started. How do I start/stop them manually? Do I have to run the playbook every time I want to run galaxy or only after I modify the playbook? Also, if I don't look at the log, I don't even know that the UI is at 127.0.0.1:4001. Is there any documentation for this? Thanks, Rui error message: galaxy.web.stack INFO 2018-10-12 19:41:53,874 [p:102477,w:1,m:0] [MainThread] Galaxy server instance 'main.web.1' is running Starting server in PID 101567. serving on uwsgi://127.0.0.1:4001 galaxy.jobs.handler ERROR 2018-10-12 19:42:48,487 [p:102477,w:1,m:0] [JobHandlerQueue.monitor_thread] Exception in monitor_step Traceback (most recent call last): File "lib/galaxy/jobs/handler.py", line 213, in __monitor self.__monitor_step() File "lib/galaxy/jobs/handler.py", line 272, in __monitor_step .order_by(model.Job.id).all() File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2737, in all return list(self) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2889, in __iter__ return self._execute_and_instances(context) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/orm/query.py", line 2912, in _execute_and_instances result = conn.execute(querycontext.statement, self._params) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 948, in execute return meth(self, multiparams, params) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/sql/elements.py", line 269, in _execute_on_connection return connection._execute_clauseelement(self, multiparams, params) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1060, in _execute_clauseelement compiled_sql, distilled_params File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1200, in _execute_context context) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1413, in _handle_dbapi_exception exc_info File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/util/compat.py", line 203, in raise_from_cause reraise(type(exception), exception, tb=exc_tb, cause=cause) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/base.py", line 1193, in _execute_context context) File "/media/libraryfiles/bioinfoadmin/bioinfoadmin/.venv/local/lib/python2.7/site-packages/sqlalchemy/engine/default.py", line 507, in do_execute cursor.execute(statement, parameters) OperationalError: (psycopg2.OperationalError) server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. [SQL: 'SELECT EXISTS (SELECT history_dataset_association.id, history_dataset_association.history_id, history_dataset_association.dataset_id, history_dataset_association.create_time, history_dataset_association.update_time, history_dataset_association.state, history_dataset_association.copied_from_history_dataset_association_id, history_dataset_association.copied_from_library_dataset_dataset_association_id, history_dataset_association.name, history_dataset_association.info, history_dataset_association.blurb, history_dataset_association.peek, history_dataset_association.tool_version, history_dataset_association.extension, history_dataset_association.metadata, history_dataset_association.parent_id, history_dataset_association.designation, history_dataset_association.deleted, history_dataset_association.visible, history_dataset_association.extended_metadata_id, history_dataset_association.version, history_dataset_association.hid, history_dataset_association.purged, history_dataset_association.hidden_beneath_collection_instance_id \nFROM history_dataset_association, job_to_output_dataset \nWHERE job.id = job_to_output_dataset.job_id AND history_dataset_association.id = job_to_output_dataset.dataset_id AND history_dataset_association.deleted = true) AS anon_1, EXISTS (SELECT history_dataset_collection_association.id \nFROM
Re: [galaxy-dev] can't create user on a new instance
Hey Folks,
When I used the kickstart, I hit this always:
TASK [galaxyprojectdotorg.galaxy-os : Update APT cache]
*
[WARNING]: sftp transfer mechanism failed on [localhost]. Use
ANSIBLE_DEBUG=1 to see detailed information
fatal: [localhost]: FAILED! => {"changed": false, "failed": true, "msg":
"Failed to update apt cache."}
Have you seen this before? If you do, please give me a hand. :)
Thanks,
Rui
On Fri, Oct 12, 2018 at 2:17 PM Rui Wang wrote:
> Hi Qiang,
>
> Let me try that. I think the postgres might be contaminated by the attempt
> to use kickstart. During that it modify the config of postgres permissions
> and it took me a while to clean those to get postgres working again(which
> may or may not really clean the change completely).
>
> I'll get back to you on this. Also I'll let you know my attempts on the
> kickstart. The problem was with the updater. :-(
>
> Thanks,
> Rui
>
> On Fri, Oct 12, 2018 at 12:23 PM Qiang Gu wrote:
>
>> Hi Rui,
>>
>> Galaxy will use the default sqlite if you comment out the db setting the
>> config file (`config/galaxy.yml`). You mean the sqlite works the same as
>> the postgresql, which doesn't allow you to create users?
>> If that's the case, try `git clone` a new galaxy repo, in the galaxy
>> folder, `git checkout remotes/original/release_18.05`, `git checkout -b
>> release_18.05`, `./run.sh`.
>> Basically, I would like to make the sqlite working first, then switch to
>> postgresql. The above-mentioned steps may help identify the hidden issue.
>>
>> Good luck!
>>
>> -Qiang
>>
>>
>> --
>> *From:* Rui Wang [ruiwang...@gmail.com]
>> *Sent:* Friday, October 12, 2018 1:01 AM
>> *To:* Qiang Gu
>> *Cc:* galaxy-dev@lists.galaxyproject.org
>> *Subject:* Re: [galaxy-dev] can't create user on a new instance
>>
>> Hi Qiang,
>>
>> Thanks so much for the email. The default sqlite seems to be the same. I
>> spent some time with the kickstart. That would be fantastic if it
>> works...sadly it failed on me. :-( Let me make some more effort on that.
>> Btw, do you have a better version of the instructions for the kickstart?
>>
>> Cheers,
>> Rui
>>
>> On Wed, Oct 10, 2018 at 10:12 PM Qiang Gu wrote:
>>
>>> Hi Rui,
>>>
>>> Does the default database sqlite work for you? I guess there is certain
>>> mis-configuration in your
>>> postgresql settings or certain element in the config/galaxy.yml file is
>>> broken. Try to enter your postgresql database in terminal using the
>>> same login info and create a table to make sure you have proper privileges.
>>> Alternatively, using GalaxyKickStart (
>>> https://github.com/ARTbio/GalaxyKickStart) to deploy a server
>>> isn't that difficult and a postgresql database comes with it by default.
>>> Good luck!
>>>
>>> Thanks,
>>>
>>> -Qiang
>>>
>>> --
>>> *From:* galaxy-dev [galaxy-dev-boun...@lists.galaxyproject.org] on
>>> behalf of Rui Wang [ruiwang...@gmail.com]
>>> *Sent:* Wednesday, October 10, 2018 9:30 PM
>>> *To:* galaxy-dev@lists.galaxyproject.org
>>> *Subject:* Re: [galaxy-dev] can't create user on a new instance
>>>
>>> Hi Folks,
>>>
>>> I still could not create new user account with the same error message.
>>> Has anyone happened to see this before?
>>>
>>> Cheers,
>>> Rui
>>>
>>> On Tue, Oct 9, 2018 at 5:48 PM Rui Wang wrote:
>>>
Hey Folks,
I just installed a new 18.05 instance with a new postgresql db created.
However, the UI doesn't allow me to create any user. After I provided all
input information, it says
galaxy.web.framework.webapp WARNING 2018-10-09 17:28:35,735
[p:32925,w:1,m:0] [uWSGIWorker1Core2] Wrong session token found, denying
request
in the server log. Btw, I enabled 'allow to create user' and admin user
list is empty.
I looked into it, and it's a function in
lib/galaxy/web/framework/webapp.py:
def check_csrf_token(self):
session_csrf_token =
self.request.params.get("session_csrf_token", None)
problem = False
if not session_csrf_token:
log.warning("No session_csrf_token set, denying request.")
problem = True
elif session_csrf_token != self.session_csrf_token:
log.warning("Wrong session token found, denying request.")
problem = True
if problem:
return self.show_warn_message("Failed to authorize action.")
Could someone give me a hand? :-)
Cheers,
Rui
>>>
___
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/
Re: [galaxy-dev] can't create user on a new instance
Hi Qiang,
I looked at the postgres, here is the ownership info:
bioinfoadmin=> \l
List of databases
Name |Owner | Encoding | Collate |Ctype|
Access privileges
--+--+--+-+-+---
bioinfoadmin | bioinfoadmin | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
citation | bioinfoadmin | 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)
Does this look okay to you? the db bioinfoadmin is the one that is set in
the galaxy config, and it's owned by
the user bioinfoadmin which is used to start galaxy.
Thanks,
Rui
On Wed, Oct 10, 2018 at 10:12 PM Qiang Gu wrote:
> Hi Rui,
>
> Does the default database sqlite work for you? I guess there is certain
> mis-configuration in your
> postgresql settings or certain element in the config/galaxy.yml file is
> broken. Try to enter your postgresql database in terminal using the same
> login info and create a table to make sure you have proper privileges.
> Alternatively, using GalaxyKickStart (
> https://github.com/ARTbio/GalaxyKickStart) to deploy a server
> isn't that difficult and a postgresql database comes with it by default.
> Good luck!
>
> Thanks,
>
> -Qiang
>
> --
> *From:* galaxy-dev [galaxy-dev-boun...@lists.galaxyproject.org] on behalf
> of Rui Wang [ruiwang...@gmail.com]
> *Sent:* Wednesday, October 10, 2018 9:30 PM
> *To:* galaxy-dev@lists.galaxyproject.org
> *Subject:* Re: [galaxy-dev] can't create user on a new instance
>
> Hi Folks,
>
> I still could not create new user account with the same error message. Has
> anyone happened to see this before?
>
> Cheers,
> Rui
>
> On Tue, Oct 9, 2018 at 5:48 PM Rui Wang wrote:
>
>> Hey Folks,
>>
>> I just installed a new 18.05 instance with a new postgresql db created.
>> However, the UI doesn't allow me to create any user. After I provided all
>> input information, it says
>>
>> galaxy.web.framework.webapp WARNING 2018-10-09 17:28:35,735
>> [p:32925,w:1,m:0] [uWSGIWorker1Core2] Wrong session token found, denying
>> request
>>
>> in the server log. Btw, I enabled 'allow to create user' and admin user
>> list is empty.
>>
>> I looked into it, and it's a function in
>> lib/galaxy/web/framework/webapp.py:
>>
>> def check_csrf_token(self):
>> session_csrf_token =
>> self.request.params.get("session_csrf_token", None)
>> problem = False
>> if not session_csrf_token:
>> log.warning("No session_csrf_token set, denying request.")
>> problem = True
>> elif session_csrf_token != self.session_csrf_token:
>> log.warning("Wrong session token found, denying request.")
>> problem = True
>>
>> if problem:
>> return self.show_warn_message("Failed to authorize action.")
>>
>> Could someone give me a hand? :-)
>>
>> Cheers,
>> Rui
>>
>
___
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/
Re: [galaxy-dev] can't create user on a new instance
Hi Marius,
Thanks for your suggestion! I tried it with a different browser that never
accessed galaxy, but it still gave me the same message. :-( Any thoughts?
Cheers,
Rui
On Wed, Oct 10, 2018 at 11:25 PM Marius van den Beek
wrote:
> Hi Rui,
>
> The session token is used to prevent certain kinds of attacks. Your
> browser may still have a session token for the old instance. You can delete
> the cookies for this address in your browser and you should be issued a new
> and valid token.
>
> Hope that helps,
> Marius
>
> On Thu, Oct 11, 2018, 7:12 AM Qiang Gu wrote:
>
>> Hi Rui,
>>
>> Does the default database sqlite work for you? I guess there is certain
>> mis-configuration in your
>> postgresql settings or certain element in the config/galaxy.yml file is
>> broken. Try to enter your postgresql database in terminal using the same
>> login info and create a table to make sure you have proper privileges.
>> Alternatively, using GalaxyKickStart (
>> https://github.com/ARTbio/GalaxyKickStart) to deploy a server
>> isn't that difficult and a postgresql database comes with it by default.
>> Good luck!
>>
>> Thanks,
>>
>> -Qiang
>>
>> --
>> *From:* galaxy-dev [galaxy-dev-boun...@lists.galaxyproject.org] on
>> behalf of Rui Wang [ruiwang...@gmail.com]
>> *Sent:* Wednesday, October 10, 2018 9:30 PM
>> *To:* galaxy-dev@lists.galaxyproject.org
>> *Subject:* Re: [galaxy-dev] can't create user on a new instance
>>
>> Hi Folks,
>>
>> I still could not create new user account with the same error message.
>> Has anyone happened to see this before?
>>
>> Cheers,
>> Rui
>>
>> On Tue, Oct 9, 2018 at 5:48 PM Rui Wang wrote:
>>
>>> Hey Folks,
>>>
>>> I just installed a new 18.05 instance with a new postgresql db created.
>>> However, the UI doesn't allow me to create any user. After I provided all
>>> input information, it says
>>>
>>> galaxy.web.framework.webapp WARNING 2018-10-09 17:28:35,735
>>> [p:32925,w:1,m:0] [uWSGIWorker1Core2] Wrong session token found, denying
>>> request
>>>
>>> in the server log. Btw, I enabled 'allow to create user' and admin user
>>> list is empty.
>>>
>>> I looked into it, and it's a function in
>>> lib/galaxy/web/framework/webapp.py:
>>>
>>> def check_csrf_token(self):
>>> session_csrf_token =
>>> self.request.params.get("session_csrf_token", None)
>>> problem = False
>>> if not session_csrf_token:
>>> log.warning("No session_csrf_token set, denying request.")
>>> problem = True
>>> elif session_csrf_token != self.session_csrf_token:
>>> log.warning("Wrong session token found, denying request.")
>>> problem = True
>>>
>>> if problem:
>>> return self.show_warn_message("Failed to authorize action.")
>>>
>>> Could someone give me a hand? :-)
>>>
>>> Cheers,
>>> Rui
>>>
>> ___
>> Please keep all replies on the list by using "reply all"
>> in your mail client. To manage your subscriptions to this
>> and other Galaxy lists, please use the interface at:
>> https://lists.galaxyproject.org/
>>
>> To search Galaxy mailing lists use the unified search at:
>> http://galaxyproject.org/search/
>
>
___
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/
[galaxy-dev] Error when trying to update tool vcf_to_alignment in testtoolshed
Hi there
I had a failed updated (network problem) of the sanbi-uwc tool
vcf_to_alignment and now when I try and do an update I get:
$ planemo shed_update --shed_target testtoolshed
cd '/home/pvh/Documents/code/SANBI/tools-sanbi-uwc/tools/vcf_to_alignment'
&& git rev-parse HEAD
cd '/home/pvh/Documents/code/SANBI/tools-sanbi-uwc/tools/vcf_to_alignment'
&& git diff --quiet
Could not update vcf_to_alignment
('Connection aborted.', RemoteDisconnected('Remote end closed connection
without response',))
Repository metadata updated successfully for repository 'vcf_to_alignment'
on the test Tool Shed.
Failed to update repository contents for repository 'vcf_to_alignment' on
the test Tool Shed.
Nothing that I try on my side seems to resolve this. Any ideas? Is the
problem on the toolshed side?
Thanks,
Peter
___
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/
Re: [galaxy-dev] can't create user on a new instance
Hi Qiang,
Thanks so much for the email. The default sqlite seems to be the same. I
spent some time with the kickstart. That would be fantastic if it
works...sadly it failed on me. :-( Let me make some more effort on that.
Btw, do you have a better version of the instructions for the kickstart?
Cheers,
Rui
On Wed, Oct 10, 2018 at 10:12 PM Qiang Gu wrote:
> Hi Rui,
>
> Does the default database sqlite work for you? I guess there is certain
> mis-configuration in your
> postgresql settings or certain element in the config/galaxy.yml file is
> broken. Try to enter your postgresql database in terminal using the same
> login info and create a table to make sure you have proper privileges.
> Alternatively, using GalaxyKickStart (
> https://github.com/ARTbio/GalaxyKickStart) to deploy a server
> isn't that difficult and a postgresql database comes with it by default.
> Good luck!
>
> Thanks,
>
> -Qiang
>
> --
> *From:* galaxy-dev [galaxy-dev-boun...@lists.galaxyproject.org] on behalf
> of Rui Wang [ruiwang...@gmail.com]
> *Sent:* Wednesday, October 10, 2018 9:30 PM
> *To:* galaxy-dev@lists.galaxyproject.org
> *Subject:* Re: [galaxy-dev] can't create user on a new instance
>
> Hi Folks,
>
> I still could not create new user account with the same error message. Has
> anyone happened to see this before?
>
> Cheers,
> Rui
>
> On Tue, Oct 9, 2018 at 5:48 PM Rui Wang wrote:
>
>> Hey Folks,
>>
>> I just installed a new 18.05 instance with a new postgresql db created.
>> However, the UI doesn't allow me to create any user. After I provided all
>> input information, it says
>>
>> galaxy.web.framework.webapp WARNING 2018-10-09 17:28:35,735
>> [p:32925,w:1,m:0] [uWSGIWorker1Core2] Wrong session token found, denying
>> request
>>
>> in the server log. Btw, I enabled 'allow to create user' and admin user
>> list is empty.
>>
>> I looked into it, and it's a function in
>> lib/galaxy/web/framework/webapp.py:
>>
>> def check_csrf_token(self):
>> session_csrf_token =
>> self.request.params.get("session_csrf_token", None)
>> problem = False
>> if not session_csrf_token:
>> log.warning("No session_csrf_token set, denying request.")
>> problem = True
>> elif session_csrf_token != self.session_csrf_token:
>> log.warning("Wrong session token found, denying request.")
>> problem = True
>>
>> if problem:
>> return self.show_warn_message("Failed to authorize action.")
>>
>> Could someone give me a hand? :-)
>>
>> Cheers,
>> Rui
>>
>
___
Please keep all replies on the list by using "reply all"
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
https://lists.galaxyproject.org/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/
