FAQs: Checking Error Logs
SirsiDynix Symphony administrators should check the workstation error log daily to look for unusual messages. These messages are often valuable clues in assisting SirsiDynix Customer Support to resolve software and hardware issues. Details about the process for both UNIX and Windows Server platforms are available.
Checking the Error Log on a UNIX Server
|
1
|
Login as the admin user with the appropriate password and PIN. It is important that you use lower case for the username and password. |
|
2
|
From the Utility Selection menu, select Unicornadmin by typing either the word “unicornadmin” or the number beside it. |
UNICORNADMIN Utility Selection MM/DD/YYYY
---------------------------------------------------------------------
Select the utility you want to use:
1) Backup 5) Report 9) Unicornadmin
2) Computeradmin 6) Standalone 10) Updategui
3) Import_export 7) Systemconfig 11) Updatewsdisk
4) Logs 8) Terminaltype 12) Wsclient
Type HELP for help,
EXIT to quit UNICORN Utilities,
or a NUMBER.
|
3
|
From the resulting menu, type status. |
UNICORNADMIN Operation Selection MM/DD/YYYY
* There are 1 user(s) logged in.
* UNICORN workstation server 2004.0 is RUNNING.
* Netserver 2004.0 is RUNNING.
* WebCat server 2004.0 is RUNNING.
* UNICORN report server 2004.0 is RUNNING.
* Z39.50 server is RUNNING.
(To return to previous level, press the ESCAPE key .)
---------------------------------------------------------------------
Select operation:
Type HELP for help,
EXIT to quit the UNICORN Administration Utility,
HALT to halt selected server(s),
INITIALIZE to initialize servers/stations/users/utilities,
LOCK to lock or unlock gateway element(s),RUN to run selected server(s),
or STATUS to view the status of servers/stations/users/utilities.
|
4
|
From the resulting menu, select workstation server. |
UNICORNADMIN/STATUS Type Selection MM/DD/YYYY
(To return to previous level, press the ESCAPE key .)
---------------------------------------------------------------------
Which status would you like to view?
1) gateway server 4) stations 7) webcat_server
2) netserver 5) users 8) workstation server
3) report server 6) utilities 9) z39.50 server
Type EXIT to discontinue status,
ALL to view all of them,
or a NUMBER.
|
5
|
From the resulting display, press ENTER to accept the default. |
UNICORNADMIN/STATUS/WS SERVER Status Of Workstation Server MM/DD/YYYY
(To return to previous level, press the ESCAPE key .)
---------------------------------------------------------------------
*** UNICORN Workstation server 2004.0 is RUNNING.
*** UNICORN Workstation socket server 2004.0 is RUNNING.
Show status for which date?
Date must be input in the format of MONTH/DAY/YEAR or NEVER
[9/9/2003]
|
6
|
If there are multiple pages, you can page through them by pressing ENTER. |
|
7
|
The following are normal error log messages that result from a halt and run. |
20030909141238 UNICORN Netserver v2003 started on
Tuesday, September 9, 2003, 2:12 PM
20030909141242 UNICORN Starter v2003 started on
Tuesday, September 9, 2003, 2:12 PM
20030909141242 UNICORN Monitor v2003 started on
Tuesday, September 9, 2003, 2:12 PM
UNICORN Socket Server v2003 started on
Tuesday, September 9, 2003, 2:12 PM
20030909142545 monitor: services: starting up pid =
6279020030909142545 monitor: accountability: starting up pid =
2818020030909142545 monitor: authority: starting up pid =
2113820030909142545 monitor: bibtext: starting up pid =
3401620030909142545 monitor: bill: starting up pid =
1348020030909142545 monitor: booking: starting up pid =
5440620030909142545 monitor: circ: starting up pid =
3002420030909142545 monitor: course: starting up pid =
860420030909142545 monitor: crossref: starting up pid =
6395220030909142545 monitor: fundven: starting up pid =
4683420030909142545 monitor: gateway: starting up pid =
6048820030909142545 monitor: hold: starting up pid =
3701220030909142545 monitor: loadmarc: starting up pid =
6587820030909142545 monitor: invoice: starting up pid =
6994820030909142545 monitor: loadmarc: starting up pid =
6587820030909142545 monitor: invoice: starting up pid =
6994820030909142545 monitor: order: starting up pid =
6152620030909142545 monitor: outreach: starting up pid =
5074620030909142545 monitor: policy: starting up pid =
1829620030909142545 monitor: reports: starting up pid =
4468420030909142545 monitor: request: starting up pid =
1617820030909142545 monitor: reserve: starting up pid =
2351420030909142545 monitor: search: starting up pid =
1066220030909142545 monitor: search: starting up pid =
6946420030909142545 monitor: search: starting up pid =
2326820030909142545 monitor: search: starting up pid =
6670020030909142545 monitor: searchorder: starting up pid =
4065420030909142545 monitor: serctl: starting up pid =
6755020030909142545 monitor: user: starting up pid =
5038020030909142547 BRS/Search-Engine v.62 started for crossref
120030909142547 BRS/Search-Engine v.62 started for outreach
120030909142548 BRS/Search-Engine v.62 started for booking
120030909142548 BRS/Search-Engine v.62 started for search
120030909142548 BRS/Search-Engine v.62 started for search
220030909142550 BRS/Search-Engine v.62 started for search
320030909142550 BRS/Search-Engine v.62 started for search
420030909142647 monitor: services: shutting down pid =
6279020030909142647 monitor: accountability: shutting down pid = 2818020030909142647 monitor: authority: shutting down pid =
2113820030909142647 monitor: bibtext: shutting down pid =
3401620030909142647 monitor: bill: shutting down pid =
1348020030909142647 $: reached maximum FIFO queue depth of
120030909142647 $: services: 1 busy responses out of 17 attempts
20030909142647 $: gateway: 0 busy responses out of 1 attempts
20030909142647 $: policy: 0 busy responses out of 6 attempts
20030909142647 monitor: booking: shutting down pid =
5440620030909142647 monitor: course: shutting down pid =
860420030909142647 monitor: crossref: shutting down pid =
6395220030909142647 monitor: fundven: shutting down pid =
4683420030909142647 monitor: gateway: shutting down pid =
6048820030909142647 monitor: hold: shutting down pid =
3701220030909142647 monitor: loadmarc: shutting down pid =
6587820030909142647 monitor: invoice: shutting down pid =
6994820030909142647 monitor: order: shutting down pid =
6152620030909142647 monitor: outreach: shutting down pid =
5074620030909142647 monitor: outreach: shutting down pid =
5074620030909142647 monitor: policy: shutting down pid =
1829620030909142647 monitor: reports: shutting down pid =
4468420030909142647 monitor: request: shutting down pid =
1617820030909142647 monitor: reserve: shutting down pid =
2351420030909142648 monitor: search: shutting down pid =
1066220030909142648 monitor: search: shutting down pid =
6946420030909142648 monitor: search: shutting down pid =
2326820030909142648 monitor: search: shutting down pid =
6670020030909142648 monitor: searchorder: shutting down pid = 4065420030909142648 monitor: serctl: shutting down pid =
6755020030909142648 monitor: user: shutting down pid = 50380
The following error log messages are problematic.
20030909152446 $(67):LIBR
20030909083752 monitor: circ: failed exit status 0x100 pid =
6901620030909101405 monitor: bill: failed exit status 0x0 pid =
4617420030909101405 monitor: user: failed exit status 0x0 pid =
4925820030909101405 monitor: policy: failed exit status 0x0 pid =
1410620030909101405 monitor: loadmarc: failed exit status 0x0 pid =
5300220030909101405 monitor: bibtext: failed exit status 0x0 pid =
3262220030909101405 monitor: authority: failed exit status 0x0 pid =
6753420030909101405 monitor: accountability: failed exit status 0x0 pid =
4052820030909101405 monitor: hold: failed exit status 0x0 pid =
6221420030909101406 monitor: request: failed exit status 0x0 pid =
7013020030909101406 monitor: gateway: failed exit status 0x0 pid =
5968620030909101406 monitor: serctl: failed exit status 0x0 pid =
3149820030724105225 $: fatal: message read error, exception = 1, errno =
3620030724123013 crossref: fatal communication error
20030724123013 monitor: fatal: message read error, exception = 1, errno =
3620030724123013 user: fatal communication error
20030724123013 search: fatal communication error
20030724123013 $: fatal: message read error, exception = 1, errno =
3620030724123013 services: fatal communication error
20030724123013 warn?: fatal communication error
20030724123013 fatal communication error
20030724123013 bib: fatal communication error
20030724123013 order: fatal communication error
20030724123013 request: fatal communication error
20030724123013 bill: fatal communication error
20030724123013 warn?: fatal communication error
20030724123013 hold: fatal communication error
20030724123013 circ: fatal communication error
**error on text: 4; open
|
8
|
If you see any of the preceeding messages, contact SirsiDynix Customer Support for assistance. |
|
9
|
When you have finished viewing the log, press ESC. Continue pressing ESC until you return to the Utilities menu. |
Utility Selection MM/DD/YYYY
---------------------------------------------------------------------
Select the utility you want to use:
1) Backup 5) Report 9) Unicornadmin
2) Computeradmin 6) Standalone 10) Updategui
3) Import_export 7) Systemconfig 11) Updatewsdisk
4) Logs 8) Terminaltype 12) Wsclient
Type HELP for help,
EXIT to quit UNICORN Utilities
or a NUMBER.
Type exit and press ENTER to logout.
Checking the Error Log on a Windows Server
|
1
|
Use Windows Explorer to navigate to D:\sirsi\Unicorn\Logs. |
|
2
|
Copy the file named “error” to error_copy. |
|
3
|
Use Wordpad to open the error_copy file. |
|
4
|
Scroll or use the Find command to get to the end of the log where you will find entries for the current date. Each line begins with a series of numbers like “20030724105225” where the format is YYYYMMDD. |
|
6
|
Close and remove the error_copy file when you are done. |