UMP Error and Portal.log showing Can't create/write to file ... MYI' (Errcode: 13)

Document ID : KB000047852
Last Modified Date : 14/02/2018
Show Technical Document Details
Case Summary
The wasp process will send error messages from the database server to the client directly; in this case, UMP fails to load after resizing the partition containing MySQL SLM/ CA_UIM database. The customer had created a symlink in order to manage the server during the partition resize, and MySQL was not able to create files in /tmp/ because it pointed to a new folder, /data/tmp/ and seemed to be okay, as the mysql user was set as the owner.

The UMP webpage only displays:?"ERROR: An internal server error occurred. See the UMP log files for more information. "

The portal.log file shows:?
ERROR [DataFactoryException:82] Can't create/write to file '/tmp/#sql_1ffa_0.MYI' (Errcode: 13) ?where the green text is substituted with a random client connection ID.

The issue is actually occurring on the database server.

1. Run the df command on the system running MySQL Database Server, and ensure that the / mount or /tmp/ mount has at least some free space.

2. Ensure /tmp/ exists and root is the owner with User/Group/Other all having Full Read+Write+Execute permissions. This is the default permissions, and can be copied from any base installation of linux.

3. Restart wasp.

See also:

keywords: mysql, database, linux, solaris, centos, redhat, rhel, debian, ubuntu, wasp, ump, mobile, permissions, security, chmod, chown, mount, temporary, temp, errcode, portal