Upload file problem

J

JohnTBD

New member
Joined
Sep 1, 2005
Messages
3
Location
Australia
When I attempt to upload a .htm file from my desktop at work via the admin page, it comes up with an error:

"There is a symbolic link in that path. The path must be a full non-linked path."

I am only trying from my desktop. What the hell does this mean?

Thanks in advance.

:D
 
same problem, too

I am getting the same error message. Please tell us why it's doing that. I haven't done anything differently and get that message as well:

An Error Occurred

Details

There is a symbolic link in that path. The path must be a full non-linked path.


(Replied to bump the message and get a response)
 
This looks like a bug in the new 1.252 release.

It only occurs when you use the DA File Manager in the control panel - we can't replicate it using FTP at all.

I'm alerting John of this issue - since it just popped up, it should be an easy fix.

In the meantime, use FTP instead of the control panel to upload your files.
 
some customers are now complaining about segmentation fault when trying to upgrade

FreeBSD 4.1x

I didn't test it yet, because they didn't give me the steps to reproduce
didn't it happen to anyone else?
 
Jeeze, sorry John - I had no way of knowing you "knew" about this issue - forgive me for interrupting you and alerting you to a bug.
Click to expand...
Sorry Joe, that didn't come out the way I meant. I appreciate the bug alerts ;) I just posted it here for anyone to take note of after I posted it. (Ie: so we don't get another couple hundred emails about the same issue from end Users ;))

As for this latest post, let me know if you find out where the segfault is coming from (Are you using 1.25.3?). I'm going to start poking at everything I can find in the filemanager to see if I can duplicate it). I didn't notice anything when testing.

John
 
DirectAdmin Support said:
Sorry Joe, that didn't come out the way I meant. I appreciate the bug alerts ;) I just posted it here for anyone to take note of after I posted it. (Ie: so we don't get another couple hundred emails about the same issue from end Users ;))

As for this latest post, let me know if you find out where the segfault is coming from (Are you using 1.25.3?). I'm going to start poking at everything I can find in the filemanager to see if I can duplicate it). I didn't notice anything when testing.

John
Click to expand...

yes
I'm using 1.25.3
I just click on "Files" and try to send a file (no need to click on the symlink directory... can be to the root dir) and get this message
I sent you an E-Mail
If you don't get to reproduce it, please let me know and I can create an account for you on my server, so you can check it

thanks
 
Hello,

Thanks for the info. I've managed to reproduce it. Seems like a bug in the vfprintf funcion (called by fprintf), or else I'm out to lunch on something. For anyone insterested, this didn't work:
PHP: 
fprintf(fp, "%Ld=type=fileupload&time=%d&file=%s/%s\n", fileSize(files[i]), (int)time(NULL), cf[FRM_PATH], file);
But this works fine:
PHP: 
fprintf(fp, "%Ld", fileSize(files[i]));
fprintf(fp, "=type=fileupload&time=%d&file=%s/%s\n", (int)time(NULL), cf[FRM_PATH], file);
Only difference from the last release is the "unsigned long long"being returned from fileSize() and %Ld being used instead of %ld. It appears as that only freebsd is affected. I'll fix and release this right away.

John
 
DirectAdmin Support said:
Ok, updated. To get the fix, use this guide:
http://help.directadmin.com/item.php?id=29

Updates done after this post will get the fixed version.

I'm trying to avoid increasing the version number (we'll see how that goes). If needed, I'll set it to 1.25.4 and re-release everything.

John
Click to expand...

hello

it won't work here, have tried before
wget doesn't let me download because I'm using a 15minuteservers server and they configure a specific IP (on another interface) just for the DirectAdmin... so the "normal" external IP of the server has no rights to download the file

-su-2.05b# wget -O update.tar.gz https://www.directadmin.com/cgi-bin/daupdate?uid=650\&lid=3464
--17:09:34-- https://www.directadmin.com/cgi-bin/daupdate?uid=650&lid=3464
=> `update.tar.gz'
Resolving www.directadmin.com... 66.51.122.131
Connecting to www.directadmin.com|66.51.122.131|:443... connected.
ERROR: Certificate verification error for www.directadmin.com: unable to get local issuer certificate
To connect to www.directadmin.com insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
-su-2.05b# wget --no-check-certificate -O update.tar.gz https://www.directadmin.com/cgi-bin/daupdate?uid=650\&lid=3464
--17:09:53-- https://www.directadmin.com/cgi-bin/daupdate?uid=650&lid=3464
=> `update.tar.gz'
Resolving www.directadmin.com... 66.51.122.131
Connecting to www.directadmin.com|66.51.122.131|:443... connected.
WARNING: Certificate verification error for www.directadmin.com: unable to get local issuer certificate
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]

[ <=> ] 45 --.--K/s

17:09:53 (2.15 MB/s) - `update.tar.gz' saved [45]

-su-2.05b# ls -la update.tar.gz
-rw------- 1 diradmin diradmin 45 Oct 20 17:09 update.tar.gz
-su-2.05b# cat update.tar.gz
* You are not allowed to run this program *

-su-2.05b#
Click to expand...
 
about the --no-check-certificate
is there some problem of just using this option, instead of upgrading wget?
 
I've got 45 DA servers up and running in 2 datacenters (RH9, FC, Cent) - all are now displaying this error, even after the latest upgrade

Server Version 1.25.3
Current Available Version 1.253000
Click to expand...

To manually have to login to each server, with a UID/LID and do this is going to take forever. Wouldn't this qualify as a bugfix release 1.25.4 ?
 
You must log in or register to reply here.
Back
Top