Help - Search - Members - Calendar
Full Version: Urchin for RHEL4?
The Planet Forums > Control Panels > Urchin
acidbox
Does anyone know if the RHEL3 version of Urchin works on RHEL4? I'd like to install Urchin 5 on an EL4 box, but I'm not sure if it is compatible.

Thanks.
aussie
I dont see why it wouldn't.
acidbox
Well I ended up installing it and it appears to work normally, so for anyone else, it does work on RHEL4.
coaster1
I'm seeing an issue on EL4.

I downloaded the El3 script and tried the normal extract procedures:

CODE
[root@srv01 admin]# sh urchin5702_redhat_ent3_13652_en.sh

x - creating lock directory

x - extracting install.sh (binary)

urchin5702_redhat_ent3_13652_en.sh: line 66: uudecode: command not found

restore of install.sh failed

install.sh: MD5 check failed

x - extracting install.txt (text)

x - extracting license.txt (text)

x - extracting README (text)

x - extracting inspector (binary)

urchin5702_redhat_ent3_13652_en.sh: line 1619: uudecode: command not found

restore of inspector failed

inspector: MD5 check failed

x - extracting gunzip (binary)

urchin5702_redhat_ent3_13652_en.sh: line 12649: uudecode: command not found

restore of gunzip failed

gunzip: MD5 check failed

x - extracting urchin.tar.gz (binary)

urchin5702_redhat_ent3_13652_en.sh: line 13867: uudecode: command not found

restore of urchin.tar.gz failed

urchin.tar.gz: MD5 check failed

[root@srv01 admin]# ls -l

total 26060

-rw-r--r-- 1 root root 5894 Mar 1 14:47 install.txt

-rw-r--r-- 1 root root 10476 Mar 1 14:47 license.txt

-rw-r--r-- 1 root root 1792 Mar 1 14:47 README

-rw-r--r-- 1 root root 26625743 Mar 1 14:47 urchin5702_redhat_ent3_13652_en.sh

[root@srv01 admin]#


Any ideas?
Penguin
Try getting the later release of Urchin which is urchin5703_redhat_ent3.tar.gz - I've built this on RHEL4 servers with no apparent issues
kwitko
I was getting that error, and I found the latest version here and it worked.
http://urchinexperts.com/software/trial/

Regards
Andrew
clanscc
Hm, when I try to install urchin on RHEL4 I get:

./install.sh: line 1278: 3098 Segmentation fault "$INSTALLDIR/util/inspector" -R
r3dh4t
up2date -i sharutils
clanscc
That has been already installed previously and still gives that error.
CyberSEAL
clanscc, did you ever get Urchin installed properly? I'm running into the same error.
clanscc
Ah, no. Could never figure out a solution for it to work yet..
CyberSEAL
Hmm, not good. I requested support from Urchin/Google and they referred me back to Ev1. I'll guess we'll see if they can help, I have a ticket in.
alinteractive
I was getting the same errors as coaster1. I ran up2date (sharutils) as suggested by r3dh4t, then ran the script again and all worked fine. I'm on RHEL4 as well.
da644
Hi all.

I managed to install Urchin on RHEL4 without any issues at all, but when I configured a site it will only pick up visitors if configured for IP/User Agent tracking and not UTM. I have check and double checked the UTM configuration stuff and it is all configured the same as a RHEL3 box we have which works perfectly, anyone else come across this problem?

Kind regards,

Andrew.
clanscc
I finally got Urchin working for RHEL4. icon_smile.gif
Catalyst
Something to keep in mind, if you use the HOWTO elsewhere in the forum, is that Ensim Pro X uses Port 8080 (for reasons useless, but hey)...
foxintampa
Problems with Urchin on Ensim Pro 4.1.0-8.rhel.4ES new server install, getting error durning install. I was able to login to 9999 after install and register the licence, set up a log source and profile. It says: Warning! Task scheduler disabled when I run reports, cant get rid of it. Here are the install details and errors. Any help appreciated!

CODE
[root@secure ~]# ./install.sh

Choose Language: [Default: 1]

  1. English

  2. Japanese / ÆüËܸì

  3. Spanish / Español

-> 1

------------------------------------------------------------------------

-- Welcome to the Urchin Installation and Upgrade Utility

-- Version 5.703

------------------------------------------------------------------------



Please read the install.txt file before continuing.  Urchin installs and

uses a lightweight Apache webserver for web-based administration and

report delivery.  The installer may ask for the following information

during installation:

  1. A port number for the Urchin webserver.  Port numbers below 1024

  require superuser privileges.

  2. A valid user and group for ownership and operation.



Please select the installation type [Default: 1]

  1. New

  2. Upgrade

-> 1



Specify the installation directory [Default: /usr/local/urchin]:

-> /usr/local/urchin



The specified directory does not exist: /usr/local/urchin



Do you want the script to create it? [Default: 1]

  1. Yes

  2. No

-> 1



Choose a port number for the webserver [Default: 9999]

-> 9999



Choose a user for the webserver and file ownership [Default: nobody]

-> nobody



Choose a group for the webserver and file ownership [Default: nobody]

-> nobody



Would you like the installer to start the Urchin webserver and scheduler

at the end of the installation? [Default: 1]

  1. Yes

  2. No

-> 1



------------------------------------------------------------------------

-- Summary Information

-- Installing Urchin 5.703

------------------------------------------------------------------------



Installation Directory: /usr/local/urchin

Webserver Port: 9999

Webserver User: nobody

Webserver Group: nobody

Start Webserver and Scheduler: Yes



Please select continue or exit [Default: 1]

  1. Continue

  2. Exit

-> 1



Installing Urchin



Creating webserver configuration



Initializing the configuration databases



Importing default configuration

removed 0 records.

added 11 records.

edited 11 records.



Setting file ownership and permission

./install.sh: line 1278:  6661 Segmentation fault      "$INSTALLDIR/util/inspect                        or" -R



## Error: Problems changing permissions on the distribution files



Starting the Urchin webserver and scheduler daemon

Urchin webserver started on port 9999

Urchin scheduler started



------------------------------------------------------------------------

-- Installation Complete

------------------------------------------------------------------------



The Urchin administrative interface should be ready to use at



  [url="http://secure.xxxx.com:9999/"]http://secure.xxxx.com:9999/[/url]
Penguin
QUOTE
It says: Warning! Task scheduler disabled when I run reports, cant get rid of it


It's because urchin is owned by the user 'nobody' and you're running it as root. The process must be owned by nobody instead or the task scheduler will not run correctly
foxintampa
Ok, I got it. Thanks.

chown -R admin:admin /usr/local/urchin
changed nobody to admin in the following files :
/usr/local/urchin/var/urchinwebd.conf.template
/usr/local/urchin/var/urchinwebd.conf.template

and logged in under admin and bin/urchinctl start
acider
QUOTE (foxintampa @ Oct 14 2006, 10:08 PM) *
Ok, I got it. Thanks.
chown -R admin:admin /usr/local/urchin
changed nobody to admin in the following files :
/usr/local/urchin/var/urchinwebd.conf.template
/usr/local/urchin/var/urchinwebd.conf.template
and logged in under admin and bin/urchinctl start


i installed urchin using admin user and admin group instead, still i faced a similar situation of a task schedule warning message.

what should i do?
marauder
That did it for me as well...

Thanks you are awesome my friend! Next step... migrate my old servers urchin crap on over...

QUOTE (foxintampa @ Oct 14 2006, 10:08 PM) *
Ok, I got it. Thanks.
chown -R admin:admin /usr/local/urchin
changed nobody to admin in the following files :
/usr/local/urchin/var/urchinwebd.conf.template
/usr/local/urchin/var/urchinwebd.conf.template
and logged in under admin and bin/urchinctl start


Quick update now I cant login to urchin... so I started by resetting the password- but then noticed that the error i'm gettign when attempting a login is:
"Authentication Error - can't grab global config from db. (6006) Please log-in again"

So then to check things out I attempted to ruin teh inspector and got this:

# ./inspector -r
Urchin Inspector: Urchin 5.7.03

Server Information
--------------------------------------------------
Operating System: Linux
Network Name: our third server hostname
OS Release: 2.6.9-42.ELsmp
OS Version: #1 SMP Wed Jul 12 23:27:17 EDT 2006
Machine: i686
--------------------------------------------------

Verifying Files and Directories
--------------------------------------------------
Segmentation fault

Any ideas?? Thanks
marauder
OK I reinstalled everything from scratch with using admin as user/ group and the server starts up and reports everything as just fine... however urchin scheduler is disabled. "Warning! Task scheduler disabled" seen when i try and run a profile manually. I also checked to see what user urchin is being run as and got this:

ps aux | grep urchin
root 21534 0.0 0.0 3364 1468 ? Ss 20:04 0:00 /usr/local/urchin/bin/urchinwebd -f /usr/local/urchin/var/urchinwebd.conf
admin 21535 0.0 0.0 3364 872 ? S 20:04 0:00 /usr/local/urchin/bin/urchinwebd -f /usr/local/urchin/var/urchinwebd.conf
admin 21536 0.0 0.0 3364 872 ? S 20:04 0:00 /usr/local/urchin/bin/urchinwebd -f /usr/local/urchin/var/urchinwebd.conf
admin 21537 0.0 0.0 3364 872 ? S 20:04 0:00 /usr/local/urchin/bin/urchinwebd -f /usr/local/urchin/var/urchinwebd.conf
admin 21538 0.0 0.0 3364 872 ? S 20:04 0:00 /usr/local/urchin/bin/urchinwebd -f /usr/local/urchin/var/urchinwebd.conf
admin 21539 0.0 0.0 3364 872 ? S 20:04 0:00 /usr/local/urchin/bin/urchinwebd -f /usr/local/urchin/var/urchinwebd.conf
root 32341 0.0 0.0 5856 588 pts/2 S+ 20:39 0:00 grep urchin

So the problem I am having seems to be related possibly to urchin being ran from the wrong user.

pico /usr/local/urchin/var/urchinwebd.conf
User admin
Group admin

I 1quickly chowned all /usr/local/urchin once again recursively and found it was still running as root. I went one step further and started the urchin daemon from teh admin user su - admin
cd /usr/local/urchin/bin
./urchinctl start

And everything works just fine that I can find.

My apologies for such a long post- but I cant be the only one having these problems so i figured I'd share.

I hope urchin 6 is released for us at some point... I have never had these kinds of problems. I';ve installed urchin easilly 40 or more times... prior to RHEL4 tho
gbock
QUOTE (marauder @ Jan 26 2007, 02:59 AM) *
I hope urchin 6 is released for us at some point.


Google bought Urchin and has replaced it with Google Analytics. I am not sure if they will be releasing any more versions of Urchin.
marauder
http://www.google.com/support/analytics/bi...opic=&type=

Basically I noticed google says they supposedly will release it as a software version at some point...

We'll see.

QUOTE (gbock @ Jan 27 2007, 09:23 PM) *
Google bought Urchin and has replaced it with Google Analytics. I am not sure if they will be releasing any more versions of Urchin.
acider
now that i have changed urchin to be owned by user/group to "admin", there are no more warning messages.

however, this is what i have do everytime i reboot my server:

login as root

cd to /usr/.../urchin

bin/urchinctl stop

su admin

bin/urchinctl start

could anyone guide me how to start urchinctl from admin automatically everytime when i reboot the server. i am quite new to linux
marauder
I dont reboot servers often... but heres an idea

youc an setup a shell script with the following commands in it

service urchin stop
su - admin
cd /usr/local/urchin/bin (If i remember correctly)
./urchinctl start
exit

Something like that if I recall but of course it requires root permissions- but that is a quick idea. Not possitive for sure whether it will work or not.

you will need to add a call to the rc.local file at /etc/rc.local saying something liek this

sh /root/dir/to/urchin/script (the one listed above)

I believe that will possibly do it.

Hope that helps some...
yet its bs that urchin wont run the way it has for years.

QUOTE (acider @ Jan 30 2007, 04:05 PM) *
now that i have changed urchin to be owned by user/group to "admin", there are no more warning messages.

however, this is what i have do everytime i reboot my server:

login as root

cd to /usr/.../urchin

bin/urchinctl stop

su admin

bin/urchinctl start

could anyone guide me how to start urchinctl from admin automatically everytime when i reboot the server. i am quite new to linux
marauder
Anyone using the atomated urchin profile creation script at:
http://www.outofcontrol.ca/2005/11/19/inst...im-rhel-3-or-4/

That is teh same script I have used for quite a long time on probabloy a good 10 servers or so... Since RHEL5 has been released on top of the orriginal problems i was having the importing script with urchin seems to not work very well. Any one using the script?

I cna't be the only one have trouble with this urchin software which seems to be technically not supported. Either way I will probably need to start a migration to a new analyutics software....
plattapuss
marauder, I have updated the link on my site at outofcontrol.ca, to point to the original posting by Foggy at EV1. It now points to the proper post on The Planet.

Also, I use this script on 2 RHEL4 boxes with no fatal issues. The only issue I do have is the scheduler not running error, but Urchin still runs every night right on schedule, so I see no issues there. I originally followed Foggy's script to the letter and had no issues with it.

Here is the link, in case any one needs it.
gbock
QUOTE (marauder @ Jan 30 2007, 11:04 PM) *
I dont reboot servers often... but heres an idea

youc an setup a shell script with the following commands in it

service urchin stop
su - admin
cd /usr/local/urchin/bin (If i remember correctly)
./urchinctl start
exit

Something like that if I recall but of course it requires root permissions- but that is a quick idea. Not possitive for sure whether it will work or not.

you will need to add a call to the rc.local file at /etc/rc.local saying something liek this

sh /root/dir/to/urchin/script (the one listed above)

I believe that will possibly do it.

Hope that helps some...
yet its bs that urchin wont run the way it has for years.


There is a daemon script for linux in the utils directory. Copy it to /etc/init.d/urchin and run chkconfig urchin on.
Penguin
Just to update this thread, there's a much easier way of getting the task schedulder to run at startup without making loads of modifications - keep everything owned as nobody as per a standard install and just use the following:

chmod 6755 /usr/local/urchin/bin/urchinctl

This will set the Suid bit and so will cause urchin to run as user nobody, regardless of who executes it, including root.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2010 Invision Power Services, Inc.