urchin broken on client side

Secret Agent · Nov 9, 2004

I installed Urchin on my server (integreated with cpanel). When viewing Urchin via client side (in cpanel's web/ftp stats area) I get this:

Unable to access configuration or direct linking is off

How do I fix this?

cpanel build: 9.9.8-CURRENT 88

I've searched the forums but every thread seemed too old for my cpanel version to even compare.

Secret Agent · Nov 10, 2004

Someone please help

Solokron · Jan 23, 2005

I am also having this issue. I have not found any resolutions to it.

mdweb · Feb 8, 2005

urchin

You need to go into the Urchin administration
servename.com:9999 (open port on your firewall).

Then go into the settings and turn direct linking on.

21chosting · Sep 15, 2005

Nope

In my experience, this does not work. I have tried several things now. I am running cPanel 10.6.0-CURRENT 214 and Urchin v5.7.03 and they simply do not work with each other!!!

All I get is :

"Unable to access configuration or direct linking is off "

I have (and I mean several times) set Direct Linking to ON and clicked update but still this does not work!!!

I have run /usr/local/urchin/util/inspector and the output is:

The webserver is configured to run as user nobody and group nobody

/usr/local/urchin/bin/admin: Urchin 5703 (redhat_ent3)
/usr/local/urchin/bin/auth: Urchin 5703 (redhat_ent3)
/usr/local/urchin/bin/rollup.cgi: Urchin 5703 (redhat_ent3)
/usr/local/urchin/bin/urchin: Urchin 5703 (redhat_ent3)
/usr/local/urchin/bin/urchin.cgi: Urchin 5703 (redhat_ent3)
/usr/local/urchin/bin/urchinctl: Urchin 5703 (redhat_ent3)
/usr/local/urchin/bin/urchind: Urchin 5703 (redhat_ent3)
-->Missing File: /usr/local/urchin/data/conf/uconf.log
/usr/local/urchin/htdocs/report.cgi: Urchin 5703 (redhat_ent3)
/usr/local/urchin/htdocs/session.cgi: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/geo-update: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/inspector: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/u3importer: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/uconf-driver: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/uconf-export: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/uconf-import: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/uconf-schedule: Urchin 5703 (redhat_ent3)
/usr/local/urchin/util/udb-sanitizer: Urchin 5703 (redhat_ent3)
-->/usr/local/urchin/var/urchinwebd.conf is not owned by the user nobody
-->/usr/local/urchin/var/urchinwebd.conf is not owned by the group nobody

My only assumptions are that:

-->Missing File: /usr/local/urchin/data/conf/uconf.log

This part of this message means a critical file is missing. Well failing everything else I thought I would raise a ticket at my host. Here is what I got:

Dear Customer,
The cPanel backend does all the urchin processing itself; it doesn't use the urchin daemon or scheduler at all (and in fact forcibly shuts them off). Urchin profiles are created automatically (in theory) for each domain by cpanellogd, and the logs are processed by the same script at the same time that the analyzer stats etc. are updated. The actual data for each site is stored separately per-domain (normally under /home/domainname/tmp/urchin), not in the global urchin location (normally under /usr/local/urchin). The urchin stats link available for each site via the cPanel interface uses the per-site data (under /home/domainname/tmp/urchin), not the data stored under the global urchin directory.

So there are basically two ways to use urchin with cpanel:

1. Install urchin and run the urchin daemon (usually on port 9999) and scheduler; set up profiles for the domains you care about manually using the urchin administration interface, and schedule periodic updates via the urchin scheduler --- users can log into the urchin interface on port 9999 and view their stats that way, but not via the link in their cPanel interface: that link will point to the per-domain urchin data created by cPanel and show zeroes (at best) or errors (at worst) for the domain. You'll also have to live with cpanellogd shutting down your urchin daemons every time it processes the logs; alternatively you can hack cpanellogd to have it skip urchin processing or install a monitoring script to restart the urchin daemons as required. Obviously this approach is not the one intended by cpanel.

2. Use the cPanel urchin integration. Shut off the urchin daemons and remove them from your startup scripts so they won't get started. Let cPanel process urchin data and store it per-domain, for each domain on your site. Users can see their urchin stats via the urchin link in their cPanel interface.

I suspect that most people would opt for #2 if it actually worked. Unfortunately it really doesn't, for the following reasons:

1. There's a bug in cpanellogd (not sure if it's corrected as of 9.1.0-C118) that prevents the profiles from getting created automatically for each domain, leading to errors of the " unable to find profile" variety when users click on the urchin stats link. That problem can be worked around -- simply create the profiles manually in the urchin interface, or via /usr/local/urchin/util/uconf-driver. Profiles must be named the same as the domain, without the leading www, e.g. mydomain.com, and log file sources must be labelled the same way, i.e. mydomain.com.

2. Urchin can't actually read the log files in a default cPanel installation -- log files are by default 640 permission and need to be 644 for urchin to read them. Change that in your cPanel settings if you need to. If you don't, no urchin data will be generated for any of the profiles. Manually chmoding the log file permissions won't work -- cpanel will just change it back to 640 (or whatever you've got it set to).

3. To use cpanel's Urchin integration, direct-linking must be enabled in Urchin. It's not clear whether cPanel's setting this flag in the urchin database -- it's supposed to, but if you're experiencing problem #1 you may be experiencing this problem as well. Solution: enable direct-linking from the urchin admin interface (or uconf-driver) if necessary.

3. Assuming you fix problems #1, #2 and #3, Urchin itself seems to have an error creating backup data when run from the per-domain locations set up by cPanel. The same error doesn't exist if you run it from the global urchin location. You can see this yourself as follows:

cd /usr/local/urchin
bin/urchin -p mydomain.com

That should process the logs for the profile called " mydomain.com" , in the global urchin data location (which is actually unusable by cpanel). Then for the sake of comparison try this:

cd /home/mydomain/tmp/urchin
bin/urchin -p mydomain.com

That does the same thing, only storing the urchin data under /home/mydomain/tmp/urchin, and it results in errors of the " unable to create backup" variety. In Urchin 5.1 the error is fatal -- the data remains " locked" for that profile and when the logs are next processed for that profile Urchin attempts an auto-rollback (which also fails, actually). In Urchin 5.5 the error still occurs but it's not fatal; you'll get no backups or rollback capability but you should at least be able to see the data that was generated. Solution: upgrade to Urchin 5.5, or keep 5.1 but edit each profile manually to turn off the backup and auto-rollback functions.

Long story short, urchin and cpanel don't really play very well together at this time... mostly because cpanel's doing a bunch of things that don't quite work, and partly because of an issue in urchin 5.1. You can work around the problems using the info above if you're industrious or bored and you really, really must have urchin stats available from cpanel, or if you can live with running the urchin daemons yourself and screwing the cpanel integration. But people running the urchin daemons themselves should at least be aware that they're not operating in the way cpanel's designed to. I suspect (from reading various forums) that a lot of people are trying to get things to work by running the urchin daemons themselves, processing the logs manually or via the urchin scheduler and storing the resulting data in the global urchin location, and then seeing zeroes when they try to view urchin stats in cpanel (because the right profile exists but the data can't be found in /home/domain/tmp/urchin/data). If I hadn't already spent a bit of time this weekend getting things to work I wouldn't advise exerting a lot of effort here -- just wait for cPanel to fix the broken urchin integration or better yet use a different stats/reporting package (one that isn't so heavyweight and slow).
Click to expand...

So now what? Do I give in and stick to AWStats or do I keep battling??? Come on cPanel, get together with Urchin and make this work!

If anyone has any clues, please let me know!!

Thanks
Liam

payne · Sep 28, 2005

You can install Urchin in a non-standard named directory and cpanellogd will not turn it off every night. For example, I installed urchin in /usr/local/urchin-nocpanel and it works beautifully. I manually create profiles for big customers and give them their own logins outside of their cpanel. Not the perfect world, but it has been SOOOOOOO much easier to manage than the cpanel-integrated way.

vikas_adhangale · Nov 3, 2005

One more problem about Urchin stats

Hello,

If you are getting "Direct Linking is disabled to this application" error , then you will have to make sure that you are using proper cpanel version, probably RELEASE version using
#cat /usr/local/cpanel/version . If it's not updated Cpanel version then it may flash the errors. Please make sure to change the Cpanel versio and then run upcp /scripts/upcp --force
Get Urchin stats working....... Enjoy... :D

Thank you
Vikas A.
http://eTechsupport.net

Forums

The Community Forums

Interact with an entire community of cPanel & WHM users!

urchin broken on client side

Secret Agent Guest

Secret Agent Guest

Solokron Well-Known Member

mdweb Member
PartnerNOC

21chosting Registered

payne Well-Known Member

vikas_adhangale Member

Very broken iptables 1.4.21 after upgrade to kernel 3.10.0-514.26.2.el7.x86_64

SOLVED Account suspension is broken in cPanel 66

Yet Another RVskin is Broken Thread

yum check-updates seems broken

Broken site due to failed redirect

Share This Page

Useful Searches

The Community Forums

Interact with an entire community of cPanel & WHM users!

urchin broken on client side

Secret Agent Guest

Secret Agent Guest

Solokron Well-Known Member

mdweb Member PartnerNOC

21chosting Registered

payne Well-Known Member

vikas_adhangale Member

Very broken iptables 1.4.21 after upgrade to kernel 3.10.0-514.26.2.el7.x86_64

SOLVED Account suspension is broken in cPanel 66

Yet Another RVskin is Broken Thread

yum check-updates seems broken

Broken site due to failed redirect

Share This Page

mdweb Member
PartnerNOC