Skip to main content
aagrafi
aagrafi
New Member
March 1, 2018
Solved

How to identify CLI script errors

  • March 1, 2018
  • 1 reply
  • 20584 views

Hello,

I'm trying to upload CLI scripts from FG in 5.6.3 and I have noticed that when the script fails, the GUI reports the failure in the script execution history, but it does not tell me wtf the error is inside the script. As you can imagine, without this information in hand it is very difficult to locate CLI script errors in very large scripts. Does anybody know where/how can I locate this information?

 

Thanks

Andreas

    Best answer by Philippe_Gagne

    Hi,

     

    oupsss, use "diag debug cli 7". My mistake. I often use -1 in debug with application.

     

    Can you tell me what you want to do?

     

    Philippe

    1 reply

    Philippe_Gagne
    Philippe_Gagne
    New Member
    March 1, 2018

    Hi,

     

    Best way to do it: diag debug cli -1 in ssh windows then start you script.

     

    All lines will start with 0: except errors! :)

     

    Have a nice day!

     

    Philippe

     

    Toshi_Esumi
    SuperUser
    Toshi_Esumi
    SuperUser
    March 1, 2018

    Thank you for the info. Looks like the level range is 1-8.  level 0 would disable it.

     

    sea5601-fg1 # diag debug cli -1 Invalid level, set to level 5 sea5601-fg1 # diag debug info debug output:           disable console timestamp:      disable console no user log message:    disable CLI debug level:        5 sea5601-fg1 # diag debug cli ? <Integer>    Debug level (0 - 8). sea5601-fg1 (interface) # edit internal10 new entry 'internal10' added sea5601-fg1 (internal10) # end Attribute 'vdom' MUST be set. child return 0x0 Command fail. Return code -56

    Philippe_Gagne
    Philippe_GagneAnswer
    New Member
    March 1, 2018

    Hi,

     

    oupsss, use "diag debug cli 7". My mistake. I often use -1 in debug with application.

     

    Can you tell me what you want to do?

     

    Philippe

    Terms & ConditionsAccessibility statement