[codeface] Re: shiny server
- From: Wolfgang Mauerer <wm@xxxxxxxxxxxxxxxx>
- To: codeface@xxxxxxxxxxxxx
- Date: Sat, 07 Mar 2015 20:37:23 +0100
Am 07/03/2015 um 18:18 schrieb peguet:
> I don't succeed to make the shiny server work but:
>
> When I use wireshark, I see that the page not found error is sent by the
> docker container to the host, so they can comunicate.
thanks for investigating this.
> Besides, there is no log in codeface/log/shiny-server after the error,
> and the message is not helpfull : Sorry, but the page you requested
> doesn't exist.
>
> I tried to execute shiny-server as root, but it appears to be a mistake,
> because it bring an other error "initialization failed"
> I first think about the previous error with library, so I did the
> modification related to but I realized that nothing happened and being
> root make shiny server failed every time.
> ( I tried using my shiny-server working codeface with this new
> configuration and I got the same error : "initialization failed")
>
> So I am back to the Page not found error.
> yet, I know that the port binding is correctly done so the error may
> comes from the shiny server configurations and other r files, inside
> the container.
>
> for now, I have two different codeface instances that can run
> shiny-server with exactly the same files, and one is working while the
> other fails.
it's a bit hard to judge what's going on.
- Can you see from the wireshark log which page is being requested?
If the request make it through to the docker instance, but the desired
page is not available, the requested URL could be wrong for some
reason.
- If you post your Dockerfile somewhere, we can try to reproduce
your issue.
Thanks & best regards, Wolfgang Mauerer
>
> Best Regards,Florian Peguet.
>
>
>>> that sounds good; however, I'm curious why these includes are necessary.
>>> Since the web front end used to work, and there were no changes to it
>>> lately, things should work as-is. Can you post you code somewhere to
>>> make the problem reproducible?
>>
>> I think, my code the same as yours.
>> Maybe you did something to load these libraries before you run R.
>> I am not used to R, so it's just an idea but maybe you have a .Rprofile
>> in your home directory that do the trick?
> no, that's not the case.
>
> With code I meant the Docker file (or some other form of script-based
> installation) so that we can reproduce your issue.
>
> Best regards, Wolfgang Mauerer
>
>>
>> Best Regards,Florian Peguet.
>>
>>
>>> You were right, I have added the breadcrumb source to the ui.r file in
>>> $CFDIR/codeface/R/shiny/apps/dashboard that way
>>> (I don't know if it is the best)
>>> source("../../nav/breadcrum.shiny.r", chdir = TRUE)
>>> source("../../nav/widgets.r", chdir = TRUE)
>>> source("../../nav/qa_cookie.r", chdir = TRUE)
>>> source("gridsterWidgetsExt.r", chdir = TRUE) ( to correct an other
>>> error)
>>>
>>> I also add library(stringr) to $CFDIR/codeface/R/shiny/figure.of.merit.r
>>> and library(shinyGridster) to
>>> $CFDIR/codeface/R/shiny/apps/dashboard/gridsterWidgetsExt.r so that
>>> error all errors disappears
>>
>> that sounds good; however, I'm curious why these includes are necessary.
>> Since the web front end used to work, and there were no changes to it
>> lately, things should work as-is. Can you post you code somewhere to
>> make the problem reproducible?
>>>
>>> I now have some widgets that appears on the screen, but not enough, I
>>> think.
>>>
>>> I still have nothing for docker
>>
>> please follow the suggestions from my previous email.
>>
>> Best regards, Wolfgang Mauerer
>>>
>>>> Dear all,
>>>>
>>>> I managed to solve my previous problem ( the command xsltproc was not
>>>> installed and seems to be mandatory for cppstats, maybe it could be a
>>>> good thing to add apt-get install xsltproc, in the README process)
>>>
>>> yes, this requirement is indeed documented on cppstat's homepage:
>>> http://www.infosun.fim.uni-passau.de/cl/staff/liebig/cppstats/
>>> Good catch - could you please submit a patch for the README file?
>>>>
>>>> "Codeface test" now give the same result wether I execute it from the
>>>> regensburg server or the docker images.
>>>> The enhancements of analyses for project may be pass on the docker
>>>> instance since I use git clone.
>>>>
>>>> I am now thinking about using shiny server so that users can use
>>>> codeface easily from their web browser, but I got errors.
>>>>
>>>> When I run shiny server (with the command shiny-server
>>>> shiny-server.config) from my computer (same as the regensburg-server) I
>>>> got this at localhost with firefox :
>>>> ERROR: impossible to find the function "breadcrumbOutput".
>>>> Have I missed something?
>>>
>>> the function should be defined in
>>> codeface/R/shiny/nav/breadcrumb.shiny.r,
>>> maybe there a file inclusion missing somewhere. Can you look at the log
>>> files (there are several of them, look for *.log in the installation
>>> directory) and post the complete error message?
>>>>
>>>> for docker, it is harder to run shiny-server, because localhost is
>>>> running on the virtual container and not on the real computer/server.
>>>> The solution is to create a bridge between ports.
>>>> I tried to make a bridge for port 8081 where the shiny server may run
>>>> but i got Page not found on my web browser. This means something
>>>> happened otherwise I would get "connection failed"
>>>
>>> the approach is sound; naturally, docker cannot use the host
>>> ports directly because otherwise you would not be able to run,
>>> for instance, two containers with different versions of a server
>>> software on one single machine.
>>>>
>>>> for now I don't understand why I don't get the previous error with
>>>> docker (breadcrumbOutput not found) .
>>>> Is there more than one port to bind?
>>>
>>> did you properly expose the port in the dockerfile? Can you sniff
>>> the traffic with, say, wireshark to see what it going on on the wire?
>>>
>>> Best regards, Wolfgang Mauerer
>>>>
>>>> I use docker like that:
>>>> docker run -p port_on_docker:port_on_the_real_computer
>>>> folder_name/my_image_name:tag
>>>>
>>>> Florian.
>>>>
>>>
>>>
>>>
>>>
>>
>>
>
Other related posts:
