Drizzle

Can't run drizzle on OSX when building with visibility flag

Bug #709948 reported by Lee Bieber
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Critical
Monty Taylor
Drizzle 2011-01-31
7.0
Fix Released
Critical
Monty Taylor
Drizzle 2011-01-31

Bug Description

As of build 2122 drizzled does not start on OSX. However the only two changes in the 2122 build were

680715: A better /var/drizzle missing error message
702286: libz valgrind warnings should be suppressed

So the correlation to that build doesn't make sense. However the reality is that you can't start drizzled on our OSX machines (abyss, cronus and hades). I also tried on my machine and saw the same problem.

On my machine:
% /Users/lbieber/repos/debug//drizzled/drizzled --drizzle-protocol.port=9306 --datadir=/tmp/drizzle/var

hangs and produces the following in drizzled.err

InnoDB: The InnoDB memory heap is disabled
InnoDB: Mutexes use GCC atomic builtins, rw_locks do not
InnoDB: Compressed tables use zlib 1.2.3
110129 15:10:35 InnoDB: Initializing buffer pool, size = 128.0M
110129 15:10:35 InnoDB: Completed initialization of buffer pool
110129 15:10:36 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
110129 15:10:36 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
110129 15:10:36 InnoDB 1.1.4 started; log sequence number 1598206
Listening on :::9306
Listening on 0.0.0.0:9306
Listening on :::3306
Listening on 0.0.0.0:3306
Listening on /tmp/mysql.socket
/Users/lbieber/repos/debug/drizzled/.libs/drizzled: ready for connections.
Version: '2011.01.2126' Source distribution (debug)
Session killed before thread could execute

Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote :

Output from dtrace

Changed in drizzle:
status: New → Confirmed
importance: Undecided → Critical
Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote :

Sorry Monty, its the visibility changes, I built with out visibility turned on and everything is fine.

summary: - Can't run drizzle on OSX
+ Can't run drizzle on OSX when building with visibility flag
Revision history for this message
Lee Bieber (kalebral-deactivatedaccount) wrote :

So the first time we tried building with visibility feature it was build 2122, but had problems and had to roll back. Thats why the build 2122 of record is different.

Revision history for this message
Monty Taylor (mordred) wrote : Re: [Bug 709948] Re: Can't run drizzle on OSX when building with visibility flag

On 01/29/2011 05:31 PM, Lee Bieber wrote:
> So the first time we tried building with visibility feature it was build
> 2122, but had problems and had to roll back. Thats why the build 2122 of
> record is different.
>

Well piddle. Ok - I'll sort it out.

Revision history for this message
Monty Taylor (mordred) wrote :

On 01/29/2011 06:59 PM, Monty Taylor wrote:
> On 01/29/2011 05:31 PM, Lee Bieber wrote:
>> So the first time we tried building with visibility feature it was build
>> 2122, but had problems and had to roll back. Thats why the build 2122 of
>> record is different.
>>
>
> Well piddle. Ok - I'll sort it out.
>

This may have something to do with it:

mysql_protocol_port | 609887322

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.