mount point

Hi,

when df -k is executed I get somethign like this.

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
703874584 23000708 644542356 4% /
/dev/sda1 101086 19387 76480 21% /boot
tmpfs 1890996 0 1890996 0% /dev/shm
none 703874584 23000708 644542356 4% /iwmnt/default
none 703874584 23000708 644542356 4% /iwmnt/iwadmin

does none here means something is going wrong?
content store anyway is present in another directory /content

Thanks,
Aditya

Find more posts tagged with

Comments

Migrateduser

There is nothing wrong with this, these are the NFS server mount points of TeamSite. Pls refer the documentation for more details.

Adi123

Hi,

ok, now the problem is i we preview the image present in workarea, it does not get rendered in the browser, instead an image box is shown.
When I check properties of this image box, it lists the dimensions of image, but size of image is always 0.

On the backend, the access.log shows the request has been success with http status as 200

What could be going wrong?

Thanks,
Aditya

Report and Data file.zip

Adam Stoller

Hi,

ok, now the problem is i we preview the image present in workarea, it does not get rendered in the browser, instead an image box is shown.
When I check properties of this image box, it lists the dimensions of image, but size of image is always 0.

On the backend, the access.log shows the request has been success with http status as 200

What could be going wrong?

Thanks,
Aditya

These are two very different questions.
This issue is usually due to a proxy setting. Unless the file in question is actually 0-bytes, the problem is usually that your URI for the image is not being interpreted in a manner that allows the browser to find the actual image to display.

To debug - if you cannot figure it out through simpler means - you need to stop iwproxy, run it in debug mode with the output redirected to a file, refresh the page in question, then kill and restart iwproxy in normal mode (so as not to disrupt everyone else), then carefully examine the output in the log file.