Automic Workload Automation

  • 1.  U0011625 Logging was changed.

    Posted Aug 17, 2016 02:00 AM
    Hi 

    What is the meaning of this error message.



    Thansk


  • 2.  U0011625 Logging was changed.

    Posted Aug 17, 2016 02:06 AM
    It's not an Error Message - just and information that the logging from that point onwards will be written to a different File
    See the below Explanation from the Messages Documentation

    U0011625 Logging was changed.

    Explanation: The point in time when the logging is changed depends on the settings made in the UC4 variable UC_SYSTEM_SETTINGS. You may specify the time with the entries CHANGE_LOGGING_DAYS and CHANGE_LOGGING_MB. You may also change settings on a temporary basis. They are then valid until the Server processes are restarted.





  • 3.  U0011625 Logging was changed.

    Posted Aug 17, 2016 02:33 AM
    Hi,

     and what if Logging changes was failed. like I encounter. what is the meaning of this?  Please see the  screenshot


    3pu34ynr0q2m.pnghttps://us.v-cdn.net/5019921/uploads/editor/q3/3pu34ynr0q2m.png" width="1424">


  • 4.  U0011625 Logging was changed.

    Posted Aug 17, 2016 02:46 AM
    It's unclear from the screenshot where the message is encountered.  Is it so that the Job failed with this message?
    Can you provide the screenshot of the 'Details' window of this failed object.  Then there will be more clarity.

    Alternately you may raise a ticket with Automic Support.


  • 5.  U0011625 Logging was changed.

    Posted Aug 17, 2016 04:51 AM

    Please be more concrete as: what if Logging changes was failed.

    was the new logfile from the Agent created (number xxxx_00 renamed to xxxx_01 AND the new logfile xxxx_00 successfully created?

    Usually the fail of a Job and the Change of the Agent logging has no dependency from each other



  • 6.  U0011625 Logging was changed.

    Posted Aug 17, 2016 08:54 AM
      |   view attached
    Hi,


    I attach here the detail of the job.

    Thanks

    Attachment(s)



  • 7.  U0011625 Logging was changed.

    Posted Aug 18, 2016 09:45 PM
    Sorry, it is still unclear - I understand there is on Period object failed with Ended Not OK and the last message is a log change.  But this log change cannot be the root cause of the failure. 
    Typically you can avoid issues with regular scheduling by using a Scheduler Object or an Event.Time Object.
    Period object is useful for testing or use for a temporary / limited usage case.   But it is not suitable for productive continuous scheduling.


  • 8.  U0011625 Logging was changed.

    Posted Aug 19, 2016 12:48 PM
    Hi 

    Thanks for your help. 


    Thanks