my site is cityhall.
and then incvisu log indicate the log.
26/03/10 10:43:25 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 7 850
26/03/10 10:47:19 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 2 0
26/03/10 10:47:21 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 62 6
26/03/10 10:47:21 000001M|---/--/-/---|=2:0275=ACCOUNTING: Appli PRINTING : feature incident 62 1
this log incinfo is certain.
but i don't know why it does.
pls reply my question.
thanks
Incident number (q to quit):0275
INCIDENT NUMBER: 275
Network indicator: Alcatel 4400
OBJECT CLASS: Dhs3x_node
EVENT TYPE: ProcessingErrorAlarm (10)
PROBABLE CAUSE: Unknown (0)
SEVERITY: Major
"ACCOUNTING: Appli P1 : feature incident P2 P3"
"P1:"
" 10 APL_ACCOUNTING. Routing of accounting tickets."
" 11 APL_FREPORT. Application of Financial Report (financial report)."
" 12 APL_MONITORING. Monitoring application."
" 13 APL_PRINTING. Real time printout of tickets."
" 19 APL_SAVE. Ticket Backup."
" 30 APL_ACC_CHECK_FILES. Checking the coherence of ticket files."
" 31 APL_ACC_DUPLICATION. Duplication."
" 32 APL_ASCII. Transfer of ticket files."
" 38 APL_ACC_ETH. Print of tickets over Ethernet."
"P2: If P1 = 10 (Routing of accounting tickets)"
" 0 DATE_NOT_COHERENT. The dates entered are incoherent."
" 2 BUF_OVERFLOW. The capacity of the internal accounting buffer is"
" exceeded."
" This incident is cyclical."
" 5 NEG_NUM_RECORDS. The number of tickets in the database is incoherent."
" 8 LOSING_TICKETS. Impossibility of assigning a booth ticket to a room."
" 9 UNKNOWN_MESS. Unknown message received."
" 11 STRING_FILE. Problem in opening the string file."
" 12 SAVE_DISABLED. Backup disabled by account off command."
" 19 CHO_THREAD_CREATE. Cannot execute the task."
" 20 CHO_THREAD_DELETE. The task is killed."
" 38 EXT_ACCOUNTING_ALARM. The accounting external application has not"
" queried the A4400 accounting for a period of time."
" This time is determined from the interval of the previous requests."
" P3 indicates the number of hours which have passed since the last"
" connection of the external accounting application."
" This incident is available for software versions before"
" the releases R1.3.2 etR1.5.1 (included)."
" 54 FNCL_OPENREAD. Opening error in reading the file"
" /DHS3data/mao/TAXFNCL.dat."
" 55 FNCL_READ. Error in reading the file /DHS3data/mao/TAXFNCL.dat."
" 56 FNCL_OPENWRITE. Opening error in reading the file"
" /DHS3data/mao/TAXFNCL.dat."
" 57 FNCL_WRITE. Error in writing the file /DHS3data/mao/TAXFNCL.dat."
" 60 BUFFER_FILE_NOT_COMPATIBLE. Problem of incompatibility with file"
" /DHS3dyn/account/BUFFER.dat."
" 61 BAD_MSG_SIZE. unexpected ticket size."
" 71 UNEXPECTED_TICKET. The ticket contains invalid information."
" P3 = 0, The ticket references not the expected one."
" P3 = 100, The seconds in a field date are invalid."
" P3 = 101, The minutes in a field date are invalid."
" P3 = 102, The hours in a field date are invalid."
" P3 = 103, Year/Month/Day in a field date are invalid."
" P3 = 104, Duration calculation from invalid dates."
" P3 = 105, Negative duration."
" In all the cases, the ticket is not lost."
" 75 WINNT_ERROR. The V24 features are forbidden."
"Incident 275"
"If P1 = 11 (Financial Report Application)"
" 0 OPEN_ERROR. Problem initializing the serial port."
" 1 FORBIDDEN_ACTION. The execution of the financial report is not"
" allowed, either it has not been validated in MAO or it has not been"
" bought."
" 2 WRITE_ERROR. Problem of output on the serial port."
" 50 FR_RENAMEFILE. Problem for renaming the FR*.dat files into FR*.tmp in"
" the /DHS3dyn/account repertory."
" 51 FR_ERASINGFILE. Problem for deleting the FR*.tmp files in the"
" /DHS3dyn/account repertory."
" 52 FR_CREATE_NODE. Problem in allocating soft memory."
" 53 FR_OPENFILE. Problem in opening a FR*.dat or FR*.tmp file in the"
" /DHS3dyn/account repertory."
" 58 FR_CHDIR. The correct repertory is not found."
" 59 FR_DB_CONCURRENT_ACCESS. The access to the database is locked by"
" another task."
"If P1 = 12 (Observation application)"
" 1 FORBIDDEN_ACTION. Monitoring is forbidden."
"If P1 = 13 (real time, booth and monitoring printouts of tickets)"
" 0 OPEN_ERROR. Problem in opening the file of installation parameters."
" 1 READ_ERROR. Problem in reading the file of installation parameters."
" 2 BUF_OVERFLOW. The buffer is full (P3=0: real time printer, P3=1:"
" booth printer, P3=2: monitoring printer)."
" 6 ALARM1. The alarm threshold 1 has been reached by the level of filling"
" of a buffer (60%). P3 indicates the alarm threshold and the type of"
" buffer (P3 unit=0: real-time, P3 unit=1: booth, P3 unit=2: monitoring)."
" Example P3= 612: monitoring buffer61% full, P3=650: real time buffer"
" 65% full."
" This incident is cyclical."
" 7 ALARM2. The alarm threshold 2 has been reached by the level of filling"
" of a buffer (85%). P3 indicates the alarm threshold and the type of"
" buffer (P3 unit=0: real-time, P3 unit=1: booth, P3 unit=2: monitoring)."
" This incident is cyclical."
" 10 STATUS_PRINTER. Problem of output on the serial port."
" This incident is cyclical."
" 19 CHO_THREAD_CREATE. Impossibility of executing the task."
" 20 CHO_THREAD_DELETE. The task is killed."
" 60 BUFFER_FILE_NOT_COMPATIBLE. Impossible to read tickets from disk."
" 62 LOST_TICKETS. This incident is displayed 2 times consecutively on"
" restarting a printer when the tickets have been lost due to a full"
" buffer (see P2=2)."
" It indicates the total number of tickets that have been lost since"
" the system was started. It is always followed by incident 63."
" For the first incident 62, P3 indicates the buffer (0:real time, 1:booth,"
" 2:monitoring)."
" For the second incident62, P3 indicates the number of lost tickets (P3"
" Cannot exceed 32767)."
" Example:"
" 1st incident of type 62P3=1"
" 2nd incident of type 62P3=87"
" The booth printer (1)has lost 87tickets."
" This incident is cyclical."
"Incident 275"
" 63 LOST_CHARGE_UNITS. This incident is displayed on restarting a printer"
" when the tickets have been lost due to a full buffer (see P2=2)."
" It comes always after the incident 62."
" P3 indicates the number of lost charging units, P3 cannot exceed 32767."
" This incident is cyclical."
" 68 BUFFER_FILE_OPEN_ERROR. Cannot read tickets from disk."
" 69 BUFFER_FILE_WRITE_ERROR. Cannot save tickets to the disk."
" 70 POP_ERROR. Error when retrieving tickets from buffer."
"If P1 = 19 (Storage of the tickets)"
" 2 BUF_OVERFLOW. Problem with the command buffer."
" 3 SAVE_DATA_CTR. Error in the file of the user counters."
" 4 SAVE_DATA_DON. Error in the file of the accounting parameters."
" 6 ALARM1. The alarm threshold 1 has been reached by the level of filling"
" of the base."
" This incident is cyclical."
" 7 ALARM2. The alarm threshold 2 has been reached by the level of filling"
" of the base."
" This incident is cyclical."
" 8 LOSING_TICKETS. It is no longer possible to store the tickets in the base"
" because the allocated space is full."
" P3 indicates the number of tickets lost since the allocated space is full."
" 12 SAVE_DISABLED. The backup of tickets on the disk is forbidden."
" This incident is cyclical."
" 19 CHO_THREAD_CREATE. Impossibility of executing the task."
" 20 CHO_THREAD_DELETE. The task is killed."
" 39 AVAILABLE_SQL_SPACE_ON_DISK. The free space of /DHS3dyn partition is"
" inferior to the volume allocated for storing tickets in MAO."
" This incident is cyclical."
" 62 LOST_TICKETS. This incident is displayed 2 times consecutively when"
" tickets could not be saved on disk."
" It indicates the total number of tickets that have been lost since"
" the system was started."
" It is always followed by incident 63."
" For the first incident 62, P3 indicates the trouble"
" (1:internal buffer full,2:database,3:ascii files)."
" For the second incident62, P3 indicates the number of lost tickets"
" (P3 cannot exceed 32767)."
" Example:"
" 1st incident of type 62P3=2"
" 2nd incident of type 62P3=12"
" 12 tickets have been lost for the database storage."
" This incident is cyclical."
" 63 LOST_CHARGE_UNITS. This incident is displayed when accounting tickets"
" could not be saved on disk."
" It comes always after the incident 62."
" P3 indicates the number of lost charging units, P3 cannot exceed 32767."
" This incident is cyclical."
" 72 TMP_MAO_FILE_DESCRIPTOR. The management ticket descriptor"
" can't be written into the current file."
" 73 TMP_MAO_FILE_TICKET. A management ticket can't be written into the"
" current file."
" 76 TMP_IP_FILE_TICKET. An IP ticket can't be written into the current"
" file"
"Incident 275"
"If P1 = 30 (Check of coherence of the ticket files)"
" 13 ACC_FILES_ERROR. Problems in reconditioning the accounting files."
" 19 CHO_THREAD_CREATE. Cannot execute the task."
"If P1 = 31 (Duplication)"
" 6 IPC_IPC_SEND. Impossibility of sending a message to the accounting for"
" starting the update of the duplicated CPU."
" 14 DUPLI_RETRIEVE_ERROR. Cannot read the file in which the"
" accounting tickets are stored during the updating step of the duplicated"
" CPU."
" 16 DUPLI_SEND_CPU_SEC. Impossible to send a message to the duplicated CPU."
" 17 DUPLI_CPU_IS_NOT_MAIN. The update of the duplicated CPU has been started"
" on the wrong CPU (the MAIN and not the other)."
" 18 DUPLI_TIMEOUT. A "time-out" has occurred during the updating step of the"
" duplicated CPU."
" 19 DUPLI_FAILED. The updating of the duplicated CPU has failed."
" 20 DUPLI_BUFFER_ERROR. Impossibility of saving the tickets received by the"
" accounting when updating the duplicated CPU."
" 21 DUPLI_FORBIDDEN_ACTION. An operation requested to accounting by another"
" task is forbidden when updating the duplicated CPU."
" 22 DUPLI_PREVIOUSLY_LOST_TICKETS. Accounting tickets which were lost in a"
" previous attempt of updating the duplicated CPU are detected."
" 23 DUPLI_RCP_CPU_SEC. The files of accounting (updated) cannot be copied"
" from the MAIN CPU to the duplicated CPU."
" 24 DUPLI_COULD_NOT_START_CPU_SEC. The duplicated CPU cannot be started"
" again (to be set in STAND_BY) after its files have been updated."
" 25 DUPLI_END. End of the update procedure of the duplicated CPU (whether it"
" has failed or succeeded)."
" 66 TAR_CPU. The tar command on the MAIN CPU failed."
" 67 RSH_CPU_SEC. The tar command on the TWIN CPU failed."
"If P1 = 32 (Transfer of ticket files)"
" 12 SAVE_DISABLED. Backup disabled by account off command."
" 19 CHO_THREAD_CREATE. Cannot execute the task."
" 20 CHO_THREAD_DELETE. The task is killed."
" 26 ACCOUNT_FILES_ERROR. Error in compressed file."
" 27 CREATE_ACCOUNT_LIS. Cannot create the list file (.LIS)."
" 28 OPEN_ACCOUNT_LIS. Cannot open the list file (.LIS)."
" 29 RENAME_ACCOUNT_LIS. Cannot rename the list file (.LIS)."
" 30 CREATE_ACCOUNT_TMP. Cannot create the temporary file (.tmp)."
" 31 RENAME_ACCOUNT_TMP. Cannot rename the temporary file (.tmp)."
" 32 RENAME_ACCOUNT_OLT. Cannot rename the working file (.olt)."
" 33 RENAME_TAX_TMP. Cannot rename the temporary file (.tmp)."
" 34 WRITE_TAX_TMP. Cannot write in the temporary file (.tmp)."
" 35 COMPRESS_FILES_ERROR. Error when compressed."
" 36 NO_DISK_SPACE. Not enough disk space."
" 37 NO_MEM_ALLOC. No more RAM available."
" 61 BAD_MSG_SIZE. The ticket has not the expected size."
" This incident is cyclical."
" 64 BAD_FILE_NUMBER. Incoherency in the number of compressed files."
" 65 BAD_FILE_NAME. Bad filename for a compressed file."
" 74 APPLICATION_TYPE. This incident differentiates the type"
" of files concerned by the next incident."
" 0 accounting tickets files"
" 1 management tickets files"
" 2 IP tickets files"
"P3 Status of the operation"
"Si P1 = 38 (Edition des tickets sur Ethernet)"
" 2 BUF_OVERFLOW. The ethernet buffer is full."
" P3 is equal to 3 (ethernet thread)."
" 6 ALARM1: The alarm threshold 1 of the ethernet buffer has been "
" reached by the level of filling of a buffer (60%)."
" P3 indicates the filling rate of the ethernet buffer."
" This incident is cyclical."
" 7 ALARM2: The alarm threshold 2 of the ethernet buffer has been "
" reached by the level of filling of a buffer (85%)."
" P3 indicates the filling rate of the ethernet buffer."
" This incident is cyclical."
" 10 STATUS_PRINTER. Problem of Ethernet output."
" 19 CHO_THREAD_CREATE. Impossibility of executing the task."
" 20 CHO_THREAD_DELETE.The task is killed."
" 60 BUFFER_FILE_NOT_COMPATIBLE. Impossible to read the ethernet buffer"
" backup file (BUFFERE.dat) "
" 62 LOST_TICKETS. This incident is displayed 2 times consecutively when"
" some tickets have not been sent over Ethernet due to "
" an ethernet buffer full."
" It is always followed by incident 63."
" P3 is equal to 3 (ethernet buffer full)."
" This incident is cyclical."
" 63 LOST_CHARGE_UNITS. This incident is displayed 2 times consecutively when"
" some tickets have not been sent over Ethernet due to "
" an ethernet buffer full."
" It comes always after the incident 62."
" P3 indicates the number of lost charging units, The VoIP tickets are not"
" taken into account for the sum of this number."
" This incident is cyclical."
" 68 BUFFER_FILE_OPEN_ERROR. Impossible to open the ethernet buffer"
" backup file (BUFFERE.dat) "
" 69 BUFFER_FILE_WRITE_ERROR. Impossible to write into the ethernet buffer"
" backup file (BUFFERE.dat)."
" 70 POP_ERROR. Error when poping tickets from buffer."
"Problem of accounting"
"according to (P1, P2):"
"-(10, 2) No ticket is saved in the database. An alarm is triggered on a station."
"-(10, 38) Tickets have not been retrieved by the external accounting"
" application within the normal period. The disk space decreases and may be"
" saturated after a time. An alarm is triggered on station."
"-(10, and 54 to 57) The parameters of the financial report are incorrect. An "
"alarm is triggered on station."
"-(10, 60) The tickets in the/DHS3dyn/account/BUFFER.dat file are not loaded in"
" the buffer when the system reboots. They are lost. Do not trigger an alarm on"
" a station."
"-(10, 61) The message received by the accounting application has not been"
" interpreted because its size is not compatible with the size expected. Do not"
" trigger an alarm on a station."
"-(11, 0 or 2) The financial report will not be edited on the serial port."
"-(11, 1) The financial report will not be executed."
"-(11, 50) The next financial report maybe erroneous. An alarm is triggered on"
" a station."
"-(11, 51) The FR*.tmp files have not been removed in the /DHS3dyn/account"
" repertory."
"-(11, 52 et 53) The content of the financial report will be erroneous. An alarm"
" is triggered on a station."
"-(11, 58) The execution of the financial report has stopped. An alarm is"
" triggered on a station."
"-(13, 2) Tickets are lost during the process. An alarm is triggered on a "
"station."
"-(13, 6, or 7) The tickets are buffered but not printed. An alarm is "
"triggered on a station."
"-(13, 10) The real time printer is out of order or out of paper. An alarm is"
" triggered on a station."
"-(13, 60 or 68) Loss of tickets stored at the previous shutdown."
"-(13, 69) Loss of tickets during the shutdown."
"-(19, 3) Erroneous counters for users."
"-(19, 4) Wrong parameters for managing the accounting application."
"-(19, 6) An alarm is triggered on a station."
"-(19, 7) An alarm is triggered on a station."
"-(19,
Tickets are no longer stored. An alarm is triggered on a station.""-(19, 12) Tickets are no longer stored. An alarm is triggered on a station."
"-(19, 39) The disk space decreases and may be saturated after a time. An"
" alarm is triggered on a station."
"-(19, 62, 63, 72 and 73) It is no longer possible to store the tickets in the"
" SQL database and/or in the compressed files."
" The accounting tickets are lost for storage but edited toward the real time"
" printer if it is not usually operational (real time printout is not"
" validated and/or software protection key has not been bought)."
"-(30, 13) An alarm is triggered on a station."
"-(31, 66) The twin CPU duplication failed."
"-(31, 67) The twin CPU duplication failed."
"-(32, and 12 to 37) Tickets are no longer stored. An alarm is triggered on "
" a station."
"- (38, 19) The tickets can't be sent over Ethernet."
"- (38, 2) The tickets are not bufferized anymore and they are lost."
"- (38, 69) During a reboot, the tickets which are stored "
" in the ethernet buffer can't be saved into the file BUFFERE.dat."
" Then, they are lost."
" according to (P1, P2)"
"-(10, 0) Operation must be done again with coherent data."
"-(10, 2) Check that the backup is allowed by /DHS3bin/oneshot/mtcl/account"
" on."
" Force the buffer to dump by entering /DHS3bin/oneshot/mtcl/account save, or "
" else restart the accounting application."
"-(10, 38) Retrieve the tickets as soon as possible using the accounting"
" application. If this does not take place correctly, check the chain of ticket"
" retrieval:"
" 1 Management of the A4400."
" 2 Link between the A4400 and the external accounting application."
" 3 Management of the external accounting application and checking of the"
" failures of operations (no response of A4400, broken connections)."
" 4 Checking the incidents of A4400. '/DHS3bin/oneshot/mtcl/account external'"
" command edits the most recent connections of the external accounting"
" application."
"-(10, and 54 to 57) Manage the parameters of the financial report using the MAO."
" Check that the /DHS3data/mao/TAXFNCL.dat file exists. If this is not the case,"
" create it by /DHS3bin/fab/fichges and manage its data."
"-(10, 58) None."
"-(10, 61) In the case of a duplication, it is very likely that the software"
" versions of the main and standby CPUs are different. In this case, stop the"
" standby CPU and load on it the software version of the main CPU. In any other"
" case, send a problem report to the technical support."
"-(11, 0, or 2) Check the coherence for the serial port configuration."
"-(11, 1) Allow the financial report for the MAO. If the incident is still"
" occurring, the financial report feature has not been bought."
"-(11, 50) Check the available space for /DHS3dyn partition. This must be higher"
" than twice the size of the 4 files FRCC.dat, FRDA.dat, FRTG.dat and FRAC.dat."
" Check that these four files are present in the /DHS3dyn/account repertory."
" These 4 files can be removed providing the day corresponds to the date when"
" the financial report has been edited. In the opposite case do not do anything."
"-(11, 51) Check the available space for /DHS3dyn partition. This must be higher"
" than twice the size of the 4 files FRCC.tmp, FRDA.tmp, FRTG.tmp and FRAC.tmp."
" Remove manually the remaining .tmp files (rm /DHS3dyn/account/FR*.tmp)."
"-(11, 52) Check the available system memory with the relevant tools."
"-(11, 53) Check the available space for the /DHS3dyn partition and the access"
" rights to FR*.dat and FR*.tmp files."
"-(11, 58) Check that the/DHS3data/mao directory really exists."
"-(12, 1) Allow MAO monitoring."
"-(13, 2, 6, or 7) Check the printer (offline, no paper, flow problem)"
" control, etc.)."
"-(19, 3) Remove and create a new file of user counters with sheets."
"-(19, 4) Remove and create a new file of the accounting parameters with sheets."
" Manage through MAO the management parameters of the accounting application"
" initialized by default."
"Incident 275"
"-(19, 6 or 7 or
Needs a quick intervention. By means of the financial report"" or external accounting, request a removal of the tickets to dump the database."
"-(19, 12) Needs a quick intervention. The backup has been forbidden. Authorize"
" the backup by entering "/DHS3bin/one"shot/mtcl/account on". If the incident"
" still occurs, stop and restart accounting."
"-(19, 39) Needs a quick intervention. Remove the files which are contained in"
" the /usr4/lost+found repertory if any (root login). Remove all the unused"
" files out of the directories of /DHS3dyn partition. If you did not note"
" anything abnormal, enter the command 'ls - lR /usr4' and transmit the result to"
" the people concerned."
"-(19, 57 and 58) Check that the /DHS3data/mao/TAXFNCL.dat file exists. If not,"
" create it by /DHS3bin/fab/fichges and manage its data."
"-(19, 62, 63, 72 and 73) Analyze the available disk space of partition"
" /DHS3dyn. Check the size of all the files of this partition by the"
" 'ls - l /DHS3dyn/*'.command. Does the external accounting application"
" regularly retrieve the accounting tickets ? Account is on or is off ?"
"-(30, 13) Major problem when restarting accounting; tickets will no longer be"
" stored. Check if the disk is full."
"-(31, 14) The tickets received by accounting since the beginning of the update"
" of the duplicated CPU are lost. Check if the disk is full."
"-(31, 16) Check the link between the two CPUs (e.g. slot in the boards)"
"-(31, 17) Restart the update procedure of the duplicated CPU from the latter"
" and not from the MAIN CPU."
"-(31, 18) Restart the update of the duplicated CPU when the telephone traffic"
" is lower."
"-(31, 19) The procedure for updating the duplicated CPU has failed. Restart it."
"-(31, 20) Some of the tickets received by accounting from the beginning of the"
" update of the duplicated CPU are definitively lost. Check if the disk is full."
"-(31, 21) The task which has requested it (hotel, for example) will have to"
" repeat its request later."
"-(31, 22) Tickets lost during a previous update of the duplicated CPU are"
" retrieved if P3 = 1 and definitely lost if P3 = 0."
"-(31, 23) Check the correct operation of the Ethernet link between the two"
" CPUs."
"-(31, 24) Restart the update of the duplicated CPU; tickets that should be lost"
" will be retrieved during this second attempt."
"-(31, 25) If P3 = 1, the duplicated CPU has been updated correctly and is in"
" the STANDBYSTANDBY status; otherwise (P3 =0): failure of the operation."
"-(31, 66) Check that the tar command runs."
"-(31, 67) Check the rsh command runs and the Ethernet link between the two"
" CPUs."
"-(32, 12) Needs a quick intervention. The backup has been forbidden. Authorize"
" the backup by entering "/DHS3bin/oneshot/mtcl/account on". If the incident"
" still occurs, stop and start accounting."
"-(32, 26 to 35) Check the available space in the "/DHS3dyn" partition as well"
" as the owner, the group and the rights for reading and writing."
"-(32, 36) Save space in the "/DHS3dyn" partition."
" If your problems cannot be solved with these indications, it is recommended to"
" write a problem report precise as possible concerning the conditions and"
" consequences of malfunctions and incidents you have met. Transmit it to the"
" people concerned to be analyzed and processed."
"-(32, 64) Check that no compressed file misses."
"-(32, 65) Check the name of all the compressed files.";
