Floating Point exception

[lions-tambua.livejournal.com]

thinking: . o O (Lets see what /var/log/messages says)

me: Please send me an complete report of the system. i'll send you an tool
customre: Ok
------
file sent.
mail from CS:
File is too big to send via email. please give me an FTP Link where i can upload it.
thinking: . o O (Ok, i cant recieve more then 3,5mb here. so it might be about 5mb. thats already unusually BIG for that report (zipped!)
------
file recieved
file size: 54mb .zip file!
i didnt notice. -> Unzip

Open Report
1) no info
2) no info
3) no info
4) no info
thinking . o O (any usefull informations in that Report ????)
5) no information
6) /var/log/messages *click*
*waiting*
*still waiting*
System freezes.... uh oh...
7) kill every process on system
8) system unfreezed
9) try open /var/log/messages with .....oh.. better not.
i dont think i have an editor on my main-Workstation that would be able to open an 1.3gb Text-file.
and iam not sure if i want to read 1.3gb of text

HELLO ????? /var/log/message with 1.3gb ? *knockknock* anyone home ??

okay.... mail to customer
Please "tail" me the last 300 rows of /var/log/messages
--------------------
waiting for further infos from customer *pffffff*

Comments

[torkell]

I have to admit, log files compress suprisingly well. Was trying to sort out some stuff with web logs from a friends website, and was a bit suprised to see the 2.5MB bzip2 files turn into ~90MB logfiles. I *did* wonder why they took a while to uncompress...

If you're determined to open it, then something like more/less would probably be your best bet. Failing that, a decent hex editor should cope. The trick is finding a program that only loads the file as needed, rather than loading the entire file into memory.

[lions-tambua.livejournal.com]

yea ;) but 1.3gb ?? *G*
oh.. btw... whole log looks like:
Oct 25 13:42:44 serv15 sshd(pam_unix)[25421]: session opened for user root by (uid=0)
Oct 25 13:42:45 serv15 sshd(pam_unix)[25421]: session closed for user root
Oct 25 13:42:46 serv15 sshd(pam_unix)[25429]: session opened for user root by (uid=0)
Oct 25 13:42:46 serv15 sshd(pam_unix)[25429]: session closed for user root
Oct 25 13:44:17 serv15 sshd(pam_unix)[25439]: session opened for user root by (uid=0)
Oct 25 13:44:17 serv15 sshd(pam_unix)[25439]: session closed for user root

[reynardo.livejournal.com]

So he's rooted then?




*ducks*

[lions-tambua.livejournal.com]

I'd say... too much "root beer" :))

[compwizrd.livejournal.com]

walk him through logrotate? :)

[lions-tambua.livejournal.com]

there is logrotate installed. but it doesnt seem to work on Redhat AS 2.1

[jon787.livejournal.com]

There is a group[1] here at my college who runs a server that regularly has multi-gig log files because they never rotate them.


(where s/group/undergraduate student government/)

[jecook]

Ouchies.

Frankly, I'm not quite sure how large the 'messages' logfile I have on universe is. Now my httpd.access log, that's another story... ::snicker::

[lions-tambua.livejournal.com]

if the messages is going to be really BIG, there is something wrong with the system ;)
as written above, it gets spammed full with just 2 repeating rows.
looks like cron-job hung up somewhere

Solution

[lions-tambua.livejournal.com]

Reboot.
after 337 days of uptime, system just needed to be rebooted. moved log and the admin will see if messages will be spammed again ;)