[ipac] Question about services not properly starting after reboot; remote access tools
Natasha Stephan
stephann at lindahall.org
Tue Aug 19 11:31:33 EDT 2008
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.tblc.org/pipermail/ipac/attachments/20080819/46a844fb/attachment.html
More information about the ipac
mailing list