Systems Team - contact if something breaks during non-business hours, or if Leif is out and Sirsi needs to talk to someone in IT
IT@SAM Operations - cc if something breaks during non-business hours, notify if need to restart during business and non business hours. If operations isn't notified, they will contact the server admin to let them know the server is going down
Error: Too Many Login
Fix: clear user locks -- /s/sirsi/Unicorn/Locks/Users
to remove all type: rm *
Remove policy.lck in Unicorn/Config
Notes:
CONTACT IT@Sam Operations and cc systems@shsu.edu to notify when you are during a full HIR (halt initialize and run)
If Sirsi goes down before the indexing reports are ran, the reports will run after the restart which will kick everyone off again. Wait 30min - 1 hr and try again.
Failed communication error- typically this is due to both ORACLE and REPORT servers not running (or halted), you can try to restart them but more than likely IT will have to do a full reboot of the server to get them up and running.
Other connection issues are typically fixed with restarting services
There are two commands to stop or start Sirsi services:
auto_haltrun - halt/initialize/run all servers at once
unicornadmin - halt/initialize/run specific servers
sudo to sirsi user and use the auto_haltrun script
auto_haltrun {cycle|halt|init|run|status} [force]
auto_haltrun status - checks the status of all servers
auto_haltrun cycle
When "cycle" is specified, auto_haltrun attempts to halt, initialize, run, and provide the status of the Unicorn servers, in that sequence. It does this using standard administration tools which have been altered to operate without requiring user intervention.
auto_haltrun halt
When "halt" is specified, or during the "halt" phase of a "cycle," auto_haltrun checks the state of the system for the following conditions.
Users logged in
Running reports
If either of these conditions is found to be true, the system is not halted.
auto_haltrun init
When "init" is specified, or during the "init" phase of a "cycle," auto_haltrun checks the state of the system for the following conditions.
Servers running
Users logged in
Running reports
If any of these conditions is found to be true, initialization is not performed.
auto_haltrun run
When "run" is specified, or during the "run" phase of a "cycle," auto_haltrun checks the state of the system to see if there are any servers running. If any servers are running, auto_haltrun prints an informational message and continues, running any halted servers.
Status
A "status" phase is always performed by auto_haltrun to report the final state of the system after all other phases have been attempted. The status argument only reports, and never changes the state of the running system.
Note: The auto_haltrun script cannot be run as the root user, and should always be run from the sirsi user account.
Force Option
If the force option is specified, the halt, initialize, run, and cycle operations will be performed regardless of whether users are logged in or reports are running. If the force option is used, a message displays to warn that no checking will be done before action is taken.
type unicornadmin (will default to statuses)
type in desired operation
Newton Gresham Library | (936) 294-1614 | (866) NGL-INFO | Ask a Question | Share a Suggestion
Sam Houston State University | Huntsville, Texas 77341 | (936) 294-1111 | (866) BEARKAT
© Copyright Sam Houston State University | All rights reserved. | A Member of The Texas State University System