Linux
--
Questions
--
Followers
Top Experts
Self hosting OpenStreetMap OSM and Layers
If we self hosted the full OSM database and what ever else is needed, could we be 100% independent of any external services to render our maps/layers?
I don't want to sound cheap but we'll be using this ten thousand times a day (don't ask) so paying for hosted service would add up like mad. Instead, I would like to self host everything we need including being able to have fast direct local access to the data.
Am I missing something?
And, if I am not missing something, does anyone know of a good tutorial on how to go about installing everything needed or some already existing package or script, etc.
I don't want to sound cheap but we'll be using this ten thousand times a day (don't ask) so paying for hosted service would add up like mad. Instead, I would like to self host everything we need including being able to have fast direct local access to the data.
Am I missing something?
And, if I am not missing something, does anyone know of a good tutorial on how to go about installing everything needed or some already existing package or script, etc.
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Do you want routing or just render?
Why you added MySQL tag?
Why you added MySQL tag?
If routing means from one destination to another, then I only need render.
As for why I entered mysql, I forgot that osm only runs on postgress and also didn't see much else for categories.
As for why I entered mysql, I forgot that osm only runs on postgress and also didn't see much else for categories.
Linux or Windows? Approx versions would be handy too.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Linux would be best and any flavor, just like to be current as possible of course.
All current distributions can sustain it:
e.g. https://switch2osm.org/serving-tiles/manually-building-a-tile-server-14-04/
Should be straightforward with Debian 8 , and a bit more work to make it run on RPM distribution.
e.g. https://switch2osm.org/serving-tiles/manually-building-a-tile-server-14-04/
Should be straightforward with Debian 8 , and a bit more work to make it run on RPM distribution.
Nice tutorial. I'll give it a try.
It doesn't mention the hardware requirements but I've read that a minimum of 32GB should be used and of course multiple cores.
I wonder if it could be a KVM vm however, simply to make it that much more portable, so I can start it small, then move it to a bigger machine when needed.
It doesn't mention the hardware requirements but I've read that a minimum of 32GB should be used and of course multiple cores.
I wonder if it could be a KVM vm however, simply to make it that much more portable, so I can start it small, then move it to a bigger machine when needed.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
You dont need to keep all data in RAM. 10% should suffice - and you will not be navigating world over at highest detail.
I would suggest to start at 4GB like old laptop to see where performance is needed and how to fir postgis in memory.
I would suggest to start at 4GB like old laptop to see where performance is needed and how to fir postgis in memory.
I've plenty of servers. I'll try building one on a 16GB dual quad core blade and see how it goes.
Are you saying this can work fine on a vm, so long as it has the resources it needs?
I'd love to make it as portable as possible so I can move it to different hardware.
I can either dedicate the blade to it or install Centos7 on the blade, then build only the one vm so I can move it later.
Are you saying this can work fine on a vm, so long as it has the resources it needs?
I'd love to make it as portable as possible so I can move it to different hardware.
I can either dedicate the blade to it or install Centos7 on the blade, then build only the one vm so I can move it later.
VM is easier to carry around and resize.
Thousand times a day is not that much, it can read tile data from database disks each time.
CentOS7 is the hard way, try debian with other hand too...
Thousand times a day is not that much, it can read tile data from database disks each time.
CentOS7 is the hard way, try debian with other hand too...
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Only reason I was thinking of using Centos was to use a KVM based vm which I could later move from the dev server to a production one if this worked out. Meaning, I would actually dedicate the whole blade just to the single vm in order to give it more resources but would build it as a vm so I could more easily move it later.
If I recall, the DB is some 400GB for the whole world.
If I recall, the DB is some 400GB for the whole world.
It will be a little bit harder to install CentOS alone, others could serve as reference while getting CentOS up and running (and not to keep after CentOS works)
For starters - postgis extension is in postgresql yum repository and geos, gdal in Fedora EPEL
For starters - postgis extension is in postgresql yum repository and geos, gdal in Fedora EPEL
Sorry, not quite understanding the last comment.
What I mean is that I am using Centos KVM these days so thinking I'll install Centos/KVM on a blade, then install a Debian VM to build the OSM server on. That way, once tested, I can migrate it to a more powerful Centos KVM host if it goes to production.
What I mean is that I am using Centos KVM these days so thinking I'll install Centos/KVM on a blade, then install a Debian VM to build the OSM server on. That way, once tested, I can migrate it to a more powerful Centos KVM host if it goes to production.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
I've built a ubuntu server and am trying to follow the tutorial but am at a stop.
This is just a trial run to see if things go well but am already at a problem at this point.
Now you need to create a postgis database.
I followed the steps replacing 'username' with one I've created on the server. For some reason, creating the user is mentioned after this step but I went ahead and did it before anyhow.
This is where I am stuck now.
Set up PostGIS on the PostgreSQL database:
Any thoughts on how I can get past this? The user I created is '80000'.
This is just a trial run to see if things go well but am already at a problem at this point.
Now you need to create a postgis database.
I followed the steps replacing 'username' with one I've created on the server. For some reason, creating the user is mentioned after this step but I went ahead and did it before anyhow.
This is where I am stuck now.
Set up PostGIS on the PostgreSQL database:
root@osm1:/home/user# sudo -u postgres psql
psql (9.3.9)
Type "help" for help.
postgres=# \c gis
You are now connected to database "gis" as user "postgres".
gis=# CREATE EXTENSION postgis;
CREATE EXTENSION
gis=# ALTER TABLE geometry_columns OWNER TO username;
ERROR: role "username" does not exist
gis=# ALTER TABLE geometry_columns OWNER TO 80000;
ERROR: syntax error at or near "80000"
LINE 1: ALTER TABLE geometry_columns OWNER TO 80000;
^Any thoughts on how I can get past this? The user I created is '80000'.
Did you create postgresql user or system user "on the server"? You dont need later one for database.
I got past that and now am not sure where to put certain files.
We then move the downloaded data into the osm-bright-master project directory:
unzip '*.zip'
mkdir osm-bright-master/shp
mv land-polygons-split-3857 osm-bright-master/shp/
mv simplified-land-polygons-c
mv ne_10m_populated_places_si
The last file doesn't have a sub-directory, all of the files are into the top of the archive.
I went ahead and created a osm-bright-master/shp/ne_1
We then move the downloaded data into the osm-bright-master project directory:
unzip '*.zip'
mkdir osm-bright-master/shp
mv land-polygons-split-3857 osm-bright-master/shp/
mv simplified-land-polygons-c
mv ne_10m_populated_places_si
The last file doesn't have a sub-directory, all of the files are into the top of the archive.
I went ahead and created a osm-bright-master/shp/ne_1
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
You can import files one by one too.
That's what I did with the last one since the archive didn't contain a sub-directory. But, I was checking to make sure I got this right. I'm assuming you know this, have done it, can help :)
So, I'm at the point of importing the world map but it isn't clear how storage should work for this.
The compressed file is 30GB then of course, it will be inflated. I have all kinds of storage but I need to know where it should be used.
Meaning, for the main drive, I set up 146GB but postgres also resides in this partition. Assuming I need more space, it means I'll need to map something for the db and for the tiles maps. Again, not sure if this is all in the db or if part is in db and tile maps are just stored somewhere in a partition.
http://wiki.openstreetmap.org/wiki/Tile_disk_usage
The compressed file is 30GB then of course, it will be inflated. I have all kinds of storage but I need to know where it should be used.
Meaning, for the main drive, I set up 146GB but postgres also resides in this partition. Assuming I need more space, it means I'll need to map something for the db and for the tiles maps. Again, not sure if this is all in the db or if part is in db and tile maps are just stored somewhere in a partition.
http://wiki.openstreetmap.org/wiki/Tile_disk_usage
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Seems I need to move the postgres /lib/postgresql to another partition that has enough space. I've read here and there that doing that sometimes message up postgresql.
I have tile server running for couple of years, i remember removing and recreating postgres DB until I got importing right.
Yup, that's what I did. I created a 2TB partition and moved the server there along with the import files.
I'm nervous that after who knows how long the import will take, that it will crap out if large files are next extracted into the main OS areas. As far as I understand it, what I am importing now is only the database so I think nothing else will be extracted from that file.
I'm nervous that after who knows how long the import will take, that it will crap out if large files are next extracted into the main OS areas. As far as I understand it, what I am importing now is only the database so I think nothing else will be extracted from that file.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
It is limited by disk IOPs. Say raid5 wont be funny.
I'm not asking about the throughput, I'm asking if anything will try to be written to the main partitions instead of this 2TB one I created for the postgres server and its db's.
I'm saying that I am at the import stage of the document right now;
Importing data into the database
But, it's not 100% clear if this is only the database import into the postgre server or if some things will be extracted into other areas of the system which I've not added extra space for.
I'm saying that I am at the import stage of the document right now;
Importing data into the database
But, it's not 100% clear if this is only the database import into the postgre server or if some things will be extracted into other areas of the system which I've not added extra space for.
It will make about 50GB PostgreSQL database (/var/lib/postgresql on normal systems)
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Still not sure what you mean, sorry.
So far, it's over 260GB of import and still going. I expect it will be done around the 400GB mark.
What I'm asking is, are there any other files that will be extracted from the planet file, which the osm2pgsql tool will try putting somewhere else on the system?
This is what it's done so far;
So far, it's over 260GB of import and still going. I expect it will be done around the 400GB mark.
What I'm asking is, are there any other files that will be extracted from the planet file, which the osm2pgsql tool will try putting somewhere else on the system?
This is what it's done so far;
# du -h
16K ./lost+found
12K ./9.3/main/pg_clog
4.0K ./9.3/main/pg_stat
12K ./9.3/main/pg_subtrans
12K ./9.3/main/pg_multixact/members
12K ./9.3/main/pg_multixact/offsets
28K ./9.3/main/pg_multixact
4.0K ./9.3/main/pg_stat_tmp
6.2M ./9.3/main/base/1
6.2M ./9.3/main/base/12061
6.3M ./9.3/main/base/12066
236G ./9.3/main/base/16385
236G ./9.3/main/base
448K ./9.3/main/global
4.0K ./9.3/main/pg_twophase
12K ./9.3/main/pg_notify
4.0K ./9.3/main/pg_serial
4.0K ./9.3/main/pg_snapshots
4.0K ./9.3/main/pg_xlog/archive_status
673M ./9.3/main/pg_xlog
4.0K ./9.3/main/pg_tblspc
236G ./9.3/main
236G ./9.3
266G .
Table descriptions will go into system database - like numbers of rows etc. Certainly it will grow but not much (say couple of megabytes for 100s of tables)
I'm not concerned about MBytes.
Right now, the only thing I've accounted for is the database. What I am concerned about is waiting three+ days for this import only to find out that the tool will write files where I didn't add additional storage to account for this.
Right now, the only thing I've accounted for is the database. What I am concerned about is waiting three+ days for this import only to find out that the tool will write files where I didn't add additional storage to account for this.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
You can mount new disk into /var/lib/psql (or whatever it is named)
Or change data directory in /etc/defaults/ ???
(i dont know layout of debian well)
Or change data directory in /etc/defaults/ ???
(i dont know layout of debian well)
Guessing you're just guessing then since you've not done this yourself :).
It's already running and has been for a couple of days now. I can't really pause it or change anything now, it's too late for that.
It's already running and has been for a couple of days now. I can't really pause it or change anything now, it's too late for that.
Ive done on RHEL6, since then it just flows, i have no clue if it still updates OSM etc. And I am fine while nobody complains.
You have 2 options - mount whole postgresql directory on separate filesystem, or change location of it to separate filesystem...
Then you are certain all data is there. I just grew / in vmware...
You have 2 options - mount whole postgresql directory on separate filesystem, or change location of it to separate filesystem...
Then you are certain all data is there. I just grew / in vmware...
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
That's what I explained above, I did that. I moved the entire /var/lib/postgresql directory to a 2TB mount.
What I've been saying is that I am not sure if something other than db files are going to be written to the drive using the above command at the stage I am at in the document.
I am hoping not because I did not account for any other directories needing to be larger.
What I've been saying is that I am not sure if something other than db files are going to be written to the drive using the above command at the stage I am at in the document.
I am hoping not because I did not account for any other directories needing to be larger.
Couple of lines to syslog from startup script, you can throw all logs at syslog later in production.
This is still running. Wish I'd have used more processes instead of following the doc because the system is almost idle while doing this and could have done it faster.
Will update when it is done.
Will update when it is done.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
It had completed but there was some odd drive error. I checked and found nothing wrong with the partition so had to start all over again.
Postgresql has internal journal, you can remove ext4 journal (man tune2fs) on database disk.
Not sure what you mean.
Location       SCSI device C partition 1       Device file       /dev/sdc1
Type       Linux EXT       Extent       1 - 267350 of 267349
Status       Mounted on /var/lib/postgresql as ext2
Location       SCSI device C partition 1       Device file       /dev/sdc1
Type       Linux EXT       Extent       1 - 267350 of 267349
Status       Mounted on /var/lib/postgresql as ext2
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
As an update, all this time later, I'm still trying to import that world map. Every time it gets near the end, it craps out complaining about not being able to access postgres and other similar errors.
Not exactly an accurate error msg because postgres is fine, I can access it from another session and everything else on the system is fine. No idea but pretty close to giving up on this.
Not exactly an accurate error msg because postgres is fine, I can access it from another session and everything else on the system is fine. No idea but pretty close to giving up on this.
Please check postgresql logs. (/var/log/postgresql/*)
And system messages (dmesg)
It would be interesting to know if problem is creating spatial index or committing table data.
Default settings provide veery small per-session memory for such big import. Make it temporarily half of RAM for import.
And system messages (dmesg)
It would be interesting to know if problem is creating spatial index or committing table data.
Default settings provide veery small per-session memory for such big import. Make it temporarily half of RAM for import.
Here is a snippet of the log.
I have 50GB of memory on the server, nothing else running on it. The command I used the last time I tried was;
sudo -u postgres -i osm2pgsql --slim -d gis -C 50000 --number-processes 4 /var/lib/postgresql/planet
I have 50GB of memory on the server, nothing else running on it. The command I used the last time I tried was;
sudo -u postgres -i osm2pgsql --slim -d gis -C 50000 --number-processes 4 /var/lib/postgresql/planet
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 04:16:24 MST WARNING: there is no transaction in progress
2015-10-13 07:21:16 MST ERROR: could not fsync file "base/16385/992881.3": Input/output error
2015-10-13 07:27:28 MST PANIC: could not fdatasync log file 00000001000000AE00000051: Input/output error
2015-10-13 07:27:29 MST LOG: WAL writer process (PID 1891) was terminated by signal 6: Aborted
2015-10-13 07:27:29 MST LOG: terminating any other active server processes
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, bec
ause another server process exited abnormally and possibly corrupted shared memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, bec
ause another server process exited abnormally and possibly corrupted shared memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, bec
ause another server process exited abnormally and possibly corrupted shared memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, bec
ause another server process exited abnormally and possibly corrupted shared memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, bec
ause another server process exited abnormally and possibly corrupted shared memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:30 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:30 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:30 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:32 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:32 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:32 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:27:33 MST WARNING: terminating connection because of crash of another server process
2015-10-13 07:27:33 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-13 07:27:33 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-13 07:28:22 MST LOG: all server processes terminated; reinitializing
2015-10-13 07:29:08 MST LOG: database system was interrupted; last known up at 2015-10-13 07:01:59 MST
2015-10-13 07:29:09 MST LOG: database system was not properly shut down; automatic recovery in progress
2015-10-13 07:29:09 MST LOG: redo starts at AE/48400068
2015-10-13 07:29:19 MST LOG: unexpected pageaddr AE/C924000 in log segment 00000001000000AE00000051, offset 9584640
2015-10-13 07:29:19 MST LOG: redo done at AE/51923F88
2015-10-13 07:29:31 MST LOG: MultiXact member wraparound protections are now enabled
2015-10-13 07:29:31 MST LOG: database system is ready to accept connections
2015-10-13 09:44:13 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:44:13 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-13 09:44:13 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:44:13 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-13 09:44:13 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:44:13 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-13 09:44:13 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:44:13 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-13 09:53:43 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:53:43 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-13 09:53:43 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:53:43 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-13 09:53:43 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:53:43 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-13 09:53:43 MST ERROR: permission denied for relation planet_osm_polygon
2015-10-13 09:53:43 MST STATEMENT: SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, amenity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;
2015-10-16 06:50:00 MST LOG: received fast shutdown request
2015-10-16 06:50:00 MST LOG: aborting any active transactions
2015-10-16 06:50:00 MST FATAL: terminating connection due to administrator command
2015-10-16 06:50:00 MST FATAL: terminating connection due to administrator command
2015-10-16 06:50:00 MST CONTEXT: COPY planet_osm_line, line 47248758, column way: "SRID=900913;LINESTRING (628022.5400000000372529 8726668.4600000008940697, 627994.8800000000046566 87..."
2015-10-16 06:50:00 MST STATEMENT: COPY planet_osm_line (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","br
and","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","junctio
n","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religion",
"route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 06:50:00 MST FATAL: terminating connection due to administrator command
2015-10-16 06:50:00 MST CONTEXT: COPY planet_osm_ways, line 114962769
2015-10-16 06:50:00 MST STATEMENT: COPY planet_osm_ways FROM STDIN;
2015-10-16 06:50:00 MST FATAL: terminating connection due to administrator command
2015-10-16 06:50:00 MST CONTEXT: COPY planet_osm_roads, line 4685365, column way: "SRID=900913;LINESTRING (-123395.6799999999930151 7162862.7900000000372529, -123439.7500000000000000 ..."
2015-10-16 06:50:00 MST STATEMENT: COPY planet_osm_roads (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","b
rand","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","juncti
on","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religion"
,"route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 06:51:00 MST LOG: received immediate shutdown request
2015-10-16 06:51:00 MST WARNING: terminating connection because of crash of another server process
2015-10-16 06:51:00 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-16 06:51:00 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-16 06:51:00 MST CONTEXT: COPY planet_osm_polygon, line 1
2015-10-16 06:51:00 MST WARNING: terminating connection because of crash of another server process
2015-10-16 06:51:00 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-16 06:51:00 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-16 06:51:00 MST CONTEXT: COPY planet_osm_point, line 74142775
2015-10-16 06:51:00 MST WARNING: terminating connection because of crash of another server process
2015-10-16 06:51:00 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared
memory.
2015-10-16 06:51:00 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-10-16 06:51:00 MST CONTEXT: COPY planet_osm_rels, line 1
2015-10-16 06:51:13 MST LOG: database system was interrupted; last known up at 2015-10-16 06:47:53 MST
2015-10-16 06:51:13 MST LOG: incomplete startup packet
2015-10-16 06:51:13 MST FATAL: the database system is starting up
2015-10-16 06:51:14 MST FATAL: the database system is starting up
2015-10-16 06:51:14 MST LOG: database system was not properly shut down; automatic recovery in progress
2015-10-16 06:51:14 MST LOG: redo starts at E6/F9D0D9E0
2015-10-16 06:51:14 MST FATAL: the database system is starting up
2015-10-16 06:51:15 MST FATAL: the database system is starting up
2015-10-16 06:51:15 MST FATAL: the database system is starting up
2015-10-16 06:51:16 MST FATAL: the database system is starting up
2015-10-16 06:51:16 MST FATAL: the database system is starting up
2015-10-16 06:51:17 MST FATAL: the database system is starting up
2015-10-16 06:51:17 MST FATAL: the database system is starting up
2015-10-16 06:51:18 MST FATAL: the database system is starting up
2015-10-16 06:51:18 MST FATAL: the database system is starting up
2015-10-16 06:51:18 MST LOG: incomplete startup packet
2015-10-16 06:51:33 MST LOG: unexpected pageaddr E6/E708A000 in log segment 00000001000000E700000005, offset 565248
2015-10-16 06:51:33 MST LOG: redo done at E7/5089F80
2015-10-16 06:51:44 MST LOG: MultiXact member wraparound protections are now enabled
2015-10-16 06:51:44 MST LOG: database system is ready to accept connections
2015-10-16 08:10:24 MST LOG: received fast shutdown request
2015-10-16 08:10:24 MST LOG: aborting any active transactions
2015-10-16 08:10:24 MST LOG: shutting down
2015-10-16 08:10:24 MST LOG: database system is shut down
2015-10-16 08:48:36 MST LOG: database system was shut down at 2015-10-16 08:10:24 MST
2015-10-16 08:48:36 MST LOG: MultiXact member wraparound protections are now enabled
2015-10-16 08:48:36 MST LOG: database system is ready to accept connections
2015-10-16 08:48:36 MST LOG: incomplete startup packet
2015-10-16 16:30:06 MST LOG: incomplete message from client
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_nodes, line 1432282688
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_nodes FROM STDIN;
2015-10-16 16:30:06 MST LOG: incomplete message from client
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_point, line 27843348
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_point (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","b
rand","bridge","boundary","building","capital","construction","covered","culvert","cutting","denomination","disused","ele","embankment","foot","generator:source","harbour","highway","historic","horse","inter
mittent","junction","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","poi","population","power","power_source","public_transport","rai
lway","ref","religion","route","service","shop","sport","surface","toll","tourism","tower:type","tunnel","water","waterway","wetland","width","wood","z_order",way) FROM STDIN
2015-10-16 16:30:06 MST ERROR: unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_rels, line 1
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_rels FROM STDIN;
2015-10-16 16:30:06 MST ERROR: unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_polygon, line 1
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_polygon (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle",
"brand","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","junc
tion","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religio
n","route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 16:30:06 MST ERROR: unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_nodes, line 1432282688
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_nodes FROM STDIN;
2015-10-16 16:30:06 MST ERROR: unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_point, line 27843348
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_point (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","b
rand","bridge","boundary","building","capital","construction","covered","culvert","cutting","denomination","disused","ele","embankment","foot","generator:source","harbour","highway","historic","horse","inter
mittent","junction","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","poi","population","power","power_source","public_transport","rai
lway","ref","religion","route","service","shop","sport","surface","toll","tourism","tower:type","tunnel","water","waterway","wetland","width","wood","z_order",way) FROM STDIN
2015-10-16 16:30:06 MST ERROR: unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_ways, line 1
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_ways FROM STDIN;
2015-10-16 16:30:06 MST ERROR: unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_roads, line 1
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_roads (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","b
rand","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","juncti
on","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religion"
,"route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 16:30:06 MST LOG: could not send data to client: Broken pipe
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_point (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","b
rand","bridge","boundary","building","capital","construction","covered","culvert","cutting","denomination","disused","ele","embankment","foot","generator:source","harbour","highway","historic","horse","inter
mittent","junction","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","poi","population","power","power_source","public_transport","rai
lway","ref","religion","route","service","shop","sport","surface","toll","tourism","tower:type","tunnel","water","waterway","wetland","width","wood","z_order",way) FROM STDIN
2015-10-16 16:30:06 MST LOG: could not send data to client: Broken pipe
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_ways FROM STDIN;
2015-10-16 16:30:06 MST LOG: could not send data to client: Broken pipe
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_polygon (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle",
"brand","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","junc
tion","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religio
n","route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 16:30:06 MST LOG: could not send data to client: Broken pipe
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_rels FROM STDIN;
2015-10-16 16:30:06 MST LOG: could not send data to client: Broken pipe
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_nodes FROM STDIN;
2015-10-16 16:30:06 MST LOG: could not send data to client: Broken pipe
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_roads (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","b
rand","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","juncti
on","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religion"
,"route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 16:30:06 MST FATAL: terminating connection because protocol sync was lost
2015-10-16 16:30:06 MST FATAL: terminating connection because protocol sync was lost
2015-10-16 16:30:06 MST FATAL: terminating connection because protocol sync was lost
2015-10-16 16:30:06 MST FATAL: terminating connection because protocol sync was lost
2015-10-16 16:30:06 MST ERROR: unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST CONTEXT: COPY planet_osm_line, line 1
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_line (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","br
and","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","junctio
n","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religion",
"route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 16:30:06 MST LOG: could not send data to client: Broken pipe
2015-10-16 16:30:06 MST STATEMENT: COPY planet_osm_line (osm_id,"access","addr:housename","addr:housenumber","addr:interpolation","admin_level","aerialway","aeroway","amenity","area","barrier","bicycle","br
and","bridge","boundary","building","construction","covered","culvert","cutting","denomination","disused","embankment","foot","generator:source","harbour","highway","historic","horse","intermittent","junctio
n","landuse","layer","leisure","lock","man_made","military","motorcar","name","natural","office","oneway","operator","place","population","power","power_source","public_transport","railway","ref","religion",
"route","service","shop","sport","surface","toll","tourism","tower:type","tracktype","tunnel","water","waterway","wetland","width","wood","z_order","way_area",way) FROM STDIN
2015-10-16 16:30:06 MST FATAL: terminating connection because protocol sync was lost
2015-10-16 16:30:07 MST FATAL: terminating connection because protocol sync was lost
2015-10-16 16:30:35 MST FATAL: terminating connection because protocol sync was lostEARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
And yet again, days into this, it blows up at the end.
Always the same thing which makes me feel this is not a server related issue but a osm2pgsql one.
Reading in file: /var/lib/postgresql/planet-latest.osm.pbf
Using PBF parser.
Processing: Node(3038306k 51.8k/s) Way(309061k 9.65k/s) Relation(3631140 21.23/s)
Standard exception processing relation id=5480194: TopologyException: side location conflict at 32619.389999999999 4904568.9699999997
Processing: Node(3038306k 51.8k/s) Way(309061k 9.65k/s) Relation(3668010 21.30/s) parse time: 262891s
Node stats: total(3038306927), max(3752289672) in 58668s
Way stats: total(309061030), max(371669320) in 32011s
Relation stats: total(3668018), max(5519092) in 172212s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels
Using built-in tag processing pipeline
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels
Using built-in tag processing pipeline
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels
Using built-in tag processing pipeline
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels
Using built-in tag processing pipeline
Going over pending ways...
204865914 ways are pending
Using 4 helper-processes
Finished processing 204865914 ways in 39881 sec
204865914 Pending ways took 39881s at a rate of 5136.93/s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Going over pending relations...
0 relations are pending
Using 4 helper-processes
Finished processing 0 relations in 0 sec
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Sorting data and creating indexes for planet_osm_point
Sorting data and creating indexes for planet_osm_line
Stopping table: planet_osm_ways
Building index on table: planet_osm_ways
Sorting data and creating indexes for planet_osm_roads
Sorting data and creating indexes for planet_osm_polygon
Stopping table: planet_osm_rels
Building index on table: planet_osm_rels
Stopping table: planet_osm_nodes
Stopped table: planet_osm_nodes in 0s
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally a nd possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally a nd possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally a nd possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally a nd possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally a nd possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally a nd possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
terminate called after throwing an instance of 'std::runtime_error'
terminate called recursively
root@osm1:/var/lib/postgresql#Always the same thing which makes me feel this is not a server related issue but a osm2pgsql one.
Can you try importing with one thread?
Will not change speed,DB loading is bound to IO, not CPU
Will not change speed,DB loading is bound to IO, not CPU
This is what I've been trying
 sudo -u postgres -i osm2pgsql --slim -d gis -C 90000 --number-processes 4 /var/lib/postgresql/planet
You want me to change --number-processes to 1?
 sudo -u postgres -i osm2pgsql --slim -d gis -C 90000 --number-processes 4 /var/lib/postgresql/planet
You want me to change --number-processes to 1?
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Slightly different but similar result using a single process.
This time, they mostly seem to be warnings but the very end means what? Did it actually complete or not?
HINT: Â In a moment you should be able to reconnect to the database and repeat your command.
terminate called after throwing an instance of 'std::runtime_error'
terminate called recursively
sudo -u postgres -i osm2pgsql --slim -d gis -C 90000 --number-processes 1 /var/lib/postgresql/planet
This time, they mostly seem to be warnings but the very end means what? Did it actually complete or not?
HINT: Â In a moment you should be able to reconnect to the database and repeat your command.
terminate called after throwing an instance of 'std::runtime_error'
terminate called recursively
sudo -u postgres -i osm2pgsql --slim -d gis -C 90000 --number-processes 1 /var/lib/postgresql/planet
Using 1 helper-processes
Finished processing 0 relations in 0 sec
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Stopping table: planet_osm_nodes
Stopped table: planet_osm_nodes in 0s
Sorting data and creating indexes for planet_osm_line
Stopping table: planet_osm_ways
Building index on table: planet_osm_ways
Sorting data and creating indexes for planet_osm_point
Sorting data and creating indexes for planet_osm_polygon
Stopping table: planet_osm_rels
Building index on table: planet_osm_rels
Sorting data and creating indexes for planet_osm_roads
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
CONTEXT: writing block 908544 of relation base/16385/3065961
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
CONTEXT: writing block 910873 of relation base/16385/3065961
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
terminate called after throwing an instance of 'std::runtime_error'
terminate called recursively
Also, when I try to start it, there is always a permissions error which I cannot seem to find.
root@osm1:/var/log/postgresql# sudo -u mapuser renderd -f -c /usr/local/etc/renderd.conf
renderd[8484]: Rendering daemon started
renderd[8484]: Initiating reqyest_queue
renderd[8484]: Parsing section renderd
renderd[8484]: Parsing render section 0
renderd[8484]: Parsing section mapnik
renderd[8484]: Parsing section default
renderd[8484]: config renderd: unix socketname=/var/run/renderd/renderd.sock
renderd[8484]: config renderd: num_threads=4
renderd[8484]: config renderd: num_slaves=0
renderd[8484]: config renderd: tile_dir=/var/lib/mod_tile
renderd[8484]: config renderd: stats_file=/var/run/renderd/renderd.stats
renderd[8484]: config mapnik: plugins_dir=/usr/local/lib/mapnik/input
renderd[8484]: config mapnik: font_dir=/usr/share/fonts/truetype/ttf-dejavu
renderd[8484]: config mapnik: font_dir_recurse=1
renderd[8484]: config renderd(0): Active
renderd[8484]: config renderd(0): unix socketname=/var/run/renderd/renderd.sock
renderd[8484]: config renderd(0): num_threads=4
renderd[8484]: config renderd(0): tile_dir=/var/lib/mod_tile
renderd[8484]: config renderd(0): stats_file=/var/run/renderd/renderd.stats
renderd[8484]: config map 0: name(default) file(/usr/local/share/maps/style/OSMBright/OSMBright.xml) uri(/osm_tiles/) htcp() host( localhost)
renderd[8484]: Initialising unix server socket on /var/run/renderd/renderd.sock
renderd[8484]: Created server socket 4
renderd[8484]: Renderd is using mapnik version 2.2.0
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif-BoldItalic.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Oblique.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-ExtraLight.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Oblique.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-BoldOblique.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif-Italic.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif-Bold.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-BoldOblique.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed-BoldItalic.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-Bold.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-BoldOblique.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed-Italic.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-Oblique.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed-Bold.ttf
renderd[8484]: DEBUG: Loading font: /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed.ttf
Running in foreground mode...
renderd[8484]: Starting stats thread
debug: init_storage_backend: initialising file storage backend at: /var/lib/mod_tile
renderd[8484]: Loading parameterization function for
debug: init_storage_backend: initialising file storage backend at: /var/lib/mod_tile
renderd[8484]: Loading parameterization function for
debug: init_storage_backend: initialising file storage backend at: /var/lib/mod_tile
debug: init_storage_backend: initialising file storage backend at: /var/lib/mod_tile
renderd[8484]: Loading parameterization function for
renderd[8484]: Loading parameterization function for
renderd[8484]: An error occurred while loading the map layer 'default': Postgis Plugin: ERROR: permission denied for relation plane t_osm_polygon
Full sql was: 'SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, ame nity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;'
encountered during parsing of layer 'landuse_gen0' in Layer at line 193 of '/usr/local/share/maps/style/OSMBright/OSMBright.xml'
renderd[8484]: An error occurred while loading the map layer 'default': Postgis Plugin: ERROR: permission denied for relation plane t_osm_polygon
Full sql was: 'SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, ame nity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;'
encountered during parsing of layer 'landuse_gen0' in Layer at line 193 of '/usr/local/share/maps/style/OSMBright/OSMBright.xml'
renderd[8484]: An error occurred while loading the map layer 'default': Postgis Plugin: ERROR: permission denied for relation plane t_osm_polygon
Full sql was: 'SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, ame nity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;'
encountered during parsing of layer 'landuse_gen0' in Layer at line 193 of '/usr/local/share/maps/style/OSMBright/OSMBright.xml'
renderd[8484]: An error occurred while loading the map layer 'default': Postgis Plugin: ERROR: permission denied for relation plane t_osm_polygon
Full sql was: 'SELECT ST_SRID("way") AS srid FROM ( SELECT way, way_area AS area, COALESCE(landuse, leisure, "natural", highway, ame nity, tourism) AS type
FROM planet_osm_polygon
WHERE way_area > 100000
ORDER BY way_area DESC
) AS data WHERE "way" IS NOT NULL LIMIT 1;'
encountered during parsing of layer 'landuse_gen0' in Layer at line 193 of '/usr/local/share/maps/style/OSMBright/OSMBright.xml'
Finally, when I try to run the test, the part where it says if you don't see any fatal errors, then try this; http://192.168.1.25/osm_tiles/0/0/0.png
Which results in this;
Which results in this;
renderd[8484]: DEBUG: Got incoming connection, fd 8, number 1
renderd[8484]: DEBUG: Got incoming request with protocol version 2
renderd[8484]: DEBUG: Got command RenderPrio fd(8) xml(default), z(0), x(0), y(0), mime(image/png), options()
renderd[8484]: Received request for map layer 'default' which failed to load
renderd[8484]: DEBUG: Sending render cmd(4 default 0/0/0) with protocol version 2 to fd 8
renderd[8484]: DEBUG: Failed to read cmd on fd 8
renderd[8484]: DEBUG: Connection 0, fd 8 closed, now 0 leftEARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Check dmesg if system did not kill postgresql (client or server) Â for out of memory.
2015-10-16 16:30:06 MST ERROR: Â unexpected EOF on client connection with an open transaction
2015-10-16 16:30:06 MST ERROR: Â unexpected EOF on client connection with an open transaction
This is interesting. The partition that postgres and the data are on are over a fibre channel storage device. It seems that the adapter is timing out?
The problem?
The problem?
[312969.093717] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313002.792466] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313025.832131] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313029.832367] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313065.800556] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313080.436060] INFO: task postgres:1393 blocked for more than 120 seconds.
[313080.436161] Not tainted 3.19.0-30-generic #34~14.04.1-Ubuntu
[313080.436250] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[313080.436370] postgres D ffff8800de817d08 0 1393 1391 0x00000000
[313080.436375] ffff8800de817d08 ffff880602659d70 0000000000013e80 ffff8800de817fd8
[313080.436378] 0000000000013e80 ffff880604646bf0 ffff880602659d70 ffff880c017d61e8
[313080.436381] ffff8800de817e48 7fffffffffffffff ffff8800de817e40 ffff880602659d70
[313080.436384] Call Trace:
[313080.436395] [<ffffffff817b2a99>] schedule+0x29/0x70
[313080.436399] [<ffffffff817b5b5c>] schedule_timeout+0x20c/0x280
[313080.436406] [<ffffffff81378d33>] ? blk_queue_bio+0x323/0x390
[313080.436409] [<ffffffff81373f20>] ? generic_make_request+0xc0/0x110
[313080.436412] [<ffffffff817b37c4>] wait_for_completion+0xa4/0x170
[313080.436416] [<ffffffff810a0a90>] ? wake_up_state+0x20/0x20
[313080.436419] [<ffffffff8136d9fe>] submit_bio_wait+0x5e/0x70
[313080.436423] [<ffffffff8137a30e>] blkdev_issue_flush+0x5e/0x90
[313080.436426] [<ffffffff81213eb8>] generic_file_fsync+0x38/0x40
[313080.436432] [<ffffffff8126acf3>] ext4_sync_file+0x183/0x320
[313080.436436] [<ffffffff8121cc41>] do_fsync+0x51/0x80
[313080.436439] [<ffffffff8121ced0>] SyS_fsync+0x10/0x20
[313080.436442] [<ffffffff817b6e4d>] system_call_fastpath+0x16/0x1b
[313080.436445] INFO: task postgres:1395 blocked for more than 120 seconds.
[313080.436535] Not tainted 3.19.0-30-generic #34~14.04.1-Ubuntu
[313080.436626] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[313080.436744] postgres D ffff8800dec37d08 0 1395 1391 0x00000000
[313080.436747] ffff8800dec37d08 ffff88060265d850 0000000000013e80 ffff8800dec37fd8
[313080.436750] 0000000000013e80 ffff880604646bf0 ffff88060265d850 ffff880c017d61e8
[313080.436752] ffff8800dec37e48 7fffffffffffffff ffff8800dec37e40 ffff88060265d850
[313080.436755] Call Trace:
[313080.436758] [<ffffffff817b2a99>] schedule+0x29/0x70
[313080.436760] [<ffffffff817b5b5c>] schedule_timeout+0x20c/0x280
[313080.436763] [<ffffffff81378d33>] ? blk_queue_bio+0x323/0x390
[313080.436766] [<ffffffff81373f20>] ? generic_make_request+0xc0/0x110
[313080.436769] [<ffffffff817b37c4>] wait_for_completion+0xa4/0x170
[313080.436771] [<ffffffff810a0a90>] ? wake_up_state+0x20/0x20
[313080.436774] [<ffffffff8136d9fe>] submit_bio_wait+0x5e/0x70
[313080.436776] [<ffffffff8137a30e>] blkdev_issue_flush+0x5e/0x90
[313080.436779] [<ffffffff81213eb8>] generic_file_fsync+0x38/0x40
[313080.436782] [<ffffffff8126acf3>] ext4_sync_file+0x183/0x320
[313080.436784] [<ffffffff8121cc41>] do_fsync+0x51/0x80
[313080.436787] [<ffffffff8121cef3>] SyS_fdatasync+0x13/0x20
[313080.436790] [<ffffffff817b6e4d>] system_call_fastpath+0x16/0x1b
[313113.804023] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313113.804277] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313113.804778] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313120.121458] blk_update_request: I/O error, dev sdc, sector 0
[313180.840137] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[313200.436055] INFO: task postgres:1393 blocked for more than 120 seconds.
[313200.436155] Not tainted 3.19.0-30-generic #34~14.04.1-Ubuntu
[313200.436245] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[313200.436365] postgres D ffff8800de817d08 0 1393 1391 0x00000004
[313200.436370] ffff8800de817d08 ffff880602659d70 0000000000013e80 ffff8800de817fd8
[313200.436374] 0000000000013e80 ffff880604646bf0 ffff880602659d70 ffff880c017d61e8
[313200.436376] ffff8800de817e48 7fffffffffffffff ffff8800de817e40 ffff880602659d70
[313200.436380] Call Trace:
[313200.436391] [<ffffffff817b2a99>] schedule+0x29/0x70
[313200.436395] [<ffffffff817b5b5c>] schedule_timeout+0x20c/0x280
[313200.436402] [<ffffffff81378d33>] ? blk_queue_bio+0x323/0x390
[313200.436405] [<ffffffff81373f20>] ? generic_make_request+0xc0/0x110
[313200.436408] [<ffffffff817b37c4>] wait_for_completion+0xa4/0x170
[313200.436412] [<ffffffff810a0a90>] ? wake_up_state+0x20/0x20
[313200.436415] [<ffffffff8136d9fe>] submit_bio_wait+0x5e/0x70
[313200.436418] [<ffffffff8137a30e>] blkdev_issue_flush+0x5e/0x90
[313200.436422] [<ffffffff81213eb8>] generic_file_fsync+0x38/0x40
[313200.436427] [<ffffffff8126acf3>] ext4_sync_file+0x183/0x320
[313200.436431] [<ffffffff8121cc41>] do_fsync+0x51/0x80
[313200.436434] [<ffffffff8121ced0>] SyS_fsync+0x10/0x20
[313200.436438] [<ffffffff817b6e4d>] system_call_fastpath+0x16/0x1b
[313241.824265] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926670.828574] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926671.832037] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926681.832279] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926734.840154] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926752.840286] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926752.840556] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926825.832101] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926832.824318] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926832.824600] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926896.832446] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926896.832860] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926944.840438] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926944.840887] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926966.832345] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[926969.832363] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927009.832308] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927012.832330] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927041.828559] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927048.812126] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927090.808518] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927090.809007] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927091.800512] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927091.800996] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927245.832397] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927246.836028] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927288.840361] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927301.824471] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927301.824898] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927358.816536] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927415.832120] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927415.832209] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927420.840161] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927420.840292] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927490.828243] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927490.828461] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927516.824481] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927516.824938] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927573.808475] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927574.800489] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927633.832152] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927634.824170] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927636.828189] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927637.832028] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927670.832519] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927670.833009] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927681.816162] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927682.820029] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927822.840164] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927822.840302] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927940.832347] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927940.832635] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927941.824345] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927941.824659] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927974.824345] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927984.832479] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927984.832929] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927985.824501] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[927985.824970] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928067.837804] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928072.840311] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928090.840568] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928090.841128] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928133.832279] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928134.836022] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928179.832314] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928235.832423] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928235.832816] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928259.812419] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928259.812812] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928307.832180] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928307.832328] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928311.832230] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928311.832437] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928481.832442] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928481.832807] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928630.792518] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928631.796032] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928631.796527] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928765.861865] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928765.869156] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928887.812562] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928887.813099] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928923.880414] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928923.880805] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928923.881184] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928923.881561] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[928923.881940] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929022.824395] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929022.824761] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929031.816513] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929031.816992] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929216.824119] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929216.824217] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929216.824321] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929248.828184] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929310.201266] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929370.788215] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929370.788404] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929452.816572] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929452.817051] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929481.816439] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929539.800521] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929539.801021] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929540.788541] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929567.832506] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929688.824424] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929692.824526] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929693.812526] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929759.792537] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929809.824295] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929932.788367] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929932.788705] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929991.800340] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[929991.800646] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930123.800123] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930123.800215] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930125.792146] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930125.792272] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930125.792397] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930249.800452] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930251.792512] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930251.793022] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930354.824280] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930356.816289] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930356.816549] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930379.816496] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930379.816961] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930392.812288] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930423.812145] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930424.812147] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930431.812265] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930431.812484] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930436.824296] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930438.816301] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930462.832505] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930462.833029] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930548.792254] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930548.792477] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930549.788243] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930565.816378] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930567.816451] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930634.816206] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930672.824366] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930763.800446] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930763.800897] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930766.792327] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930810.816311] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930810.816521] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930810.816742] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930828.824419] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930828.824813] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930854.792232] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[930854.792478] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931005.800568] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931005.801094] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931060.824436] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931072.808549] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931072.809077] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931124.824505] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931124.824983] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931137.792174] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931166.792472] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931167.788472] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931211.792186] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931211.792296] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931213.792150] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931213.792263] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931328.840161] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931328.840313] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931336.792403] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931337.788413] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931371.159647] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931405.832493] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931410.840131] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931435.788484] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931561.792234] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931637.816281] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931649.800350] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931653.800424] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931698.832430] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931698.832837] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931736.828566] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931737.824173] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931737.824264] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931739.828133] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931747.816245] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931760.840377] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931760.840730] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931808.828355] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931841.832215] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931843.828229] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931843.828411] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931859.832456] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931860.824491] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931870.832163] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931870.832278] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[931960.792238] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932019.832410] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932020.824403] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932086.788281] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932086.788527] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932087.788309] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932090.792339] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932197.792140] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932198.788149] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932219.800299] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932219.800572] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932261.832161] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932332.792383] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932351.832493] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932351.832969] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932415.808523] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932415.809022] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932448.089434] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932482.824299] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932482.824569] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932576.832436] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932580.832486] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932634.840566] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932634.841144] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932638.832287] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932696.828143] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932696.828244] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932749.832153] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932750.836025] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932750.836169] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932750.836337] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932750.836462] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932751.824217] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932752.828036] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932800.824229] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932866.840458] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932866.840865] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932879.816220] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932879.816382] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932930.804479] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932930.804931] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932930.805365] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932960.808419] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932960.808771] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932992.824396] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932993.824410] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932997.832102] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[932997.832174] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933044.804398] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933044.804776] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933044.805134] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933051.812455] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933051.812886] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933053.816481] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933054.812484] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933072.824360] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933099.832386] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933137.808520] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933137.809012] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933157.792148] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933157.792265] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933197.802141] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933197.820580] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933275.804515] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933275.804999] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933277.804546] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933277.805030] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933289.816550] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933320.820021] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933352.808104] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933352.808180] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933354.804110] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933354.804203] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933383.177999] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933445.816323] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933446.800300] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933447.800307] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933447.800636] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933477.999834] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933478.000281] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933551.792573] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933596.804231] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933630.832349] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933875.800405] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933893.816363] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933932.993458] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933974.824223] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[933974.824400] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934006.728170] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934041.812548] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934041.813046] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934066.840446] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934080.436047] INFO: task postgres:20289 blocked for more than 120 seconds.
[934080.436153] Not tainted 3.19.0-30-generic #34~14.04.1-Ubuntu
[934080.436243] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[934080.436362] postgres D ffff8805fd28fd08 0 20289 1391 0x00000000
[934080.436366] ffff8805fd28fd08 ffff8806012f44b0 0000000000013e80 ffff8805fd28ffd8
[934080.436369] 0000000000013e80 ffff8806046475c0 ffff8806012f44b0 ffff880602657830
[934080.436372] ffff8805fd28fe48 7fffffffffffffff ffff8805fd28fe40 ffff8806012f44b0
[934080.436374] Call Trace:
[934080.436383] [<ffffffff817b2a99>] schedule+0x29/0x70
[934080.436387] [<ffffffff817b5b5c>] schedule_timeout+0x20c/0x280
[934080.436392] [<ffffffff81378d33>] ? blk_queue_bio+0x323/0x390
[934080.436395] [<ffffffff81373f20>] ? generic_make_request+0xc0/0x110
[934080.436398] [<ffffffff817b37c4>] wait_for_completion+0xa4/0x170
[934080.436401] [<ffffffff810a0a90>] ? wake_up_state+0x20/0x20
[934080.436404] [<ffffffff8136d9fe>] submit_bio_wait+0x5e/0x70
[934080.436406] [<ffffffff8137a30e>] blkdev_issue_flush+0x5e/0x90
[934080.436410] [<ffffffff81213eb8>] generic_file_fsync+0x38/0x40
[934080.436414] [<ffffffff8126acf3>] ext4_sync_file+0x183/0x320
[934080.436417] [<ffffffff8121cc41>] do_fsync+0x51/0x80
[934080.436420] [<ffffffff81201f05>] ? SyS_poll+0x65/0x100
[934080.436423] [<ffffffff8121cef3>] SyS_fdatasync+0x13/0x20
[934080.436426] [<ffffffff817b6e4d>] system_call_fastpath+0x16/0x1b
[934106.808365] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934128.394645] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934188.840548] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934200.436043] INFO: task postgres:20289 blocked for more than 120 seconds.
[934200.436149] Not tainted 3.19.0-30-generic #34~14.04.1-Ubuntu
[934200.436238] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[934200.436357] postgres D ffff8805fd28fd08 0 20289 1391 0x00000000
[934200.436362] ffff8805fd28fd08 ffff8806012f44b0 0000000000013e80 ffff8805fd28ffd8
[934200.436364] 0000000000013e80 ffff8806046475c0 ffff8806012f44b0 ffff880602657830
[934200.436367] ffff8805fd28fe48 7fffffffffffffff ffff8805fd28fe40 ffff8806012f44b0
[934200.436370] Call Trace:
[934200.436378] [<ffffffff817b2a99>] schedule+0x29/0x70
[934200.436382] [<ffffffff817b5b5c>] schedule_timeout+0x20c/0x280
[934200.436387] [<ffffffff81378d33>] ? blk_queue_bio+0x323/0x390
[934200.436390] [<ffffffff81373f20>] ? generic_make_request+0xc0/0x110
[934200.436392] [<ffffffff817b37c4>] wait_for_completion+0xa4/0x170
[934200.436395] [<ffffffff810a0a90>] ? wake_up_state+0x20/0x20
[934200.436398] [<ffffffff8136d9fe>] submit_bio_wait+0x5e/0x70
[934200.436401] [<ffffffff8137a30e>] blkdev_issue_flush+0x5e/0x90
[934200.436404] [<ffffffff81213eb8>] generic_file_fsync+0x38/0x40
[934200.436408] [<ffffffff8126acf3>] ext4_sync_file+0x183/0x320
[934200.436412] [<ffffffff8121cc41>] do_fsync+0x51/0x80
[934200.436415] [<ffffffff81201f05>] ? SyS_poll+0x65/0x100
[934200.436417] [<ffffffff8121cef3>] SyS_fdatasync+0x13/0x20
[934200.436420] [<ffffffff817b6e4d>] system_call_fastpath+0x16/0x1b
[934213.800516] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934249.868750] qla2xxx [0000:2d:00.0]-801c:3: Abort command issued nexus=3:0:1 -- 1 2002.
[934249.876420] blk_update_request: I/O error, dev sdc, sector 0
sysctl kernel.hung_task_timeout_s
<import data>
Read qlogic documentation and set task timeout to value bigger than disk timeout.
<import data>
Read qlogic documentation and set task timeout to value bigger than disk timeout.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
The only thing I can find is in /etc/sysctl.conf:
kernel.hung_task_timeout_s
But, everyone mentions disabled, and it's not clear if that will make it no longer time out.
kernel.hung_task_timeout_s
But, everyone mentions disabled, and it's not clear if that will make it no longer time out.
before importing data run:
sysctl kernel.hung_task_timeout_s
It should be zero.
sysctl kernel.hung_task_timeout_s
It should be zero.
Yes, I tested and the result is 0 so I restarted it yesterday. Now to wait a couple days for the result again.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
it's almost done... I see a new error I've not seen before however so getting nervous.
Reading in file: /var/lib/postgresql/planet-latest.osm.pbf
Using PBF parser.
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3631140 27.69/s)
Standard exception processing relation id=5480194: TopologyException: side location conflict at 32619.389999999999 4904568.9699999997
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3668010 27.78/s) parse time: 217644s
Node stats: total(3038306927), max(3752289672) in 57553s
Way stats: total(309061030), max(371669320) in 28031s
Relation stats: total(3668018), max(5519092) in 132060s
I don't know how anyone can use this OSM solution when you can't ever get past this problem. Even running in single process and with the timeout disabled, days later, still broken.
Using PBF parser.
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3631140 27.69/s)
Standard exception processing relation id=5480194: TopologyException: side location conflict at 32619.389999999999 4904568.9699999997
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3668010 27.78/s) parse time: 217644s
Node stats: total(3038306927), max(3752289672) in 57553s
Way stats: total(309061030), max(371669320) in 28031s
Relation stats: total(3668018), max(5519092) in 132060s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels
Using built-in tag processing pipeline
Going over pending ways...
204865914 ways are pending
Using 1 helper-processes
Finished processing 204865914 ways in 77482 sec
204865914 Pending ways took 77482s at a rate of 2644.05/s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Going over pending relations...
0 relations are pending
Using 1 helper-processes
Finished processing 0 relations in 0 sec
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Stopping table: planet_osm_nodes
Sorting data and creating indexes for planet_osm_point
Sorting data and creating indexes for planet_osm_line
Stopping table: planet_osm_ways
Building index on table: planet_osm_ways
Stopping table: planet_osm_rels
Building index on table: planet_osm_rels
Sorting data and creating indexes for planet_osm_roads
Stopped table: planet_osm_nodes in 0s
Sorting data and creating indexes for planet_osm_polygon
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
terminate called after throwing an instance of 'std::runtime_error'
terminate called recursively
Can't tell if the problem is the qlogic card or something else or a mix of things.
Nov 5 06:58:18 osm1 kernel: [303138.792486] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 06:59:05 osm1 kernel: [303185.800408] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:00:01 osm1 CRON[7660]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
Nov 5 07:00:01 osm1 CRON[7661]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Nov 5 07:00:19 osm1 kernel: [303259.832487] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:01:21 osm1 kernel: [303321.672484] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:02:02 osm1 kernel: [303362.792235] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:02:21 osm1 kernel: [303381.828159] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:03:25 osm1 kernel: [303445.839832] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:04:26 osm1 kernel: [303506.804486] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:01 osm1 CRON[8035]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
Nov 5 07:05:01 osm1 CRON[8036]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Nov 5 07:05:08 osm1 kernel: [303548.236306] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.237053] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.237814] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.238572] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.239337] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.240122] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.240870] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.241621] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.242410] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.242926] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.243443] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.243959] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.244469] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.244985] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.245501] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.246017] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.246534] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.247060] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.247620] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.248178] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.248738] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.249295] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.249854] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.250373] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.250930] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.251490] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.252146] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:08 osm1 kernel: [303548.816594] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:27 osm1 kernel: [303567.840369] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 -- 1 2002.
Nov 5 07:05:27 osm1 kernel: [303567.849252] blk_update_request: I/O error, dev sdc, sector 0
Nov 5 07:10:01 osm1 CRON[8417]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
Nov 5 07:10:01 osm1 CRON[8418]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Nov 5 07:15:01 osm1 CRON[8791]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
Nov 5 07:15:01 osm1 CRON[8792]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)
Nov 5 07:17:01 osm1 CRON[9136]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 5 07:20:01 osm1 CRON[9169]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
Nov 5 07:20:01 osm1 CRON[9170]: (munin) CMD (if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; fi)# cat apport.log
ERROR: apport (pid 8378) Thu Nov 5 07:05:28 2015: called for pid 1432, signal 6, core limit 0
ERROR: apport (pid 8378) Thu Nov 5 07:05:28 2015: executable: /usr/lib/postgresql/9.3/bin/postgres (command line "postgres:\ writer\ process\ \ \ ")
ERROR: apport (pid 8378) Thu Nov 5 07:05:28 2015: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 8378) Thu Nov 5 07:05:54 2015: wrote report /var/crash/_usr_lib_postgresql_9.3_bin_postgres.106.crash
ERROR: apport (pid 8380) Thu Nov 5 07:05:55 2015: called for pid 1627, signal 6, core limit 0
ERROR: apport (pid 8380) Thu Nov 5 07:05:55 2015: executable: /usr/local/bin/osm2pgsql (command line "osm2pgsql --slim -d gis -C 90000 --number-processes 1 /var/lib/postgresql/planet-latest.osm.pbf")
ERROR: apport (pid 8380) Thu Nov 5 07:05:55 2015: executable does not belong to a package, ignoring2015-11-05 07:05:54 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2015-11-05 07:05:54 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-11-05 07:06:12 MST WARNING: terminating connection because of crash of another server process
2015-11-05 07:06:12 MST DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
2015-11-05 07:06:12 MST HINT: In a moment you should be able to reconnect to the database and repeat your command.
2015-11-05 07:06:12 MST LOG: could not send data to client: Broken pipe
2015-11-05 07:06:12 MST STATEMENT: CREATE TABLE planet_osm_polygon_tmp AS SELECT * FROM planet_osm_polygon ORDER BY CASE WHEN ST_IsEmpty(way) THEN NULL ELSE ST_GeoHash(ST_Transform(ST_Envelope(way),4326),10) END
2015-11-05 07:06:25 MST LOG: all server processes terminated; reinitializing
2015-11-05 07:07:10 MST LOG: database system was interrupted; last known up at 2015-11-05 06:26:16 MST
2015-11-05 07:07:11 MST LOG: database system was not properly shut down; automatic recovery in progress
2015-11-05 07:07:11 MST LOG: redo starts at 1F8/344274B0
2015-11-05 07:07:19 MST LOG: unexpected pageaddr 1F8/11000000 in log segment 00000001000001F800000040, offset 0
2015-11-05 07:07:19 MST LOG: redo done at 1F8/3FFFE7B0
2015-11-05 07:07:31 MST LOG: MultiXact member wraparound protections are now enabled
2015-11-05 07:07:31 MST LOG: database system is ready to accept connectionsReading in file: /var/lib/postgresql/planet-latest.osm.pbf
Using PBF parser.
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3631140 27.69/s)
Standard exception processing relation id=5480194: TopologyException: side location conflict at 32619.389999999999 4904568.9699999997
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3668010 27.78/s) parse time: 217644s
Node stats: total(3038306927), max(3752289672) in 57553s
Way stats: total(309061030), max(371669320) in 28031s
Relation stats: total(3668018), max(5519092) in 132060sUsing PBF parser.
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3631140 27.69/s)
Standard exception processing relation id=5480194: TopologyException: side location conflict at 32619.389999999999 4904568.9699999997
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3668010 27.78/s) parse time: 217644s
Node stats: total(3038306927), max(3752289672) in 57553s
Way stats: total(309061030), max(371669320) in 28031s
Relation stats: total(3668018), max(5519092) in 132060s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels
Using built-in tag processing pipeline
Going over pending ways...
204865914 ways are pending
Using 1 helper-processes
Finished processing 204865914 ways in 77482 sec
204865914 Pending ways took 77482s at a rate of 2644.05/s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Going over pending relations...
0 relations are pending
Using 1 helper-processes
Finished processing 0 relations in 0 sec
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Stopping table: planet_osm_nodes
Sorting data and creating indexes for planet_osm_point
Sorting data and creating indexes for planet_osm_line
Stopping table: planet_osm_ways
Building index on table: planet_osm_ways
Stopping table: planet_osm_rels
Building index on table: planet_osm_rels
Sorting data and creating indexes for planet_osm_roads
Stopped table: planet_osm_nodes in 0s
Sorting data and creating indexes for planet_osm_polygon
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
terminate called after throwing an instance of 'std::runtime_error'
terminate called recursivelyGet a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Using PBF parser.
Processing: Node(3038306k 52.8k/s) Way(309061k 11.03k/s) Relation(3631140 27.69/s)There is no wall time logged - can you check syslog for damage in dmesg?
Check syslog for dmesg?
All I see in syslog as a hint is lots of
Nov  5 07:05:08 osm1 kernel: [303548.816594] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 --  1 2002.
Seems this will never work using fibre channel for some weird reason. I've not ever seen fibre channel issues in the 15 years I've been using it.
All I see in syslog as a hint is lots of
Nov  5 07:05:08 osm1 kernel: [303548.816594] qla2xxx [0000:2d:00.0]-801c:2: Abort command issued nexus=2:0:1 --  1 2002.
Seems this will never work using fibre channel for some weird reason. I've not ever seen fibre channel issues in the 15 years I've been using it.
In short: DB import is pushing your storage past its limits
Plan A
Check all pieces of FC - cables, firmwares, swap ports if possible.
https://bugzilla.redhat.com/show_bug.cgi?id=643933
This should not appear in good environment.
Plan B
My guess - storage unit queues grow too long and cause timeouts -
Can you add "elevator=deadline" to kernel boot options and try importing again?
Plan C
Do you have a desktop PC with SSD anywhere - that should be snap to import, just like 40GB ram disk (tmpfs in Linux terms), and then copying postgresql data dir to server disk... (again qla may time out)
Plan A
Check all pieces of FC - cables, firmwares, swap ports if possible.
https://bugzilla.redhat.com/show_bug.cgi?id=643933
This should not appear in good environment.
Plan B
My guess - storage unit queues grow too long and cause timeouts -
Can you add "elevator=deadline" to kernel boot options and try importing again?
Plan C
Do you have a desktop PC with SSD anywhere - that should be snap to import, just like 40GB ram disk (tmpfs in Linux terms), and then copying postgresql data dir to server disk... (again qla may time out)
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
The FC storage servers are being used with a number of other servers but there is of course always a chance of problems.
I've ordered some cables so I can add some drives into the server. That way, I'll be able to try this with local storage and see what happens. Cables should be in today or tomorrow.
I've ordered some cables so I can add some drives into the server. That way, I'll be able to try this with local storage and see what happens. Cables should be in today or tomorrow.
It is not about cables. 64GB SD card  from digital cameras should permit you to import data in an hour or so...
Plan B looks quickest to implement - what do you think?
It can be done on working system:
echo deadline | tee /sys/block/*/queue/schedul
(default is cfq if you want to switch back without reboot)
Plan B looks quickest to implement - what do you think?
It can be done on working system:
echo deadline | tee /sys/block/*/queue/schedul
(default is cfq if you want to switch back without reboot)
I'm not saying it's about cables :). I meant I ordered cables so I can put local storage onto the server, removing the qlogic problem potential.
Anyhow, add elevator=deadline to what? This is a ubuntu server. Same place as the other, sysctl.conf?
Also, what do you mean this should not take long? It takes several days each time.
Anyhow, add elevator=deadline to what? This is a ubuntu server. Same place as the other, sysctl.conf?
Also, what do you mean this should not take long? It takes several days each time.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
boot command line.
either /boot/grub.conf
or /etc/sysconfig/grub + rebuild grub conf with grub-mkconfig.
either /boot/grub.conf
or /etc/sysconfig/grub + rebuild grub conf with grub-mkconfig.
I've added it to my version of Ubuntu, now rebooting then restarting the process yet again.
Even after adding your last suggestion, the problem remains. I'm stumped.
Reading in file: /var/lib/postgresql/planet-latest.osm.pbf
Using PBF parser.
Processing: Node(3038306k 51.6k/s) Way(309061k 10.30k/s) Relation(3631140 26.50/s)
Standard exception processing relation id=5480194: TopologyException: side location conflict at 32619.389999999999 4904568.9699999997
Processing: Node(3038306k 51.6k/s) Way(309061k 10.30k/s) Relation(3668010 26.58/s) parse time: 226895s
Node stats: total(3038306927), max(3752289672) in 58875s
Way stats: total(309061030), max(371669320) in 30006s
Relation stats: total(3668018), max(5519092) in 138013s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Setting up table: planet_osm_nodes
Setting up table: planet_osm_ways
Setting up table: planet_osm_rels
Using built-in tag processing pipeline
Going over pending ways...
204865914 ways are pending
Using 1 helper-processes
Finished processing 204865914 ways in 78725 sec
204865914 Pending ways took 78725s at a rate of 2602.30/s
Committing transaction for planet_osm_point
Committing transaction for planet_osm_line
Committing transaction for planet_osm_polygon
Committing transaction for planet_osm_roads
Going over pending relations...
0 relations are pending
Using 1 helper-processes
Finished processing 0 relations in 0 sec
Committing transaction for planet_osm_point
WARNING: there is no transaction in progress
Committing transaction for planet_osm_line
WARNING: there is no transaction in progress
Committing transaction for planet_osm_polygon
WARNING: there is no transaction in progress
Committing transaction for planet_osm_roads
WARNING: there is no transaction in progress
Stopping table: planet_osm_nodes
Stopping table: planet_osm_ways
Building index on table: planet_osm_ways
Sorting data and creating indexes for planet_osm_point
Sorting data and creating indexes for planet_osm_line
Sorting data and creating indexes for planet_osm_polygon
Sorting data and creating indexes for planet_osm_roads
Stopped table: planet_osm_nodes in 0s
Stopping table: planet_osm_rels
Building index on table: planet_osm_rels
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat your command.
terminate called after throwing an instance of 'terminate called recursivelyEARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Ran the final tests anyhow just to see what happens.
http://192.168.1.25/osm_tiles/0/0/0.png
renderd[10697]: DEBUG: Got incoming connection, fd 8, number 1
renderd[10697]: DEBUG: Got incoming request with protocol version 2
renderd[10697]: DEBUG: Got command RenderPrio fd(8) xml(default), z(0), x(0), y(0), mime(image/png), options()
renderd[10697]: Received request for map layer 'default' which failed to load
renderd[10697]: DEBUG: Sending render cmd(4 default 0/0/0) with protocol version 2 to fd 8
renderd[10697]: DEBUG: Failed to read cmd on fd 8
renderd[10697]: DEBUG: Connection 0, fd 8 closed, now 0 left
http://192.168.1.25/osm_tiles/0/0/0.png
renderd[10697]: DEBUG: Got incoming connection, fd 8, number 1
renderd[10697]: DEBUG: Got incoming request with protocol version 2
renderd[10697]: DEBUG: Got command RenderPrio fd(8) xml(default), z(0), x(0), y(0), mime(image/png), options()
renderd[10697]: Received request for map layer 'default' which failed to load
renderd[10697]: DEBUG: Sending render cmd(4 default 0/0/0) with protocol version 2 to fd 8
renderd[10697]: DEBUG: Failed to read cmd on fd 8
renderd[10697]: DEBUG: Connection 0, fd 8 closed, now 0 left
No postgresql process crashed ever on my tile server.
Maybe disk writes were lost already installing software or initialising database.
Maybe disk writes were lost already installing software or initialising database.
But have you loaded the whole planet like I've been doing?
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Yes. with osm2pgsql script.
It can be slow, that is OK, but there should be no disk errors logged in dmesg, even less by postgresql.
Check with your SAN (disk box) Â vendor what settings they expect on linux client. Something is fatally wrong with your current storage setup.
It can be slow, that is OK, but there should be no disk errors logged in dmesg, even less by postgresql.
Check with your SAN (disk box) Â vendor what settings they expect on linux client. Something is fatally wrong with your current storage setup.
That same storage handles dozens of vmware vms, storage for various servers and backups. It never shows any sign of problems but of course, can never rule that out.
I'll install local drives and see what happens today.
I'll install local drives and see what happens today.
You can import to Windows 7 in first attempt, just to move blame from storage to linux.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Sure but that means having to build a external server instead of using blades I already have. Will have to look at what I have and see what can be tried next.
You can use your desktop PC. SATA disks at least dont choke receiving 2 requests.
But that doesn't solve why it's not working over otherwise fine hardware.
As I said, I'm going to try it on another server and see what happens. Building it now.
As I said, I'm going to try it on another server and see what happens. Building it now.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Hardware is not fine. Disk read and write errors are absolute doom. You cannot work around those.
I mean something is causing that problem because it's not showing up on anything else. Maybe it's the server I used, maybe it's the kernel settings, I don't know but I'm trying another machine to see if there is any difference.
Yes - read your storage vendor guides on Linux kernel settings...
You have disk requests taking more than 2 minutes as seen on hung_task_timeout_secs message.
You have disk requests taking more than 2 minutes as seen on hung_task_timeout_secs message.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Trying once more for a different server connected to that storage.
If that doesn't work, then I'll try direct SATA.
If that doesn't work, then I'll try direct SATA.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
I use FC because of how flexible it is. I've never seen this problem and run dozens of vms all over the FC network.
If this doesn't work, I'll be trying DAS for sure.
If this doesn't work, I'll be trying DAS for sure.
Why you need to complicate simple things. DAS TAS QAS - whatever
I bet your dektop PC has 200GB free disk space - just go ahead and import database.
I would make 100GB ram disk, but maybe you feel more attached to flexing optical fiber. (they are fragile btw)
I bet your dektop PC has 200GB free disk space - just go ahead and import database.
I would make 100GB ram disk, but maybe you feel more attached to flexing optical fiber. (they are fragile btw)
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Why did you bother posting all that above? Pretty useless commenting, not helpful, rude, etc.
We all have to work with what we have and in my case, most hardware doesn't have much local storage. Hence, using external storage.
We all have to work with what we have and in my case, most hardware doesn't have much local storage. Hence, using external storage.
I dont see other way to get you away from completely broken hardware setup.
If you get write errors on the hard drive - so you try to write it until you succeed or replace it ASAP?
If you get write errors on the hard drive - so you try to write it until you succeed or replace it ASAP?
It's not completely broken, I've said many times that there are no issues with all of the vms running over the FC network.
It's still running the final try over FC however and will take a couple more days as I've set it to be very slow and sure.
It's still running the final try over FC however and will take a couple more days as I've set it to be very slow and sure.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Not leaving FC alone, it's too big a part of the backbone but using local storage did the trick.
Did you contact FC vendors with this test case? They should fix it. Kind of local USB pen drive beats them in stability at 1/10000th of price.
I've not bothered because it would turn into a long situation which I don't have time for.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Unstable "backbone" is kind of serious problem... Take care some day.
I've said before, it is not unstable, it has simply not been optimized for this kind of traffic. It works perfectly handing dozens of VM's over several BladeCenter blades, nothing wrong with it. However, in this case, for some reason, it won't work out.
You are losing your data and smiling... Sorry for sarcasm.
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Not losing any data what so ever but in this case yes, FC doesn't work well for some reason.
Linux
--
Questions
--
Followers
Top Experts
Linux is a UNIX-like open source operating system with hundreds of distinct distributions, including: Fedora, openSUSE, Ubuntu, Debian, Slackware, Gentoo, CentOS, and Arch Linux. Linux is generally associated with web and database servers, but has become popular in many niche industries and applications.