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 

phpbb and mysql errors
Goto page 1, 2, 3, 4  Next
 
Post new topic   Reply to topic    forum.vmspython.org Forum Index -> MySQL for OpenVMS
View previous topic :: View next topic  
Author Message
rft



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Wed Jun 20, 2007 9:45 pm    Post subject: phpbb and mysql errors Reply with quote

We had mysql and phpbb working well for several months and then some application caused a serious crash in mysql that left the innodb database in an unrecoverable state so that we could get mysql to start. Unfortunately we had no useable backups.

We wiped the mysql databases and re-installed mysql and phpbb. Things work but we get database corruptions that require running mysqlcheck to repair various of the tables used by phpbb.

When we try to administer the board and return to the forum we get the following error:

Code:

phpBB : Critical Error

Error updating sessions table

DEBUG MODE

SQL Error : 1034 Incorrect key file for table 'phpbb_users'; try to repair it

UPDATE phpbb_users SET user_session_time = 1182370539, user_session_page = 0 WHERE user_id = 2

Line : 360
File : sessions.php


The repair yields the following messages:

Code:

SWING > mysqlcheck --auto-repair phpbb_masc -u xxxxxxxxxxx
phpbb_masc.phpbb_auth_access                       OK
phpbb_masc.phpbb_banlist                           OK
phpbb_masc.phpbb_categories                        OK
phpbb_masc.phpbb_config                            OK
phpbb_masc.phpbb_confirm                           OK
phpbb_masc.phpbb_disallow                          OK
phpbb_masc.phpbb_easymod                           OK
phpbb_masc.phpbb_easymod_processed_files           OK
phpbb_masc.phpbb_forum_prune                       OK
phpbb_masc.phpbb_forums                            OK
phpbb_masc.phpbb_groups                            OK
phpbb_masc.phpbb_inline_ads                        OK
phpbb_masc.phpbb_posts                             OK
phpbb_masc.phpbb_posts_text                        OK
phpbb_masc.phpbb_privmsgs                          OK
phpbb_masc.phpbb_privmsgs_text                     OK
phpbb_masc.phpbb_ranks                             OK
phpbb_masc.phpbb_search_results                    OK
phpbb_masc.phpbb_search_wordlist                   OK
phpbb_masc.phpbb_search_wordmatch                  OK
phpbb_masc.phpbb_sessions
warning  : Size of indexfile is: 18432      Should be: 8192
status   : OK
phpbb_masc.phpbb_sessions_keys                     OK
phpbb_masc.phpbb_smilies                           OK
phpbb_masc.phpbb_themes                            OK
phpbb_masc.phpbb_themes_name                       OK
phpbb_masc.phpbb_topics                            OK
phpbb_masc.phpbb_topics_watch                      OK
phpbb_masc.phpbb_user_group                        OK
phpbb_masc.phpbb_users
warning  : Table is marked as crashed
error    : Checksum for key:  2 doesn't match checksum for records
error    : Corrupt
phpbb_masc.phpbb_vote_desc                         OK
phpbb_masc.phpbb_vote_results                      OK
phpbb_masc.phpbb_vote_voters                       OK
phpbb_masc.phpbb_words                             OK

Repairing tables
phpbb_masc.phpbb_users                             OK
SWING >


Did we miss some mysql parameters?
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 623

PostPosted: Thu Jun 21, 2007 8:28 pm    Post subject: Reply with quote

Which version of MySQL ?

You may try the latest 4.1 (4.1.14) or try 5.1.11 which is a beta but was reported to work better.

Are you sure that your table are use InnoDB?

I also strongly suggest to do backup on a regular basis.

I can post a procedure I wrote to backup all my database twice a day.


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



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Thu Jun 21, 2007 9:24 pm    Post subject: Reply with quote

JF,

We are using MYSQL V4.1.14-log

The tables are not INNODB. They are MYISAM.

We are using other php/mysql applications with no problems, e.g. JOOMLA (although we did have to force use of INNODB) and MEDIAWIKI.

Code:

phpBB : Critical Error

Error updating last visit time

DEBUG MODE

SQL Error : 1034 Incorrect key file for table 'phpbb_users'; try to repair it

UPDATE phpbb_users SET user_session_time = 1182453966, user_session_page = 0, user_lastvisit = 1182383435 WHERE user_id = 2

Line : 202
File : sessions.php


Code:

SWING > mysqlcheck --auto-repair phpbb_masc phpbb_users -u xxxxx
phpbb_masc.phpbb_users
warning  : Table is marked as crashed
error    : Checksum for key:  2 doesn't match checksum for records
error    : Corrupt

Repairing tables
phpbb_masc.phpbb_users
warning  : Number of rows changed from 4 to 3
status   : OK


Last edited by rft on Thu Jun 21, 2007 9:31 pm; edited 1 time in total
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 623

PostPosted: Thu Jun 21, 2007 9:29 pm    Post subject: Reply with quote

Quote:
The tables are not INNODB. They are MYISAM.

This is the problem, MyIsam is not reliable on VMS, this is an old but tricky problem, 5.1 seem to have less problem with MyISAM but I'm not sure if it is completely error prone.

Change your table to InnoDB and I expect that your problem will disappear.


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



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Thu Jun 21, 2007 9:51 pm    Post subject: Reply with quote

Have altered the table to INNODB.

Hopefully the problem vanishes.

Is there a way to force INNODB as the default instead of MYISAM?
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 623

PostPosted: Thu Jun 21, 2007 9:58 pm    Post subject: Reply with quote

Quote:
s there a way to force INNODB as the default instead of MYISAM?

On OpenVMS the default is InnoDB but it the creation script force MyISAM then a MyISAM table is create.

If you look at the procedure run_mysqld.com you will notice the qualifier
Code:
 --default-storage-engine=InnoDB


JF

You may run MySQL 5.1 and 4.1 on the same system simultaneous, just use 2 different port.
I do this on my systems (Alpha and Itanium)
Back to top
View user's profile Send private message Send e-mail Visit poster's website
rft



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Thu Jun 21, 2007 10:26 pm    Post subject: Reply with quote

We have the InnoDB default in the command file, but all new tables are created using MYISAM by default.

The following is the run_mysqld.com file:

Code:

$ set process/parse=extend
$ mysqld :== $ mysql_root:[vms.bin]mysqld
$ define /noLOG TMPDIR "/mysql_root/mysql_server/tmp"
$ define /noLOG DECC$EFS_CASE_PRESERVE enable
$ define /noLOG DECC$EFS_CHARSET enable
$ define /noLOG DECC$READDIR_DROPDOTNOTYPE enable
$ define /noLOG DECC$FILENAME_UNIX_REPORT enable
$ define /noLOG DECC$FILE_SHARING enable
$ define /noLOG DECC$EFS_CASE_SPECIAL disable
$ define /noLOG DECC$FILENAME_UNIX_ONLY enable
$ define /noLOG DECC$ALLOW_REMOVE_OPEN_FILES enable
$ define /noLOG TCPIP$SELECT_ABORT_ON_SIGNAL enable
$! mysqld  --default-storage-engine=InnoDB --old-passwords --innodb-safe-binlog>
$ mysqld  --default-storage-engine=InnoDB --innodb-safe-binlog --ansi --myisam->
$ delete mysql_root:[mysql_server.tmp]*.*.*


Code:

070620 16:39:12  InnoDB: Started; log sequence number 0 60236
/ASTC08$DKA100/SYS0/SYSCOMMON/MYSQL/VMS/BIN/mysqld.exe: ready for connections.
Version: '4.1.14-log'  socket: ''  port: 3306  Source distribution
070621 15:30:31 [Note] Found 3 of 4 rows when repairing './phpbb_masc/phpbb_use>
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 623

PostPosted: Thu Jun 21, 2007 10:41 pm    Post subject: Reply with quote

I suspect that the database creation script specified MyISAM for the various tables. I would be very surprised if not. Shocked


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



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Thu Jun 21, 2007 10:48 pm    Post subject: Reply with quote

Thank you for the help. We have appreciated the various ports that you have made available allowing us to leverage the advantages of OpenVMS into various web enabled applications.

The performance of php, mysql, and CWS (VAMP) has been most satisfactory.
Back to top
View user's profile Send private message
rft



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Wed Jun 27, 2007 5:24 am    Post subject: Problem Returned Reply with quote

MYSQL crashed with the following error in the log:

Code:
$   set noon
070620 16:39:12  InnoDB: Started; log sequence number 0 60236
/ASTC08$DKA100/SYS0/SYSCOMMON/MYSQL/VMS/BIN/mysqld.exe: ready for connections.
Version: '4.1.14-log'  socket: ''  port: 3306  Source distribution
070621 15:30:31 [Note] Found 3 of 4 rows when repairing './phpbb_masc/phpbb_users'
mysqld got signal 10;
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=12
max_connections=100
threads_connected=8
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 80383 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000003A, PC=FFFFFFFF80B13711, PS=0000001B

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 0000000000000005
                        Name   = 000000000000000C
                                 0000000000000000
                                 000000000000003A
                                 FFFFFFFF80B13711
                                 000000000000001B

    Register dump:
    R0  = 0000000000000000  R1  = FFFFFFFF84340400  R2  = 000000004000BED0
    R3  = 0000000001AB1E00  R4  = 0000000006AEE4C4  R5  = 0000000006AEDC70
    R6  = 0000000000000000  R7  = 0000000000000000  R8  = 0000000000000001
    R9  = 0000000006AEDC70  R10 = FFFFFFFF84197E20  R11 = 0000000000039990
    SP  = 0000000006AEDB70  TP  = 0000000006AF1300  R14 = 0000000000000004
    R15 = 00000000000081A4  R16 = 000000004000BFF0  R17 = 0000000006AEDB3C
    R18 = 0000000006AEDB30  R19 = 00000000000004FC  R20 = 000007FDBFFFCDC0
    R21 = FFFFFFFF842A59F0  R22 = 000000000000003A  R23 = 0000000006AEDB68
    R24 = 0000000000000010  R25 = 0010000002790001  R26 = 0000000006AEDB00
    R27 = 0000000006AEDB18  R28 = 000000000000003A  R29 = 0000000006AEDB70
    R30 = FFFFFFFF80B12E90  R31 = FFFFFFFF80B137CF  PC  = FFFFFFFF80B13711
    BSP/STORE = 0000000006AD6DD8 / 0000000006AD6DD8 PSR = 0000121308426030
    IIPA = FFFFFFFF80B13710
    B0  = FFFFFFFF80B136C0  B6  = FFFFFFFF800CD4A0  B7  = FFFFFFFF80B25480

    Interrupted Frame RSE Backing Store, Size = 45 registers

    R32 = 0000000006AEE4C4  R33 = 0000000006AEDC70  R34 = 000000000000000D
    R35 = 0000000000000003  R36 = 000000007FFF0278  R37 = 0000000000000001
    R38 = 0000000003FFFFFF  R39 = 0000000006AEDB60  R40 = FFFFFFFF844A4A00
    R41 = 0000000000000002  R42 = 0000000001AB1E00  R43 = 0000000006AEDB00
    R44 = 0000000006AEDB18  R45 = FFFFFFFF84197E20  R46 = 0000000000039990
    R47 = FFFFFFFF80B12E90  R48 = FFFFFFFF80B137CF  R49 = 000007FDBFFFCDC0
    R50 = FFFFFFFF842A59F0  R51 = 0000000006AEDB70  R52 = FFFFFFFF8038EB80
    R53 = C000000000000389  R54 = 0000000006AEDB80  R55 = 0000000001AB1E00
    R56 = FFFFFFFF82547620  R57 = 0000000000000000  R58 = 0000000000000000
    R59 = 0000000000000000  R60 = FFFFFFFF84197E20  R61 = 0000000000039990
    R62 = 000007FDBFFFCDC0  R63 = FFFFFFFF842A59F0  R64 = 0000000006AEDB00
    R65 = 0000000006AEDB18  R66 = 00000000000049D0  R67 = FFFFFFFF80B12E90
    R68 = FFFFFFFF80B137CF  R69 = DA0A96B9A0B39CA5  R70 = 72C7F52F77CEA321
    R71 = 58F4ADCAC211ECC0  R72 = 5139943D290E0119  R73 = 500B358E55A1C44E
    R74 = 962065231A995317  R75 = B8500506325C2F8A  R76 = AC36A901036629E6
%DELETE-W-SEARCHFAIL, error searching for MYSQL_ROOT:[MYSQL_SERVER.TMP]*.*;*
-RMS-E-FNF, file not found
  MYSQL_SERVER job terminated at 26-JUN-2007 07:25:26.29

  Accounting information:
  Buffered I/O count:             882495      Peak working set size:     117248
  Direct I/O count:                77031      Peak virtual size:         480432
  Page faults:                     11393      Mounted volumes:                0
  Charged CPU time:        0 00:04:40.02      Elapsed time:       5 14:46:16.45

When we attempt to restart the MYSQL server we get the following errors:
Code:
$   set noon
070626 22:24:09  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: cannot read directory ./joomla, error 17
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory ./joomla
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: cannot read directory ./joomla, error 17
.
.
.
InnoDB: cannot read directory ., error 17
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: cannot read directory ., error 17
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: cannot read directory ., error 17
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: cannot read directory ., error 17
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: cannot read directory ., error 17
InnoDB: Error: os_file_readdir_next_file() returned -1 in
InnoDB: directory .
InnoDB: Crash recovery may have failed for some .ibd files!
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
070626 22:24:13  InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 0 2140916.
InnoDB: Doing recovery: scanned up to log sequence number 0 2203915
070626 22:24:13  InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 1698994, file name ./astc08-bin.000004
070626 22:24:14  InnoDB: Flushing modified pages from the buffer pool...
070626 22:24:14  InnoDB: Started; log sequence number 0 2203915
070626 22:24:14 [ERROR] After InnoDB crash recovery, checking if the binary log './astc08-bin.000004' contains rolled back transactions which must be removed from it...
/ASTC08$DKA100/SYS0/SYSCOMMON/MYSQL/VMS/BIN/mysqld.exe: ready for connections.
Version: '4.1.14-log'  socket: ''  port: 3306  Source distribution
mysqld got signal 10;
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 = 80383 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000000003A, PC=FFFFFFFF80B13711, PS=0000001B

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 0000000000000005
                        Name   = 000000000000000C
                                 0000000000000000
                                 000000000000003A
                                 FFFFFFFF80B13711
                                 000000000000001B

    Register dump:
    R0  = 0000000000000000  R1  = FFFFFFFF84340400  R2  = 000000004000BED0
    R3  = 0000000001AB1E00  R4  = 0000000006B00AC4  R5  = 0000000006B00270
    R6  = 0000000000000000  R7  = 0000000000000000  R8  = 0000000000000001
    R9  = 0000000006B00270  R10 = FFFFFFFF84197E20  R11 = 0000000000039990
    SP  = 0000000006B00170  TP  = 0000000006B03300  R14 = 0000000000000004
    R15 = 00000000000081A4  R16 = 000000004000BFF0  R17 = 0000000006B0013C
    R18 = 0000000006B00130  R19 = 00000000000004FC  R20 = 000007FDBFFFCDC0
    R21 = FFFFFFFF842A59F0  R22 = 000000000000003A  R23 = 0000000006B00168
    R24 = 0000000000000010  R25 = 0010000002190001  R26 = 0000000006B00100
    R27 = 0000000006B00118  R28 = 000000000000003A  R29 = 0000000006B00170
    R30 = FFFFFFFF80B12E90  R31 = FFFFFFFF80B137CF  PC  = FFFFFFFF80B13711
    BSP/STORE = 0000000006AE8DD8 / 0000000006AE8DD8 PSR = 0000121308426030
    IIPA = FFFFFFFF80B13710
    B0  = FFFFFFFF80B136C0  B6  = FFFFFFFF800CD4A0  B7  = FFFFFFFF80B25480

    Interrupted Frame RSE Backing Store, Size = 45 registers

    R32 = 0000000006B00AC4  R33 = 0000000006B00270  R34 = 000000000000000D
    R35 = 0000000000000003  R36 = 000000007FFF0278  R37 = 0000000000000001
    R38 = 0000000003FFFFFF  R39 = 0000000006B00160  R40 = FFFFFFFF844A4A00
    R41 = 0000000000000002  R42 = 0000000001AB1E00  R43 = 0000000006B00100
    R44 = 0000000006B00118  R45 = FFFFFFFF84197E20  R46 = 0000000000039990
    R47 = FFFFFFFF80B12E90  R48 = FFFFFFFF80B137CF  R49 = 000007FDBFFFCDC0
    R50 = FFFFFFFF842A59F0  R51 = 0000000006B00170  R52 = FFFFFFFF8038EB80
    R53 = C000000000000389  R54 = 0000000006B00180  R55 = 0000000001AB1E00
    R56 = FFFFFFFF82547620  R57 = 0000000000000000  R58 = 0000000000000000
    R59 = 0000000000000000  R60 = FFFFFFFF84197E20  R61 = 0000000000039990
    R62 = 000007FDBFFFCDC0  R63 = FFFFFFFF842A59F0  R64 = 0000000006B00100
    R65 = 0000000006B00118  R66 = 00000000000049D0  R67 = FFFFFFFF80B12E90
    R68 = FFFFFFFF80B137CF  R69 = DA0A96B9A0B39CA5  R70 = 72C7F52F77CEA321
    R71 = 58F4ADCAC211ECC0  R72 = 5139943D290E0119  R73 = 500B358E55A1C44E
    R74 = 962065231A995317  R75 = B8500506325C2F8A  R76 = AC36A901036629E6
%DELETE-W-SEARCHFAIL, error searching for MYSQL_ROOT:[MYSQL_SERVER.TMP]*.*;*
-RMS-E-FNF, file not found
  MYSQL_SERVER job terminated at 26-JUN-2007 22:24:16.01

  Accounting information:
  Buffered I/O count:               1187      Peak working set size:      64752
  Direct I/O count:                 1178      Peak virtual size:         435344
  Page faults:                      9149      Mounted volumes:                0
  Charged CPU time:        0 00:00:01.71      Elapsed time:       0 00:00:08.54
Back to top
View user's profile Send private message
jfp



Joined: 12 Jul 2004
Posts: 623

PostPosted: Wed Jun 27, 2007 5:42 pm    Post subject: Reply with quote

You may try to check/repair your database using the tools provide.
do
Code:
$ show symbol mysql*

to view all the commands.


4.1.14 is know to corrupt MyISAM table very often.
May be can you try to install 5.1.11.

There are also a bug in 4.1.14 whi h can produce some similar crash (bug VMS C compiler). There is a patch which can be download in the usual directory.

Do you have a backup Rolling Eyes

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



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Wed Jun 27, 2007 6:43 pm    Post subject: Reply with quote

The database is part of our normal VMS backup. This would allow us to get the complete database at the time of the backup (although InnoDB's transaction stuff might cause a problem).

What we were able to do (using information in the MySQL documentation):

1) add the following to the my.cnf file:

Code:

[mysqld]
innodb_force_recovery = 4


2) We then started MySQL. It did not crash. We couldn't do any database modifications.

3) We dumped the database using the following command:

Code:

$ assign/user mysql.dmp
$ mysqldump --all-databases - u xxxxxx


4) We stopped MySQL using the following command:

Code:

$ mysqladmin shutdown -u xxxxxx


5) We restored the old my.cnf file.

6) In the MySQL Data area we deleted:

Code:

$ del *_bin.*;*         ! all of the binary log files
$ del ib*.*;*             ! all of InnoDB files


7) We deleted all of the .frm fiels in the subdirectories for those databases that are Innodb.

8) Restarted MySQL

9) Reloaded the databases:

Code:

$ mysql -u xxxxx
mysql> source mysql.dmp
mysql> exit


Everything worked without any problems. We will write a batch file to run every night that will create a database dump. It's not perfect, but will allow us to get close.

We would love to learn why this occurs. Nothing has changed with respect to software. As our comfort has grown with MySQL (now very much gone), we have added various new applications, e.g.

Joomla - CMS system - one file needs to be edited to force Innodb as the database. Otherwise everything works out of the "box".

MediaWiki - works out of the "box".

IlohaMail - Web email client - works out of the "box".

phpbb - works out of the "box".

Among many other appliations.

We have written a Fortran API to interface with MySQL and are looking at transitioning form RMS to MySQL so that a common database might be used on all platforms. Unfortunately, these crashes are making us gun shy.
Back to top
View user's profile Send private message
rft



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Wed Jun 27, 2007 6:49 pm    Post subject: Reply with quote

jfp wrote:
4.1.14 is know to corrupt MyISAM table very often.
May be can you try to install 5.1.11.

There are also a bug in 4.1.14 whi h can produce some similar crash (bug VMS C compiler). There is a patch which can be download in the usual directory.

Where can I find 5.1.11?

Is it compatible with PHP and CWS 1.3?

At least with all of the crashes of MySQL, etc. we haven't had to reboot and Apache (CWS) and php continued to work for those applications that don't use MySQL. [We have a lot of applications that use flat files to create databases.] One has to love OpenVMS!
Back to top
View user's profile Send private message
bisonmalembouche



Joined: 01 Jun 2005
Posts: 74

PostPosted: Thu Jun 28, 2007 3:52 pm    Post subject: at the download area Reply with quote

You will find it for axp simply at
http://www.pi-net.dyndns.org/anonymous/kits/axp/
Back to top
View user's profile Send private message Send e-mail
rft



Joined: 20 Jun 2007
Posts: 43
Location: Massachusetts

PostPosted: Mon Jul 02, 2007 5:18 am    Post subject: Reply with quote

we have downloaded the kit, but we are running on IA64 so the AXP V5.1 is of little help.

We are still getting crashes and corruption of InnoDB tables/databases. This is started ahppening within the last two weeks. Until then mysql was very stable. I don't see anything new on the system.

The following is the log output:

Code:
/ASTC08$DKA100/SYS0/SYSCOMMON/MYSQL/VMS/BIN/mysqld.exe: ready for connections.
Version: '4.1.14-log'  socket: ''  port: 3306  Source distribution
mysqld got signal 10;
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=2
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 = 80383>
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000000>

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 0000000000000005
                        Name   = 000000000000000C
                                 0000000000000000
                                 000000000000003A
                                 FFFFFFFF80B13711
                                 000000000000001B

    Register dump:
    R0  = 0000000000000000  R1  = FFFFFFFF84340400  R2  = 000000004000BED0
    R3  = 0000000001AB1E00  R4  = 0000000006AEE4C4  R5  = 0000000006AEDC70
    R6  = 0000000000000000  R7  = 0000000000000000  R8  = 0000000000000001
    R9  = 0000000006AEDC70  R10 = FFFFFFFF84197E20  R11 = 0000000000039990
    SP  = 0000000006AEDB70  TP  = 0000000006AF1300  R14 = 0000000000000004
    R15 = 00000000000081A4  R16 = 000000004000BFF0  R17 = 0000000006AEDB3C



Any suggestions on what is wrong?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    forum.vmspython.org Forum Index -> MySQL for OpenVMS All times are GMT + 2 Hours
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
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