[Skatiechik]

I copied all the files to the right directory, then edited the conf file for domain, where the data files are to be stored (including uploading the old ones), etc.

Then I used the following location for the log files (also making sure permissions was set to 777)

/home/useraccount/access-logs/domainnamelog

When I go to

www. domain. co.uk/cgi-bin/awstats.pl (or www.domain.co.uk.cgi-bin/awstats.pl?config=model as in the userguide) I just get a 505 error.

[Kieran]

Ah, I think I see what is going on here. I've just had to resolve a problem just like this for a stats research project I'm doing on one of my sites.

Does /home/user/access-logs/ actually exist? As in when logged in using normal FTP can you browse this directory?

My recent experience seems to indicate you can't. It would seem that /home/useraccount/access-logs/domainnamelog doesn't actually exists any more in the CPanel setup, perhaps a recent upgrade or something else. Now the only way to get at the raw logs (which is what you need) is by using a separate FTP account (see the configure ftp page for the account I'm on about).

Clearly this will not work with your script but what I've done is setup a cron job to periodically pull the file I want from the ftp and dump it in a directory in my home area, so for instance I end up with /home/user/rawlogs/domain.com

You can then use this path in whatever script you want to use.

Given you are using awstats you would also need to configure a cron for awstats to update in this case as well, unless I am mistaken. Also try and make sure that this runs a few minutes after the ftp one so that you don't get empty files or any nasties like that.

Please also note that you should disable the option to allow viewers to manually update the stats. If you let people do this then server loads can get high and your account will be suspended.

Hope this helps anyway

[Skatiechik]

Hi,

I thought similiar along the same lines last night, hence doublechecking and doublechecking the location of the raw access logs. When I log in just using filezilla and the ftp username sent to me via email (the one where you can see everything on the account from top level down, rather than any I have set up) they are there. Although not viewable via the web as you can only see the public-html files via the ipaddress.

The instructions do say I need to set up a cron job for the awstats to update. I hadn't got the far yet was just trying to get it so I can visually see it first. From memory the update is disabled as I took a gander at the conf settings that were on the old h-sphere account and tried to match them (theory being what was right for the h-sphere awstats should also be right for me).

[Kieran]

I assume that things like the path to perl are correctly setup and all that jazz? These things are not always as simple as they seem.

It also seems that you can access the logs directly, which helps. You might want to experiment by making a copy in your home directory and using these to make sure; I'm convinced that even if you can see them under access-logs they still might not be there if you access via a script.

[Skatiechik]

I assumed they were, but perhaps the files locations are wrong. I am having another go at it tonight changing the file locations around in the configuration file.

[Dom]

Morning all,

I thought I'd jump in on this converstation as I'm transferring from Golf to Indigo as well.

A few of my questions have been answered in this thread, so thanks for that, although I do have a couple more.

1. When uploading websites with an FTP client, do you upload your files to the 'public_html' directory, or the 'www' directory, because I uploaded mine to the 'www' directory but I'm not sure I should have.

2. Where do you upload your primary domain files to? For each add-on domain, a separate folder is created and you can upload your files for those sites to their own folder, but the primary domain doesn't seem to have it's own directory. I don't really want to upload them directly into the root; I'd much rather it have it's own directory as well, just to keep things organised.

I asked in my support ticket, but the Xilo guys seem to have dropped off the face of the Earth! :P

Thanks all.

[Kieran]

Originally Posted by Dom

1. When uploading websites with an FTP client, do you upload your files to the 'public_html' directory, or the 'www' directory, because I uploaded mine to the 'www' directory but I'm not sure I should have.

The 'www' directory isn't in fact a directory its a symlink to public_html. In other words, public_html is the right place to upload website files to BUT uploading them to www will actually result in them being put in public_html. Try it

Originally Posted by Dom

2. Where do you upload your primary domain files to? For each add-on domain, a separate folder is created and you can upload your files for those sites to their own folder, but the primary domain doesn't seem to have it's own directory. I don't really want to upload them directly into the root; I'd much rather it have it's own directory as well, just to keep things organised.

The primary domain is points to the files and directories placed in public_html. Sub directories in here can either be subdirectories of your main domain like domain.com/directory or they can be assigned to sub-domains or add-on domains. Indeed even if a directory is assigned to a subdomain it can still be accessed using domain.com/sub-domain-directory. It can be confusing but this is the way it is - it can't be changed.

I guess if you were really intent on having the main domain in a subdirectory you could do some trickery with mod_rewrite so the only file you had in the root was a .htaccess file but it hardly seems worth it to me; you'd need a fair few lines of rewrite rules.

[Dom]

OK thanks for the info. I did notice that my files appeared in both the 'www' and 'public_html' directories actually. :P

So as far as my primary domain goes, I still need to upload the files straight into the root of 'public_html', unless I want to try some jiggery pokery with mod_rewrite and .htaccess files.

Going on what you've written, am I right in thinking that if I've got another domain (separate from my primary domain, such as www.another-domain.com) and I've got a directory inside 'public_html' called 'www.another-domian.com' that my files are uploaded to, that a user could get to the 2nd domain through the first? For example, by typing:

www.primary-domain.com/www.another-domain.com

into the address bar? That seems a bit, well, poo really. In my case, they're totally separate domains and I wouldn't really want them to access one website by going through another...

:s

[Kieran]

Originally Posted by Dom

OK thanks for the info. I did notice that my files appeared in both the 'www' and 'public_html' directories actually. :P

Good, good

Originally Posted by Dom

So as far as my primary domain goes, I still need to upload the files straight into the root of 'public_html', unless I want to try some jiggery pokery with mod_rewrite and .htaccess files.

Correct

Originally Posted by Dom

Going on what you've written, am I right in thinking that if I've got another domain (separate from my primary domain, such as www.another-domain.com) and I've got a directory inside 'public_html' called 'www.another-domian.com' that my files are uploaded to, that a user could get to the 2nd domain through the first? For example, by typing:

www.primary-domain.com/www.another-domain.com

into the address bar?

Yes, that is true

Originally Posted by Dom

That seems a bit, well, poo really. In my case, they're totally separate domains and I wouldn't really want them to access one website by going through another...

This is possible with, yes, you've guessed it, mod_rewrite rules. With the right rules you can keep the same directory structure but make the domains completely seperate. I'll cite examples if you need them.

[Matt]

Originally Posted by Dom

Going on what you've written, am I right in thinking that if I've got another domain (separate from my primary domain, such as www.another-domain.com) and I've got a directory inside 'public_html' called 'www.another-domian.com' that my files are uploaded to, that a user could get to the 2nd domain through the first? For example, by typing:

www.primary-domain.com/www.another-domain.com

into the address bar?

Not exactly. When adding the add-on domain - the path is auto filled. You CAN remove public_html and just set a folder name which will mean that you wont be able to access it from your master domain as you have posted.

Matt