I recently set up shop on a Debian ServerMatrix with Urchin. I couldn't find a help page on Urchin anywhere on the net, could only piece together bits. The main bit I discovered is that it normally runs on port 9999, but it wasn't already running. The software is installed, and I was able to get the daemon up by running /usr/local/urchin/bin/urchinctl.

My questions:

(1) How do I have urchin re-start automatically at reboot? This forum page attempts to provide the answer but apparently no solution suggested has worked.

(2) What username/password do I use to login? Neither my orbit login nor my regular user login works.

(3) Can anyone point me to a web page that provides newbie help on urchin? In particular, I'll be setting up to monitor multiple named virtual hosts on a single IP. I've seen the word 'profile' being thrown around.

Thanks for your help!
~joe

This should be the same root/administrator login details for the server.



Yes, it can handle virtual accounts even if they are hosted on the same IP. The Profile is based on the domain names and not on the IP address. Each virtual site as long as they have their own log files would work.

Thanks, but none of my valid username/passwords work.

I have since changed my root password as well, and I saved that new password in orbit, so I don't know what the original was (didn't know it might still be needed).

In any case, this login isn't secured by ssl and I really ought not be entering any user credentials except for something registered specifically with urchin.



Excellent! Thank you! Now if only I could get in to see!

~joe

You will definitely need to use the original server password to enter Urchin. After which you can always change it. The password in Orbit is merely just a convenient place to store your password just so that admin can get into your server if you require their assistance.

Since you do not know your original password, you will probably need to open a support ticket and have support reset the Urchin password.

Urchin is not supported on Debian.

gbock:



Not sure what you mean by that. I submitted a trouble ticket and got a near-instantaneous response. I was assigned a new password (the username is 'admin'), I've logged in and configured a few profiles.

eddy2099:

Thank you! I seem to be in business, except for this message, "Warning! Task scheduler disabled."

I found this forum page suggesting that I stop urchin, delete the pid file, and restart urchin. But stopping urching auto-deletes both pid files, and restarting urchin both creates new pid files and still gives me that warning.

Any more wisdom? Thanks!

~joe

http://www.google.com/support/urchin45/bin...py?answer=28672

http://www.google.com/support/urchin45/bin...py?answer=28747

If you are non stable packages on Sarge (namely glibc) this may work, but I do not remember us every explicitly supporting Debian+Urchin.

Okay, thanks, but it seems to be working. glibc is pretty basic stuff and I can't imagine how the daemon could serve pages error-free without it. I think I've got it linked in just fine.

For the moment, assume that it does work on Debian. How do I get the task scheduler to run. I saw:

http://forums.theplanet.com/viewtopic.php?...p=148356#148356

But per my above post, this approach isn't working for me.

Thanks for your help!
~joe

I know that it can be made to work, I was simply stating that I didn't remember officially supporting it. If I remember correctly, the version of Debian we install(ed) had a version of glibc that was too old.

As far as the scheduler, what does the inspector binany output? It should be in /usr/local/urchin/util and may need to be run from the pwd, IE

cd /usr/local/urchin/util/ && ./inspector

Any error output from:

/usr/local/urchin/bin/urchinctl -s start

Oh hi gbock. I actually just submitted a ticket on the issue. Per this web page, my problem is that the urchin installation owner is different from the urchin process owner. Running "urchinctl status" tells me that both the daemon and scheduler are actually running. No error messages anywhere, not even stopping and restarting.

That web page tells me to swich owners, but I need a solution that works at boot time, and one that doesn't require special handling.

Thanks!
~joe

Configurations can be found in /usr/local/urchin/var.

Doh, brain wasn't quite working there.

You should also be able to set user/group in the startup script. The daemon is fairly straight forward, remove the urchin startup if it is in /etc/local.rc and use the daemon template:

root@cpdemo [/usr/local/urchin/util]# ls *dae*
urchin_daemons urchin_daemons.template

Either call the binary with su or you can also set the binary suid/sgid so it always runs as the user you need.

Good info! If only I could make sense of it!

I don't have an /etc/local.rc. Is it possible that the startup scripts are those in etc/init.d? I have a maybe 30-line script here named 'urchin_daemons', but urchin is not presently starting at boot time -- I have to start it manually, though I want it to start at boot time.

I'm not sure how to apply your suggestion. Thanks!

http://www.infodrom.org/Debian/doc/maint/M...e-runlevel.html

So you would want to copy urchin_daemons to /etc/init.d/urchin then add it with:

update-rc.d urchin default

The daemon file may need a few tweaks to work properly on Debian.

Thank you, gbock. theplanet staff resolved the problem via a ticket I posted. It apparently took a few people before we finally figured it out.

I'm not quite sure exactly what they did, but it involved a re-installation (and hence re-licensing) of Urchin.

Urchin was originally installed running as root. That seems like a huge security problem. It is now running as 'nobody' -- solving both the security problem and the scheduler problem.

Thank you for your help. Now I have to figure out why Apache2 stopped writing logs a few weeks ago...

~joe