Video Screencast Help

Problem when install agent on Slackware Linux

Created: 16 Nov 2008 • Updated: 22 May 2010 | 1 comment
Intasunta N.'s picture

After installation SSIM Linux Agent completed. But I didn't see any process running. Then I try to tracking what going on with agentmgmnt.sh. 

 

After try to stop, start agent and rebootstrab many time on Slackware Linux the result still occured like this

 

SESA Data Gathering and Information Utility
Version: 4.5.0.12

./agentmgmt.sh: line 209: /etc/init.d/sesagentd: No such file or directory
Waiting for agent to stop - 1 ...
Agent has successfully stopped.
Enter the Hostname of machine to bootstrap to:
log-dede
Updating configprovider.cfg...
Please enter the installation path [/opt/Symantec/sesa/Agent]:
Deleting ses_store.dat if present...
Deleting ses_machine.dat if present...
./agentmgmt.sh: line 229: /etc/init.d/sesagentd: No such file or directory
Waiting for agent to start - 1 ...
Waiting for agent to start - 2 ...
Waiting for agent to start - 3 ...
Waiting for agent to start - 4 ...
Waiting for agent to start - 5 ...
Waiting for agent to start - 6 ...
Waiting for agent to start - 7 ...
Waiting for agent to start - 8 ...
Waiting for agent to start - 9 ...
Waiting for agent to start - 10 ...
Waiting for agent to start - 11 ...
Waiting for agent to start - 12 ...
Waiting for agent to start - 13 ...
Waiting for agent to start - 14 ...
Waiting for agent to start - 15 ...
Waiting for agent to start - 16 ...
Waiting for agent to start - 17 ...
Waiting for agent to start - 18 ...
Waiting for agent to start - 19 ...
Waiting for agent to start - 20 ...
Waiting for agent to start - 21 ...
Waiting for agent to start - 22 ...

 

 

So, Is there a solution to run SSIM Agent on Slackware linux ?

 

I think I can't convince the customer to change their system to running on RH linux that complatiple with our agent.

Comments 1 CommentJump to latest comment

gk's picture

Slackware Linux is not an officially supported Linux distribution for the Agent.  Your problems are probably due to Slackware's different (from Red Hat) startup script directory structure.

What you could try is to create an /etc/init.d directory and then create the following links like this:

ln -s /etc/init.d/sesagentd /etc/rc0.d/K01sesagentd
ln -s /etc/init.d/sesagentd /etc/rc1.d/K01sesagentd
ln -s /etc/init.d/sesagentd /etc/rc2.d/S99sesagentd