[mapserver-users] MapCache - failed to remove lockfile error
Stephen Woodbridge
woodbri at swoodbridge.com
Thu Oct 6 11:19:13 PDT 2011
Have you verified that you have not filled up the disk or run out of inodes?
# check the diskspace with
df -h
# check for inode issues
touch /path/to/cache/test.junk
# if the touch failed then you have run out of inodes
# otherwise clean up
rm /path/to/cache/test.junk
Thanks,
-Steve W
On 10/6/2011 12:14 PM, thomas bonfort wrote:
> I don't have a specific advice to give unfortunately. There have been
> some fixes lately (macpcache only, not mod-geocache) to the way
> multiple threads accessed the curl library that might help, so you
> might want to try with a fresh checkout from the mapserver svn.
>
> --
> thomas
>
> On Thu, Oct 6, 2011 at 18:08, Travis Kirstine<traviskirstine at gmail.com> wrote:
>> Thomas,
>>
>> My command is below, I'm using a disk cache, my config file is below.
>> I'm using a local copy of MapServer for the source image generation
>>
>>
>> ./geocache_seed -c ../geocache.xml -t ms_tileset_8 -z 0,21 -e
>> -8895580.772,5411569.158,-8797157.196,5538966.276 -n 6
>>
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <geocache>
>>
>> <metadata>
>> <title>geocache service esx11</title>
>> <abstract>mod-geocache service</abstract>
>> <!-- url>http://mysuperhost/proxy/to/geocache</url -->
>> </metadata>
>>
>> <grid name="googlemaps_grid">
>> <metadata>
>> <title>GoogleMapsCompatible</title>
>> <WellKnownScaleSet>urn:ogc:def:wkss:OGC:1.0:GoogleMapsCompatible</WellKnownScaleSet>
>> </metadata>
>> <extent>-20037508.3427892480 -20037508.3427892480
>> 20037508.3427892480 20037508.3427892480</extent>
>> <srs>EPSG:3857</srs>
>> <srsalias>EPSG:900913</srsalias>
>> <units>m</units>
>> <size>256 256</size>
>> <resolutions>156543.0339280410 78271.51696402048
>> 39135.75848201023 19567.87924100512 9783.939620502561
>> 4891.969810251280 2445.984905125640 1222.992452562820
>> 611.4962262814100 305.7481131407048 152.8740565703525
>> 76.43702828517624 38.21851414258813 19.10925707129406
>> 9.554628535647032 4.777314267823516 2.388657133911758
>> 1.194328566955879 0.5971642834779395 0.29858214173896975
>> 0.149291070869484875 0.0746455354347424375</resolutions>
>> </grid>
>>
>> <cache name="disk" type="disk">
>> <base>/var/mod-geocache/caches</base>
>> <symlink_blank/>
>> </cache>
>>
>> <format name="PNGQ_FAST" type ="PNG">
>> <compression>fast</compression> <!-- fast or best -->
>> <colors>256</colors>
>> </format>
>> <format name="myjpeg" type ="JPEG">
>> <quality>75</quality>
>> </format>
>> <format name="PNG_BEST" type ="PNG">
>> <compression>best</compression>
>> </format>
>> <format name="mixed" type="MIXED">
>> <transparent>PNG_BEST</transparent>
>> <opaque>JPEG</opaque>
>> </format>
>>
>> <source name="ms_wms" type="wms">
>> <getmap>
>> <params>
>> <FORMAT>image/png</FORMAT>
>> <LAYERS>YORK2009</LAYERS>
>> <TRANSPARENT>true</TRANSPARENT>
>> </params>
>> </getmap>
>> <http>
>> <url>http://localhost.jdbarnes.com/cgi-bin/ms_wms</url>
>> </http>
>> </source>
>>
>> <tileset name="ms_tileset_8">
>> <source>ms_wms</source>
>> <cache>disk</cache>
>> <!--grid restricted_extent="-79.8205259 43.7179074 -79.1161194
>> 44.4110187">WGS84</grid-->
>> <grid>googlemaps_grid</grid>
>> <format>mixed</format>
>> <metatile>8 8</metatile>
>> <metabuffer>0</metabuffer>
>> </tileset>
>>
>> <default_format>JPEG</default_format>
>>
>> <service type="wmts" enabled="true"/>
>> <service type="tms" enabled="true"/>
>> <service type="kml" enabled="true"/>
>> <service type="gmaps" enabled="true"/>
>> <service type="ve" enabled="true"/>
>> <service type="demo" enabled="true"/>
>>
>> <errors>report</errors>
>>
>> <lock_dir>/var/mod-geocache/caches</lock_dir>
>>
>> </geocache>
>>
>> On 6 October 2011 10:31, thomas bonfort<thomas.bonfort at gmail.com> wrote:
>>> what seed command were you using, and what kind of cache ?
>>>
>>> On Thu, Oct 6, 2011 at 15:52, Travis Kirstine<traviskirstine at gmail.com> wrote:
>>>> Thanks Thomas,
>>>>
>>>> The complete error message is below. Do you have any idea what would
>>>> cause this error - why would mapcache fail to create or delete the
>>>> lockfile.
>>>>
>>>>
>>>>
>>>> seeding tile 583296 1337304 21failed to remove lockfile
>>>> /var/mod-geocache/cachesseeding tile 583304 1337296 21failed to remove
>>>> lockfile /var/mod-geocache/caches/_gc_lock-21-167156-72919-ms_tileset_8:
>>>> No such file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-21-167157-72919-ms_tileset_8: No
>>>> such file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-20-83579-36459-ms_tileset_8: No such
>>>> file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-21-167156-72918-ms_tileset_8: No
>>>> such file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-21-167159-72918-ms_tileset_8: No
>>>> such file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-21-167158-72918-ms_tileset_8: No
>>>> such file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-21-167159-72919-ms_tileset_8: No
>>>> such file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-18-20895-9114-ms_tileset_8: No such
>>>> file or directoryfailed to remove lockfile
>>>> /var/mod-geocache/caches/_gc_lock-21-167158-72919-ms_tileset_8: No
>>>> such file or directory
>>>>
>>>>
>>>> Regards
>>>>
>>>>
>>>> On 6 October 2011 09:11, thomas bonfort<thomas.bonfort at gmail.com> wrote:
>>>>> The log message should be more explicit, and contain the reason of the
>>>>> unsuccessful removal. In any case, looking at the code, this error
>>>>> will have interrupted the seeding process.
>>>>>
>>>>> regards,
>>>>> thomas
>>>>>
>>>>> On Thu, Oct 6, 2011 at 15:03, Travis Kirstine<traviskirstine at gmail.com> wrote:
>>>>>> Hi All,
>>>>>> I hope this is the right spot to post MapCache questions. I had
>>>>>> seeded a large area and receive the error "failed to remove lockfile".
>>>>>> It appears that this error(s) happens at the end of the seeding but
>>>>>> it is hard tell as the process has been running for a few days. Does
>>>>>> this error kill the seeder process or is it simply a warning?
>>>>>>
>>>>>> Regards
>>>>>> _______________________________________________
>>>>>> mapserver-users mailing list
>>>>>> mapserver-users at lists.osgeo.org
>>>>>> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>>>>>>
>>>>>
>>>>
>>>
>>
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
More information about the MapServer-users
mailing list