daemon: severity: module: internal error, details
Explanation
An internal error occurred. details gives the cause of the error, daemon gives the name of the daemon program, severity gives the severity of the message, and module the module name (usually the internal function name) where the event was detected.
a) The following messages may be output when an I/O error occurs.
sdxservd: ERROR: module: internal error, sdxfunc=dbrw_read_dc(), rval=-1, sdxerrno=4120
sdxservd: ERROR: module: internal error, sdxfunc=dbrw_read_dc(), rval=-1, sdxerrno=4121
b) The following message may be output when a node is booted. This means the return value of the OS read(2) system call was 0 and the error number was 2. If the return value is 0, the event is not an error and the error number has no meaning, but it is recorded as a WARNING because the return value is not normal (a positive value).
sdxservd: WARNING: module: internal error, osfunc=read, rval=0, errno=2
c) If part of or all of the disks registered with the root class are not recognized by the OS at OS startup, the following message may be output.
sdxservd: ERROR: sendtd_root: internal error, sdxfunc=sv_pd_find_bytd, rval=-1, sdxerrno=2
d) If an attempt to boot a proxy volume is made when synchronization copying between the joined master and proxy is in process, the following message may be output.
sdxservd: WARNING: mv_start: internal error, sdxfunc=mv_copy_dispatch, sdxerrno=11
e) The following message may be output if restoring physical disks of the swapped internal disk when there is a device name change.
sdxservd:ERROR: internal error (pd_find_bytd,sdxerrno=2)
f) If the mirroring among servers is used when the shutdown facility (SF) of PRIMECLUSTER is not set properly, the following message may be output when one node is restarted. In this case, the synchronization copying fails, and the slice of the restarted node becomes INVALID.
sdxservd: INFO: tdmcopy_begin: internal error, can't find COPY slice
g) If the cluster application is started in the configuration of mirroring among servers, the following messages may be output by the GDS process running in the Online process.
sdxservd: ERROR: dev_rename_minor_node: internal error, /dev/sfdsk/class/dsk/volume -> /dev/sfdsk/class/dsk/volume: rename error, errno=2
sdxservd: ERROR: rcv_dev_rename_minor_node: internal error, sdxfunc=dev_rename_minor_node, sdxerrno=1026, class=class
Resolution
In the event of a), some other I/O error message will be output. Refer to the explanation of resolution for that message, and take necessary actions.
In the event of b), if no error message was output around the same period of time, GDS was behaving normally and the message b) may be ignored. If some other error message was output around the same period of time, refer to the explanation and resolution for that message, and take necessary actions.
In the event of c), the error has no effect on the system. Restore the state where the disks are recognized by the OS and reboot the system, and the message will no longer be output.
In the event of d), the error has no effect on the system. There is no need to work around.
In the event of e), reboot the system to solve the device name change.
In the event of f), use the sdxcopy -B command to perform the synchronization copying. Set the shutdown facility (SF) properly as well.
In the event of g), check the status of class class. If the class is not started, restore it.
Execute the following command on the node where the message is output.
# /etc/opt/FJSVsdx/bin/sdxdcdown |
If the class information is not displayed, the class is not started.
In this case, see the note "Shutting down the node" of the section "(2) Class cannot be started when booting the system." in "D.1.4 Class Status Abnormality", stop the node where the message is output, and then restart it.
If the class information is still not output, see the section "(2) Class cannot be started when booting the system." in "D.1.4 Class Status Abnormality" and restore.
After outputting the message, if the node is already restarted and the class is started, restoration work is not necessary.
In other events, collect investigation material and contact field engineers.
