insane console log size. Safe to delete.

[TheNightPhoenix]

I noticed recently that my hard drive was very very full.
I deleted a load of old crap and counted the major folder sizes up and they came to about 150 gig, but the drive has 300 gig in use.
Did a quick check in diskinventoryx and I found this bugger (see pic) a insane 72gig log file...

is it safe to delete and what could have caused this?

 

[WildCowboy]

Yep, they're usually safe to delete. If it happens again (or if you're just curious) you might try to investigate to see what caused it, but it's likely just a one-off occurrence.

 

[TheNightPhoenix]

Yep, they're usually safe to delete. If it happens again (or if you're just curious) you might try to investigate to see what caused it, but it's likely just a one-off occurrence.

Yer just going to delte it... any idea how to find out what made this?

 

[mac-convert]

Use the utility supplied in OS X

Applications | Utilities | Console

In the console app, click File and choose console.log

If you don't have a toolbar in the log window, click View | Show Toolbar

Use the clear button - the only safe way to do this that I know of.

EDIT: I just noticed that this was an older one - my bad...

 

[WildCowboy]

Yer just going to delte it... any idea how to find out what made this?

You'd have to open it in Console and look at what the entries say...it's likely a single entry repeated over and over. I just don't know how happy Console (and your system in general) would be trying to open a 72 GB log file.

 

[TheNightPhoenix]

I decided to to find out what it is.
I just wanted my hardrive space back!

P.S. Thanks for the speedy responses.

 

[mac-convert]

Use the utility supplied in OS X

Use the clear button - the only safe way to do this that I know of.

EDIT: I just noticed that this was an older one - my bad...

Apologies - (trying to watch Duke and Maryland while I answered this)

I meant to say use the File | Delete option. The reason is that I have seen problems in the past with people trying to delete the console.log (or other active logs). I "assume" that this app would take care of this cleanly.

WildCowboy - I agree - useless to look at this...

 

[Hoef]

what program

I noticed recently that my hard drive was very very full.
I deleted a load of old crap and counted the major folder sizes up and they came to about 150 gig, but the drive has 300 gig in use.
Did a quick check in diskinventoryx and I found this bugger (see pic) a insane 72gig log file...

is it safe to delete and what could have caused this?

Sorry, I am still an OSX noob .... what program did you use to create the file size "map"?

 

[WildCowboy]

Sorry, I am still an OSX noob .... what program did you use to create the file size "map"?

It's Disk Inventory X.

 

[4np]

You'd have to open it in Console and look at what the entries say...it's likely a single entry repeated over and over. I just don't know how happy Console (and your system in general) would be trying to open a 72 GB log file.

you could start terminal and do a:

sudo tail -n 1000 /var/log/console.log.3 | more

 

[akadmon]

It's Disk Inventory X.

Neat app -- thanks for the link!

 

[Hoef]

It's Disk Inventory X.

Excellent .. Thanks!

 

[blackscooby]

you could start terminal and do a:

sudo tail -n 1000 /var/log/console.log.3 | more

If it were my system I'd be more than interested to see what the hell it was writing.

sudo head -n 1000 /var/log/console.log.3 | more
to see the top entries to the file (earliest) and then tail to look at the end. You'll then know how long it took to use up that massive amount of space.

 

[sturigdson]

If it were my system I'd be more than interested to see what the hell it was writing.

sudo head -n 1000 /var/log/console.log.3 | more
to see the top entries to the file (earliest) and then tail to look at the end. You'll then know how long it took to use up that massive amount of space.

No doubt. It could be a serious software conflict, or a strange bug. These kinds of problems can be caused by any number of conflicts, it'd be very helpful to see what caused it.

 

[TheNightPhoenix]

Oh well too late!

Do you really believe its that big a deal not knowing what it was?