Of Sims,
Richard B
Sent: Friday, 06 February, 2015 8:45 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM issue with RedHat
From my experience, this likely has nothing to do with the TSM server, but
rather either configuration issues with the client or permissions on the
dsmerror.log, or its
-
De: Tim Brown tbr...@cenhud.com
À: ADSM-L@VM.MARIST.EDU
Envoyé: Vendredi 6 Février 2015 20:30:31
Objet: Re: [ADSM-L] TSM issue with RedHat
This just happed, had been working for months. If I use ./dsmc q fi
I get nada, hangs! Will guarantee a reboot of linux will fix it.
Also no other
] On Behalf Of
Sims, Richard B
Sent: Friday, 06 February, 2015 8:45 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM issue with RedHat
From my experience, this likely has nothing to do with the TSM server, but
rather either configuration issues with the client or permissions
Or perhaps... could it have something to do with this flash alert I
received in my inbox today?
http://www-01.ibm.com/support/docview.wss?uid=swg21696086myns=swgtivmynp=OCSSGSG7mync=Ecm_sp=swgtiv-_-OCSSGSG7-_-E
Abstract
RHEL 6.6 contains a kernel defect, which can cause Tivoli Storage Manager
How are you starting it? With service ? Did you search for multiple
copies of dsmsched/error.log? It might be updating a different one from
what you are looking at?
On Fri, Feb 6, 2015 at 8:32 AM, Tim Brown tbr...@cenhud.com wrote:
Last line in dsmsched.log
02/06/2015 08:03:48 ANS2820E An
Last line in dsmsched.log
02/06/2015 08:03:48 ANS2820E An interrupt has occurred. The current operation
will end and the
client will shut down.
I was able to kill the process but whenever I restart the scheduler, the
process starts but dsmsched.log and or dsmerror.log arent refreshed.
I even
From my experience, this likely has nothing to do with the TSM server, but
rather either configuration issues with the client or permissions on the
dsmerror.log, or its location.
Start with a simple command like ‘dsmc q fi’, as an ordinary user and then
root, to see if there are issues with
We have been fighting this kernel problem for a while but as far as we know
it only effects the server and sql calls to DB2, not a client. We are
waiting for an official RedHat patch. The latest kernel update that just
came out addresses 3-semaphore related problems but none directly list the
