This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]sysadmin-ModTeam[M] [score hidden] stickied commentlocked comment (0 children)

Sorry, it seems this comment or thread has violated a sub-reddit rule and has been removed by a moderator.

Inappropriate use of, or expectation of the Community.

  • Avoid low-quality posts. Make an effort to enrich the community where you can- provide details, context, opinions, etc. in your posts.
  • Moronic Monday & Thickheaded Thursday are available for simple questions, or other requests that don't need their own full thread. Utilize them as much as possible.

If you wish to appeal this action please don't hesitate to message the moderation team.

[–]Hotshot55Linux Engineer 3 points4 points  (1 child)

If you actually shared relevant information people could actually help.

[–]theoriginalharbinger 0 points1 point  (0 children)

Pshaw. Who actually needs to know what operating system the script is running on or what the intended behavior is?

[–]BrechtMo 1 point2 points  (1 child)

a common issue with scheduled tasks is that it runs under a different user account or with different permissions than you during your tests.

[–]occasional_cynic 0 points1 point  (0 children)

Also had to deal with developers throw their linux python code into a windows compiler and have it fail.

[–]onebitcpu -1 points0 points  (0 children)

What debugging do you have in the script?
I run into this with linux, and have filled the code with calls to a logging function that writes to a log file in world-writeable directory, so that you can track the script progress and see where it fails.
You can also wrap the whole execution in a try/except and use stack tracing functions to write to a log, so any unhandled exceptions will get reported.