[Dachs-support] dachs error

Nathanaël Jourdane njourdane at irap.omp.eu
Thu Sep 6 18:25:49 CEST 2018


Hello,

Thank you.

It will be a pleasure to contribute to the Carlos' repository when I will fix this problem. :)

In the meanwhile I tried with an other Dockerfile and this one runs dachs but services can 
not be imported (well, it's better in some way).

I installed postgresql with pg-sphere and pg-q3 extensions:

PG_VERSION=9.4
apt-get install -y postgresql-$PG_VERSION postgresql-$PG_VERSION-pgsphere postgresql-
$PG_VERSION-q3c

But on pgAdmin I see that the only installed extension is plpgsql, and the logs/dcErrors. 
says that "the type "spoly" does not exist", which is, I suppose, related to the pg-sphere 
extension.

Does someone know why these pg extensions are badly installed?

-----

Le jeudi 6 septembre 2018, 18:14:10 CEST Markus Demleitner a écrit :
> Nathanaél,
> 
> On Thu, Sep 06, 2018 at 12:50:27PM +0200, Nathanaël Jourdane wrote:
> > When I run dachs, the web server doesn't start and I get the following
> > error:
> > 
> > root at 680e6baf4064:/var/gavo# dachs serve start
> > 
> >   File "/usr/lib/python2.7/logging/__init__.py", line 936, in _open
> >   
> >     stream = open(self.baseFilename, self.mode)
> > 
> > IOError: [Errno 2] No such file or directory: u'/var/gavo/logs/dcErrors'
> > 
> > Do you understand why?
> 
> The immediate reason is (with 99% certainty) that the directory
> /var/gavo/logs does not exist.
> 
> The question is: what is the reason for that?
> 
> > Notes:
> > I use Docker. See Dockerfile attached.
> > The folder /var/gavo contains only the files I put here with docker
> > COPY command.
> 
> That's a good candidate for a reason.  DaCHS insists on several
> directories in there, and on the server-writability of a couple of
> them (most importantly, cache).  This is why there's the dachs init
> subcommand that creates these properly.
> 
> So, recommendations:
> 
> 1: Just have Debian (or whatever) install itself from package.  The
> post-install script does the dachs init for you.
> 
> 2. If that's not possible, at least run dachs init when the container
> comes up.  It shouldn't hurt if everything is in place, and it'll
> generate the necessary files and directories if they're missing (and
> it has the necessary privileges).
> 
> 3. But foremost, if marrying DaCHS and Docker, ideally contribute to
> Carlos' effort at https://github.com/chbrandt/docker-dachs -- it
> would be great if there was a rock-solid, clean solution in the end,
> and I think Carlos is at least 80% there (of course, the remaining
> 20% are the hardest, but if everyone deploying with docker helps out,
> I think ironing out the wrinkles should be feasible).
> 
>     -- Markus
> _______________________________________________
> Dachs-support mailing list
> Dachs-support at g-vo.org
> http://lists.g-vo.org/cgi-bin/mailman/listinfo/dachs-support


-- 
Nathanaël Jourdane
Développeur
IRAP - Institut de Recherche en Astrophysique et Planétologie
9 avenue du Colonel Roche - 31028 Toulouse cedex 4
+33(0)5.61.55.58.37
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.g-vo.org/pipermail/dachs-support/attachments/20180906/bb2bafca/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 484 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.g-vo.org/pipermail/dachs-support/attachments/20180906/bb2bafca/attachment-0002.sig>


More information about the Dachs-support mailing list