headers
joea@j4computers.com | 1 Jun 2008 21:02
Favicon

Re: NW 6.5 BackupExec 9.2 hangs server

FWIW, reinstalling BE did not resolve the problem.

Renamed the bexec folder on SYS and reinstalled BW "from scratch".  Works fine now.

joe a.

>>> On 5/27/2008 at 6:18 AM, joea <at> j4computers.com wrote:
> 
> No, of course not.  They are on the RAID card, as in O.
> 
> joe a.
> 
> >>> On 5/27/2008 at 1:59 AM, Randy Grein <randygrein <at> comcast.net> wrote:
> > You didn't put the new drives on the tape SCSI channel, did you?
> > 
> > Randy Grein, Master CNE, CCNA
> > 
> > On May 26, 2008, at 7:56 AM, joea <at> j4computers.com wrote:
> > 
> >> Have a NW 6.5 sp5 server that had been running backps flawlessly.   
> >> One day, the server hung.  I mean, it would not respond to pings.  
> >> The server console seemed "up", but any attempt to load a module, or  
> >> do anything at all, simply hung the console.  Could get into  
> >> debugger to quit.
> >>
> >> The Tape backup seems to be at fault.  Have changed the drive, scsi  
> >> controller and cables.  Have updated to latest BE 9.2.
> >>
> >> The tape log is incomplete,  last entry being "backup set ended at"  
> >> blah.  Yet, I happened to be watching the job, remotely, and know it
(Continue reading)

Permalink | Reply | 0 comments |
headers
Colin Connolly | 2 Jun 2008 01:27
Picon
Picon

Tcopy error message

I need to copy the trustee rights on a folder & subdirs on an old NW5.1 server onto a copy of 
the same folder structure on a NW6.5 server (different tree). I used the SCMT to migrate the 
data, but SCMT couldn't keep the trustee rights as the IDs are different on each user/group 
object on the new tree.

A colleague recommended looking at tcopy and it seems it should do the job for me but it's 
not working... 

With tcopy.exe in sys:\public on the old box, the root of the data 5.1 dir mapped as M: and 
the root of the copied dir on the NW6.5 box as N:  on my workstation, while logged in as 
Admin to both servers, I did:

tcopy m: n: /s and got:

NWAllocTempNDSirHandle(Destination) returned 89FF for DATA:MLADMIN51 on line #28

(MLADMIN51 is the target dir on the NW6.5 box)

I can't find this error message in either the Novell KB on using Google - can any one help? 
One reference I found to 89FF which was very old (referred to NW4.x) seemed to suggest 
that tcopy be used after ncopy... but doesn't the SCMT do the same job as ncopy would?

Or is there another, better, way to do this? The data folder needs to go over "as is" so a 
group of admin users can pick their folders/files out of it and populate a new admin filestore 
on the 6.5 box.

Thanks.

Colin
(Continue reading)

Permalink | Reply | 1 comment |
headers
Peter Van Lone | 2 Jun 2008 05:03
Picon

sigh -- abend log -- opinions?

Below are some snippets from an abend log. The server that is abending
has been fine for a couple years, until the admin put a second
processor in, and added ram. Now, even with the second processor out,
and ram back to what it was, it is abending (often "silently") and
having odd comms issues (ie, people can't login, then if they keep
trying they can, but then they get bumped out, again).

Please peruse and advise, if you have any ideas. The admin has
recently updated from sp6 to sp7 and he may (I'm not sure right now)
have updated to the post sp7 winsock and clib. Hardware diags return
no issues.

Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.07

Server BT2M halted Sunday, June 1, 2008   8:17:26.273 pm
Abend 1 on P01: Server-5.70.07: Page Fault Processor Exception (Error
code 00000000)

Registers:
    CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
    EAX = 00000001 EBX = 2C91E1A8 ECX = 928943DC EDX = 00000020
    ESI = 898E97A4 EDI = 00000000 EBP = 928943DC ESP = 8A1D3F74
    EIP = 918807A8 FLAGS = 00010002
    918807A8 8B07           MOV     EAX, [EDI]=?
    EIP in ETHERTSM.NLM at code start +000007A8h
    Access Location: 0x00000000

The violation occurred while processing the following instruction:
918807A8 8B07           MOV     EAX, [EDI]
(Continue reading)

Permalink | Reply | 8 comments |
headers
Tim Heywood | 2 Jun 2008 08:14
Picon

Re: sigh -- abend log -- opinions?

BX2.LAN 3.70

>>> On 02 June 2008 at 04:03, "Peter Van Lone" <petervl <at> gmail.com> wrote:
> Below are some snippets from an abend log. The server that is abending
> has been fine for a couple years, until the admin put a second
> processor in, and added ram. Now, even with the second processor out,
> and ram back to what it was, it is abending (often "silently") and
> having odd comms issues (ie, people can't login, then if they keep
> trying they can, but then they get bumped out, again).
> 
> Please peruse and advise, if you have any ideas. The admin has
> recently updated from sp6 to sp7 and he may (I'm not sure right now)
> have updated to the post sp7 winsock and clib. Hardware diags return
> no issues.
> 
> 
> Novell Open Enterprise Server, NetWare 6.5
> PVER: 6.50.07
> 
> Server BT2M halted Sunday, June 1, 2008   8:17:26.273 pm
> Abend 1 on P01: Server-5.70.07: Page Fault Processor Exception (Error
> code 00000000)
> 
> Registers:
>     CS = 0008 DS = 0023 ES = 0023 FS = 0023 GS = 0023 SS = 0010
>     EAX = 00000001 EBX = 2C91E1A8 ECX = 928943DC EDX = 00000020
>     ESI = 898E97A4 EDI = 00000000 EBP = 928943DC ESP = 8A1D3F74
>     EIP = 918807A8 FLAGS = 00010002
>     918807A8 8B07           MOV     EAX, [EDI]=?
>     EIP in ETHERTSM.NLM at code start +000007A8h
(Continue reading)

Permalink | Reply | 7 comments |
headers
Peter Van Lone | 2 Jun 2008 14:02
Picon

Re: sigh -- abend log -- opinions?

On Mon, Jun 2, 2008 at 1:14 AM, Tim Heywood <tim <at> nds8.co.uk> wrote:
> BX2.LAN 3.70
>

Tim --

to put a few more words into it:

you think the culprit is the LAN driver? That does happen to be the
driver and version that is loaded -- how did you come to know that? Is
there a known issue with that driver version?

>From what I understand, the admin has recently run the most recent
Proliant Support Pack, so ... this must be the most recent available
version of this file? (Though I will check to be sure he has done that
...)

Peter
Permalink | Reply | 6 comments |
headers
Toomas Aas | 2 Jun 2008 14:40
Picon
Favicon

Re: sigh -- abend log -- opinions?

Peter Van Lone wrote:

> On Mon, Jun 2, 2008 at 1:14 AM, Tim Heywood <tim <at> nds8.co.uk> wrote:
>> BX2.LAN 3.70
>>
> 
> you think the culprit is the LAN driver? That does happen to be the
> driver and version that is loaded -- how did you come to know that? Is
> there a known issue with that driver version?

FWIW, I also had abends after updating BX2.LAN to 3.70. The abend logs that 
I kept are similar to yours (EIP in ETHERTSM.NLM at code start +000007A8h
). After going back to BX2 ver 3.41 the abends ceased.

--

-- 
Toomas Aas
Permalink | Reply | 3 comments |
headers
Peter Van Lone | 2 Jun 2008 15:07
Picon

Re: sigh -- abend log -- opinions?

OK, I will suggest back-dating that module as a test. Then, if this
abend goes away, he can test re-adding the second processor to confirm
whether that was an issue in any of the first series of abends.

Thnx ...

Peter

On Mon, Jun 2, 2008 at 7:40 AM, Toomas Aas <toomas.aas <at> raad.tartu.ee> wrote:
> Peter Van Lone wrote:
>
>> On Mon, Jun 2, 2008 at 1:14 AM, Tim Heywood <tim <at> nds8.co.uk> wrote:
>>> BX2.LAN 3.70
>>>
>>
>> you think the culprit is the LAN driver? That does happen to be the
>> driver and version that is loaded -- how did you come to know that? Is
>> there a known issue with that driver version?
>
> FWIW, I also had abends after updating BX2.LAN to 3.70. The abend logs that
> I kept are similar to yours (EIP in ETHERTSM.NLM at code start +000007A8h
> ). After going back to BX2 ver 3.41 the abends ceased.
>
> --
> Toomas Aas
> _______________________________________________
> Novell mailing list
> Novell <at> netlab1.oucs.ox.ac.uk
> http://netlab1.usu.edu/mailman/listinfo/novell
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Peter Van Lone | 2 Jun 2008 15:13
Picon

Re: sigh -- abend log -- opinions?

One more thing ... what is the story with acpi on netware? For a while
several years ago (nw5.0/5.1), it seemed to be the cause of lots of
problems. Recently I have begun to suspect it again ... anyone else
suspecting the same thing?

Peter

On Mon, Jun 2, 2008 at 7:40 AM, Toomas Aas <toomas.aas <at> raad.tartu.ee> wrote:
> Peter Van Lone wrote:
>
>> On Mon, Jun 2, 2008 at 1:14 AM, Tim Heywood <tim <at> nds8.co.uk> wrote:
>>> BX2.LAN 3.70
>>>
>>
>> you think the culprit is the LAN driver? That does happen to be the
>> driver and version that is loaded -- how did you come to know that? Is
>> there a known issue with that driver version?
>
> FWIW, I also had abends after updating BX2.LAN to 3.70. The abend logs that
> I kept are similar to yours (EIP in ETHERTSM.NLM at code start +000007A8h
> ). After going back to BX2 ver 3.41 the abends ceased.
>
> --
> Toomas Aas
> _______________________________________________
> Novell mailing list
> Novell <at> netlab1.oucs.ox.ac.uk
> http://netlab1.usu.edu/mailman/listinfo/novell
>
(Continue reading)

Permalink | Reply | 1 comment |
headers
Toomas Aas | 2 Jun 2008 15:29
Picon
Favicon

Re: sigh -- abend log -- opinions?

Peter Van Lone wrote:

> One more thing ... what is the story with acpi on netware? For a while
> several years ago (nw5.0/5.1), it seemed to be the cause of lots of
> problems. Recently I have begun to suspect it again ... anyone else
> suspecting the same thing?

My observations from the same server where I unsuccessfully tried BX2.LAN 
ver 3.70.

This is IBM System x3550 machine with quad core Xeon CPU. I initially 
installed NW65 from SP7 overlay CDs. This put ACPIDRV.PSM into startup.ncf.

Later I wiped this install and made new install from SP5 overlay CDs, then 
applied SP7. This way I ended up with MPS14.PSM in startup.ndf. Before 
finally putting the machine into production, I manually replaced MPS14 with 
ACPIDRV.

During its first couple of days in production, the machine had various 
abends. I replaced ACPIDRV.PSM with MPS14.PSM, and the machine has been 
stable since, except the problem with BX2.LAN.

--

-- 
Toomas Aas
Permalink | Reply | 0 comments |
headers
Bud Durland | 2 Jun 2008 18:27
Picon

Re: Tcopy error message

On Sun, Jun 1, 2008 at 7:27 PM, Colin Connolly
<colin.connolly <at> phon.ox.ac.uk> wrote:
> I need to copy the trustee rights on a folder & subdirs on an old NW5.1 server onto a copy of
> the same folder structure on a NW6.5 server (different tree). I used the SCMT to migrate the
> data, but SCMT couldn't keep the trustee rights as the IDs are different on each user/group
> object on the new tree.

I suspect the tcopy is failing for the same reason.

You might want to try TRUSTBAR.NLM.  IIRC, it should be on the NetWare
CD.  During backup, TRUSTBAR creates an XML file with the folder
names, along with user/group names & rights to the folders.  I used it
a few years back to migrate a 4.x server to 6.0.  The XML is pretty
much plain text, which made editing for renamed volumes and folders
pretty easy.  I ran TRUSTBAR (backup) on the source server, used NCOPY
to move data from one to the other,  then TRUSTBAR (restore) to apply
the rights.

--

-- 
----------------------------------------------------------
I'm in my own little world. But that's OK,
because they all know me here.
Permalink | Reply | 0 comments |

Gmane