Ignite unattended

[Jose Javier Sianes Ruiz]

Im installing a Ignite UX server. Clients are correctly configured with scripts than executed at programed times make_net_recovery to IgniteUX Server. Only problem is that if ignite process is not running when make_net_recovery from client is performed, process fails. The ignite process needs a X server to display the GUI, or at least, launch a ncurse version. I would like to know if there is a way to launch ignite process in daemon mode, without need GUI or TUI interface to be running on any machine in order to schedule make_net_recovery of clients without human intervention. Thanks.

[Eric Antunes]

Hi Jose,

I don't think you need a GUI environement to do that. This may be hapening because you have your DISPLAY environement variable set for that specific user...

Best Regards,

Eric Antunes

[Jose Javier Sianes Ruiz]

I think I haven't explain clear enough. I want to schedule make_net_recovery to launch unattended from several clients. In make_net_recovery process, every client try to connect with Ignite-UX server. The problem is that if this server doesn't run ignite process, the connection failed and no make_net_recovery is made. The only way to make it works is to launch ignite on Ignite-UX server, but this process needs to work interactity with an GUI or TUI display. This is a problem, because I want to make make_net_recovery without human intervention, I would like to know if there is any way I can launch ignite process in Ignite-UX Server without human intervention (no GUI or TUI interface needed) just to stay listen for clients make_net_recovery connections.

[Enrico P.]

Have you tried with the command

nohup make_net_recovery -s &

from the client?

What command have you tried?

Enrico

[Steven E. Protter · Accepted solution]

On the client that requires manual intervention.

There is a log of why it is failing on the client. That will show an error code on the cron job that fails. Its important to look at that and respond to the actual problem.

Without benefit of the log, several potential areas of concern:

* The NFS mount on the Ignite server is not allowing write access to the Ignite client. This is pretty common, but may not fit because you report the GUI completes.

* The command line options in the unattended run do not match those of the GUI/human guided make_net_recovery. This is certainly possible, even probable, since the Ignite process could care less whether the GUI is running.

* Permissions may not be right on the target directory of the NFS share being written to.

There is a lot of available information. You can and should monitor the syslog file on the server /var/adm/syslog/syslog.log with the tail -f command and then fire the make_tape_recovery with cron. You may see results that guide you to a solution.

SEP

[Jose Javier Sianes Ruiz]

SERV_IGNITE=Name of Ignite-UX server where it suposed to be running ignite process.
NAS_SERVER=Server where tar file is stored
POOL_IGNITE=The pool where is stored inside NAS_SERVER
CLIENT=Client name


/opt/ignite/bin/make_net_recovery -v -P s -s ${SERV_IGNITE} -a ${NAS_IGNITE}:/${POOL_IGNITE}/${CLIENT} -x inc_entire=vg00


The problem is that if ignite process in SERV_IGNITE isn't running when make_net_recovery is started, command fails. ignite process is designed like an interactive program, so I cant start it in a batch proccess to make all the process humanless.

[Jose Javier Sianes Ruiz]

It was a permission problem on one Pool. Thanks for all your help.