Linux updater

[a19183]

Hello,
first of all i would like to say that i am pretty new to Linux 

But installation went well and was pretty easy.
Thx Xordan.

But when i run the updater he wants to download a huge amount of stuff.
Only he says that he downloads with ridiculous 2KB/sec.
My usual internet is much faster and working as you see my post here 
What is going wrong here?
And why do i have to update immediatly after installation such a huge amount of data?

Bye
Vestere

[Furik Lamatt]

You don't HAVE to, it's just a recommendation that you do. Also one of the first things to know about internet speed connections is that web surfing is fast, downloads NEVER as fast, and uploads never as fast as downloads.

[snwod]

Hello.  I was having this problem as well.  The GUI for the updater was running obscenely slow (I think I also had 2 KB/s).

What I ended up doing was running the updater from the command line.  It's not as hard as it sounds.  I am running openSUSE 10.2, and this is what I did (I think that the PlaneShift installer loads files into the same places in most distros):

open up a console and type the following

Code: [Select]

~$ cd /opt/PlaneShift
~$ ./updater
It ran the updater in the console, and the download speeds were normal.  I think it took about a minute or so.

Hope this helps.

[serspock]

I'm running Mandriva/KDE.
Each time I run "./updater -auto", always it finishes with "segment fault" 
Even if I delete the file "version.dat".
Important or not? The last time, I had to reinstall all 

[Xordan]

Not important, it's normal for it to end like that. It's just crashing when it's exiting for some reason, but this'll have no effect on your update.

[Araye]

I suggest using ./updater -auto

It is MUCH faster than the gui updater.  And just so you know, all of my PS programs end in a seg fault (./pssetup, ./updater, ./psclient).

Araye

[Jannis]

The segfault at the end of the programs happens here with the binaries, too. With self-built-version I get:

Code: [Select]

psEngine destroyed.
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  4 (X_DestroyWindow)
  Resource id in failed request:  0x2200003
  Serial number of failed request:  138
  Current serial number in output stream:  140
kripton@nebuchadnezzar /mnt/gentoo/psbuild $ So: No segfault but maybe it's related?

[Induane]

Were you compiling remotely or in a session without X?

[Jannis]

How do you mean that? I compiled the thing on my own PC, in a konsole-window and ran it afterwards.

[Araye]

Sorry, I wasn't trying to say that the seg fault was a problem, but rather a very common occurance whenever any PS program shuts down on my computer (quite normal and not an issue).  And as Jannis says, If I build it myself, I don't get the seg fault.  But I would rather have the seg fault than build it myself...  

Thank you Xordan for your build (and time)!

Araye

[mage.merlyn]

Hi all,

I thought I'd drop by the trusty forums to find an answer to my own updating woes, (Linux), and to a degree this thread has helped.

Like others have experienced while attempting to update, the download was very slow, (1-2k).

As a previous poster has mentioned download rates can vary markedly, however on my connection downloads usually come down at about 50-70k. While this is quite slow to others I know living nearby me with similar ADSL plans to myself, through other ISP's (180-200k), but I digress.

Apart from the slow download rate, I have also experienced another problem not mentioned by anyone else.

The update always appeared to 'hang' at 11% while fetching the file "up". So I left it updating while I went to do my grocery shopping today. Three hours later and there was still no progress beyond 11%.

I followed the advice offered by other posters in the following order.

1. launching the updater via the command line.

Unfortunately this did not improve my situation at all.

2. launching the updater via the command line with the '-auto' flag.

Yay! this worked to a point. Of the three files required "up" did not successfully update, (output provided below). Download rates also improved to something more 'typical' for my connection.

Code: [Select]

#:/opt/PlaneShift$ ./updater -auto
Critical files (<critical>) not found (Server only)
NOTIFY: psUpdaterEngine initialized.
Checking registry version...
Downloading registry...
0%....25%....50%....75%....100% (46 KB/s)
Loaded registry
Checking for updates...  This may take a while.
Using newregistry
I'll perform the following updates:
Update   up
Update   pss
Update   psc
Total size 21.62 MB in 3 files
Updates: 3
==== Update started ====
up (5.34 MB) 0%....25%....50%....75%....100% (52 KB/s)
Failed to update up!
pss (4.57 MB) 0%....25%....50%....75%....100% (51 KB/s)
Written /this/pss!
Updated  pss
psc (11.70 MB) 0%....25%....50%....75%....100% (52 KB/s)
Written /this/psc!
Updated  psc
Following files failed:
up
Please wait while saving files..
==== Update complete ====
At this stage I am now able to login and play, though a message appears reminding me that 'updates are still available'.

I would appreciate any advise on recitifying this problem.

My system is as follows,

Ubuntu 6.10 (Edgy Eft), kernel 2.6.17-10-generic. If there are any other specs required please let me know.

Cheers all.

[Finira]

Looks completely OK to me. "Failed to update up!" seems to be pretty normal, and I've got used to the client telling me there are new updates available, even if there are none. You can play, which means it can't get any better even if you managed to get rid of those messages.

Cheers,
- Finira -

[Eagel]

I get
Updated  vfs.cfg
up (5.34 MB) 0%....25%....50%....75%....100% (68 KB/s)
Failed to update up!
when i run ./updater -auto from command line (also from gui)
vfs.cfg is the only that failed... is this ok? how can i solve that?

[Wired_Crawler]

vfs.cfg was updated successfully. It is updater which fails to be updated. This happens because updater tries to overwrite the file (up), which is in use. You can update it manually after updater ends this way:

Code: [Select]

mv download.tmp up
chmod 755 up

Linux updater should first delete a file before replacing it with new version (but it also must set proper file attributes afterwards). In most cases executable in use can be safely deleted without disturbing a running program. You can try it the following way: start updater then delete file "up" before download of registry ends. Don't forget to do "chmod 755 up" then.

[mage.merlyn]

Looks completely OK to me. "Failed to update up!" seems to be pretty normal, and I've got used to the client telling me there are new updates available, even if there are none. You can play, which means it can't get any better even if you managed to get rid of those messages.

Thanks for the advice. I hadn't actually made the 'connection' between up and updater, up being the binary 'updater'.

Code: [Select]

mv download.tmp up
chmod 755 up

Linux updater should first delete a file before replacing it with new version (but it also must set proper file attributes afterwards). In most cases executable in use can be safely deleted without disturbing a running program. You can try it the following way: start updater then delete file "up" before download of registry ends. Don't forget to do "chmod 755 up" then.

Thanks heaps for the tip, worked like a charm.

Cheers all.