forum.vmspython.org Forum Index forum.vmspython.org
Forum system
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

MySQL server gets a stack overflow error on startup

 
Post new topic   Reply to topic    forum.vmspython.org Forum Index -> MySQL for OpenVMS
View previous topic :: View next topic  
Author Message
berryman



Joined: 04 Sep 2009
Posts: 5

PostPosted: Fri Sep 04, 2009 7:45 pm    Post subject: MySQL server gets a stack overflow error on startup Reply with quote

After shutting down the MySQL server and then attempting to restart, the server aborts with a stack overflow error as shown below. Is this a known error or, more hopefully, is there a known solution?

090904 10:42:58 InnoDB: Started; log sequence number 0 76650839
090904 10:42:58 [Note] Recovering after a crash using mysql-bin
090904 10:42:58 [Note] Starting crash recovery...
090904 10:42:58 [Note] Crash recovery finished.
090904 10:42:59 [Note] Event Scheduler: Loaded 0 events
090904 10:42:59 [Note] /$2$DKA300/MYSQL051/VMS/BIN/mysqld.exe: ready for connections.
Version: '5.1.23-rc-log' socket: '' port: 3306 Source distribution
090904 10:42:59 [Note] Event Scheduler: scheduler thread started with id 1
%SYSTEM-F-STKOVF, stack overflow, PC=00000000003877D0, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
mysqld btr0cur btr_cur_search_to_nth_level
62708 0000000000000FC0 00000000003877D0
mysqld btr0pcur btr_pcur_open ? ?
mysqld btr0pcur btr_pcur_open_on_user_rec
52990 000000000000228C 000000000043B44C
mysqld dict0load dict_load_fields 56295 00000000000017CC 0000000000589F0C
mysqld dict0load dict_load_indexes 56504 0000000000002210 000000000058A950
mysqld dict0load dict_load_table 56665 0000000000002A98 000000000058B1D8
mysqld dict0load dict_load_foreign 57002 0000000000003B98 000000000058C2D8
mysqld dict0load dict_load_foreigns 57128 00000000000040F8 000000000058C838
mysqld dict0load dict_load_table 56675 0000000000002AE4 000000000058B224
mysqld dict0load dict_load_foreign 57002 0000000000003B98 000000000058C2D8
mysqld dict0load dict_load_foreigns 57128 00000000000040F8 000000000058C838
mysqld dict0load dict_load_table 56675 0000000000002AE4 000000000058B224
mysqld dict0load dict_load_table_on_id
56788 0000000000002EF4 000000000058B634
mysqld dict0dict dict_table_get_on_id_low
47205 00000000000006D8 00000000007EC1B8
mysqld row0purge row_purge_parse_undo_rec
64487 0000000000000A68 0000000000417D28
mysqld row0purge 64574 0000000000417D28 0000000000000000
mysqld que0que que_thr_step 67347 0000000000001EF4 0000000000364A34
mysqld que0que que_run_threads_low 67410 00000000000022B4 0000000000364DF4
mysqld que0que 67446 0000000000364DF4 0000000000000000
mysqld trx0purge trx_purge 63198 0000000000001F3C 000000000083320C
mysqld srv0srv srv_master_thread 70547 0000000000003B48 0000000000825778
PTHREAD$RTL 0 000000000005763C FFFFFFFF80E7763C
PTHREAD$RTL 0 00000000000437A0 FFFFFFFF80E637A0
0 0000000000000000 0000000000000000
PTHREAD$RTL ? ?
0 FFFFFFFF8037DCE4 FFFFFFFF8037DCE4
%TRACE-I-END, end of TRACE stack dump
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 618

PostPosted: Tue Sep 08, 2009 10:11 am    Post subject: Reply with quote

Can you post more informations:
platform, vms version, patch level, it is the first time you stop/start MySQL,
does a retry of the startup solve the problem, etc...?


JF
Back to top
View user's profile Send private message Send e-mail Visit poster's website
berryman



Joined: 04 Sep 2009
Posts: 5

PostPosted: Tue Sep 08, 2009 4:28 pm    Post subject: Reply with quote

The platform is OpenVMS Alpha V8.3 (on a DS10 if you want hardware info).

VMS, itself, has been patched up to update 8. This is not the first time MySQL has been stopped and restarted (always via the mysqladmin shutdown command). Once the error occurs, nothing I can think of doing resolves the issue. The stack overflow occurs on every startup thereafter. The only thing I was able to do to get MySQL back up and running was to remove the DATA directory and recreate the entire database from scratch. However, I have saved the failing copy of the database and can recreate the problem at will.
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 618

PostPosted: Tue Sep 08, 2009 4:53 pm    Post subject: Reply with quote

Thanks for the informations.

We plan to release a new MySQL kit, latest 5.1 and fixes for the myisam problem on OpenVMS.
I expect to build an AXP kit before the end of the month.
So, if you can, keep the offending database, it will be interesting to try to use it with the forthcoming version.

I can put somewhere the news mysql* exe if you want to try.

JF
Back to top
View user's profile Send private message Send e-mail Visit poster's website
berryman



Joined: 04 Sep 2009
Posts: 5

PostPosted: Tue Sep 08, 2009 6:31 pm    Post subject: Reply with quote

Yes, I would happy to test with a new kit to see what impact that has on this problem.

On a (probably) unrelated note, when I built PHP 5.2.10, I discovered a problem with the MySQL interface. When I built against either a 5.1.23 or a 5.1.22 library, the connection to the MySQL server would abort with a CR_SERVER_LOST (2013) error and all transactions would fail. Building against the same 4.1.14 version that HP uses, or with the 5.1.11-beta library does not exhibit this error. Are you acquainted with any errors of this nature? If not, I'd like to build PHP using the new version when it is ready and see if the problem still exists. If it does, I'd be very interested in a collaboration to try to track down where the problem lies.
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 618

PostPosted: Mon Sep 14, 2009 2:54 pm    Post subject: Reply with quote

I have put a kit online:

I have put in
http://www.vmsmysql.org/anonymous/kits/tmp/axp/

a mysql 5.1.36 axp kit

I have done very few test.


Before install the new kit don't forget to stop mysql...

you need to upgrade the system table:
start mysql (@mysql051_root:[vms]mysql_startup)

$ set def mysql051_root:[scripts]
$ mysql -uroot -pxxxx mysql
mysql> source mysql_fix_privilege_tables.sql
.
.
mysqL> source fill_help_tables.sql
.
.


then stop and restart mysql


JF
Back to top
View user's profile Send private message Send e-mail Visit poster's website
berryman



Joined: 04 Sep 2009
Posts: 5

PostPosted: Mon Sep 14, 2009 6:14 pm    Post subject: Reply with quote

I fetched this kit and attempted to build PHP against it. There appears to be a VMS specific module missing from the .OLB libraries as the following 3 references remain undefined:

VMS_SHARED_CONTROL
VMS_SHARED_OPEN
VMS_SHARED_PRECLOSE
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 618

PostPosted: Mon Sep 14, 2009 7:36 pm    Post subject: Reply with quote

That correct,

it's a new module which contains the code to fix the myIsam problems.
You can take a look in the repository (http://hg.vmsmysql.org/)

I have put online a new kit with the updated libraries.

Sorry,


JF
Back to top
View user's profile Send private message Send e-mail Visit poster's website
berryman



Joined: 04 Sep 2009
Posts: 5

PostPosted: Tue Sep 15, 2009 12:13 am    Post subject: Reply with quote

Ok, I have now confirmed that this library has the same problem that 5.1.22 and 5.1.23 have; once the connection is established to the server, the very next call via the library reports that the connection has been lost.

I have done some very preliminary debugging that indicates that the MySQL library may be issuing a non-blocking socket call and not correctly handling the fact that there is no data yet. I stress that this is preliminary. I believe I saw an ERRNO code of 35 somewhere in the transaction but need to properly confirm this.
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 618

PostPosted: Wed Sep 23, 2009 2:14 pm    Post subject: Reply with quote

Thanks for reporting.

What seem strange is that all clients use the same library without any (known) problems...

JF
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    forum.vmspython.org Forum Index -> MySQL for OpenVMS All times are GMT + 2 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group