im having an issue as suddenly my go script is not executing. i made no changes to the GO script and the only thing i have in there is a line to run a python script. i made some changes to the python script that the go script runs and added influencer's transmission plugin. since then the go script doesn't run. it is not the python script erring out as i can run it manually. are there just too many plugins running or something?

What symptom are you having that makes you think the go script is not executing? Is the webgui accessible? Normally the go script has a line to start emhttp. Did you remove it?

 

Attach your go script and maybe the python script as well and maybe we will have more to go on.

 

the script runs continually in the background. i use it to manage my downloads during off peak hours. i made no changes to the go script when it quit working. i noticed it wasnt working because the script is supposed to automate some things and they werent happening. i checked the running processes and it isnt there until i manually start it. the webui is still accessible. i don't have the go script or python script on this pc right now but the go script is just the default script with "python /boot/downloadscript.py" added. i doubt it's the python script since all it does is interact with the sabnzbd api and the script itself isnt erring out as when i run it manually it is fine. the only changes i made to the server were adding the transmission plugin and tweaking my python script. i seem to recall having this issue before in relation to a plg preventing the go script from running but my memory is fuzzy.

well now i dont know what the hell is going on. when i got home the server was still on. it has not been turning off the last few days for some reason. the script is supposed to run "/sbin/powerdown &" at 8:00, which it did, yet it did not shutdown and i dont know why. there was never an issue before.

 

as influencer suggested, i also checked the processes for transmission and only grep and the daemon were running. went to disable the plugin but i couldnt access the windows share. i did it through ftp. disabled the plugin and restarted but it is still not running the python script.

 

i have a debug log in my script and also changed it to write any python interpreter errors to a log file. they are both time stamped. the most recent logs are from yesterday, meaning when i restarted the server, the script was not executed. this is driving me crazy.

 

here is my go script:

 

#!/bin/bash
# Start the Management Utility
/usr/local/sbin/emhttp &
echo "anon_world_readable_only=NO" >> /etc/vsftpd.conf
sed -i 's/.*local_root=.*/local_root=\//' /etc/vsftpd.conf
python /boot/sabnzbd_shutdown.py &

 

originally i did not have the ampersand at the end but changed it to see if it would help. it did not. it is also taking usually long to start since this started happening.

ok, i think i found a possible reason why this isnt working. to aid in trouble shooting i added those log files but i think those are what are causing the issues. the logs are saved to a user share like /mnt/user/plugins/<date>.log

 

when i manually run it, everything is fine but i when i went down to the server room and looked at the screen while it was booting i saw this:

 

Traceback (most recent call last):
File "/boot/shutdown.py", line 98, in (module)
sys.stderr = open('/mnt/user/plugins/' + datetime.datetime.now().strftime("%Y%m%d-%H%M%S") + '.log', 'w')
IOError: [Errno 2] No such file or directory: '/mnt/user/plugins/20130103-155733.log

 

so it seems the script is trying to create a log file on the user share (as it should) but the user share is not up and running yet. does that sound right?

yes, it sounds like you need to wait until the user-shares are enabled PRIOR to creating a file on one of the underlying disks.

 

Be aware that an open file on a user-share will prevent the server from stopping cleanly until the file is closed (or the program holding it open terminated)

 

Joe L.

well, i tried changing it to just a specific disk but that didnt work either. they must be taking too long to mount. i fixed it by changing it to the flash drive for now. i'll see if it will properly shut down tomorrow. thanks for the confirmation.