Recently created topics in Wuala tagged with upload

Hi folks,

I have a really annoying error.
On my server, Wuala keeps on popping up the following dialogue box:

Problem

Could not upload file xxx.yyy
Reason: [Path to Local Settings]\Temp\Wuala\zzz-xxx.yyy (The system cannot find the file specified)


zzz is some random goup of numbers/letters
xxx.yyy is a specific file. It occurs for the following files:
extensions.rdf
localstore.rdf
content-prefs.sqlite
install.rdf
ietabOverlay.js
chatzilla.jar
downloads.sqlite
places.sqlite

The result is that every so many minutes wuala will pop up about 20 'problem' dialogues and it is really annoying since after about 10 minutes these boxes do no longer respond and I subsequently have to kill the wuala process.

Some more info:
Some of these files seem to be files which were sent to wuala via the filesystem integration and they are (some of them) backups of my ff-settings/bookmarks etc.
None of the files show up in the 'My Uploads' field and also not under maintainance.

Hope some1 can help me fix this cause its really annoying and I don't want to reinstall Wuala since my uptime is very high and built up over month.

Greetz
Darkstriker

iTunes changed a file, Wuala displayed a dialog saying it failed to upload that change and now file is lost because it was supposedly never completely uploaded. The dialog stated the file was not in /tmp but I certainly didn't remove it.

This isn't the first time this has happened to me and it certainly wouldn't be a problem if I was allowed to mount readonly. (I'm on OSX 10.5.4)

I'm really starting to not like your product because of this continuing problem. I'm sure iTunes is doing something weird but you should certainly handle it.

- Saved a file (mp3) on my desktop;
- Dragged it onto my group's music folder;
- Opened the Uploads window by double clicking in the upload icon - status bar;
- After the file got send it disappeared from the Uploads window (as it should);
- I tried to delete the file from my desktop and I couldn't - tried many times;
- Closing the Uploads window solved it - I could delete the file;

Ich versuche seit zwei Tagen eine Datei (4.2G) hochzuladen aber nach ein paar Minuten bis zu einer Stunde verschwindet der Upload aus dem Uploadfenster.
Die einzige möglichkeit den Upload fortzusetzen ist WUALA beenden und neustarten.

Ich habe letzte Woche mehrer (ca.10) grosse Dateien (350 - 800MB) in einem Rutsch hochgeladen, ohne Probleme.

Jetzt bin ich froh wenn ich 1% ohne Unterbrechung uploade.

cu wxi_

hallo,

hab das ganze zwar schon als frage gepostet aber nun wächst es sich langsam zum problem aus:

trotz der meldung
'... akzeptiert eingehende Verbindungen.
Gratulation, Ihre Verbindung ist für das Tauschen von Speicherplatz geeignet!'
fällt der graph unter den 'schwellenwert' auf 16 % online-zeit und das macht mich sehr traurig ... war ja schon fast bei 22 % ... nun ist seit tagen das speicher-tauschen nicht mehr möglich.
es ist mir ja auch möglich durch die wuala-welt zu surfen, daten rauf- und runterzuladen ...
bin also 100%ig online! trotzdem sinkt der online-graph gleichbleibend seit tagen stetig gen keller ...

help blees!

Hejhej,

when I try to upload a file into a shared folder I get this error message: "Transaktion153 fehlgeschlagen. ... Element is not in cache, [some numbers]". The folder is set on "shared with all and future friends". Uploading the same file into a privat or public folder and then copy it into the shared folder works fine.
I'm running Build 426 on WinXP SP2.

This problem is probably similar to:
http://getsatisfaction.com/wuala/topi...

hi there,

during my recent upload tests via filesystem integration method (see other thread http://getsatisfaction.com/wuala/topi... ) i somewhen realized that there are hugeloads of files in %temp%\wuala\ which wasnt the case in former builds of wuala.

there are also two directories in there (download and upload)

in the actual %temp%\wuala\ folder there seem to be a very big number of "original" files which i was trying to upload into the wuala store it seems.

the filenames have been changed somewhat to

hexnumber-originalfilename.extension

example:
f3edab22-mypicture.jpg
(hexnumber is maybe some hash/crc/crc32 or something)
the files are unencrypted, so i can actually use them with the appropriate application as they all hold the actual data (pictures, and so on....)

is this some bug? anyway related to my other thread? i suppose this is a huge security risk as even with reboots, wuala clients shutdown/restart these folders dont seem to go away or dont get empied nor cleaned up and the files can be seen by "anybody" who has access to the physical machine.

this is really weird. anyone else having this behaviour? win32/winxp that is. wuala426

lately i have experimented with wuala and fileintegration on win32 (xp) and latest wuala builds (426). i was copying whole cd contents (different files, loads of folder structures) into a semi-private (group/friendshared(only 1 friend as an example/test)) to the wuala network drive (w: for example).

the copying went normally, but only some days after (this happened first some days ago, but i verified it today with other content (CDs)) i realized that the uploaded wuala content of the folder i copied the files into wasnt exactly the same as my original sources. some bytes/megabytes were missing, and i tracked down some of the files/folders that were created but only with filesize=0 (zero), or were missing completely.

i was copying the stuff with the help of total commander, so not the basic builtin explorer.exe functions, nor commandline copy stuff...

i might try some more of this stuff at a later time.

the missing/incomplete files dont seem to follow any certain rules or patterns, there are simply some folders that are completely identical/complete and some files are missing or come with zero size.

totalcommander never complained that it couldnt write to w: or anything else like that.

i was manually looking for the differences, found the missing/incomplete files and was overwriting the files on the wuala store again.

after these second tries and overwriting procedure the wuala store was eventually finally complete and identical to my source material.

i guess that some of the queues in the wuala client, the pending transactions, the chunk-creation and distribution or related functions and parts of the wuala client program are still lacking robustness.

please take a look at this and do your own tests with lots of files/folders and different objectsizes.
thanks.

I'm getting this error with one of the files of a directory I put into Wuala last night. All files from the same directory uploaded correctly (According to the Wuala client on that PC). All Files are basically of the same type (avi videos, around 300 Megs).

The above message instantly pops up when trying to download the entire folder. The other files can all be downloaded successfully.

client: linux 106 (both uploader and downloader)

After the May 5 Update (419), all outstanding uploads vanished. This happened on Windows Vista x64 and Windows XP x86.
Vista seems to be slowly doing maintenance. XP has no activity.