CMDTUX Messages 3100-3199
|
|
3110
ERROR: [Failed to get field fieldname from _tppost message]
Description
The Event Server couldn't get a field from the FML buffer.
Action
The EVENT API inserts various FML fields into the buffer before dispatching it to the Event Server. This message indicates that the Event Server couldn't get the field out of the FML buffer.
See Also
Fget32(3fml)
3112
ERROR: Cannot open database, tperrno=tperrno
Description
While initializing the Event Server, tpopen returned an error. The server will not boot.
Action
Use the returned tperrno and check the userlog to determine what the error was. Resolve the problem and re-boot the server.
See Also
tpopen(3c), TMSYSEVT(5), TMUSREVT(5)
3113
WARN: internal received the wrong buffer type - buftype
Description
The Event Server received a message from an application program that was sent via tpcall or tpconnect instead of tppost. A failure message is returned to the originator.
Action
Re-write the application software or reconfigure the TUXCONFIG file so that messages are sent to the correct services using the correct primitives.
See Also
tppost(3c)
3114
WARN: [internal posting function received a buffer for other than TPPOST, opcode opcode]
Description
The Event Server received a message with an invalid operation code, opcode.
Action
Contact your BEA TUXEDO system Technical Support.
3115
WARN: Primary Event Server received the wrong buffer type - buftype
Description
The Event Server received a message from an application program that was sent via tpcall or tpconnect instead of tpsubscribe or tpunsubscribe. A failure message is returned to the originator.
Action
Re-write the application software or reconfigure the TUXCONFIG file so that messages are sent to the correct services using the correct primitives.
See Also
tpsubscribe(3c), tpunsubscribe(3c), EVENT_MIB(5)
3117
ERROR: Failed to advertise svc service for System Event Server. tperrno=tperrno
Description
The event server couldn't advertise service svc.
Action
The event server couldn't advertise service svc. Make sure that the MAXSERVICES parameter in RESOURCES section of UBBCONFIG is big enough. If it is not big enough, either change the parameter dynamically, or shut down the application and rebuild TUXCONFIG and then reboot the event server.
See Also
tpadvertise(3c)
3118
ERROR: _tmformat() failed for TA_COMMAND cmd for event eventname
Description
The Event Server couldn't format the command string before invoking the command.
Action
When the Event Server receives a message due to some client or server posting an event, the data associated with the event is also sent. Then, the Event Server looks up the subscriptions that match this posted event and formats the string as per the subscription before calling system command. This messages indicates that the formatting failed. Make sure that the Event Server has the required environment variables for the posted data buffer and that the names of the variables in the subscription record are correct.
See Also
TMSYSEVT(5), TMUSREVT(5), tpsubscribe(3c), tppost(3c)
3120
ERROR: _tmformat() failed for TA_USERLOG userlog for event eventname
Description
The Event Server couldn't format the command string before invoking the command itself.
Action
When the Event Server receives a message due to some client or server posting an event, the data associated with the event is also sent. Then, the Event Server looks up the subscriptions that match this posted event and formats the string as per the subscription before calling system command. This messages indicates that the formatting failed. Make sure that the Event Server has the required environment variables for the posted data buffer and that the names of the variables in the subscription record are correct.
See Also
TMSYSEVT(5), TMUSREVT(5), tpsubscribe(3c), tppost(3c)
3122
ERROR: Event Broker is not configured for processing notifications in transactional mode
Description
During Event Server's booting, tpopen failed which means that Event Server cannot process any notifications in transactional mode.
Action
Check the userlog for the message stating that tpopen failed for this Event Server. Correct this error and restart the server.
See Also
TMSYSEVT(5), TMUSREVT(5), EVENT_MIB(5), tpsubscribe(3c), tppost(3c)
3123
ERROR: Event Broker can't begin a transaction. tperrno=tperrno
Description
The Event Server couldn't begin a transaction to do the notifications transactionally.
Action
Make sure that MAXGTT in the UBBCONFIG file is big enough for the application needs. If not, increase the value and restart the application.
See Also
tpbegin(3c), UBBCONFIG(5)
3124
ERROR: Event Broker can't abort a transaction. tperrno=tperrno
Description
The Event Server failed to abort the transaction it started earlier.
Action
When the Event Server does notifications in transactional mode, it makes one or more tpcall's or tpenqueue's depending upon the subscriptions that matched the posted event. If any of the calls fail, the server aborts the transaction. This message indicates that tpabort failed. Check the error string and take corrective action.
See Also
tpbegin(3c), UBBCONFIG(5)
3125
ERROR: Event Broker can't abort a transaction. tperrno=tperrno
Description
The Event Server failed to abort the transaction it started earlier.
Action
When the Event Server does notifications in transactional mode, it makes one or more tpcall's or tpenqueue's depending upon the subscriptions that matched the posted event. If any of the calls fail, the server aborts the transaction. This message indicates that tpabort failed. Check the error string and take corrective action.
See Also
tpabort(3c)
3126
ERROR: Event Broker can't abort a transaction. tperrno=tperrno
Description
The Event Server failed to abort the transaction it started earlier.
Action
When the Event Server does notifications in transactional mode, it makes one or more tpcall's or tpenqueue's depending upon the subscriptions that matched the posted event. If any of the calls fail, the server aborts the transaction. This message indicates that tpabort failed. Check the error string and take corrective action.
See Also
tpbegin(3c), UBBCONFIG(5)
3127
ERROR: Event Broker can't commit a transaction. tperrno=tperrno
Description
The Event Server failed to commit the transaction it started earlier.
Action
When the Event Server does notifications in transactional mode, it makes one or more tpcall's or tpenqueue's depending upon the subscriptions that matched the posted event. If all of the requests complete successfully, the server commits the transaction. This message indicates that tpcommit failed. Check the error string and take corrective action.
See Also
tpcommit(3c)
3128
ERROR: tpacall() to svc svc failed for event eventname tperrno=tperrno
Description
The Event Server made a tpcall on behalf of a subscription due to a posted event.
Action
This message indicates that a posted event eventname resulted in a service call to svc and it failed with tperrno tperrno. Check the message and take corrective action. If this is a non-persistent subscription, the subscription will be removed. So, you may have to resubscribe to that event before this condition can be reproduced.
See Also
tpacall(3c)
3129
ERROR: tpenqueue() to qname qname failed for event eventname tperrno=tperrno
Description
The Event Server made a tpenqueue on behalf of a subscription due to a posted event.
Action
This message indicates that a posted event eventname resulted in enqueuing a message to queue name qname and it failed with tperrno tperrno. Check the message and take corrective action. If this is a non-persistent subscription, the subscription will be removed. So, you may have to resubscribe to that event before this condition can be reproduced.
See Also
tpenqueue(3c)
3130
ERROR: Cannot allocate memory for receiving reply
Description
Memory allocation failed for receiving reply message.
Action
Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.
3131
ERROR: tpgetrply() failed for eventname eventname. tperrno=tperrno
Description
The Event Server made a tpacall on behalf of a subscription due to a posted event. Then, it tried to get the reply for the service call.
Action
This message indicates that a posted event eventname resulted in a service call to svc. When trying to get a reply, it failed with tperrno tperrno. Check the message and take corrective action. If this is a non-persistent subscription, the subscription will be removed. So, you may have to resubscribe to that event before this condition can be reproduced.
See Also
tpgetrply(3c)
3134
ERROR: *MIBPERMS entries out of order
Description
tmloadcf was run on an ASCII configuration file originally created using tmunloadcf in which the internally generated *MIBPERMS section has been modified by the user.
Action
If you have not yet destroyed your previous TUXCONFIG file, it may be unloaded again using tmunloadcf to get a valid ASCII image of the configuration file. You may then edit that image, but be certain not to change the *MIBPERMS section if one exists. If the previous TUXCONFIG file has been destroyed, then you can delete the *MIBPERMS section in its entirety and rerun tmloadcf to regenerate the TUXCONFIG file; however, all application customized permissions for /AdminAPI access will be lost using this method. Alternatively, you can reorder the entries in the *MIBPERMS section using the field name as the primary sort key and the field identifier as the secondary key before rerunning tmloadcf.
See Also
tmloadcf (1), tmunloadcf (1), MIB(5)
3135
ERROR: tpadmcall() failed when processing event. strerr=string
Description
While posting a system event, a MIB GET call to tpadmcall to retrieve associated information for the event failed. Additional information is printed indicating the cause of the failure.
Action
Check the reason for the failure. No action required.
See Also
TM_MIB(5)
3136
ERROR: Cannot open file file for writing
Description
The secondary event server couldn't open file file for writing the subscription database it got from the primary event server.
Action
Make sure that the server can create the file file and that there are enough inodes in the file system.
See Also
TMSYSEVT(5), TMUSREVT(5)
3137
ERROR: Couldn't initialize the allocated memory as a fielded buffer, Ferror32=errno
Description
The Event Server failed to Finit32 an FML32 buffer.
Action
Contact your BEA TUXEDO system Technical Support and provide the Ferror32 errno.
See Also
Finit32(3fml)
3138
ERROR: Cannot write FML32 buffer in file file, Ferror32=errno
Description
The event server failed to write a subscription record in the file file.
Action
Make sure that the control file is not inadvertently deleted while the server is running. Check the Ferror32 errno in the message and take corrective action.
See Also
Ffprint32(3fml)
3139
ERROR: Secondary Event Server failed to get a new copy of subscription database from the Primary, errstr=errstr
Description
The secondary server made a tpcall to primary event server to get a new copy of the subscription database. This message states that the call failed.
Action
Check the error string errstr in the message and take corrective action.
See Also
TMSYSEVT(5), TMUSREVT(5)
3140
ERROR: Primary Server can't unload subscription database into a file
Description
The primary event server couldn't unload the subscription database into a file.
Action
The primary event server updates the control file whenever a client or server unsubscribes to a subscription or if the event server garbage-collects stale subscriptions. This message indicates that the server failed to write the new database to the file. Check for other messages preceding this message and take corrective action.
See Also
TMSYSEVT(5), TMUSREVT(5)
3141
ERROR: Primary Server can't set CURSID in the FML buffer. Ferror=errno
Description
The primary event server can't add CURSID to FML buffer.
Action
The primary server uses a sequence number to generate subscription handles. When a secondary event server queries the primary for a new copy of the subscription database, this sequence number is also sent with it. Later on, when the secondary queries again, this sequence number is used to determine if a new copy of the subscription database needs to be sent or not. This message indicates that the primary server couldn't set the sequence number in the FML buffer. Contact your BEA TUXEDO system Technical Support and provide the Ferror errno.
See Also
Fchg(3fml)
3142
ERROR: Primary Server can't tpalloc CARRAY buffer. tperrno=tperrno
Description
The primary event server failed to allocate a CARRAY buffer.
Action
If the userlog message preceding this message states that it is out of memory, then add more memory to the system or configure the system to allow more virtual memory for the processes. If the tperrno tperrno is anything else, contact your BEA TUXEDO system Technical Support and provide the tperrno.
See Also
tpalloc(3c)
3143
ERROR: Primary Server can't save subscription database inside the COMPOSITE buffer
Description
Contact your BEA TUXEDO system Technical Support.
Action
Contact your BEA TUXEDO system Technical Support.
3144
ERROR: Secondary Server can't allocate a FML buffer. tperrno=tperrno
Description
The primary event server failed to allocate an FML buffer.
Action
If the userlog message preceding this message states that it is out of memory, then add more memory to the system or configure the system to allow more virtual memory for the processes. If the tperrno tperrno is anything else, contact your BEA TUXEDO system Technical Support and provide the tperrno.
See Also
tpalloc(3c)
3145
ERROR: Secondary Server can't set CURSID in the FML buffer. Ferror=errno
Description
The secondary event server can't add CURSID to FML buffer.
Action
When the secondary event server polls the primary server for subscription database, it sends the sequence number it received previously from the primary server. This message states that the secondary server couldn't insert the sequence number field to FML buffer. Contact your BEA TUXEDO system Technical Support and provide the Ferror errno.
See Also
Fchg(3fml)
3146
ERROR: Secondary Server can't set CURSOC in the FML buffer. Ferror=errno
Description
The secondary event server can't add CURSOC to FML buffer.
Action
When the secondary event server polls the primary server for subscription database, it sends its poll interval. This message states that the secondary server couldn't insert the poll interval field to FML buffer. Contact your BEA TUXEDO system Technical Support and provide the Ferror errno.
See Also
Fchg(3fml)
3147
ERROR: Secondary Server can't get CURSID from the FML buffer. Ferror=errno
Description
The secondary event server can't get CURSID from FML buffer.
Action
When the secondary event server polls the primary server for subscription database, the primary server sends its sequence number back to the secondary server. This message states that the secondary server couldn't extract the sequence number field from the FML buffer. Contact your BEA TUXEDO system Technical Support and provide the Ferror errno.
See Also
Fget(3fml)
3148
ERROR: Secondary Server can't delete the old subscription database
Description
When the secondary event server receives a new copy of subscription database, it first deletes the old subscription records and then adds the new records into memory. This message indicates that it could not delete the old database.
Action
Contact your BEA TUXEDO system Technical Support.
3150
ERROR: Secondary Server can't extract subscription database from the COMPOSITE buffer
Description
Contact your BEA TUXEDO system Technical Support.
Action
Contact your BEA TUXEDO system Technical Support.
3151
ERROR: Secondary Server failed to write subscription database to file file, errno=errno
Description
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a file file and then starts parsing the file to load it into memory. This message states that it couldn't write to the file.
Action
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
See Also
Fwrite(3fml)
3152
ERROR: Secondary Server failed to link file file to file, errno=errno
Description
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a temporary file file and then starts parsing the file to load it into memory. After parsing the file, it links the temporary file to the control file. This message states that the attempt to link failed with errno errno.
Action
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
3153
ERROR: Secondary Server failed to unlink file file. errno=errno
Description
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a temporary file file and then starts parsing the file to load it into memory. After parsing the file, it links the temporary file to the control file. After linking the file, it deletes the temporary file. This message states that the attempt to unlink failed with errno errno.
Action
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
See Also
unlink(2) in Unix System reference manuals
3154
ERROR: Secondary Server failed to parse the new subscription database in file file
Description
The secondary event server failed to parse the control file file.
Action
Make sure that the file file was not inadvertently deleted while the server is running. Also, check for userlog messages preceding this message for a more descriptive message.
See Also
TMSYSEVT(5), TMUSREVT(5)
3156
ERROR: Secondary Server can't get CURSID from the FML buffer. Ferror=errno
Description
The secondary event server can't get CURSID from FML buffer.
Action
When the secondary event server polls the primary server for the subscription database, the primary server sends its sequence number back to the secondary server. This message states that the secondary server couldn't extract the sequence number field from the FML buffer. Contact your BEA TUXEDO system Technical Support and provide the Ferror errno.
See Also
Fget(3fml), TMSYSEVT(5), TMUSREVT(5)
3157
ERROR: Secondary Server failed to link file file to file. errno=errno
Description
After the secondary event server receives a copy of the subscription database from the primary, it first loads into a temporary file file and then starts parsing the file to load it into memory. After parsing the file, it links (renames) the temporary file to the control file. This message states that the attempt to link failed with errno errno.
Action
Check the errno errno and take corrective action. Make sure that the directory is writable and that there is enough space in the file system.
 |
 |
 |