From: "Paul Smedley" <ecs-isp@2rosenthals.com>
Subject: Re: Updated MySQL 5.7.35 build (mysqld not yet working)
To: eCS ISP Mailing List <ecs-isp@2rosenthals.com>,
 Apache HTTP Server for OS/2 <apache2@googlegroups.com>
References: <03374287-e6df-bedb-1571-6e12c4038af8@smedley.id.au>
Message-ID: <1ab8fe59-6fc7-dbf3-760d-e97519dd92eb@smedley.id.au>
Date: Sun, 22 Aug 2021 18:50:45 +0930
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <03374287-e6df-bedb-1571-6e12c4038af8@smedley.id.au>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit

Update:
unix socket issue is fixed, the file write one isn't.

debug build is now at 
https://smedley.id.au/tmp/mysql-5.7.35-os2-debug-20210822.zip

The file write one is interesting, as plenty of other file writes are 
succeeding :(

On 22/8/21 9:35 am, Paul Smedley wrote:
> 
> Hi All,
> 
> I posted an earlier build to the apache2 mailing list, also posting this 
> to ecs-isp
> 
> Binaries: https://smedley.id.au/tmp/mysql-5.7.35-os2-20210822.zip
> Source diff: https://smedley.id.au/tmp/mysql-5.7.35.diff
> 
> Changes since the last build:
> - passwords now seem to work correctly with mysql.exe
> - Server no longer crashes in my_timer_deinitialize, but it still 
> doesn't (quite) start
> 
> The server now fails in:
> 2021-08-21T23:52:55.256000Z 0 [ERROR] Could not create unix socket lock 
> file \socket\mysql.lock.
> 2021-08-21T23:52:55.262000Z 0 [ERROR] Unable to setup unix socket lock 
> file.
> 2021-08-21T23:52:55.262000Z 0 [ERROR] Aborting
> 
> 
> & later:
> 2021-08-21T23:52:55.777000Z 0 [ERROR] InnoDB: Write to file 
> ./ibtmp1failed at offset 0, 16384 bytes should have been written, only 0 
> were written. Operating system error number 22. Check that your OS and 
> file system support files of this size. Check also that the disk is not 
> full or a disk quota exceeded.
> 2021-08-21T23:52:55.779000Z 0 [ERROR] InnoDB: Error number 22 means 
> 'Invalid argument'
> 2021-08-21T23:52:55.781000Z 0 [Note] InnoDB: Some operating system error 
> numbers are described at 
> http://dev.mysql.com/doc/refman/5.7/en/operating-system-error-codes.html
> 2021-08-22 10:22:55 0x335d53a0  InnoDB: Assertion failure in thread 
> 861754272 in file os0file.cc line 7841
> 
> Whilst mysqld isn't working, I'd be interested if anyone can test some 
> of the other client utilities.
> 
> Cheers,
> 
> Paul