basically same thing happened again when asked this question. time cannot right again. tried answer of burhan khalid again , same errors again. tried copy pasting zoneinfo folder backup again, time did not fix errors.
version of django = 1.4.5
version of celery = 3.0.8
version of django-celery = 3.0.6
version of pytz = 2013b (same files downloading)
os = mac mountain lion
attempt 1:
- clear zoneinfo folder (/usr/share/zoneinfo/)
- paste tar gz file in folder (tzdata2013b.tar.gz)
- extract tar gz file using command provided burhan khalid
- create script provided burhan khalid
- run script
result:
valueerror: incorrect timezone setting: europe/amsterdam when trying run celery beat. when check there indeed no folder named europ in zoneinfo folder there 1 before
attempt 2:
- do not clear zoneinfo folder (i put backup made before attempting above)
- paste tar gz file in folder (tzdata2013b.tar.gz)
- extract tar gz file using command provided burhan khalid
- create script provided burhan khalid in zoneinfo folder
- run script
result 2:
at step 3 following output, including errors:
[13:59:07] /usr/share/zoneinfo $ tar xvzf tzdata2013b.tar.gz x makefile x africa: can't remove already-existing dir x antarctica: can't remove already-existing dir x asia: can't remove already-existing dir x australasia x europe: can't remove already-existing dir x northamerica x southamerica x pacificnew x etcetera x backward x systemv x factory x solar87 x solar88 x solar89 x iso3166.tab x zone.tab x leapseconds x yearistype.sh tar: error exit delayed previous errors. at step 5 following output, including errors:
[13:59:13] /usr/share/zoneinfo $ sudo ./the_script.sh password: zic: error reading africa zic: error reading antarctica zic: error reading asia zic: error reading europe and still have corrupt file.
attempt 3:
- restore backup zoneinfo folder again
- create seperate folder on desktop
- paste tar gz file , script in new folder on desktop
- extract tar gz file using command
- execute script
result 3:
step 3 , 5 give no errors or unusual output
trying run celery beat still gives corrupt file error
question doing wrong here. cannot seem figure out...
edit
so have done more digging around , found following:
- if run same command via foreman run instead of via procfile no error, when command in procfile
- bad file descriptor error means python tries close file closed instead of file being corrupt
which leads me conclusion in foreman while using procfile forces file close before closed correctly... thoughts?
Comments
Post a Comment