SmartStorTools returns "java.io.IOException: No space left on device."

Document ID : KB000020029
Last Modified Date : 14/02/2018
Show Technical Document Details

 Symptoms:

 Seeing the following error when executing SmartStorTools.sh per manual instruction:

./tools/SmartStorTools.sh  test_regex -metrics ".*" -src /opt/wily_data/data/
Debug options:
   file:/tmp/.options not found
An exception occurred while writing to the platform log:
java.io.IOException: No space left on device
       at java.io.FileOutputStream.writeBytes(Native Method)
       at java.io.FileOutputStream.write(FileOutputStream.java:260)
       at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
       at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
       at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
       at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
       at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
       at java.io.BufferedWriter.flush(BufferedWriter.java:236)
       at org.eclipse.core.runtime.adaptor.EclipseLog.log(EclipseLog.java:307)
       at org.eclipse.update.internal.configurator.Utils.log(Utils.java:109)
       at org.eclipse.update.internal.configurator.ConfigurationParser.parse(ConfigurationParser.java:79)
       at org.eclipse.update.internal.configurator.PlatformConfiguration.loadConfig(PlatformConfiguration.java:1101)
       at org.eclipse.update.internal.configurator.PlatformConfiguration.initializeCurrent(PlatformConfiguration.java:756)
       at org.eclipse.update.internal.configurator.PlatformConfiguration.(PlatformConfiguration.java:104)
       at org.eclipse.update.internal.configurator.PlatformConfiguration.startup(PlatformConfiguration.java:710)
       at org.eclipse.update.internal.configurator.ConfigurationActivator.getPlatformConfiguration(ConfigurationActivator.java:382)
       at org.eclipse.update.internal.configurator.ConfigurationActivator.initialize(ConfigurationActivator.java:111)
       at org.eclipse.update.internal.configurator.ConfigurationActivator.start(ConfigurationActivator.java:69)
       at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2.run(BundleContextImpl.java:1009)
       at java.security.AccessController.doPrivileged(Native Method)
       at org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1003)
       at org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:984)
       at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:346)
       at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:355)
       at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1074)
       at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:616)
       at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:508)
       at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:299)
       at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:489)
       at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:211)
       at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:321)
Logging to the console instead.;

 Environment:  

 Introscope 9.1x, 9.5x and 9.6x

 Cause:  

  The /tmp directory is full and has no available space left.

 

 Workaround:

  Make sure disk space is available from /tmp directory. You can run "df -k" to verify this condition