Troubleshooting 32-bit Application Faults
Symptom
32-bit applications are faulty; for example, applications cannot be started or crash on startup. However, 64-bit applications are normal.
Impact on the System
All 32-bit applications are affected.
Possible Causes
If only 32-bit applications are faulty, the transcoding software may be faulty. Possible causes are as follows:
- The transcoding software fails to be registered.
- The transcoding software version does not match.
- The transcoding software patch is not installed.
Procedure
- Run the following command and check whether the command output is normal. If enable is displayed, the command output is normal.
cat /proc/sys/fs/binfmt_misc/ubt_a32a64
- If the command output is abnormal, run the following command to register the transcoding software again:
echo ":ubt_a32a64:M::\x7fELF\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00:\xff\xff\xff\xff\xff\xff\xff\x00\x00\x00\x00\x00\x00\x00\x00\x00\xfe\xff\xff\xff:/opt/exagear/ubt_a32a64:POCF" > /proc/sys/fs/binfmt_misc/register
- Perform 1 again and check whether the command output is normal.
- Run the following command to check the transcoding software version:
/opt/exagear/ubt_a32a64 -V
- Compare the displayed software version with the transcoding software version in the version mapping table. If the versions do not match, contact technical support to obtain the matching software version.
If the fault persists, collect information and contact technical support.
Parent topic: Troubleshooting