Failed to open data_base to read

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install software
2. Start Up
3. Select a website to update
4. Go to Site Configuration
5. Enter Host Name
6. Enter Pathname for log file(s)
7. Save Settings
8. Look at log file
9. cd /usr/local/google-sitemap-generator/log/
10. tail google-sitemap-generator.log

What is the expected output? What do you see instead?
I expected to see it running with no errors.

Instead I saw these errors in the log and after waiting 24 hours got a
Failed message in the admin:
2009-06-16T16:30:09Z: Save memory data for
[www.mywebsite.com,xxx.xxx.x.xxx:443] successfully.
2009-06-16T16:31:02Z: Next service scheduling time in [547]S.
2009-06-16T16:31:02Z: Start to generate [Web Sitemap] for site
[www.mywebsite.com,xxx.xxx.x.xxx:443].
2009-06-16T16:31:02Z: No new record to update news data.
2009-06-16T16:31:02Z: Failed to open
[/usr/local/google-sitemap-generator/cache//www_mywebsite_com_192_168_1_65_443/d
ata_base]
to read.
2009-06-16T16:31:02Z: www.mywebsite.com,xxx.xxx.x.xxx:443: record can't be
merged.
2009-06-16T16:31:02Z: Failed to update database.
2009-06-16T16:31:02Z: Failed to generate [Web Sitemap] for site
[www.mywebsite.com,xxx.xxx.x.xxx:443].

What version of the product are you using? On what operating system?
sitemap_linux-i386-beta1-20090225.tar.gz
Redhat 3.0ES
Apache 2.0.46

Please provide any additional information below.
I tried this on 2 different servers running the same OS and webserver and
obtained the same results.

Thanks

Original issue reported on code.google.com by cvazquez...@gmail.com on 16 Jun 2009 at 4:43

[GoogleCodeExporter]

Same problem - has anyone found a fix to this?

Original comment by dotsp...@gmail.com on 13 Nov 2009 at 8:20

[GoogleCodeExporter]

same problem here, sadly.

Original comment by dennen_b...@gtempaccount.com on 27 Jul 2010 at 6:31

[GoogleCodeExporter]

Same here too, as the original post is quite old did anybody found a 
solution/workaround?

Original comment by Stephane...@gmail.com on 11 Nov 2010 at 11:48

[GoogleCodeExporter]

maybe I have a workaround - in my case (Ubuntu) the apache webroot resides in 
/var/www/ - but the sitemap generator looks always after /htdocs - i don't know 
maybe it is possible to change this.

in my case I've made a symlink  for /htdocs -> /var/www/

on the next scan the missing data_base file has been created

Original comment by bause...@gmail.com on 12 Nov 2010 at 1:54

[GoogleCodeExporter]

Hey Guys,

This error is due to the Generator trying to create sitemaps for the SSL 
version of the site, that's why port 443 is showed. For sure you will have 2 
options in the manager for the same site, you need to select the other one and 
it will solve the issue.

Regards.

Original comment by netb...@gmail.com on 24 Apr 2011 at 3:04

[GoogleCodeExporter]

Hi Guys,
I am getting the same error Failed to open 
[/usr/local/google-sitemap-generator/cache/ 
on Google Sitemap generator whenever it executes.
I am using Ubuntu 10.10 version OS and Apache 2.2

I've made a symlink  for /htdocs -> /var/www/ but it is not working.

Please help me out

Original comment by mohit.ku...@dbydx.com on 23 Aug 2011 at 6:04

[GoogleCodeExporter]

I have to admit this project looked promising in the beginning, but the 
community support around it looks to have severely faded.  I am having this 
same issue and as I can see no one has found an answer to it yet.  The 
community support needs to be better around this or else this thing is not 
going to be around.  I'm hoping more support comes along, because I'd like to 
use this, but as of now I'm not very confident.

Original comment by mobilejo...@gmail.com on 4 Nov 2011 at 9:57

[GoogleCodeExporter]

Same errors with port 80 and yes looks like project is not being 
maintained/supported actively :

Start to generate [Web Sitemap] for site [XYZ.co.uk,192.168.0.X:80].
No new record to update news data.
Failed to open 
[/usr/local/google-sitemap-generator/cache//XYZ_co_uk_192_168_0_X_80/data_base] 
to read.
XYZ.co.uk,192.168.0.X:80: record can't be merged.
Failed to update database.
Failed to generate [Web Sitemap] for site [XYZ.co.uk,192.168.0.X:80].

Original comment by rizwan.z...@gmail.com on 11 Nov 2011 at 1:06

[GoogleCodeExporter]

I have been searching and searching the Internet for a solution to this double 
slash issue. I searched the generator files to try and find a point to edit and 
I can't find anything. How can this continue to be an issue for so long?

Original comment by ja...@hgmail.com on 22 May 2012 at 4:04

[GoogleCodeExporter]

Yeah, this is sad.

Is it only with servers using /var/www rather than htdocs?

Original comment by footsys...@gmail.com on 3 Jun 2012 at 1:00

[GoogleCodeExporter]

there is really NO EXCUSE for this type of pathing error. and worse, there is 
no excuse not to fix it. this "/" pathing issue has been around for a couple 
decades and is always progammer managed on at least a char check on last 
position. the protocol is to always leave the proceeding path with an ending 
slash and to concantenate with a filename or continuing path without preceding 
with a slash.

do you think we can get a STATE OF CONDITION page? the best solution is of 
course a settings file where you can re-specify pathing with and without 
slashes. but of course that common practice has been around so long that 
perhaps it just gets stale and allows new programmers to make the same errors 
as the old pros did when they first started. 

in any event, i didnt find a conf file with pathing and a symlink without a 
trailing slash didnt workaround. so if we cant get the source and this sits 
around another 10 years, we will have some entertainment for generations to 
come.

Original comment by globalin...@gmail.com on 29 Aug 2012 at 12:39

[GoogleCodeExporter]

I have download the source from SVN and found the file containing the cache/ 
path error. It's on line 58 of /src/sitemapservice/recordfilemanager.cc
home.append("/cache/"); 
where it should be 
home.append("/cache");

Unfortunately I cannot re-compile it myself. 

Can anyone else assist pls?

The other problem with hardcoded htdocs path should be able to workaround with 
symlink as above.

Cheers

Original comment by dave.bla...@gmail.com on 12 Apr 2013 at 9:24

[GoogleCodeExporter]

apacheconfig.cc shows it just loads htdocs because the path is empty

// set default values for mainserver
  if (mainserver_.servername.length() == 0) {
    mainserver_.servername = GetLocalHost();
  }
  if (mainserver_.documentroot.length() == 0) {
    mainserver_.documentroot = "/htdocs";
  }
  mainserver_.address = ":*";

when using install.sh set the -c path/to/configuration-file.conf

You can set a conifguration-file.conf containing all paths to you various 
configuration files such as 

Include '/var/www/mysite1/etc/httpd.conf'
Include '/var/www/mysite2/etc/httpd.conf'
Include '/var/www/mysite3/etc/httpd.conf'

and so on. It seems quite poorly documented but this works for me. No fix on 
why :443 does not work.

Original comment by joris.la...@gmail.com on 26 Apr 2013 at 1:09

[GoogleCodeExporter]

has there been any movement/resolution on this issue?

Original comment by barry.ch...@gmail.com on 28 Dec 2013 at 6:09