Re: [ADSM-L] Making sure clientactions start
2009-06-23 09:48:53
Randomization doesn't apply when SCHEDMODE is PROMPTED.
You know, I've seen this a couple of times: whether it's with CLIENTACTION
or just a normal schedule, when you set the schedule's starttime to NOW, it
takes a long time for the client to start: 30 seconds, 5 minutes, even
longer. Sometimes reproducible, sometimes not.
>From memory, the client software was running; had schedmode prompted set;
had been restarted after that; not firewalled away; up-to-date versions.
Is there a tracing flag on client or server that would show us what's
happening?
On Tue, Jun 23, 2009 at 9:06 AM, AKiT ADSM-L <adsm-l AT akit DOT biz> wrote:
> looking at all replies so far I saw no one mentioning the schedule
> randomization. default 25% randomization multiplied by default client
> action duration of 5 days makes 30 hours.
>
> see the "help SET CLIENTACTDuration" and "help SET RANDomize" commands
>
> Zlatko Krastev
> IT Consultant
>
>
>
>
> "Lee, Gary D." <GLEE AT BSU DOT EDU>
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> 19.06.2009 18:16
> Please respond to
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
>
> To
> ADSM-L AT VM.MARIST DOT EDU
> cc
>
> Subject
> [ADSM-L] Making sure clientactions start
>
>
>
>
>
>
> I have a clientaction defined for a node whose schedmode is set to
> prompted.
> However, I have now been waiting for 45 minutes for the action to take
> place.
>
> Is there a way to get the server to kick itself and prompt the client to
> perform the actions in a clientaction?
>
> Gary Lee
> Senior System Programmer
> Ball State University
> phone: 765-285-1310
>
--
Lindsay Morris
Principal
TSMworks
Tel. 1-859-539-9900
lindsay AT tsmworks DOT com
|
|
|