Groups > Novell > MySQL with Novell > Re: Abend caused by LIBMYSQL.NLM




Abend caused by LIBMYSQL.NLM

Abend caused by LIBMYSQL.NLM
Tue, 24 Jan 2006 21:42:57 GMT
Hello,

I need some help in trying to resolve the following abend.

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.04

Server MYSQL halted Monday, 23 January 2006  12:43:02.717 pm
Abend 1 on P01: Server-5.70.04: Page Fault Processor Exception (Error code
00000000)

Registers:
    CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
    EAX = 77F882F4 EBX = 00000000 ECX = 77F882F4 EDX = 0000006F
    ESI = 00000000 EDI = 77F882F4 EBP = 7791FF40 ESP = 7791FF20
    EIP = 8682100D FLAGS = 00010246 
    8682100D FF5604         CALL    near ptr [ESI+04]=?
    EIP in LIBMYSQL.NLM at code start +0000D00Dh
    Access Location: 0x00000004

The violation occurred while processing the following instruction:
8682100D FF5604         CALL    near ptr [ESI+04]
86821010 83C41C         ADD     ESP, 0000001C
86821013 0FBEC0         MOVSX   EAX, AL
86821016 EB00           JMP     86821018
86821018 8D65FC         LEA     ESP, [EBP-04]
8682101B 5E             POP     ESI
8682101C 5D             POP     EBP
8682101D C3             RET     
LIBMYSQL.NLM|mysql_real_query:
8682101E 55             PUSH    EBP
8682101F 89E5           MOV     EBP, ESP



Running process: PERL.NLM's main thread Process
Thread Owned by NLM: PERL.NLM
Stack pointer: 779202A0
OS Stack limit: 778A0D20
Scheduling priority: 67371008
Wait state: 3030070  Yielded CPU
Stack: --77F882F4  ?
       --00000003  ?
       --00000000  ?
       --00000000  ?
       --7824C8E0  ?
       --000006B6  ?
       --00000001  ?
       --7824C8E0  ?
       --7791FF58  ?
       86821030  (LIBMYSQL.NLM|mysql_real_query+12)
       --77F882F4  ?
       --7824C8E0  ?
       --000006B6  ?
       --7824C8E0  ?
       --7791FF88  ?
       9336A761  (PMYSQL.NLM|PMYSQL@mysql_st_internal_execute+A1)
       --77F882F4  ?
       --7824C8E0  ?
       --000006B6  ?
       --0000006F  ?
       --00000000  ?
       --00000002  ?
       --000006B6  ?
       --86C26944  ?
       --00000000  ?
       --00000002  ?
       --7791FFE8  ?
       93370721  (PMYSQL.NLM|PMYSQL@XS_DBD__mysql__db_do+111)
       --77879060  ?
       --86C26944  ?
       --86C14384  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --7791FFD8  ?
       --77F882F4  ?
       --00000000  ?
       --86C26944  ?
       --78046300  ?
       --00000002  ?
       --00000000  ?
       --77F882A0  ?
       --00000000  ?
       --86C14384  ?
       --86C26944  ?
       --00000001  ?
       --00000000  ?
       --77879060  ?
       --00000000  ?
       --00000001  ?
       --77920268  ?
       933608A8  (DBI.NLM|DBI@XS_DBI_dispatch+24C8)
       --77879060  ?
       --86C25918  ?
       --78046300  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --86C25884  ?
       --77F882A0  ?
       --00003201  ?
       --78046300  ?
       --00000000  ?
       --00000000  ?
       --00000001  ?
       --00000000  ?
       --00000000  ?
       --FFFFFFFF  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --86BDE278  ?
       --9211E7B4  ?
       --86C14384  ?
       --86C26944  ?
       --77F9DB60  ?
       --00000002  ?
       --00000001  ?
       --00000000  ?
       --920B94A8  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       --00000000  ?
       
Additional Information:
    The CPU encountered a problem executing code in LIBMYSQL.NLM.  The
problem may be in that module or in data passed to that module by a
process owned by PERL.NLM.

Thanks
Peter Culshaw
Post Reply
Re: Abend caused by LIBMYSQL.NLM
Wed, 25 Jan 2006 00:13:05 GMT
Hi Peter,
please see:
Subject: Re: mysqlhotcopy.pl abends the server
From: KMurugan <murugankg@yahoo.com>
Newsgroups: novell.devsup.perl,novell.devsup.mysql

Guenter.

pculshaw@fantech.com.au (fantech) wrote in news:BbxBf.34$IK1.20@prv-
forum2.provo.novell.com:

> Hello,
> 
> I need some help in trying to resolve the following abend.
> 
> Novell Open Enterprise Server, NetWare 6.5
> PVER: 6.50.04
> 
> Server MYSQL halted Monday, 23 January 2006  12:43:02.717 pm
> Abend 1 on P01: Server-5.70.04: Page Fault Processor Exception (Error 
code
> 00000000)
> 
> Registers:
>     CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
>     EAX = 77F882F4 EBX = 00000000 ECX = 77F882F4 EDX = 0000006F
>     ESI = 00000000 EDI = 77F882F4 EBP = 7791FF40 ESP = 7791FF20
>     EIP = 8682100D FLAGS = 00010246 
>     8682100D FF5604         CALL    near ptr [ESI+04]=?
>     EIP in LIBMYSQL.NLM at code start +0000D00Dh
>     Access Location: 0x00000004
> 
> The violation occurred while processing the following instruction:
> 8682100D FF5604         CALL    near ptr [ESI+04]
> 86821010 83C41C         ADD     ESP, 0000001C
> 86821013 0FBEC0         MOVSX   EAX, AL
> 86821016 EB00           JMP     86821018
> 86821018 8D65FC         LEA     ESP, [EBP-04]
> 8682101B 5E             POP     ESI
> 8682101C 5D             POP     EBP
> 8682101D C3             RET     
> LIBMYSQL.NLM|mysql_real_query:
> 8682101E 55             PUSH    EBP
> 8682101F 89E5           MOV     EBP, ESP
> 
> 
> 
> Running process: PERL.NLM's main thread Process
> Thread Owned by NLM: PERL.NLM
> Stack pointer: 779202A0
> OS Stack limit: 778A0D20
> Scheduling priority: 67371008
> Wait state: 3030070  Yielded CPU
> Stack: --77F882F4  ?
>        --00000003  ?
>        --00000000  ?
>        --00000000  ?
>        --7824C8E0  ?
>        --000006B6  ?
>        --00000001  ?
>        --7824C8E0  ?
>        --7791FF58  ?
>        86821030  (LIBMYSQL.NLM|mysql_real_query+12)
>        --77F882F4  ?
>        --7824C8E0  ?
>        --000006B6  ?
>        --7824C8E0  ?
>        --7791FF88  ?
>        9336A761  (PMYSQL.NLM|PMYSQL@mysql_st_internal_execute+A1)
>        --77F882F4  ?
>        --7824C8E0  ?
>        --000006B6  ?
>        --0000006F  ?
>        --00000000  ?
>        --00000002  ?
>        --000006B6  ?
>        --86C26944  ?
>        --00000000  ?
>        --00000002  ?
>        --7791FFE8  ?
>        93370721  (PMYSQL.NLM|PMYSQL@XS_DBD__mysql__db_do+111)
>        --77879060  ?
>        --86C26944  ?
>        --86C14384  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --7791FFD8  ?
>        --77F882F4  ?
>        --00000000  ?
>        --86C26944  ?
>        --78046300  ?
>        --00000002  ?
>        --00000000  ?
>        --77F882A0  ?
>        --00000000  ?
>        --86C14384  ?
>        --86C26944  ?
>        --00000001  ?
>        --00000000  ?
>        --77879060  ?
>        --00000000  ?
>        --00000001  ?
>        --77920268  ?
>        933608A8  (DBI.NLM|DBI@XS_DBI_dispatch+24C8)
>        --77879060  ?
>        --86C25918  ?
>        --78046300  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --86C25884  ?
>        --77F882A0  ?
>        --00003201  ?
>        --78046300  ?
>        --00000000  ?
>        --00000000  ?
>        --00000001  ?
>        --00000000  ?
>        --00000000  ?
>        --FFFFFFFF  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --86BDE278  ?
>        --9211E7B4  ?
>        --86C14384  ?
>        --86C26944  ?
>        --77F9DB60  ?
>        --00000002  ?
>        --00000001  ?
>        --00000000  ?
>        --920B94A8  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        --00000000  ?
>        
> Additional Information:
>     The CPU encountered a problem executing code in LIBMYSQL.NLM.  The
> problem may be in that module or in data passed to that module by a
> process owned by PERL.NLM.
> 
> Thanks
> Peter Culshaw
> 
> 
Post Reply
Re: Abend caused by LIBMYSQL.NLM
Sun, 29 Jan 2006 22:34:00 GMT
Hi,

In checking the previous messages as you suggested I found the following.

'The updated modules for Perl 5.8.4 and MySQL 4.1.10 (I'm using 4.1.14a 
and about to upgrade to 4.1.15a) appear to have fixed the abends I was 
experiencing when attempting to use the mysqlhotcopy script.'

We are currently using Perl 5.8.4 and MySQL 4.1.16.

So your suggestion is not valid with our situation, still require help in
resolving this issue.

Thanks,
Peter Culshaw
Fantech Pty Ltd


Guenter Knauf, DevNet SysOp 32 wrote:

> Hi Peter,
> please see:
> Subject: Re: mysqlhotcopy.pl abends the server
> From: KMurugan <murugankg@yahoo.com>
> Newsgroups: novell.devsup.perl,novell.devsup.mysql

> Guenter.

> pculshaw@fantech.com.au (fantech) wrote in news:BbxBf.34$IK1.20@prv-
> forum2.provo.novell.com:

> > Hello,
> > 
> > I need some help in trying to resolve the following abend.
> > 
> > Novell Open Enterprise Server, NetWare 6.5
> > PVER: 6.50.04
> > 
> > Server MYSQL halted Monday, 23 January 2006  12:43:02.717 pm
> > Abend 1 on P01: Server-5.70.04: Page Fault Processor Exception (Error

> code
> > 00000000)
> > 
> > Registers:
> >     CS = 0060 DS = 007B ES = 007B FS = 007B GS = 007B SS = 0068
> >     EAX = 77F882F4 EBX = 00000000 ECX = 77F882F4 EDX = 0000006F
> >     ESI = 00000000 EDI = 77F882F4 EBP = 7791FF40 ESP = 7791FF20
> >     EIP = 8682100D FLAGS = 00010246 
> >     8682100D FF5604         CALL    near ptr [ESI+04]=?
> >     EIP in LIBMYSQL.NLM at code start +0000D00Dh
> >     Access Location: 0x00000004
> > 
> > The violation occurred while processing the following instruction:
> > 8682100D FF5604         CALL    near ptr [ESI+04]
> > 86821010 83C41C         ADD     ESP, 0000001C
> > 86821013 0FBEC0         MOVSX   EAX, AL
> > 86821016 EB00           JMP     86821018
> > 86821018 8D65FC         LEA     ESP, [EBP-04]
> > 8682101B 5E             POP     ESI
> > 8682101C 5D             POP     EBP
> > 8682101D C3             RET     
> > LIBMYSQL.NLM|mysql_real_query:
> > 8682101E 55             PUSH    EBP
> > 8682101F 89E5           MOV     EBP, ESP
> > 
> > 
> > 
> > Running process: PERL.NLM's main thread Process
> > Thread Owned by NLM: PERL.NLM
> > Stack pointer: 779202A0
> > OS Stack limit: 778A0D20
> > Scheduling priority: 67371008
> > Wait state: 3030070  Yielded CPU
> > Stack: --77F882F4  ?
> >        --00000003  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --7824C8E0  ?
> >        --000006B6  ?
> >        --00000001  ?
> >        --7824C8E0  ?
> >        --7791FF58  ?
> >        86821030  (LIBMYSQL.NLM|mysql_real_query+12)
> >        --77F882F4  ?
> >        --7824C8E0  ?
> >        --000006B6  ?
> >        --7824C8E0  ?
> >        --7791FF88  ?
> >        9336A761  (PMYSQL.NLM|PMYSQL@mysql_st_internal_execute+A1)
> >        --77F882F4  ?
> >        --7824C8E0  ?
> >        --000006B6  ?
> >        --0000006F  ?
> >        --00000000  ?
> >        --00000002  ?
> >        --000006B6  ?
> >        --86C26944  ?
> >        --00000000  ?
> >        --00000002  ?
> >        --7791FFE8  ?
> >        93370721  (PMYSQL.NLM|PMYSQL@XS_DBD__mysql__db_do+111)
> >        --77879060  ?
> >        --86C26944  ?
> >        --86C14384  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --7791FFD8  ?
> >        --77F882F4  ?
> >        --00000000  ?
> >        --86C26944  ?
> >        --78046300  ?
> >        --00000002  ?
> >        --00000000  ?
> >        --77F882A0  ?
> >        --00000000  ?
> >        --86C14384  ?
> >        --86C26944  ?
> >        --00000001  ?
> >        --00000000  ?
> >        --77879060  ?
> >        --00000000  ?
> >        --00000001  ?
> >        --77920268  ?
> >        933608A8  (DBI.NLM|DBI@XS_DBI_dispatch+24C8)
> >        --77879060  ?
> >        --86C25918  ?
> >        --78046300  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --86C25884  ?
> >        --77F882A0  ?
> >        --00003201  ?
> >        --78046300  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000001  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --FFFFFFFF  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --86BDE278  ?
> >        --9211E7B4  ?
> >        --86C14384  ?
> >        --86C26944  ?
> >        --77F9DB60  ?
> >        --00000002  ?
> >        --00000001  ?
> >        --00000000  ?
> >        --920B94A8  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        --00000000  ?
> >        
> > Additional Information:
> >     The CPU encountered a problem executing code in LIBMYSQL.NLM. 
The
> > problem may be in that module or in data passed to that module by a
> > process owned by PERL.NLM.
> > 
> > Thanks
> > Peter Culshaw
> > 
> >

Post Reply
Re: Abend caused by LIBMYSQL.NLM
Mon, 30 Jan 2006 03:03:22 GMT
Hi Peter,

pculshaw@fantech.com.au (fantech) wrote in news:spbDf.2031$I_5.568@prv-
forum2.provo.novell.com:

> Hi,
> 
> In checking the previous messages as you suggested I found the following.
> 
> 'The updated modules for Perl 5.8.4 and MySQL 4.1.10 (I'm using 4.1.14a 
> and about to upgrade to 4.1.15a) appear to have fixed the abends I was 
> experiencing when attempting to use the mysqlhotcopy script.'
> 
> We are currently using Perl 5.8.4 and MySQL 4.1.16.
> 
> So your suggestion is not valid with our situation, still require help in
> resolving this issue.
sorry but cant follow up: did you now test this update?

Post Reply
about | contact