Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

/etc/init.d/monetdb5-sql uses incorrect PIDFILE to test if monetdb is running #2860

Closed
monetdb-team opened this issue Nov 30, 2020 · 0 comments
Closed

Comments

@monetdb-team
Copy link

@monetdb-team monetdb-team commented Nov 30, 2020

Date: 2011-08-14 11:28:57 +0200
From: Rémy Chibois <>
To: MonetDB5 devs <>
Version: 11.3.7 (Apr2011-SP2) [obsolete]
CC: @yzchang

Last updated: 2012-11-27 14:58:04 +0100

Comment 16104

Date: 2011-08-14 11:28:57 +0200
From: Rémy Chibois <>

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3
Build Identifier:

/etc/init.d/monetdb5-sql declares "PIDFILE=/var/run/monetdb/$NAME.pid" with "NAME" being "monetdb"
When monetdb daemon starts, it creates a pid file "/var/run/monetdb/merovingian.pid", hence when the script tests daemon's correct startup or status, it fails.

Changing the declaration to "PIDFILE=/var/run/monetdb/merovingian.pid" seems to solve this.

Reproducible: Always

Steps to Reproduce:

  1. Install MonetDB:

sudo apt-get install monetdb5-sql monetdb-client

  1. Modify /etc/default/monetdb5-sql:

STARTUP="yes"

  1. Start MonetDB

/etc/init.d/monetdb5-sql start

Actual Results:

Starting MonetDB SQL server: ERROR, monetdbd didn't start

Expected Results:

Starting MonetDB SQL server: monetdbd.

==== mserver5 --version
MonetDB 5 server v11.3.7 "Apr2011-SP2" (64-bit, 64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2011 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 4 available cpu cores
Libraries:
libpcre: 8.12 2011-01-15 (compiled with 8.12)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.8 (compiled with 2.7.8)
Compiled by: root@ottar.ins.cwi.nl (x86_64-pc-linux-gnu)
Compilation: gcc -O2 -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize
Linking : /usr/bin/ld -m elf_x86_64 -Wl,-Bsymbolic-functions

==== snippet from merovingian.log
2011-08-14 11:21:00 MSG merovingian[25261]: Merovingian 1.4 (Apr2011-SP2) starting
2011-08-14 11:21:00 MSG merovingian[25261]: monitoring dbfarm /var/monetdb5/dbfarm
2011-08-14 11:21:05 MSG merovingian[25261]: accepting connections on TCP socket 0.0.0.0:50000
2011-08-14 11:21:05 MSG merovingian[25261]: accepting connections on UNIX domain socket /tmp/.s.monetdb.50000
2011-08-14 11:21:10 MSG discovery[25261]: listening for UDP messages on 0.0.0.0:50000
2011-08-14 11:21:10 MSG control[25261]: accepting connections on UNIX domain socket /tmp/.s.merovingian.50001
2011-08-14 11:21:15 MSG control[25261]: accepting connections on TCP socket 0.0.0.0:50001
2011-08-14 11:21:15 MSG discovery[25261]: new neighbour phoenix (phoenix.expandium.com)
2011-08-14 11:21:15 MSG discovery[25261]: new database mapi:monetdb://phoenix:50000/expand (ttl=660s)
2011-08-14 11:21:15 MSG discovery[25261]: registered neighbour phoenix:50001

Comment 16105

Date: 2011-08-14 11:40:48 +0200
From: @sjoerdmullender

Changeset a4fe06e6ebfe made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a4fe06e6ebfe

Changeset description:

Fix name of PID file for monetdbd.
This fixes bug #2860.

Comment 16107

Date: 2011-08-15 11:11:24 +0200
From: @sjoerdmullender

This is fixed in the Aug2011 branch.

Comment 16248

Date: 2011-09-16 15:04:37 +0200
From: @sjoerdmullender

The Aug2011 version has been released.

Comment 18102

Date: 2012-11-27 14:58:04 +0100
From: @yzchang

Not possible to add test to this bug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant