I tested this by editing the wrapperscript and adding an 'echo "Arguments: $ARGS" >> /tmp/foo' . It seems the wrapperscript isnt being run at all on the cases where it is not working cause nothing is being written to /tmp/foo . When its working it looks like this: -log debug -ticket "XXXXXXXXX" -stub "0" -group "" -host "https://vpn.xyz.com/CACHE"; -certhash "XXXXXXXXX:? ??ef?,?K^z??11T??D" So if the wrapperscript is not being executed then cstub isnt being executed either i guess so it cant be due to a cstub crash On Tue, Nov 4, 2014 at 6:33 PM, Kevin Cernekee <cernekee at gmail.com> wrote: > On Tue, Nov 4, 2014 at 6:41 AM, Peter Magnusson <pet.magnusson at gmail.com> wrote: >> Hi David, >> >> Thank you for the reply. Ive enabled verbose log on cstub and compared >> the logs now. On the run where it is Not working (the second run) >> there are nothing at all being logged to the cstub.log. >> So it seems the hostscan parts are not being executed at all for some >> reason. On the run that is working(first run) i have alot of logentrys >> in cstub.log. Also when running with --no-xmlpost cstub.log looks >> normal aswell. > > Are the arguments provided to the wrapper script different between the > two cases? > > Is there any evidence that cstub is crashing on entry? Do you see a > core file if you set "ulimit -c unlimited"?
