Author Topic: UPUpdate - autoupdater troubleshooting and bug reports only  (Read 15697 times)

0 Members and 1 Guest are viewing this topic.

Offline DxyFlyr

  • Newbie
  • *
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #90 on: July 16, 2010, 05:43:08 AM »
Foiled again.

I disabled windows firewall, shut zone alarm completely down and bypassed my router.  I still get the same error message from my previous post.

Most frustrating.  I don't know of any other a/v or firewall on my machine.

Offline DxyFlyr

  • Newbie
  • *
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #91 on: July 16, 2010, 07:11:33 AM »
Ok, I got it now.  I had to allow rsync.exe in Net Nanny (kids share my computer) even though it is supposedly disabled when I log in.  Apparently, not everything gets disabled.

My first update seems to have gone well.

Thanks for the help.  I'm up and running now.

S!

Offline CRO_Ante

  • Administrator
  • IL2 Addict
  • *******
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #92 on: July 16, 2010, 09:09:28 AM »
See, I told you auto-updater was blocked.
 :drinks:

Offline DxyFlyr

  • Newbie
  • *
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #93 on: July 16, 2010, 05:44:10 PM »
See, I told you auto-updater was blocked.
 :drinks:


Yes you did!  Thanks again.

Offline 85FG_Hellman

  • Junior Member
  • **
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #94 on: July 28, 2010, 01:07:06 AM »
Hi guys!

I've been running the updater regularly until about 2 months ago. Always had no probs and usually enjoy about 60 fps in cockpit, and up to 200 fps when looking at clear sky. Very hi spec setup.

I ran the autoupdater last week and noticed that it picked up nearly 84 meg of updates(in fact our whole squad did), and since then my fps has peaked at 60, and alot of us are now having trouble getting on to Canons BoB maps.

Has anyone else experienced problems since this bigger update, and if so has any fix been posted?

Thx again for all your tireless work, guys.

~S~

85FG_Hellman

Offline CRO_Ante

  • Administrator
  • IL2 Addict
  • *******
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #95 on: July 28, 2010, 08:15:11 AM »
If you didn't run updater for 2 months, those were updates from 2010-06-18 -  Fixes for Channel map and P51 gauges.
 

Offline 85FG_Hellman

  • Junior Member
  • **
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #96 on: July 30, 2010, 01:41:23 AM »
Thx for the quick reply, Cro_Ante.

I'm a little confused by your reply, tho. It doesn't actually answer my question. If they were fixes then we shouldn't be having any problems but several of us get time-outs at 90% of BoB map-loading. And the frame rate has now been capped??? Any ideas?

Offline CRO_Ante

  • Administrator
  • IL2 Addict
  • *******
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #97 on: July 30, 2010, 08:59:03 AM »
 if auto-updater said it finished job successfully than it did, you have latest version of UP,  please report bug @ http://ultrapack.il2war.com/index.php/board,9.0.html  I think you will find more help there.


Offline 85FG_Hellman

  • Junior Member
  • **
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #98 on: July 31, 2010, 01:31:39 AM »
Many thx. I'll try that

~S~

Offline =BLW=PabloSniper

  • Beta-testers
  • Senior Member
  • *
    • Warbirds Photos
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #99 on: August 07, 2010, 11:49:29 AM »
this is my problem 

any suggestion ?
Since the First World War until the Korean War

Offline CRO_Ante

  • Administrator
  • IL2 Addict
  • *******
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #100 on: August 07, 2010, 01:42:59 PM »
Last night I was doing server upgrade, it could be the cause of this problem, try again,  if still have this kind of error something is wrong with your connection... NOD32 and similar AV programs can cause this kind of problems.

Offline Logan

  • DF Server Admins
  • Senior Member
  • *
  • Gender: Male
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #101 on: August 30, 2010, 05:31:40 AM »
Im getting the same error with the cross channel map 352nd_center_2.tga 0.00 kb and It just times out and freezes, xp sp3 server UP 201 never updated until now.

Offline Logan

  • DF Server Admins
  • Senior Member
  • *
  • Gender: Male
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #102 on: August 30, 2010, 05:32:16 AM »
oh no AV on at all.

Offline Logan

  • DF Server Admins
  • Senior Member
  • *
  • Gender: Male
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #103 on: August 30, 2010, 05:51:57 AM »
ok I fixed mine by just closing it and re-running it, twice the first time it said it couldnt connect to the IP, second time it did..go figure<shrugs>..try it Pablo see what happens.

Offline T_O_A_D

  • Member
  • ***
  • Grim Leeper
Re: UPUpdate - autoupdater troubleshooting and bug reports only
« Reply #104 on: November 11, 2010, 08:25:29 AM »
For over the last 6 to 8 hours all I get when trying to auto update, is this.


Quote
  Checking UPUpdate configuration files ...

rsync: failed to connect to 188.40.43.119: Connection refused (111)
rsync error: error in socket IO (code 10) at clientserver.c(124) [receiver=3.0.6
]

  Error received during update of configuration files.

Press any key to continue . . .



I get it from my dedicated server machine, and my client machine, and every install on my HD.

Here is a Trace route
Quote
Please wait...
Hop   Address   Min (ms)   Max (ms)   Avg (ms)   +/- (ms)
1   *            
2   172.30.3.153   11.58   14.53   12.81   
3   12-215-0-34.client.mchsi.com (12.215.0.34)   23.90   25.52   24.91   12.10
4   cr2.sl9mo.ip.att.net (12.122.142.130)   33.17   35.84   34.38   9.47
5   cr2.sl9mo.ip.att.net (12.123.140.169)   36.35   38.01   37.34   2.96
6   cr2.cgcil.ip.att.net (12.122.2.21)   34.57   41.06   37.63   0.29
7   cgcil02jt.ip.att.net (12.122.81.21)   29.85   33.58   31.26   -6.37
8   192.205.37.150   32.70   59.17   46.41   15.15
9   vlan52.ebr2.Chicago2.Level3.net (4.69.138.190)   30.96   34.51   33.21   -13.20
10   ae-6-6.ebr2.Washington12.Level3.net (4.69.148.145)   48.99   52.84   51.40   18.19
11   ae-5-5.ebr2.Washington1.Level3.net (4.69.143.221)   49.89   57.83   52.69   1.29
12   ae-44-44.ebr2.Frankfurt1.Level3.net (4.69.137.61)   139.51   144.09   141.06   88.37
13   ae-82-82.csw3.Frankfurt1.Level3.net (4.69.140.26)   144.28   148.00   146.33   5.26
14   ae-3-89.edge3.Frankfurt1.Level3.net (4.68.23.139)   139.48   171.44   150.79   4.46
15   HETZNER-ONL.edge3.Frankfurt1.Level3.net (212.162.40.206)   139.50   150.89   144.72   -6.07
16   hos-bb1.juniper2.fs.hetzner.de (213.239.240.243)   144.93   151.46   147.19   2.47
17   hos-tr4.ex3k2.rz10.hetzner.de (213.239.227.227)   146.01   148.81   147.55   0.36
18   static.119.43.40.188.clients.your-server.de (188.40.43.119)   145.93   148.29   146.76   -0.79
19   static.119.43.40.188.clients.your-server.de (188.40.43.119)   146.27   151.52   149.06   2.30



And one with Pingplotter, Line two is normal for my connection. It always shows that 100% loss there. I forget why, and what the ISP told me. It never affects game play or hosting. But line 19 is not normal.