Hello, It turns out I'm a doofis. I moved /lib/tls to /lib/tls.old and now mysql starts fine!
YAY! Any help with the kernel-panics would still be appreciated. Thanks for your help. Tim Ansell On Fri, 2005-04-15 at 14:15 +0930, Tim Ansell wrote: > Hello, > > I'm trying to run a LAMP (Linux, Apache, MySQL, PHP) setup inside UML > but I'm afraid I've become stuck. > > I'm running as a host kernel 2.4.27 kernel with the SKAS/SYSEMU patch > from http://www.user-mode-linux.org/~blaisorblade/ . > > vserver-host-1:/uml/scripts# cat /proc/version > Linux version 2.4.27uml ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian > 1:3.3.5-8)) #1 Fri Apr 15 12:43:30 CST 2005 > > I'm running as the uml kernel 2.6.11 with the bs4 patches from > blaisorblade. > > ws1:~# cat /proc/version > Linux version 2.6.11-ws-bs4 ([EMAIL PROTECTED]) (gcc version 3.3.5 (Debian > 1:3.3.5-8)) #1 Fri Apr 15 13:23:52 CST 2005 > > When I try and start MySQL inside the UML instance is crashes because of > a "signal 11", I have included the output of MySQL at then end. The > crash happens with version 3.3, 4.0 and 4.1 of MySQL. > > I have also tried using 2.4.24 host kernel with the plain SKAS patch. > I have also tried vanilla 2.6.11 kernel for UML. > > This seams identical to the error found here, > http://marc.theaimsgroup.com/?l=user-mode-linux-user&m=110759214208407&w=2 > > I also sometimes get kernel panics if I type at the console, it says > > Kernel panic - not syncing: Kernel mode fault at addr 0x8, ip 0x404294b8 > > EIP: 0023:[<404294b8>] CPU: 0 Not tainted ESP: 002b:bffffd10 EFLAGS: > 00000246 > Not tainted > EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000 > ESI: 00000000 EDI: bffffd40 EBP: bffffd58 DS: 002b ES: 002b > Call Trace: > 15c2f768: [<0808669d>] notifier_call_chain+0x2d/0x50 > 15c2f778: [<08118906>] bust_spinlocks+0x46/0x50 > ..... > > However none of the details seem consistent. > > I would really like to get this setup and stable as soon as possible, if > I can give you any more information to make it easier to debug just ask. > I could possibly give people login to this machine if needed to help > debug. However I'll be at linux.conf.au 2005 next week so my response > might be a bit slow. > > Thanks for your help and looking forward to using a stable UML setup. > > Tim Ansell > > > InnoDB: The first specified data file ./ibdata1 did not exist: > InnoDB: a new database to be created! > 050415 15:33:48 InnoDB: Setting file ./ibdata1 size to 10 MB > InnoDB: Database physically writes the file full: wait... > mysqld got signal 11; > This could be because you hit a bug. It is also possible that this > binary > or one of the libraries it was linked against is corrupt, improperly > built, > or misconfigured. This error can also be caused by malfunctioning > hardware. > We will try our best to scrape up some info that will hopefully help > diagnose > the problem, but since we have already crashed, something is definitely > wrong > and this may fail. > > key_buffer_size=16777216 > read_buffer_size=131072 > max_used_connections=0 > max_connections=100 > threads_connected=0 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections > = 233983 K > bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > thd=0x842a638 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > Cannot determine thread, fp=0x4261c7d8, backtrace may not be correct. > Stack range sanity check OK, backtrace follows: > 0x810e48b > 0x40037aa8 > (nil) > New value of fp=(nil) failed sanity check, terminating stack trace! > Please read http://dev.mysql.com/doc/mysql/en/Using_stack_trace.html and > follow instructions on how to resolve the stack trace. Resolved > stack trace is much more helpful in diagnosing the problem, so please do > resolve it > Trying to get some variables. > Some pointers may be invalid and cause the dump to abort... > thd->query at 0x676f6c6e is invalid pointer > thd->thread_id=138587896 > The manual page at http://www.mysql.com/doc/en/Crashing.html contains > information that should help you find out what is causing the crash. > ws1:/var/lib/mysql# > > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > User-mode-linux-user mailing list > User-mode-linux-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ User-mode-linux-user mailing list User-mode-linux-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
