[jira] [Commented] (GRIFFIN-99) Griffin - Docker - API server doesn't start as MySQL doesn't start on the docker container.

2018-03-29 Thread Lionel Liu (JIRA)

[ 
https://issues.apache.org/jira/browse/GRIFFIN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16420076#comment-16420076
 ] 

Lionel Liu commented on GRIFFIN-99:
---

Hi [~AkashSharma], it has been a long time since we've solved this bug in 
docker, have you tested it? And would you close this ticket? Thanks a lot.

> Griffin - Docker - API server doesn't start as MySQL doesn't start on the 
> docker container.
> ---
>
> Key: GRIFFIN-99
> URL: https://issues.apache.org/jira/browse/GRIFFIN-99
> Project: Griffin (Incubating)
>  Issue Type: Bug
>  Components: completeness-batch
>Affects Versions: 0.2.0-incubating
> Environment: Mac OSX
>Reporter: Akash Sharma S
>Assignee: Lionel Liu
>Priority: Critical
>  Labels: SP_4
> Fix For: 0.2.0-incubating
>
>
> * I downloaded the docker images following the steps in the below page:
>  ** 
> [https://github.com/apache/incubator-griffin/blob/master/griffin-doc/docker/griffin-docker-guide.md]
>  * I'm bringing up the docker container using the docker compose file for 
> batch mode.
>  
> Observation:
>  * I'm not able to access any of the APIs via the URL: :38080
>  * Upon further investigation, I found out after connecting to the docker 
> container that MySQL isn't running inside the container, hence the API server 
> isn't coming up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GRIFFIN-99) Griffin - Docker - API server doesn't start as MySQL doesn't start on the docker container.

2018-02-26 Thread Lionel Liu (JIRA)

[ 
https://issues.apache.org/jira/browse/GRIFFIN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16378052#comment-16378052
 ] 

Lionel Liu commented on GRIFFIN-99:
---

Hi [~Bhaumik10] and [~AkashSharma], we've found this bug, and have solved it 
now. You can try our latest docker image, just remove your local one and pull 
it again, sorry to block you so much time.

The bug comes from the OverlayFS of docker, which makes mysql startup fail. As 
described here: [https://github.com/docker/for-linux/issues/72], 
[https://github.com/geerlingguy/drupal-vm/issues/1497]

Thanks for your questions, and hope this can help you.

> Griffin - Docker - API server doesn't start as MySQL doesn't start on the 
> docker container.
> ---
>
> Key: GRIFFIN-99
> URL: https://issues.apache.org/jira/browse/GRIFFIN-99
> Project: Griffin (Incubating)
>  Issue Type: Bug
>  Components: completeness-batch
>Affects Versions: 0.2.0-incubating
> Environment: Mac OSX
>Reporter: Akash Sharma S
>Priority: Critical
>  Labels: SP_4
> Fix For: 0.2.0-incubating
>
>
> * I downloaded the docker images following the steps in the below page:
>  ** 
> [https://github.com/apache/incubator-griffin/blob/master/griffin-doc/docker/griffin-docker-guide.md]
>  * I'm bringing up the docker container using the docker compose file for 
> batch mode.
>  
> Observation:
>  * I'm not able to access any of the APIs via the URL: :38080
>  * Upon further investigation, I found out after connecting to the docker 
> container that MySQL isn't running inside the container, hence the API server 
> isn't coming up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GRIFFIN-99) Griffin - Docker - API server doesn't start as MySQL doesn't start on the docker container.

2018-02-23 Thread Lionel Liu (JIRA)

[ 
https://issues.apache.org/jira/browse/GRIFFIN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16374173#comment-16374173
 ] 

Lionel Liu commented on GRIFFIN-99:
---

Hi [~Bhaumik10] and [~AkashSharma], I've pulled the latest docker image again, 
it works well, no matter on macOS Sierra 10.12.6 or linux.

I also encountered this error message in error.log of mysql, and searched for 
the reason, it seems to be a bug of OS, and it doesn't affect my container, it 
still works.

> Griffin - Docker - API server doesn't start as MySQL doesn't start on the 
> docker container.
> ---
>
> Key: GRIFFIN-99
> URL: https://issues.apache.org/jira/browse/GRIFFIN-99
> Project: Griffin (Incubating)
>  Issue Type: Bug
>  Components: completeness-batch
>Affects Versions: 0.2.0-incubating
> Environment: Mac OSX
>Reporter: Akash Sharma S
>Priority: Critical
> Fix For: 0.2.0-incubating
>
>
> * I downloaded the docker images following the steps in the below page:
>  ** 
> [https://github.com/apache/incubator-griffin/blob/master/griffin-doc/docker/griffin-docker-guide.md]
>  * I'm bringing up the docker container using the docker compose file for 
> batch mode.
>  
> Observation:
>  * I'm not able to access any of the APIs via the URL: :38080
>  * Upon further investigation, I found out after connecting to the docker 
> container that MySQL isn't running inside the container, hence the API server 
> isn't coming up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GRIFFIN-99) Griffin - Docker - API server doesn't start as MySQL doesn't start on the docker container.

2018-02-15 Thread Akash Sharma S (JIRA)

[ 
https://issues.apache.org/jira/browse/GRIFFIN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366649#comment-16366649
 ] 

Akash Sharma S commented on GRIFFIN-99:
---

Hi [~Lionel_3L], I did try it multiple times, and waited for well over two 
minutes and still faced the issue.

The System Configuration is the same as what is mentioned in the above comment 
by [~Bhaumik10].

> Griffin - Docker - API server doesn't start as MySQL doesn't start on the 
> docker container.
> ---
>
> Key: GRIFFIN-99
> URL: https://issues.apache.org/jira/browse/GRIFFIN-99
> Project: Griffin (Incubating)
>  Issue Type: Bug
>  Components: completeness-batch
>Affects Versions: 0.2.0-incubating
> Environment: Mac OSX
>Reporter: Akash Sharma S
>Priority: Critical
> Fix For: 0.2.0-incubating
>
>
> * I downloaded the docker images following the steps in the below page:
>  ** 
> [https://github.com/apache/incubator-griffin/blob/master/griffin-doc/docker/griffin-docker-guide.md]
>  * I'm bringing up the docker container using the docker compose file for 
> batch mode.
>  
> Observation:
>  * I'm not able to access any of the APIs via the URL: :38080
>  * Upon further investigation, I found out after connecting to the docker 
> container that MySQL isn't running inside the container, hence the API server 
> isn't coming up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GRIFFIN-99) Griffin - Docker - API server doesn't start as MySQL doesn't start on the docker container.

2018-02-15 Thread Bhaumik Patel (JIRA)

[ 
https://issues.apache.org/jira/browse/GRIFFIN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366313#comment-16366313
 ] 

Bhaumik Patel commented on GRIFFIN-99:
--

I think issue is still there. Below is the detail about error in Mysql.

ERROR: 1064 You have an error in your SQL syntax; check the manual that 
corresponds to your MySQL server version for the right syntax to use near 
'ALTER TABLE user ADD column Show_view_priv enum('N','Y') CHARACTER SET utf8 
NOT ' at line 1
171024 3:03:02 [ERROR] Aborting

 

 

> Griffin - Docker - API server doesn't start as MySQL doesn't start on the 
> docker container.
> ---
>
> Key: GRIFFIN-99
> URL: https://issues.apache.org/jira/browse/GRIFFIN-99
> Project: Griffin (Incubating)
>  Issue Type: Bug
>  Components: completeness-batch
>Affects Versions: 0.2.0-incubating
> Environment: Mac OSX
>Reporter: Akash Sharma S
>Priority: Critical
> Fix For: 0.2.0-incubating
>
>
> * I downloaded the docker images following the steps in the below page:
>  ** 
> [https://github.com/apache/incubator-griffin/blob/master/griffin-doc/docker/griffin-docker-guide.md]
>  * I'm bringing up the docker container using the docker compose file for 
> batch mode.
>  
> Observation:
>  * I'm not able to access any of the APIs via the URL: :38080
>  * Upon further investigation, I found out after connecting to the docker 
> container that MySQL isn't running inside the container, hence the API server 
> isn't coming up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (GRIFFIN-99) Griffin - Docker - API server doesn't start as MySQL doesn't start on the docker container.

2018-02-14 Thread Lionel Liu (JIRA)

[ 
https://issues.apache.org/jira/browse/GRIFFIN-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364288#comment-16364288
 ] 

Lionel Liu commented on GRIFFIN-99:
---

Hi [~AkashSharma], we've uploaded griffin docker image version 0.2.0, and have 
tested for times, it works well so far. Would you have one more try?

By the way, it takes about two minutes when the docker container starts up, it 
starts hdfs first, then spark standalone cluster, hive, mysql, griffin service. 
After the start phase ends, :38080 would be accessible.

If this situation still exists, pls tell us with more details about your 
starting steps, we'll check it out.

Thanks a lot for your help.

> Griffin - Docker - API server doesn't start as MySQL doesn't start on the 
> docker container.
> ---
>
> Key: GRIFFIN-99
> URL: https://issues.apache.org/jira/browse/GRIFFIN-99
> Project: Griffin (Incubating)
>  Issue Type: Bug
>  Components: completeness-batch
>Affects Versions: 0.2.0-incubating
> Environment: Mac OSX
>Reporter: Akash Sharma S
>Priority: Critical
> Fix For: 0.2.0-incubating
>
>
> * I downloaded the docker images following the steps in the below page:
>  ** 
> [https://github.com/apache/incubator-griffin/blob/master/griffin-doc/docker/griffin-docker-guide.md]
>  * I'm bringing up the docker container using the docker compose file for 
> batch mode.
>  
> Observation:
>  * I'm not able to access any of the APIs via the URL: :38080
>  * Upon further investigation, I found out after connecting to the docker 
> container that MySQL isn't running inside the container, hence the API server 
> isn't coming up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)