next »

[webinfoguy25]

Hello I am having trouble getting awstats to work on one of my websites.  In that past I have used awstats via the control panel of my previous host.  Now I am using dreamhost and the directions aren't helping me install it.  Does anyone know an easier way for me to get this to install correctly?  I keep getting this error emailed to me for the cronjob that I have setup for awstats.
sh: 0: command not found


Thanks,

[webinfoguy25]

Nevermind I got it to work yippy skippy!

I just didn't edit the config file correctly, but now its showing up. 

[webinfoguy25]

Ok maybe I spoke too soon, cause now I am able to visit the awstats page in my browser but im getting cronjob emails with this error:

sh: 0: command not found

Anyone know how to fix this, or what it means?

Thanks,

[perkiset]

Well, congrats on getting the web portion of the package installed - looks like about 30-40 minutes. Nice.

Re. the cronjob, what command is being executed in your crontab that is causing this? Can you post it here? Essentially that means that cron is trying to execute something that (the user who executes the cron) does not have permission for or know where it is. It'd be like typing "yeahBaby" into a shell ... it'd have no idea what you were talking about (unless you had an executable in the path named "yeahBaby.")

[webinfoguy25]

0 3 * * * /usr/bin/perl /home/username/awstats/tools/awstats_buildstaticpages.pl -config=yourdomain.com -update -awstatsprog=/home/username/awstats/cgi-bin/awstats.pl -dir=/home/username/yourdomain.com/awstats/ >/dev/null

[perkiset]

/usr/bin/perl /home/username/awstats/tools/awstats_buildstaticpages.pl

That's the important part. See the part that says, "username" ? This probably means that you cut/pasted it from a website that was trying to tell you what to do, not exactly how to do it.

The inference there, is that /home/webinfoguy25/awstats/tools exists as a directory ... you need to modify the URL so that it points to the exact place where the awstats_buildstaticpages.pl script lives.

Additionally, you want to type "which perl" at the prompt, to make sure that perl is installed in the /usr/bin directory. That is *most likely* where it is, but there is no requirement that this is so. If you type "which perl" and the shell answers "/usr/bin/perl" then you're good to go. If it says something else, then the (something else) is what needs to be in that part of this command.

Hope that makes sense ...
/p

[webinfoguy25]

I changed that to username cause I didn't want to disclose what it was on a forum.  I am going to see if there is something else wrong with this cron job tommorow I am too tired to website.   

[perkiset]

LOL Gotcha, sorry if I was insulting. But the essence still stands - that command (the perl portion) and the first parameter (the script portion) are what need to be right. You can test this at any time by executing it right from the shell yourself, but kill the dev null part:

/usr/bin/perl /home/username/awstats/tools/awstats_buildstaticpages.pl -config=yourdomain.com -update -awstatsprog=/home/username/awstats/cgi-bin/awstats.pl -dir=/home/username/yourdomain.com/awstats/

... see how that complains. When you can get it to do the job from the shell, then put that successful command string into your cron job.