[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-developers] integrate the date in a filename?



the problem... is that there is around 100 domains per box and we really
can't rebuild them.  We know for sure that we don't have a hacker involved
in this, our guess is that we "overuse" the raqs.

I mean that we push them to their limits, they transfer a lot, have tons of
hits, lots of cgis, use php, mysql and we do modifications to have domain
pointers and stuff like that.

I don't know whats happening with this, but id like it to stop bugging every
weekend (is there a weekly cron job meant to crash the system or something?)
;)

-----------
[ Félix C.Courtemanche | Web Designer ]
[ Head Designer | Co-Admin ]
[ webmaster@xxxxxxxxxxxx ]
[ Can-Host Networks | http://can-host.com ]

-----Message d'origine-----
De : Jeff Lasman <jblists@xxxxxxxxxxxxx>
À : cobalt-developers@xxxxxxxxxxxxxxx <cobalt-developers@xxxxxxxxxxxxxxx>
Date : 22 juin, 2000 13:57
Objet : Re: [cobalt-developers] integrate the date in a filename?


>It really sounds to me like these systems have been compromised and
>should be rebuilt.
>
>Jeff
>
>"[Can-Host Networks] Félix C.Courtemanche" wrote:
>
>> Yes, we do make backups, but it looks like the `"records" file that the
raq3
>> is xcreating was corrupted for a long time.  Really so far look at all
the
>> problems we had:
>> RAQ2:
>> -dns total failure, 90% of the dns entries got deleted / corryupted
>> -Missing starting page for some clients on their /siteadmin
>> - last but not least... we CANNOT su from admin to root, but can log in
>> telnet as root.  Now, that means that any web sites that we add on that
>> server request a reboot to be viewable.  That also means that I am unable
to
>> upgrade any version of any software and especially apache modules... any
>> ideas why this would happen?  We are bored of trying to figure out... we
are
>> emptying that server, moving our clients elsewhere so we can re-format
the
>> whole thing.
>> RAQ3:
>> - pgsql backend failure. someday, pgsql stopped working for some unknown
>> reasons, and was fixed by doing a "chmod +t /tmp"... I tried that for an
>> unknown unrelated reason and it fixed... in aprt the problem (pgsql got
back
>> up with all the db corrupted) we then had to fix the db with the provided
>> script in the /usr part of ftp.cobaltnet.com (thanks cobalt)
>> - dns failure again.
>--
>Jeff Lasman <jblists@xxxxxxxxxxxxx>
>nobaloney.net
>P. O. Box 52672
>Riverside, CA  92517
>voice: (909) 787-8589  *  fax: (909) 782-0205
>
>_______________________________________________
>cobalt-developers mailing list
>cobalt-developers@xxxxxxxxxxxxxxx
>http://list.cobalt.com/mailman/listinfo/cobalt-developers
>