Problem viewing, doesnt seem to be permissions

[opus]

The link is http://12.32.44.140:88/images , this page obviously is readable, if you click on the link to get to the photo album though, you cant view the images. Everything in the 'images' and below is 777. What am I missing here??

[senshi]

This is Abyss users group and not Swiggle forum or help desk as it would be their job to help you, your issue is not a server one.

Also it looks like its designed for apachie servers...

[opus]

Nice way to win people wanting to change over to Abyss.....you are a GREAT asset to this forum board.

It is not a Swiggle issue, it seems to be an Abyss issue. I duplicate this on my Thttpd server and it is fine.

[senshi]

Well give that you have already asked server questions about abyss and presented issues about abyss and have been found to be running another server other than abyss, what do you expect.

Putting up the Abyss logo in and index.html page, anyone can do that, just because you present a front that your running abyss, doesnt mean that you are.

This is an exerpt from the vendors site...

[opus]

What part of this dont you understand? I am running Abyss on a different server. Swiggle works fine on every other server I have it on. I dont care a bit about the guy that wrote it, it is ported for BSD and has always worked fine.

Abyss doesnt seem to want to read dirs with a . in front of it. As in .scaled or .thumbs.

As is: http://12.32.44.140:88/images/cowans/.scaled/

[senshi]

Perhaps you should ask Aprelium about it and give them a full spec on your config and let them look into it.

I would point out that image size will also play a part in this, if the image is too large, like some of yout thumbs are, theyre well large, a thumb needs to be <10k or you will find that the browser will drop the downloading because it takes too long.

Try www.spinwave.com to crunch your .jpg's

[opus]

The thumbs are only 11k-40k maximum, which then leads you to a scaled size which ranges from 40k -70k.

My config is default as far as Abyss goes.

[opus]

The problem was what I thought. Abyss will not read files or dir's that start with a . (dot), these are hidden files in a Uni system. I hacked the source code and changed the names of the dirs to make it work.

http://12.32.44.140:88/images/

Thanks to the support guys/gals at Aprelium.

[senshi]

Good, you found the problem, I beg to differ on that one about the Abyss not able to read hidden directories, thats what the alias's are for, to put stuff into hidden folders that are not able to be accessed from the root, that possibly where things differ.

Trying to impose other working practices with another server is not how to deal with issues.

Your gallery loads fast, quicker than my ISP homepage, given the number of images.

[opus]

I guess you'll have to take that up with the Aprelium people. They are the ones that told me it wont read a .dir. They told me I could make a symlink but I would have to do too many.

Also, while you are looking, go to my album and try to enlarge an image to its full size. Most people are telling me it is rendering incorrectly. I have made this known to tech support as well.

[senshi]

I would try putting all your large images through a gif or jpg optermiser, a free one is available on line and can do wonders with the file size of the image, the picture degridation is possibly due to data loss or the fact that the image is large and anot all the data was recieved correctly.

www.spinwave.com is a free online tool, and having tried to download images at random, I keep getting a termination error which I believe is due to large file sizes, a typical photo image can be compressed to as little as 13kb with loss but a nice 30kb will store a quality picture for web purposes.

Quote:

GET /images/cowans/scaled/Christmas%20with%20Tate.jpg HTTP/1.1 Host: 12.32.44.140 HTTP/1.1 200 OK Content-Length: 51047 Content-Type: image/jpeg Last-Modified: Sat, 04 Sep 2004 01:57:54 GMT Connection: Close Date: Sun, 05 Sep 2004 00:20:16 GMT Server: Abyss/1.2.3.0-FreeBSD AbyssLib/1.1.0 GET /images/cowans/scaled/Christmas%20with%20Tate.jpg HTTP/1.1 Host: 12.32.44.140 HTTP/1.1 200 OK Content-Length: 51047 Content-Type: image/jpeg Last-Modified: Sat, 04 Sep 2004 01:57:54 GMT Connection: Close Date: Sun, 05 Sep 2004 00:20:20 GMT Server: Abyss/1.2.3.0-FreeBSD AbyssLib/1.1.0 GET /images/cowans/scaled/Christmas%20with%20Tate.jpg HTTP/1.1 Host: 12.32.44.140 HTTP/1.1 200 OK Content-Length: 51047 Content-Type: image/jpeg Last-Modified: Sat, 04 Sep 2004 01:57:54 GMT Connection: Close Date: Sun, 05 Sep 2004 00:20:24 GMT Server: Abyss/1.2.3.0-FreeBSD AbyssLib/1.1.0 The maximum number of retries has been reached.

So try to get your imaged compressed further, this should cure the issue if my assumption is right that its the size of the file, the image size shouldnt make any difference, its the file size thats important.

[opus]

Thats really not an option for someone having about 1000 images. Guess I will stick with Thttpd, I dont have any issues with it. It doesnt do PHP but then again, I dont do PHP either.

I am not sure Abyss is ready for prime-time in BSD land yet. Although I will still play with it some, the though of me changing wont happen too soon.

[senshi]

Given that lots of your images show up fine, it is one of two thing, the picture is corrupted or the browser is dropping the downloading of the image because its too large, the server doesnt do anything to the image, it simply delivers the request for data, the browser is what does the dropping, it is internal.

Looking through your site, the gallery loads lots of pictures fine, so like I said, I would be that your images when being processed by swiggle were corrupted as the thumbs show up fine, which draws me to the size issue, as the thumbs are very small files, the larger images is what seem to be the issue and IM still leaning on the file size issue and more in the direction of swiggle as the root cause.

[opus]

These images should be able to be 2mb in size, if I desire. They should render fine at any size. My main photo album http://photos.milneweb.com , which is hosted on Thttpd with Swiggle, doent have any issues at all. I find it rather odd that only the images on the Abyss server have issues.

[senshi]

Just to clarify...

I read in the swiggle site that the images are processed and stored in a directory system that also represents the various image gallerys.

Am I right in assumbing that swiggle processes the directory of images and produces thumbnails or are the produced on-the-fly? I ask because it seems odd that most load up fine yet others are corrupt

I do notice one thing, the difference between the one URL you provide and the abyss URL you supply, are they on different machines? I ask because I notice that the Abyss server seems to stutter with its image delivery and your other server does not, it could be load balancing, the other server is consuming bandwidth which is causing the issue with the other machine.

OR

it could be that could be the issue, the hardware could be causing the problem or a congested LAN, what typoe of LAN do you use? a passive or active HUB or a Network device like a port switch/router? I ask because you coulsd be recieving lots of network collisions. Theirs many things other than software that could cause the issue.

Something as silly as a dirty RJ45 connection could cause problems, had one similar example when I studied NET+ where a LAN car seemed to work fine but images ended up garbled. Try checking connects between your machine and the modem. Elimiating hardware after software issues cannot be resolved is usually the way to go next.

The real test if it is not hardware is to shut your other server off and see if your abyss serves up and if not, rebuild the swiggle directory and try again.

You have to try allsorts of things to find the cause of the problem.