That did it. Once I moved the logs over to folder on /dev drive and deleted the old logs directory it started up.
Thanks! -----Original Message----- From: Maki Watanabe [mailto:watanabe.m...@gmail.com] Sent: Tuesday, May 31, 2011 6:40 PM To: user@cassandra.apache.org Subject: Re: No space left on device problem when starting Cassandra > at org.apache.log4j.Category.info(Category.java:666) It seems that your cassandra can't write log by device full. Check where your cassanra log is written to. The log file path is configured at log4j.appender.R.File property in conf/log4j-server.properties. maki 2011/6/1 Bryce Godfrey <bryce.godf...@azaleos.com>: > Hi there, I'm a bit new to Linux and Cassandra so I'm hoping someone > can help me with this. > > > > I've been evaluating Cassandra for the last few days and I'm now > having a problem starting up the service. I receive this error below > and I'm unsure on where I'm out of space at, and how to free up more. > > > > azadmin@cassandra-01: $ sudo > /usr/tmp/apache-cassandra-0.7.6-2/bin/cassandra > -f > > INFO 18:21:46,830 Logging initialized > > log4j:ERROR Failed to flush writer, > > java.io.IOException: No space left on device > > at java.io.FileOutputStream.writeBytes(Native Method) > > at java.io.FileOutputStream.write(FileOutputStream.java:297) > > at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:220) > > at > sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:290) > > at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:294) > > at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:140) > > at > java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) > > at > org.apache.log4j.helpers.QuietWriter.flush(QuietWriter.java:59) > > at > org.apache.log4j.WriterAppender.subAppend(WriterAppender.java:324) > > at > org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.jav > a:276) > > at > org.apache.log4j.WriterAppender.append(WriterAppender.java:162) > > at > org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) > > at > org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders( > AppenderAttachableImpl.java:66) > > at org.apache.log4j.Category.callAppenders(Category.java:206) > > at org.apache.log4j.Category.forcedLog(Category.java:391) > > at org.apache.log4j.Category.info(Category.java:666) > > at > org.apache.cassandra.service.AbstractCassandraDaemon.<clinit>(Abstract > CassandraDaemon.java:79) > > INFO 18:21:46,841 Heap size: 16818110464/16819159040 > > # > > # A fatal error has been detected by the Java Runtime Environment: > > # > > # SIGBUS (0x7) at pc=0x00007f35b493f571, pid=1234, > tid=139869156091648 > > # > > # JRE version: 6.0_22-b22 > > # Java VM: OpenJDK 64-Bit Server VM (20.0-b11 mixed mode linux-amd64 > compressed oops) > > # Derivative: IcedTea6 1.10.1 > > # Distribution: Ubuntu Natty (development branch), package > 6b22-1.10.1-0ubuntu1 > > # Problematic frame: > > # C [libffi.so.5+0x2571] ffi_prep_java_raw_closure+0x541 > > # > > # An error report file with more information is saved as: > > # /media/commitlogs/hs_err_pid1234.log > > # > > # If you would like to submit a bug report, please include > > # instructions how to reproduce the bug and visit: > > # https://bugs.launchpad.net/ubuntu/+source/openjdk-6/ > > # The crash happened outside the Java Virtual Machine in native code. > > # See problematic frame for where to report the bug. > > # > > > > I seem to have enough space, except in the > /dev/mapper/Cassandra-01-root, and I'm unsure of that anyway: > > azadmin@cassandra-01:/$ df -h > > Filesystem Size Used Avail Use% Mounted on > > /dev/mapper/cassandra--01-root > > 1.2G 1.2G 0 100% / > > none 16G 236K 16G 1% /dev > > none 16G 0 16G 0% /dev/shm > > none 16G 36K 16G 1% /var/run > > none 16G 0 16G 0% /var/lock > > /dev/sdb1 33G 176M 33G 1% /media/commitlogs > > /dev/sdc1 66G 180M 66G 1% /media/data > > /dev/sda1 228M 23M 193M 11% /boot > > > > Thanks, > > ~Bryce
