Unsolved
This post is more than 5 years old
68 Posts
0
2700
Probe with powershell
Hello,
has someone tested a powershell script for inclusion in a probe resource ?
I can't do it.
Since the probe process (on a windows) cannot execute a .ps1 file directly, I've tried including it in a .bat or a .cmd file, but no way...
My group stays pending without information until I abort it.
Tested a one line .bat or .cmd file which returns an exit code leads to success but does not work when invoking powershell.exe (checked for correct paths...)
My .ps1 works perfectly when invoked by powershell or when included in a .bat file called from the 'cmd.exe' subsystem.
Ideas, clues ?
Thanks in advance.
Denis
deniscnqd
68 Posts
0
January 5th, 2016 06:00
A probe group which have one client with a probe resource selected
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
January 5th, 2016 06:00
Hi deniscnqd,
Can you please provide details as to how you are running the .ps1 inside the .bat ?
ble1
14.3K Posts
0
January 5th, 2016 06:00
How did you test it with NW? Bia backup command, via savepnpc or via probe group?
deniscnqd
68 Posts
0
January 5th, 2016 07:00
In a .bat file :
powershell.exe -File "C:\Program Files\EMC NetWorker\nsr\bin\nsrservices1.ps1"
EXIT 0
The group remains in a probe running state until I kill it
deniscnqd
68 Posts
0
January 5th, 2016 08:00
In the groupe log file (located under /nsr/logs/sg...), I've got the following line :
C:\>powershell.exe -File "C:\Program Files\EMC NetWorker\nsr\bin\nsrservices1.ps1"
The program is executed (it writes a date/time stamp in a file) but it seems that NW does not see this termination.
deniscnqd
68 Posts
0
January 6th, 2016 01:00
Put the same powershell line after the first one in the .bat file : the script is executed only once !
Ran directly from the cmd.exe dosbox : two lines of results !
Running group with -D9 looks like :
.....
01/06/16 10:04:42.660094 Received job state change message
01/06/16 10:04:42.660350 Received job 3677305 state change message from STARTED to ACTIVE
01/06/16 10:04:42.660396 S107501D228867S:Probe (3677305) Received job state change message from STARTED to ACTIVE
01/06/16 10:04:42.660436 S107501D228867S:Probe (3677305) Processing job state change from STARTED to ACTIVE
01/06/16 10:04:42.660474 sg_pick_next_job(): Entry...
01/06/16 10:04:47.660578 sg_pick_next_job(): Entry...
01/06/16 10:04:52.661278 sg_pick_next_job(): Entry...
01/06/16 10:04:57.661574 sg_pick_next_job(): Entry...
01/06/16 10:05:02.661912 sgrp_update_progress old: | backup probing|1/0/0|1/0/0|
01/06/16 10:05:02.662285 sgrp_update_progress new: | backup probing|1/0/0|1/0/0|
01/06/16 10:05:02.662326 sg_pick_next_job(): Entry...
01/06/16 10:05:07.662428 sg_pick_next_job(): Entry...
01/06/16 10:05:12.662904 sg_pick_next_job(): Entry...
01/06/16 10:05:17.663394 sg_pick_next_job(): Entry...
01/06/16 10:05:22.663830 sg_pick_next_job(): Entry...
01/06/16 10:05:27.664104 sgrp_update_progress old: | backup probing|1/0/0|1/0/0|
01/06/16 10:05:27.664536 sgrp_update_progress new: | backup probing|1/0/0|1/0/0|
01/06/16 10:05:27.664576 sg_pick_next_job(): Entry...
01/06/16 10:05:32.664859 sg_pick_next_job(): Entry...
01/06/16 10:05:37.665339 sg_pick_next_job(): Entry...
01/06/16 10:05:42.665584 sg_pick_next_job(): Entry...
01/06/16 10:05:47.666208 sg_pick_next_job(): Entry...
01/06/16 10:05:52.669144 sgrp_update_progress old: | backup probing|1/0/0|1/0/0|
01/06/16 10:05:52.669359 sgrp_update_progress new: | backup probing|1/0/0|1/0/0|
01/06/16 10:05:52.669401 sg_pick_next_job(): Entry...
01/06/16 10:05:57.669725 sg_pick_next_job(): Entry...
01/06/16 10:06:02.670004 sg_pick_next_job(): Entry...
01/06/16 10:06:07.670467 sg_pick_next_job(): Entry...
01/06/16 10:06:12.671116 sg_pick_next_job(): Entry...
01/06/16 10:06:17.671744 sgrp_update_progress old: | backup probing|1/0/0|1/0/0|
01/06/16 10:06:17.672149 sgrp_update_progress new: | backup probing|1/0/0|1/0/0|
01/06/16 10:06:17.672230 sg_pick_next_job(): Entry...
01/06/16 10:06:22.672343 sg_pick_next_job(): Entry...
01/06/16 10:06:27.672671 sg_pick_next_job(): Entry...
01/06/16 10:06:32.672978 sg_pick_next_job(): Entry...
01/06/16 10:06:37.673226 sg_pick_next_job(): Entry...
01/06/16 10:06:42.673467 sgrp_update_progress old: | backup probing|1/0/0|1/0/0|
01/06/16 10:06:42.673632 sgrp_update_progress new: | backup probing|1/0/0|1/0/0|
01/06/16 10:06:42.673662 sg_pick_next_job(): Entry...
01/06/16 10:06:47.673795 sg_pick_next_job(): Entry...
01/06/16 10:06:52.674028 sg_pick_next_job(): Entry...
01/06/16 10:06:57.674291 sg_pick_next_job(): Entry...
01/06/16 10:07:02.674535 sg_pick_next_job(): Entry...
...
until interruption
Changing my lines by :
sc query nsrexecd
EXIT 1
leads to a correct execution.
Don't see anything in order to solve it...
Maybe opening a case...
deniscnqd
68 Posts
0
January 13th, 2016 05:00
Starting the powershell with start /wait does the job,ie :
start /wait powershell.exe -NoProfile -NonInteractive -NoLogo -ExecutionPolicy Unrestricted -File "C:\Program Files\EMC NetWorker\nsr\bin\nsrservices.ps1"
exit /B %errorlevel%
Don't know how Networker monitors .bat execution or processes forks...