[Dachs-support] error in GAVO repository?

Mariangeles Mendoza ninesmp75 at gmail.com
Mon Apr 19 11:13:21 CEST 2021


Thank Carlos very much!

On Fri, Apr 16, 2021 at 4:28 PM Carlos Henrique Brandt <
carloshenriquebrandt at gmail.com> wrote:

> Hi Maria,
>
> I made a quick try and it didn't work.
>>
> I'm going to try again  more thoroughly.
>>
>
>  OK...that's is not nice of me to offer you something not working. Sorry.
> But I am glad you pointed that out.
> If you want to open an issue exposing the error or simply email me that, I
> will look through.
>
> Don't worry, it is sure due to my customizations.


>  Even better: if you feel like doing a live, pair programming session, I
> think we could fill the gaps
> in a couple of hours or less. I tend to prefer this option.
>

That would be great.
Let me check first thar everything I have done is correct

Thanks again

Dachs-support team is amazing!

Cheers,
Maria
61 / 5000
Resultados de traducció

>
> Regards,
> Carlos
>
>
>  With  our current development it's possible to access to DACHS portal,
>>
> and access to the services TAP through TOPCAT (http://localhost:8080/tap)
>>
>> But the Datalink service is not published.
>> Possibly is an error in our .rd
>>
>
>> Kind regards,
>> Maria
>>
>>
>> On Thu, Apr 15, 2021 at 5:46 PM Carlos Henrique Brandt <
>> carloshenriquebrandt at gmail.com> wrote:
>>
>>> Maria,
>>>
>>>  What is in here:
>>> * https://github.com/gavodachs/docker-dachs-compose
>>> or
>>> * https://github.com/gavodachs/docker-dachs
>>> that does *not* work for you?
>>>  You should be able to inherit from there and customize to your needs.
>>>
>>> []
>>> Carlos
>>>
>>> On Wed, Apr 7, 2021 at 4:05 PM Mariangeles Mendoza <ninesmp75 at gmail.com>
>>> wrote:
>>>
>>>> Thanks you very much.
>>>>
>>>> I will look into your email carefully.
>>>>
>>>> When we use DACHS for our own data, we are going to use a VM ;-).
>>>> Currently, my hands are tied with Docker :-(.
>>>>
>>>> Cheers,
>>>> Maria Angeles
>>>>
>>>>
>>>> On Wed, Apr 7, 2021 at 3:04 PM Markus Demleitner <
>>>> msdemlei at ari.uni-heidelberg.de> wrote:
>>>>
>>>>> Hi Maria,
>>>>>
>>>>> On Wed, Apr 07, 2021 at 01:08:27PM +0200, Mariangeles Mendoza wrote:
>>>>> >  Following Markus' guidelines, I changed the Dockerfile for the one
>>>>> copied
>>>>> > below.
>>>>> >  When I lift the dachs services, I get the following messages in
>>>>> console:
>>>>> >
>>>>> > -----------------------------------------------------------------
>>>>> > services_vo         | *** Error: Oops.  Unhandled exception
>>>>> > OperationalError.
>>>>> > services_vo         |
>>>>> > services_vo         | Exception payload: FATAL:  role "root" does
>>>>> not exist
>>>>> > services_vo         |
>>>>> > services_vo         | Updating meta for import
>>>>> > --------------------------------------------------------
>>>>>
>>>>> The "role 'root' does not exist" presumably is the result of
>>>>>
>>>>>   gavo init -d 'host=services_db dbname=db'
>>>>>
>>>>> in your startup.sh -- it simply means that DaCHS cannot create its
>>>>> environment on services_db based on the DSN you're giving it.  It
>>>>> doesn't need to do that in your special setup, though, because it
>>>>> seems you're using a "pre-owned" DB container with all that DaCHS
>>>>> needs. And you're giving DaCHS the for that credentials in your COPY
>>>>> commands.
>>>>>
>>>>> This is... daring for many reasons; in particular re-building the DB
>>>>> container will be tricky.  If you're hell-bent on using Docker
>>>>> (rather than using a proper VM, which I strongly recommend for
>>>>> longer-running services), I'd again recommend looking at Carlos'
>>>>> two-container docker setup (see below).  Perhaps, Carlos, would you
>>>>> like to comment here?
>>>>>
>>>>> > But when I look in the browser: http://localhost:8080.
>>>>> > There is no reference to my tables or services.
>>>>> > Only it appears:
>>>>> >
>>>>> > '''
>>>>> > myDATA
>>>>> >
>>>>> > Please check out our site help.
>>>>> > ''''
>>>>> >
>>>>> > and not like before (with beta version):
>>>>> > '''
>>>>> > myDATA
>>>>> >
>>>>> > "In addition to the services listed below, we offer access to
>>>>> numerous
>>>>> > tables using TAP or
>>>>> > form-based ADQL".
>>>>> >
>>>>> > Please check out our site help.
>>>>> > ''''
>>>>>
>>>>> The reference to TAP and ADQL is indeed no longer in the default root
>>>>> template, because it was inappropriate for many sites.  If you want
>>>>> it (or something in that vein) back, check out the templating guide
>>>>> and in particular its chapter on overriding the root template
>>>>> (http://docs.g-vo.org/DaCHS/templating.html#the-root-template).
>>>>>
>>>>> But that your published services are missing is a clear indication of
>>>>> an actual problem.
>>>>>
>>>>> Here's my reconstruction of what actually happened:
>>>>>
>>>>> > startup.sh
>>>>> > -------------------------------------------------------
>>>>> > gavo init -d 'host=services_db dbname=db'
>>>>>
>>>>> This fails as above, as root can't access the DB on services_db; but
>>>>> that doesn't hurt because *something* has already brought up DaCHS,
>>>>> presumably the package itself, though I cannot see where you install
>>>>> it in your dockerfile.
>>>>>
>>>>> > gavo imp -m myDATA/vo.rd
>>>>>
>>>>> Again, the output above above would indicate that that's run, too.
>>>>>
>>>>> > gavo pub myDATA/vo.rd
>>>>>
>>>>> This one probably runs, too, but the server that is already up has
>>>>> already generated its front page without this.
>>>>>
>>>>> dachs pub tries to tell a running server to discard cached front
>>>>> pages, but it can only do that if theres a [web]adminpasswd set in
>>>>> /etc/gavo.rc, which you probably don't have.  Hence, you'd be seeing
>>>>> the old front page without services.
>>>>>
>>>>> > gavo serve start -f
>>>>>
>>>>> That's the weak point of my theory: this would have to error out
>>>>> ("*** Error: Someone already listens on the configured port 8080.").
>>>>> You're sure you're not seeing this?
>>>>>
>>>>> > Is there something wrong?
>>>>>
>>>>> Well... basic rule of thumb: If you find yourself using pip on proper
>>>>> computers and outside of virtual environments, generally yes :-)
>>>>>
>>>>> More seriously: As said above, copying around pieces of configuration
>>>>> is at least a rather fragile thing, and since I can't see where you
>>>>> get the actual DaCHS code, I can't point at a very specific point
>>>>> where things go wrong.
>>>>>
>>>>> What I've not worked out yet is why you're not simply installing the
>>>>> package, preferably, as I said, into an actual VM, which simplifies
>>>>> installation, maintenance, and debugging greatly.
>>>>>
>>>>> But if that's *really* not an option for whatever reason, can you
>>>>> have another look at Carlos' Dockerfiles from
>>>>> https://github.com/gavodachs/docker-dachs?
>>>>>
>>>>> I think it'll help everyone if we try to fix any wrinkles that are
>>>>> still in those rather than roll-one's-own Docker thing -- in the end
>>>>> glueing together database, file system, and VO server is a
>>>>> non-trivial effort, and we should see we don't repeat it more often
>>>>> than absolutely necessary.
>>>>>
>>>>> Thanks,
>>>>>
>>>>>             Markus
>>>>> --
>>>>> Dachs-support mailing list
>>>>> Dachs-support at g-vo.org
>>>>> https://lists.g-vo.org/mailman/listinfo/dachs-support
>>>>>
>>>> --
>>>> Dachs-support mailing list
>>>> Dachs-support at g-vo.org
>>>> https://lists.g-vo.org/mailman/listinfo/dachs-support
>>>>
>>>
>>>
>>> --
>>> The consequences of every act are included in the act itself.
>>>
>>
>
> --
> The consequences of every act are included in the act itself.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.g-vo.org/pipermail/dachs-support/attachments/20210419/936d3005/attachment.htm>


More information about the Dachs-support mailing list