SSI - error

Question

Hello,

I have error in ssi.log

01-02-07 13:31:28 SSI[0]:
[tkp1vlpa/50004] ONC RPC: csi_ipcdisp(): status:STATUS_INVALID_TYPE;
Unsupported module type 1752134516 detected:discarded;

01-02-07 13:31:29 SSI[0]:
[tkp2vlpa/50011] ONC RPC: csi_ipcdisp(): status:STATUS_INVALID_TYPE;
Unsupported module type 1752134516 detected:discarded;

This error appears for every mount tape in drive.
Configuration:
SSI version
/usr/sbin/mini_el version 2.00 startup: Mon Dec 25 02:14:22 2006
[tkp2vlpa/50011] /usr/sbin/ssi, Legato version 2.00 startup
[tkp1vlpa/50004] /usr/sbin/ssi, Legato version 2.00 startup
Server Legato 7.2.2
OS - SUN Solris 5.8
I use virtual acsls (emulation by CentricStor).

What does it mean this error.

ble1 · Answer

Probably some debug noisy message which you should ignore unless you have real problem associated with.

ble1 · Answer

I have no idea about 1) and 2), but when it happens for example 1) simply mount from ACSLS machine tape and then unload it from NW - that should put it back to sync.

As for 3) try to run inventory against that volume and see what happens.

cziko · Answer

I have big problem with my backup serwer.
I looking for where it is problem.
I found only this error, so I would like know what does it mean this error, exactly.

I will description my problem.

All time I have not coherence between Jukebox Legato (silo) and database acsls.
1.) Legato think that have tape (e.g. A001) in drive1, but acsls have not tape (A001) in drive1. Drive1 in Acsls is empty.
2.) Legato think that, drive1 is empty, but acsls have tape (A001) in drive1.
3.) "Strangely tape"
nsrjb -j TKP1 M01344
slot: volume barcode pool
9499: M01344 LdP1WeekTKP1

Command nsrjb do not show info about barcode.

Do you know what is happened.

cziko · Answer

I know that, (do coherence) but it will be big broblem becouse I have to do it every day.I loking for reason my problem. This is question?

ble1 · Answer

If that happens on daily basis then I don't know. If it happens with the same volume then it is much easier, but with different pattern it is different story too.

My experience with ACSLS is based on 7.2.2 with real silo (no emulation) and patched ssi. In your case issue could be either bug on emulation side or bug on backup server side. In short, it is either ssi or csi that is not doing its job properly somehow. You may wish to have support provide you debug binaries to troubleshoot this further.

cziko · Answer

Thank you, I think similarly. (I want - oneself) but how I do find this problem. I have only error ssi. What will you do? (change version, patches, reinstall)

ble1 · Answer

By getting debug message you will be able to trace things from point when they are in sync to point being out of sync. You hope to see that path and to see where things break. Based on that you will know who to blame to.

ble1 · Answer

Simpy leave that to support - that's what they are paid for.

cziko · Answer

ok.
I did that but I do not know how do I find problem. I have a lot of log which include all information about comunication between backup serwer - acsls.
I do not know algoris comunictaion between backup serwer - acsls.
Do you know that?

ble1 · Answer

BTW, if you check list of patches for 7.2.2 jumbo you will find that LGTpa87725 is what you are after. Give it a try.

frankDSB · Answer

hii got the same error and asked my Storagetek ACSLS guy what it could be, he looked in their knowledgebase and told me that i had to upgrade my mini_el and ssi to version 2.01.i got those versions from my support on networker and it workedremember to stop networker and start mini_el and ssi before you start networker FrankDSB

NetWorker

SSI - error

Was this post helpful?