Overpass API developpement

Text archives Help


Re: [overpass] Segmentation fault (core dumped) when trying to start dispatcher


Chronological Thread 
  • From: Brian Vogelgesang < >
  • To: " " < >, Roland Olbricht < >
  • Subject: Re: [overpass] Segmentation fault (core dumped) when trying to start dispatcher
  • Date: Tue, 17 Dec 2019 20:10:45 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=rightpoint.com; dmarc=pass action=none header.from=rightpoint.com; dkim=pass header.d=rightpoint.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=dz+Cc8Kusw2NKUBn0tkUKWsI5wdzPCC0Td3nJqH+hvg=; b=f87qIJ7NaunSDZrsTMRG9uPUszXj7kcRSCJLEiN03BMMc1IFATZr+LZOh5evac6pqP1mW4sIz2TILg5ob8Na9m/s4f5Cr3Jdi5oEMXUSiVF884f1LR2ND55rQLzdr7lJt+4/pr1fZRLiFoEhD5SlHCK71Dep18G05sM6YAJGsux5rB6HARuSH9t9OImBmsoMxOI/pMYyjVFojBFLpOWSXG4icCCPrU9dp+FlNPukON8Ka4J2CVpRohNCG080v3BaGOXzEFu5Tf14z+ch2KF+5mbdrCo/+qR27PkBXQ02jYDIv3dOqwWT4I7PZMo14akoXy+sKH6xBH8LgdHBsvbyhQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GFAHi4W09Dxzynv9ypbgaDPQ/XQalcXf8G10VFtpdyiSRQrr3G5b5/lgwgFzqzvUPtAIsQsqGVZ7BKeOx+Q/iZtNOvixfQCME5ZK9znsAVQq5eNYHJDRL+M+PpLElUyIRmreeBRoeB9frIebhueLvZowxfteAxFqw+8OsppYY8rJOVQegKngX5ogw3vxVe21OHErpoO/lUpUfzh1SXiwvEwKkLxalby6AyQb7CcCOaZCS487a48a+xBIEU6s1kzfAxuwo9ssIEWkIMKMsy9iuAKlBdK8fFQ0WTZ/nYsrWtanQ0LkdJ+6O6+PvaVWZgVymOGC4VeMkV8KrJxIonwYbw==
  • Authentication-results: spf=none (sender IP is ) smtp.mailfrom= ;

I'm really trying every angle to get this working. I tried launching the
docker image and passing it the database files I have. I get the same error
when it tries to init the dispatcher

/launch_overpass.sh: line 17: 96 Segmentation fault (core dumped)
$BINDIR/dispatcher --osm-base --meta --db-dir=$DBDIR

What is Segment fault trying to communicate in this context?

On 12/16/19, 1:41 PM,
"
on behalf of Brian Vogelgesang"
<
on behalf of
>
wrote:

I created a new machine with Ubuntu 18.04 and I still receive the segment
fault when I try to start the dispatcher. Below are the prompts I run to get
osm3_query setup on my machine. Note that the database files have already
been downloaded with bin/download_clone.sh to a separate SSD disk that is
attached to the machine

cd ~/
# Install necessary libraries
sudo sed -i 's/# \(.*multiverse$\)/\1/g' /etc/apt/sources.list && \
sudo apt-get update && \
sudo apt-get -y upgrade && \
sudo apt-get install -y build-essential && \
sudo apt-get install -y software-properties-common && \
sudo apt-get install -y byobu curl git htop man unzip vim wget && \
sudo apt-get install -y g++ make expat libexpat1-dev zlib1g-dev && \
sudo apt-get install nginx && \
sudo apt-get install fcgiwrap && \
sudo service nginx start && \
sudo service fcgiwrap start && \
sudo service fcgiwrap restart && \
sudo service nginx restart

# Create a separate SSD Disk (150GB), format it, mount it and set
permissions
# Also follow instructions for auto mounting the disk on boot
# Follow instructions here:
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.cloudbooklet.com%2Fattach-and-mount-disks-to-vm-instance-in-google-cloud%2F&amp;data=02%7C01%7Cbvogelgesang%40rightpoint.com%7C586570a19c344c1b202408d78270bd97%7C5fbbce2ac3e64b5ea51f222674fdb44d%7C1%7C0%7C637121293064407840&amp;sdata=0WooiDBZy8DVOK7yvMAGZW%2FQBz30bk%2B6waT8VtfnAFs%3D&amp;reserved=0
# Disk should be mounted to: ~/mnt/osm-db-disk/

# Set DB_DIR Env
export DB_DIR=~/mnt/osm-db-disk

# Download, unpack and cleanup OSM application
sudo wget
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdev.overpass-api.de%2Freleases%2Fosm-3s_v0.7.55.7.tar.gz&amp;data=02%7C01%7Cbvogelgesang%40rightpoint.com%7C586570a19c344c1b202408d78270bd97%7C5fbbce2ac3e64b5ea51f222674fdb44d%7C1%7C0%7C637121293064407840&amp;sdata=cAZ1tn%2BAcOLoJMrxeIztHrDNhbsPuCxQYgCo%2Bsw1rS0%3D&amp;reserved=0
tar -zxvf osm-3s_v0.7.55.7.tar.gz
rm osm-3s_v0.7.55.7.tar.gz

# Make folder for OSM to be executed from & set EXEC_DIR env
mkdir osm_exec_files
export EXEC_DIR=~/osm_exec_files

# Compile OSM Application
cd osm-3s_v0.7.55 && ./configure CXXFLAGS="-O2" --prefix=$EXEC_DIR &&
make install

# Remove Install Files and set execution permissions
cd ~/ && rm -rf ~/osm-3s_v0.7.55

# Test that you can run queries
$EXEC_DIR/bin/osm3s_query --db-dir=$DB_DIR

# Start dispatcher
nohup $EXEC_DIR/bin/dispatcher --osm-base --db-dir=$DB_DIR &

# This is where it fails and I get segment fault

On 12/16/19, 12:57 PM,
"
on behalf of Brian Vogelgesang"
<
on behalf of
>
wrote:

I used to have a reason to be using an older version of Ubuntu, I'm
glad to update. What is the most recent supported version of Ubuntu?

Permissions:
srw-rw-rw- 1 bvogelgesang bvogelgesang 0 Dec 16 19:53
osm3s_v0.7.55_osm_base
rw-rw-rw- 1 bvogelgesang bvogelgesang 105 Dec 16 20:53
/dev/shm/osm3s_v0.7.55_osm_base

Sometimes I get an error File_Error Connection refused 111
/home/bvogelgesang/mnt/osm-db-disk//osm3s_v0.7.55_osm_base Unix_Socket::7

Transaction.log
2019-12-16 19:36:42 [1894] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 19:37:07 [1901] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 19:37:14 [1912] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 19:41:03 [2049] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 19:41:40 [2082] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 19:52:56 [1837] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 19:53:35 [1868] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 20:17:14 [2104] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 20:48:54 [2577] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 20:51:25 [2660] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 20:51:42 [2677] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 20:52:10 [2702] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 20:53:12 [2756] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.
2019-12-16 20:55:59 [2906] Dispatcher version 0.7.55.7
8b86ff77bcd2f1199f5e81ea28aac25fa5f84436 just started.

On 12/16/19, 12:46 PM, "Roland Olbricht"
< >
wrote:

Hi,

> Does anyone have any pointers on what might be causing this?
>
> I'm running Ubuntu 14.04

We have December 2019. Ubuntu 14.04 has fallen out of maintenance
for
some months. Unless you have an important reason to run a five
year old
OS, I strongly advise against that.

Other than that: Please check
- is there a file /dev/shm/osm3s_v0.7.55_osm_base
and which permissions does it have?
- is there a file $DB_DIR/osm3s_v0.7.55_osm_base
and which permissions does it have?
- What is the content of the file $DB_DIR/transactions.log ?

Best
Roland









Archive powered by MHonArc 2.6.19+.

Top of page