PDA

View Full Version : foldtraj_fileserver



IronBits
08-15-2002, 10:17 AM
None of my computers got updated.
========================[ Aug 14, 2002 11:53 PM ]========================
ERROR: [000.000] {foldtrajupdateproxy.c, line 116} Unable to check update file length
ERROR: [000.000] {foldtrajupdateproxy.c, line 315} Unable to get size of update file /~distribfold/trajfile-patch-115.tar.gz from bar.csh.rit.edu
ERROR: [000.000] {foldtrajupdateproxy.c, line 116} Unable to check update file length
ERROR: [000.000] {foldtrajupdateproxy.c, line 279} Unable to get size of update file /~distribfold/distribfold-patch-106-win9x.exe from bar.csh.rit.edu
ERROR: [000.000] {foldtrajupdateproxy.c, line 116} Unable to check update file length
ERROR: [000.000] {foldtrajupdateproxy.c, line 279} Unable to get size of update file /~distribfold/distribfold-patch-106-win9x.exe from bar.csh.rit.edu
ERROR: [000.000] {foldtrajupdateproxy.c, line 116} Unable to check update file length
ERROR: [000.000] {foldtrajupdateproxy.c, line 279} Unable to get size of update file /pub/distribfold/download/patch/distribfold-patch-106-win9x.exe from ftp.mshri.on.ca
ERROR: [000.000] {foldtrajupdateproxy.c, line 116} Unable to check update file length
ERROR: [000.000] {foldtrajupdateproxy.c, line 279} Unable to get size of update file /~distribfold/distribfold-patch-107-win9x.exe from bar.csh.rit.edu

Can ya tell me what's wrong with it by the logfile?

IronBits
08-15-2002, 08:04 PM
Howard?

beefdart
08-16-2002, 12:32 AM
due to circumstances beyond my control bar.csh.rit.edu went down late thursday night (est time)

I will give more info when it becomes availible, but bar should be back online sometime friday.

Brian the Fist
08-16-2002, 08:54 AM
I will watch what the proxy does more carefully with this next update and see if there's a problem. I've also fixed a memory leak in it which Ill post a new version of next week (memory leak is bad since it runs indefinitely in a loop) ;)

IronBits
08-16-2002, 09:06 AM
heh, thanks guys. Upon further checking, permissions were wrong on my end where the files were located, so the client couldn't check it anyways :rolleyes: that's been fixed ;)
I'll keep an eye on it for next time.
/me goes off to find the plumbers tape for Howard :)