• If we attempt to schedule a snapin task, it refuses saying the it is in the past.
    [CENTER][SIZE=16px][FONT=Ubuntu][COLOR=#ff0000]Failed to create deployment tasks for the following Hosts[/COLOR][/FONT][/SIZE][/CENTER]
    [SIZE=16px][FONT=Ubuntu][COLOR=#ff0000][CENTER] [/CENTER][/COLOR][/FONT][/SIZE]
    [*]FJQXNM1: Scheduled date is in the past. Date: 2015/20/02 12:27
    The format changes from YYYY/MM/DD to YYYY/DD/MM as you see in the error.
    I tested this by scheduling a job for the 3rd of March which works fine. Meaning that the date format changing between selection and actual scheduling is the problem.

  • Thanks, turns out restarting apache was not enough to make it work. Reboot solved the issue.

    While the change in format was not the cause, it sure as heck looks confusing.

  • Your problem? Apache date.timezone is not set properly. If you’re in the eastern half of the world, the date you were trying to “start” the task based on the time “apache” thinks it is is in the future and things would work. But my guess is you’re on the western part of the world and therefore your start time is past the time it thinks it actually is.

  • 1.2.0 on Centos 5.11

  • Developer

    fog version?