Jira (PUP-3203) Errors when using scheduled_task on windows

Josh Cooper (JIRA) Mon, 15 Sep 2014 11:02:44 -0700

Title: Message Title

Josh Cooper commented on an issue

Thanks Sam Weston, The manifest above has a problem in that the `command` property uses double-quotes and single backslashes. This will cause puppet to interpret "\P", etc as escape sequences, leading to errors like:

                                                    Warning: Unrecognised escape sequence '\P' in file C:/Users/sweston/puppettest.pp at line 2
Warning: Unrecognised escape sequence '\P' in file C:/Users/sweston/puppettest.pp at line 2
Warning: Unrecognised escape sequence '\j' in file C:/Users/sweston/puppettest.pp at line 2

                                                

See https://docs.puppetlabs.com/puppet/3.7/reference/lang_windows_file_paths.html#using-backslashes-in-double-quoted-strings for more info. You'll want to either use single quotes and single backslashes, or double quotes and double backslashes.

That said, I was not able to reproduce the problem you're seeing. From the stack trace, it looks like puppet is trying to delete a trigger (by index) that doesn't exist.

Can you try running "Start Command Prompt with Puppet" as an Administrator, save the following script to tasks.rb, execute it as ruby tasks.rb, and attach the result?

                                                    require 'puppet'
require 'puppet/util/windows'
require 'puppet/util/windows/taskscheduler'
require 'pp'
require 'ffi'
# workaround https://tickets.puppetlabs.com/browse/PUP-3247
class Win32::TaskScheduler
  def trigger_string(index)
    raise Error.new('No current task scheduler. ITaskScheduler is NULL.') if @pITS.nil?
    raise Error.new('No currently active task. ITask is NULL.') if @pITask.nil?
    raise TypeError unless index.is_a?(Numeric)

    trigger = ""

    FFI::MemoryPointer.new(:pointer) do |ptr|
      @pITask.GetTriggerString(index, ptr)

      ptr.read_com_memory_pointer do |str_ptr|
        trigger = str_ptr.read_arbitrary_wide_string_up_to(256)
      end
    end

    trigger
  end
end

Win32::TaskScheduler.new.tasks.collect do |job_file|
  task = Win32::TaskScheduler.new
  task.activate(job_file)

  puts "Task        '#{job_file}'"
  puts "Command     '#{task.application_name}'"
  puts "Args        '#{task.parameters}'"
  puts "Working dir '#{task.working_directory}'"
  puts "User        '#{task.account_information}'"

  count = task.trigger_count
  puts "Triggers #{count}"
  task.trigger_count.times do |i|
    begin
      puts "trigger #{i}"
      pp task.trigger(i)
    rescue => detail
      puts "Failed to load trigger '#{task.trigger_string(i)}'"
    end
  end
end

                                                

Add Comment

Puppet /

PUP-3203

I'm using the scheduled_task provider to create a daily task. The initial task creation goes fine, but on any future puppet run I get things like this:

{noformat}
change from {'every' => '1', 'schedule' => 'daily', 'start_date' => '2014-9-9', 'start_time' => '12:00'} to [{'every' => '1', 'schedule' => 'daily', 'start_date' => '2014-9-8', 'start_time' ...

This message was sent by Atlassian JIRA

--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.

Jira (PUP-3203) Errors when using scheduled_task on windows

Reply via email to