Hi Juan,

Make sure user and group of your dbfarm consistent in your dbfarm directory.

I just create a user and group monetdb.

then chown -R monetdb:monetdb the directory and let monetdb do the rest when you start it as that user.

Also it might be SELinux or Apparmour causing you an issue check the getenforce/setenforce commands and documentation for details.

Regards,

Brian Hood

On Nov 12, 2015 12:24 AM, "Juan Carlos Gastélum" <jcgastr@farmacon.com.mx> wrote:
Hi

The data of the database are:

mserver5 --version --dbname=alm_dat_far
MonetDB 5 server v11.21.11 "Jul2015-SP1" (64-bit, 64-bit oids, 128-bit integers)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 39.3GiB available memory, 6 available cpu cores
Libraries:
  libpcre: 8.31 2012-07-06 (compiled with 8.31)
  openssl: OpenSSL 1.0.1f 6 Jan 2014 (compiled with OpenSSL 1.0.1f 6 Jan 2014)
  libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: root@dev.monetdb.org (x86_64-pc-linux-gnu)
Compilation: gcc -O3 -fomit-frame-pointer -pipe      -g -D_FORTIFY_SOURCE=2
Linking    : /usr/bin/ld -m elf_x86_64

Juan Carlos

El 11/11/15 a las 08:19, Juan Carlos Gastélum escribió:
Hi

Yes, the disk is writeable and it has free space available.

Here are the free space that is consumed and what is available, there are 178 GB available.

681G  468G  178G  73% /usr/local

Thanks,

Juan Carlos
El 10/11/15 a las 18:29, Juan Carlos Gastélum escribió:

 







Hi

I'm getting the following error when a I try to start our production
database:

# builtin opt     gdk_dbpath = /var/monetdb5/dbfarm/demo
# builtin opt     gdk_debug = 0
# builtin opt     gdk_vmtrim = no
# builtin opt     monet_prompt = >
# builtin opt     monet_daemon = no
# builtin opt     mapi_port = 50000
# builtin opt     mapi_open = false
# builtin opt     mapi_autosense = false
# builtin opt     sql_optimizer = default_pipe
# builtin opt     sql_debug = 0
# cmdline opt     gdk_dbpath = /usr/local/monetdb/alm_dat_far
# cmdline opt     merovingian_uri =
mapi:monetdb://farser07:50000/alm_dat_far
# cmdline opt     mapi_open = false
# cmdline opt     mapi_port = 0
# cmdline opt     mapi_usock = /usr/local/monetdb/alm_dat_far/.mapi.sock
# cmdline opt     monet_vault_key = /usr/local/monetdb/alm_dat_far/.vaultkey
# cmdline opt     gdk_nr_threads = 6
# cmdline opt     max_clients = 64
# cmdline opt     sql_optimizer = default_pipe
# cmdline opt     monet_daemon = yes
# cmdline opt     gdk_debug = 10
# MonetDB 5 server v11.21.11 "Jul2015-SP1"
# Serving database 'alm_dat_far', using 6 threads
# Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs and 128bit
integers dynamically linked
# Found 39.298 GiB available main-memory.
# Copyright (c) 1993-July 2008 CWI.
# Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
# Visit http://www.monetdb.org/ for further information
# Listening for UNIX domain connection requests on
mapi:monetdb:///usr/local/monetdb/alm_dat_far/.mapi.sock
# Start processing logs sql/sql_logs version 52200
!FATAL: Logger_new: cannot create seqs bats

What can I do to solve it?

I have been trying to recover a backup of the virtual machine where the
instance of monetdb is but until now I have not been able to recover
this database.

Thanks in advance.

Juan Carlos Gastelum





_______________________________________________
users-list mailing list
users-list@monetdb.org
https://www.monetdb.org/mailman/listinfo/users-list