[Dachs-support] Fwd: Questions about DaCHS

Loïc Trompet loic.trompet at aeronomie.be
Mon Jul 31 13:42:02 CEST 2023


Dear Markus,

Thank you for your answer. Here is what I can say:

> So... do you happen to know what might have been special about these
> jobs? How did you create them, what happened to them, and how were
> they deleted?
I did not create them. I did not access our server where DaCHS is 
installed since several weeks. I think that the only possibility are 
queries to the data service made by external people.

> Can you share the content of your
> /etc/apt/sources.list and /etc/apt/sources.list.d? 
Sure:
For sources.list:
> #
>
> # deb cdrom:[Debian GNU/Linux 8.4.0 _Jessie_ - Official amd64 DVD 
> Binary-1 20160
> 402-14:46]/ jessie contrib main
>
> # deb cdrom:[Debian GNU/Linux 8.4.0 _Jessie_ - Official amd64 DVD 
> Binary-1 20160
> 402-14:46]/ jessie contrib main
> deb https://ftp.belnet.be/debian/ buster main contrib
>
> deb https://security.debian.org/ buster/updates main contrib
> deb-src https://security.debian.org/ buster/updates main contrib
>
> # jessie-updates, previously known as 'volatile'
> # A network mirror was not selected during install.  The following entries
> # are provided as examples, but you should amend them as appropriate
> # for your mirror of choice.
> #
> #deb file:/tmp/ jessie main contrib
> #deb-src file:/tmp/ jessie main contrib
> #deb http://ftp.belnet.be/debian/ jessie-updates main contrib
> #deb-src http://ftp.belnet.be/debian/ jessie-updates main contrib
>
> # DaCHS repository
> deb https://vo.ari.uni-heidelberg.de/debian release main
> #deb-src https://vo.ari.uni-heidelberg.de/debian stable main
> #deb https://vo.ari.uni-heidelberg.de/debian beta main
> deb https://vo.ari.uni-heidelberg.de/debian buster-foreports main
and sources.list.d is an empty directory.

Best regards,

Loïc


PS: The results from the "UWS async jobs" was provided to me by our IT 
team (in cc). I hoped that it would help. I'm trying to catch up but I 
still do not get everything.


-------- Forwarded Message --------
Subject: 	Re: Questions about DaCHS
Date: 	Mon, 31 Jul 2023 12:57:19 +0200
From: 	Markus Demleitner <gavo at ari.uni-heidelberg.de>
To: 	Loïc Trompet <loic.trompet at aeronomie.be>
CC: 	gavo at ari.uni-heidelberg.de



Hi Loïc,

On Mon, Jul 31, 2023 at 10:58:38AM +0200, Loïc Trompet wrote:
> Unfortunately, we might be experiencing an issue with DaCHS filling the /var
> of our server with deleted files not yet released by DaCHS. For instance:
>
>> dachs       571 28581 dachs                 gavo   21r      REG
>>               254,2      21598       3799
>> /var/gavo/state/uwsjobs/wuyi_q5y/result (deleted)

These are, as you probably know, results of UWS async jobs; the
"(deleted)", I assume, is added by you to say that the corresponding
job has been deleted and that it indeed no longer shows up in
.../tap/async, right?

In principle, DaCHS should (and will) clean up these directories.
However, I cannot entirely rule out that there aren't interaction
patterns under which it will fail to do so; now that I'm talking, I
could well imagine that when you go from EXECUTING to DELETED
directly, it will fail to clean up (I'll look when I have a bit more
time).

So... do you happen to know what might have been special about these
jobs? How did you create them, what happened to them, and how were
they deleted?

> To possibly solve this, we tried to upgrade DaCHS but we get the following
> message
>
>> The following packages will be REMOVED:
>>   gavodachs2-server python3-gavo
>> The following packages will be upgraded:
>>   python3-gavo-stc python3-gavo-utils python3-gavo-votable
> Can you tell us if this upgrade is safe ?

No, that looks horrible. I'd really be curious what could bring
about such a situation. Can you share the content of your
/etc/apt/sources.list and /etc/apt/sources.list.d? If you have our
GAVO repository configured, we're fresh through a transition of our
signging key. That shouldn't lead to such a situation, but who
knows?

> If it is of any help, "gavo --version" produces "Software (2.7) Schema
> (33/33)".

That's looking good. There is a newer release in our repository, but
that almost certainly will not fix any problem you may have. But I'd
still be curious what brought about the suggestion to drop
gavodachs2-server...

Thanks,

Markus

PS: In order to let others profit from support requests, I actually
prefer questions on the dachs-support mailing list,
<https://lists.g-vo.org/cgi-bin/mailman/listinfo/dachs-support>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.g-vo.org/pipermail/dachs-support/attachments/20230731/7e4b4bbf/attachment.htm>


More information about the Dachs-support mailing list