[ipac] Question about servicesnot properly startingafter reboot; remote access tools

Tue Aug 19 17:50:15 EDT 2008

I will second the nomination for Dameware. It is a very nice remote
control program for Windows. When we were running HIP on Windows, we
used Dameware.

John

+-----------------------------------------------------------------------
-----+

John Chadwick, Ed.D. Information Technology Manager

New Mexico State Library

1209 Camino Carlos Rey

Santa Fe, NM 87507

Phone: 505-476-9740  Cell: 505-629-8116 Fax: 505-476-9761

john.chadwick at state.nm.us

http://www.nmstatelibrary.org

________________________________

From: ipac-bounces at lists.tblc.org [mailto:ipac-bounces at lists.tblc.org]
On Behalf Of Liz Fairman - LAWLIBX
Sent: Tuesday, August 19, 2008 3:36 PM
To: Dynix's Horizon Information Portal,formerly iPac (discussion)
Subject: Re: [ipac] Question about servicesnot properly startingafter
reboot;remote access tools

We use Dameware (sounds like something that Mae West would wear) for
remote access.  HIP likes it, SD likes it, and I have access to the
server that got moved down the street.

Liz Fairman                  

Technical Services Librarian

Superior Court Law Library

Phoenix AZ 85003

602-506-3462

lfairman at scll.maricopa.gov

________________________________

From: ipac-bounces at lists.tblc.org [mailto:ipac-bounces at lists.tblc.org]
On Behalf Of Tyckoson, Mary Ellen
Sent: Tuesday, August 19, 2008 2:07 PM
To: Dynix's Horizon Information Portal, formerly iPac (discussion)
Subject: Re: [ipac] Question about servicesnot properly startingafter
reboot; remote access tools

We have our HIP servers on KVM switches with IP access ports, so I can
get to both of them in graphical mode from by desktop by logging into
the KVM switch.  No interference with HIP functioning so far on either
server.  Ours is an Autoview 3100 with one remote port and ran around
$1000.  It has Horizon & HIP (both RHEL) and WebReporter (Windows)
attached to it.  That's probably a more expensive solution than you
want, but it works here for remotely working on all of these servers.

~Mary Ellen

*****************************************
Mary Ellen Tyckoson
Library Program Manager
San Joaquin Valley Library System
559-488-3462
Mary.Tyckoson at sjvls.org
"Assumption is the mother of all screw-ups" - Wetherns Law
***************************************** 

________________________________

From: ipac-bounces at lists.tblc.org [mailto:ipac-bounces at lists.tblc.org]
On Behalf Of Brandon Walker
Sent: Tuesday, August 19, 2008 12:53 PM
To: Dynix's Horizon Information Portal, formerly iPac (discussion)
Subject: Re: [ipac] Question about services not properly startingafter
reboot; remote access tools

For the iPac to work and indexing to run the system must be logged in,
insofar as we can tell. If we log out iPac stops. So the server remains
locked all the time. And if you remote in to it using remote desktop the
iPac stops functioning for patrons. SD has told us that terminal
services logins via remote desktop mess with the iPac.

Brandon Walker

System Administrator

Western Reserve Historical Society

216.721.5722 x282

bwalker at wrhs.org

________________________________

From: ipac-bounces at lists.tblc.org [mailto:ipac-bounces at lists.tblc.org]
On Behalf Of Natasha Stephan
Sent: Tuesday, August 19, 2008 3:44 PM
To: Dynix's Horizon Information Portal, formerly iPac (discussion)
Subject: Re: [ipac] Question about services not properly startingafter
reboot; remote access tools

Hi Brandon,

Well, not all of my post was exclusive to *nix-world.  I'm pretty sure
that the order of services is applicable no matter what OS you're
running on your HIP server.  Can you tell if your services are set to
come up in the right order?  I wouldn't trust SD (based on my
experience, as I mentioned) to get that right.  And as you mentioned,
the order is important.

I'm really curious about something you said - "SD says Terminal
Services/Remote Desktop comflicts and they are right (sadly)."  What did
you mean?

Thanks,

Natasha

________________________________

From: ipac-bounces at lists.tblc.org [mailto:ipac-bounces at lists.tblc.org]
On Behalf Of Brandon Walker
Sent: Tuesday, August 19, 2008 1:21 PM
To: Dynix's Horizon Information Portal,formerly iPac (discussion)
Subject: Re: [ipac] Question about services not properly startingafter
reboot; remote access tools

Natasha,

Thanks. Too bad this *nix info isn't as applicable to this case.

Basically, when we start up the server it starts the necessary services,
but lately the web interface hasn't been coming up correctly. I have to
stop HZseach, HZapp, and HZxsl (in that order) and start them again (in
reverse order) and then I can relaunch the indexing service and the
indexer. Then everything's happy.

I've sat on this problem I'm afraid SD will try to charge us for service
as an OS problem and I was hoping there were some insights here.

Brandon Walker

System Administrator

Western Reserve Historical Society

216.721.5722 x282

bwalker at wrhs.org

________________________________

From: ipac-bounces at lists.tblc.org [mailto:ipac-bounces at lists.tblc.org]
On Behalf Of Natasha Stephan
Sent: Tuesday, August 19, 2008 11:32 AM
To: Dynix's Horizon Information Portal, formerly iPac (discussion)
Subject: Re: [ipac] Question about services not properly starting after
reboot; remote access tools

Not that this is directly useful to you, Brandon, because we're running
HIP on RHEL4... but for the sake of discussion I'll reply.  I'm always
interested in learning more about what others on this list are doing!

When we got our server from SD in late 2006, we ensured that the right
scripts were in /etc/rc[init state].d, aliased to /etc/rc.d/rc[init
state].d, and that they were symbolic links and not copies of the
scripts in /etc/init.d.  I was shocked SD's lack of quality control... I
had to do quite a bit of work.  I can ensure that the HIP services have
started by checking the process table.

You should find the equivalent data and whether the services have
started in Computer Management > Services and Applications > Services.
>From what I understand, HIP services should be started in the following
order:

Interbase/Firebird

XSL

App Server/JBoss

Search Server

Index Server

And they should be stopped in this order:

Index Server

Search Server

App Server/JBoss

XSL

Firebird

Maybe someone on this list knows whether there's a more automated way of
telling what services have started on a Windows box.

I use PuTTY to connect via SSH to my Linux boxes (Horizon and HIP) and
Remote Desktop to connect to my Windows box (Web Reporter).  I believe
my RHEL4 installs are 64-bit (I did uname -i to be sure).  My Windows
server (2003) is running a 32-bit version (no 64 mentioned in My
Computer > Properties > General).  I'd be interested to know what sort
of conflict there is with Remote Desktop.

Thanks,

Natasha

________________________________

From: ipac-bounces at lists.tblc.org [mailto:ipac-bounces at lists.tblc.org]
On Behalf Of Brandon Walker
Sent: Monday, August 18, 2008 3:58 PM
To: ipac at lists.tblc.org
Subject: [ipac] Question about services not properly starting after
reboot;remote access tools

When we got our new system in the fall SD never did get things running
completely right. We largely ignored it because the thing only gets
rebooted every month or so.

But what kinds of scripts do you folks run to make sure the proper ipac
services start up (in the proper order) and are operational on either
startup or login?

Also, what remote administration/access tools do you use? SD says
Terminal Services/Remote Desktop comflicts and they are right (sadly).
What 64-bit compliant tools do you use in its place? RSAdmin?
PCAnywhere?

Thanks,

Brandon Walker

Interim System Administrator

Western Reserve Historical Society

bwalker at wrhs.org 

______________________________________________________________________
This inbound email has been scanned by the MessageLabs Email Security
System.
______________________________________________________________________

Confidentiality Notice: This e-mail, including all attachments is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited unless specifically provided under the New Mexico Inspection of Public Records Act. If you are not the intended recipient, please contact the sender and destroy all copies of this message. -- This email has been scanned by the Sybari - Antigen Email System. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.tblc.org/pipermail/ipac/attachments/20080819/5fcf3724/attachment-0001.html 