I'm on a RaQ4r (shared hosting), and am having issues with the "web.sessionlog" file in my logs folder. I've had this account for a few months, and never had a problem until last week when I exceeded the disk space limit on my account because web.sessionlog was 80mb. The support rep. compressed the file and I thought this problem would be over for a while. But then, just a week later, I have the same problem and the file is 70MB this time.

So my 2 questions are:

1. How come I didn't have any issues with this web.sessionlog file for the past few months, and then all of a sudden I have this file size that balloons in size after just a week? My site hasn't gotten that much more hits.

2. How do I avoid this problem? I believe my previous host automatically compressed log files for me. Is there a way to just turn logging off, since I was told that logging (or one of its related functions) wasn't working correctly anyways until Cobalt issues a patch to fix the problem. The site usage page is still showing activity for one day in November.

Poohbie are you with Tera-byte by any chance? I am having the same problem with the server I am on. My web.log froze on Dec 7th. I have to admit while I like everything else about Tera-byte they have to get this problem resolved.

Little of the topic but being on (virtual account) RaQ3i can I just delete all the log files when they get too big for my liking? So that I do not have to re-create those files after deleting (server creates them automatically?)?.

The file are:
ftp.cache.new
ftp.log
ftp.stats
mail.cache.new
mail.log
mail.stats
web.cache.new
web.log
web.stats

thanks

I think it re-creates the log files on its own. you do not have to create it maunaully.

gthorley,

Yup. The support guy just deleted the web log for me, since I couldn't do it myself. I don't know if that means I'll just have to ask them to do it again in a week or not.

My site's been running smoothly without any downtime for the past month or so. Before then, I was having problems, most likely due to someone else on my shared server punishing the CPU at the expense of the rest of us.

But yah, site usage stats in the control panel hasn't been updated since middle of November.

Well poohbie touch wood but I haven't noticed any problems on the server I am on so far. It seems to be a good place to be as I have visited all the domains and an awful lot are small personal sites like my wifes. I noticed a couple that could be problems but so far things are great. Now if they could solve the web.log problem I could go back to using openwebscope right now I get stats from http://www.extreme-dm.com/tracking/
If anyone is interested only a small unobtrusive button needed and no slowdown noticeable

Originally posted by gthorley
It seems to be a good place to be as I have visited all the domains and an awful lot are small personal sites like my wifes.

How is it possible to know the other domains that are on the same server? I would very much like to know what kind of sites I'm hosted with.

I don't know how this works on all servers but on the one I'm on I kept typing cd ../ until it came to the root and there were all these domain names so I just started copying them into my browser to see whoI was keeping company with.

Which host is this? Please tell them about this problem. Its a secuirty issue.

Correct me if I'm wrong, but isn't this the problem with offering telnet access in general? Users can see (they can't touch), but can pretty much see anything they want to see???

i guess I've never looked at this closely, as I always log in as admin but...

Originally posted by kunal
Which host is this? Please tell them about this problem. Its a secuirty issue.
As all you can do is look at names it would seem to be at most a privacy issue than security issue. I don't even see it being a privacy issue as every domain is public unless they password protect it. Interestingly enough I seem to recall that about 3-4 were password protected and totally private. There were about 160 names on the server and about 25 of them were just parked names with no content and very few were significant sites. By far the most were vanity sites. I woonder if this is a typical server.

Yes, it worked for me. About 300 names listed. I did not check them all but mostly they were 1-5 html pages. Many restaurant menu sites and one sex shop but mostly personal or small hobbysites. Lots of empty sites too, at least 20%.

RaQ3i 256RAM
Uptime:
8:19pm up 7 days, 7:31, 3 users, load average: 0.52, 0.29, 0.16

Does '3 users' really mean that there are only 3 people surfing/telnetting/ftp:ing the server at the moment of 'uptime' command? Amazingly small amount considering the 300 domains.

Are there some other things one can learn about the server using telnet? Seems that these are quite helpful tools if you think of 30day trials or money backs.

[Edited by topp on 01-15-2001 at 03:48 PM]

Not surfing, but logged in yes.

Originally posted by gthorley
Originally posted by kunal
Which host is this? Please tell them about this problem. Its a secuirty issue.
As all you can do is look at names it would seem to be at most a privacy issue than security issue. I don't even see it being a privacy issue as every domain is public unless they password protect it. Interestingly enough I seem to recall that about 3-4 were password protected and totally private. There were about 160 names on the server and about 25 of them were just parked names with no content and very few were significant sites. By far the most were vanity sites. I woonder if this is a typical server.


This is. If one can browse through the server, he knows how it is setup. And can be a BIG security problem. I just think it would be a good idea to tell the host about it. I dun wanna go into the details of how the info can be used.

we know exactly how the info can be used and thats the reason why everyones actions are monitored. if anyone from any group other than wheel attempts anything on any other dir structure other than their own, their telnet access is revoked, if they try anything through php their entire account is pulled. this is a problem we must face when we allow clients as many options as we do, but to date i have only pulled two telnet accounts from approx 18,000 users.

Steve

Originally posted by Keeg
we know exactly how the info can be used and thats the reason why everyones actions are monitored. if anyone from any group other than wheel attempts anything on any other dir structure other than their own, their telnet access is revoked, if they try anything through php their entire account is pulled. this is a problem we must face when we allow clients as many options as we do, but to date i have only pulled two telnet accounts from approx 18,000 users.

Steve


Hmm..oh ok.. well as long as you know what your doing and are monitoring telnet sessions closely. Hope nothing happens to the servers ;) :)