Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can CRISPRAnalyzeR be installed on AWS instances? #36

Open
xuguorong2016 opened this issue Jan 20, 2018 · 9 comments
Open

Can CRISPRAnalyzeR be installed on AWS instances? #36

xuguorong2016 opened this issue Jan 20, 2018 · 9 comments

Comments

@xuguorong2016
Copy link

Hi Jan,

Thanks for your nice tool CRISPRAnalyzeR!
I am wondering if CRISPRAnalyzeR can be installed an AWS instance though I have installed docker and the CRISPRAnalyzeR image on an AWS instance, but I just cannot open it from the browser.
screen shot 2018-01-19 at 10 36 15 pm
screen shot 2018-01-19 at 10 36 24 pm

In the security port, I have opened the 8000 port.

Your response would be really appreciated!
Guorong

@jwinter6
Copy link
Collaborator

Hi Guorong,
thats actually interesting, as the docker container should also work on AWS machines.

Have you used the latest version V 1.50?
I updated it 3 days ago.

Please do me huge favour:
can you login to the AWS instance and get the logs for me?

Either by logging into the docker container shell or by starting the docker container with mounting the log folder:
docker run -e verbose_logfiles=TRUE -v /FOLDERONDISK:/srv/shiny-server/CRISPRAnalyzeR/log/ -v /FOLDERONDISK:/var/log/shiny-server/ -p 8000:8000 boutroslab/crispranalyzer:V1.50

Best,
Jan

@xuguorong2016
Copy link
Author

Hi Jan,

Thanks for your response!
I run CRISPRAnalyzeR v1.5 on the AWS instance and then output the logs in the logs folder. Please see the below command and logs. I still have the same issue with the v1.5.

Please let me know if you need anything else.

Thanks,
Guorong

[ec2-user@ip-172-31-17-138 ~]$ sudo docker run -e verbose_logfiles=TRUE -v /home/ec2-user/logs:/srv/shiny-server/CRISPRAnalyzeR/log/ -v /FOLDERONDISK:/var/log/shiny-server/ -p 8000:8000 boutroslab/crispranalyzer:1.50
[CUSTOM] setting enhanced websocket settings
[CUSTOM] setting verbose shiny server and application logfiles
[CUSTOM] setting the path to the COSMIC database
[CUSTOM] EnrichR interface
[CUSTOM] setting the EnrichR URL
[CUSTOM] Set maximum upload Size
[CUSTOM] setting number of threads for Bowtie2
[CUSTOM] setting Logs
Starting Shiny-Server
As a default, please navigate to http://localhost:8000/CRISPRAnalyzeR/ to access CRISPRAnalyzeR
^C[ec2-user@ip-172-31-17-138 ~]$ ls
logs
[ec2-user@ip-172-31-17-138 ~]$ cd logs/
[ec2-user@ip-172-31-17-138 logs]$ ls
access.log
[ec2-user@ip-172-31-17-138 logs]$ more access.log
108.83.5.212 - - [20/Jan/2018:17:07:32 +0000] 500
127.0.0.1 - - [20/Jan/2018:17:07:32 +0000] 500

@jwinter6
Copy link
Collaborator

Hi,

is there just an access.log?
There should be way more, app.log, analysis.log, fastq_extraction.log etc.

And there is no CRISPRAnalyzer%X_%date.log ?
COuld you start run it normal and then login to the docker container (docker ps then docker exec -it CONTAINERID /bin/bash and then get the shiny server log in /var/log/shiny-server/ ?

Thanks for your help,
Jan

@xuguorong2016
Copy link
Author

Hi Jan,

No, I did not find any other logs except access.log. And the access.log is only two lines.
I just tried the command
docker run --rm -p 8000:8000 boutroslab/crispranalyzer:latest

And then I run the commands you gave to me, I got the below error.
screen shot 2018-01-20 at 1 03 27 pm

I am not sure if the contain id is correct or not.

Thanks,
Guorong

@jwinter6
Copy link
Collaborator

jwinter6 commented Jan 20, 2018 via email

@xuguorong2016
Copy link
Author

Hi Jan,

Thanks a lot! I attached the shiny-server.log for you.
Besides, I already opened all ports on my aws instance.

shiny-server.log.zip

Best,
Guorong

@jwinter6
Copy link
Collaborator

jwinter6 commented Jan 20, 2018 via email

@xuguorong2016
Copy link
Author

Hi Jan,

Thanks a lot for your help!
I am still new to docker and just know how to copy the folder from the container to my local machine. So the whole log folder is attached for you.
log.zip

Thanks again,
Guorong

@jwinter6
Copy link
Collaborator

thanks I have a look at the logs :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants