[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re:[cobalt-users] var partition full? (was RaQ3 Telnet Login Not Working)
- Subject: Re:[cobalt-users] var partition full? (was RaQ3 Telnet Login Not Working)
- From: RaQ3 <cobalt@xxxxxxxxxxx>
- Date: Wed Feb 21 04:36:40 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Wayne Sagar <wsagar@xxxxxxxx> wrote on 20.02.01 23:44:39:
>
>Backspacing to my original post... after numerous tries at getting my
>co-location to do anything for my "unmanaged" dedicated RaQ3..... and
>finally getting to talk with someone who would cop to something more
>than an "it's your problem stance" to which my reply has been.. "it
>may be my problem but if I can't log in via telnet, what can I do
>about it other than move to another co-location?"....
>
>Long story short... Rather than a "hack" causing this problem, it
>seems. . and I hope this is true.. the problem lies in my var
>partition being full due to some huge log files in there... Problem: I
>can't do a thing about it, being unable to log in via telnet... ftp,
>server mail, all virtual sites seem to be operating fine.. Getting DNS
>server problem light in active monitor but even that seems to be
>erroneous, as the system seems able to resolve all domain requests to
>virtual's to the proper place (single ip server)
Hi Wayne !
Just a little idea to try:
Reboot the server after the normal cron jobs (I think 4 am) and telnet
in right after it. It might be that you have a few bytes more then.
And - simple second idea:
If you still have ftp. Why don't you delete stuff with ftp. Maybe a
large site that you can easily rebuild. Or a site that has some huge
graphics on it. Make an admin ftp and delete some logs (?).
Gives you the extra space needed to work with the server ...
Not sure on this but sounds logical to me.
But - a little hint: If the DNS also causes problems I still would look
for hack traces ...
Good luck !
Thomas
--
InternAd.de
Internet Advertising
Thomas Prosi
tp@xxxxxxxxxxx