aMule Forum
English => aMule Help => Topic started by: sabin on July 08, 2005, 11:30:58 AM
-
Hello hello !
I have gotten a weird bug after reinstalling aMule. (Mandriva 2005 LE)
Before that, amule would work with my username "sabin", I had even never considered using the software as root.
But now :
(I launched amule from the console so as to have detailed bug information. Another thing that might be useful, I first tried xMule, maybe that's why aMule has been forever using the xMule incoming and temp folders)
- as the "sabin" username. No root priviledge, simple user.
if I run amule as "sabin", amule won't recognize the part.met files and thus start with no file in progress, as it there were no files to download.
In console, that says this :
Loading temp files from /home/sabin/.xMule/Temp.
Loading PartFile 1 of 4: Failed to load PartFile '002.part.met'
Loading PartFile 2 of 4: Failed to load PartFile '006.part.met'
Loading PartFile 3 of 4: Failed to load PartFile '007.part.met'
Loading PartFile 4 of 4: Failed to load PartFile '008.part.met'
All PartFiles Loaded.
In amule itself, in the server info tab, it says :
CFile: Failed to open file '/home/sabin/.xMule/Temp/002.part.met'!
2005-07-08 11:15:05: Error: Failed to open part.met file: 002.part.met ==>
2005-07-08 11:15:05: CFile: Failed to open file '/home/sabin/.xMule/Temp/002.part.met.bak'!
2005-07-08 11:15:05: ERREUR: Impossible de charger le fichier de sauvegarde. (Trans : "error, impossible to load the backup file")
It says the same for each of my shared files.
- as the root user.
Now, if I run amule as the root user, things will be different.
First of all, when I launch the program, i'll have a dialog box inside amule saying this :
Directory 'home/sabin/.xMule/Incoming' couldn't be created (error 2: No such file or directory)
And yet that's the precise folder in which my files are being downloaded, the folder exists !
This time amule will recognize the files to be downloaded, and list them. At this stage, no error message in console or in the server info tab. As if everything were allright, aMule will download the files to be downloaded.
But yet if it reaches the end of a file (in aMule, it will say "finalisation", Trans: "finalization"), the bug will be back ! It will NOT manage to finish the download and display an error message :
CFile: Failed to open file 'home/sabin/.xMule/Incoming/File_Name.avi'!
2005-07-08 11:20:08: FileIO: Error on file copy. Can't create destination file: home/sabin/.xMule/Incoming/File_Name.avi
2005-07-08 11:20:08: Unexpected file error while completing File_Name.avi.avi. File paused
Hmmm, I searched the forum but didn't find any mention of that particular problem, alas. I checked the rights embedded to the incoming and temp folders, and even edited those rights so that anyone can read or edit or even execute every file in amule and xmule folders, but that didn't change anything.
Would you know what I can hope to do to solve this ? I would hate to have to start my downloads again ^^
Thanks in advance ^^ :baby:
Please do not post file names.
-
well its simple a permission problem, maybe the group and/or the userID of the files is not set right...
what means just use your root user to change that
go to /home/sabin/
and do
chown -R sabin: .xMule
chmod -R a+rwx .xMule
these settings should fix the permission problem....
and then run aMule again as sabin user...
stefanero
-
I had tried that as "sabin" instead of "root" and got a "permission denied" for the temp, part and met files in xmule/temp.
But you know what ? That made me open the concerned folder in konqueror with detailed view, have a sharper than usual look, and I learned something that I didn't know yet ^_^
- oh, and that made me find the solution too :D
On that point I thought that Linux file management was similar to that of windows file management. Of course I was wrong.
As root, I had forced read+write+execute rights on every file and folder of xmule and amule directories. I thought that enough to allow any username to use+write those files.
As a windows user, that would have been enough.
Not as a Linux user, I didn't notice the "belonging" column (i'm sorry I don't know the exact english word, I can only guess from my french, it's the username attached to the files) : some files were for the root, some files were for "sabin". That was a detail that I had not changed ! As root, setting those files to belong to "sabin" finally did the trick ! That was the command you had advised (chown), in fact, but suggesting it made me discover a part of linux that I hadn't known yet :D
Thanks Stefanero ^_^
-
np ;)
have fun :))