Can't deploy dcm4chee.archive:service=FileSystemMgt,group=ONLINE_STORAGE after running out of space

[simonmd]

Hi all,

One of my servers ran out of disk space. After clearing up some and restarting dcm4chee, I can access existing studies but cannot store. The log shows that the dcm4chee.archive:service=FileSystemMgt,group=ONLINE_STORAGE MBean failed to deploy:

--- Incompletely deployed packages ---

org.jboss.deployment.DeploymentInfo@e604ad08 { url=file:/home/deployer/apps/pacs/server/default/deploy/dcm4chee-fsmgt-online-service.xml }

  deployer: org.jboss.deployment.SARDeployer@59b55e85

  status: Deployment FAILED reason: - nested throwable: (java.lang.reflect.InvocationTargetException)

  state: FAILED

  watch: file:/home/deployer/apps/pacs/server/default/deploy/dcm4chee-fsmgt-online-service.xml

Tracing it up in server.log, I see:

2014-11-04 10:01:04,087 ERROR -> (main) [STDERR] [Fatal Error] :-1:-1: Premature end of file.

2014-11-04 10:01:04,090 WARN  -> (main) [org.jboss.mx.persistence.DelegatingPersistenceManager] Caught exception while loading

org.xml.sax.SAXParseException; Premature end of file.

at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)

and:

2014-11-04 10:01:04,092 WARN  -> (main) [org.jboss.mx.server.registry.BasicMBeanRegistry] javax.management.MBeanRegistrationException: preRegister() failed: [ObjectName='dcm4chee.archive:service=FileSystemMgt,group=ONLINE_STORAGE', Class=org.dcm4chex.archive.mbean.FileSystemMgt2Service (org.dcm4chex.archive.mbean.FileSystemMgt2Service@42c04e90)]

2014-11-04 10:01:04,092 INFO  -> (main) [org.dcm4chex.archive.mbean.FileSystemMgt2Service] Registration is not done -> stop

2014-11-04 10:01:04,095 ERROR -> (main) [org.jboss.deployment.MainDeployer] Could not create deployment: file:/home/deployer/apps/pacs/server/default/deploy/dcm4chee-fsmgt-online-service.xml

org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.InvocationTargetException)

Thinking maybe the server/default/deploy/dcm4chee-fsmgt-online-service.xml had become corrupted, I compared it to one from a working server but they appear identical.

Any tips on how I may debug or solve this problem? They would be most appreciated!

(I am attaching the relevant server.log and dcm4chee-fsmgt-online-service.xml files)

[fleetwoodfc]

Usually it is the current configuration files stored in the ../server/default/data/xmbean-attrs folder that get corrupted - changes made via jmx-console are persisted in these files. You can delete the corrupt copy and the system will revert back to the default settings as defined by the xmbean files in the conf/xmdesc folder.

[simonmd]

You sir, are a life-saver :D

Thank you!

[Markus Holzer]

Thanks, had exactly the same issue!

[Cedric Simon]

Another live saved :D

Thank you.

Now I am taking copy of that folder, just in case.

[Gustavo Fernandez Guirland]

Excellent @fleetwoodfc, the same thing happened to me after a power failure and UPS failure. I renamed the folder and autogenerated it with the original configuration. Congratulations on your contribution

gustavo.fernandez@linux-csi0:~> /opt/dcm4chee/server/default/data # ls -la
total 28
drwxr-xr-x  4 root root  4096 nov 27  2015 .
drwxr-xr-x 14 root root  4096 nov 27  2015 ..
-rw-r--r--  1 root root    46 nov 27  2015 jboss.identity
drwxr-xr-x  4 root root  4096 nov 27  2015 tx-object-store
drwxr-xr-x  2 root root 12288 nov 27  2015 xmbean-attrs

gustavo.fernandez@linux-csi0:~> mv xmbean-attrs/ xmbean-attrs_corrupto

gustavo.fernandez@linux-csi0:~> /opt/dcm4chee/server/default/data # service dcm4chee status
dcm4chee.service - LSB: JBoss 4.2 Server
   Loaded: loaded (/etc/init.d/dcm4chee)
   Active: active (running) since Mon 2016-12-12 17:18:41 UYT; 16h ago
  Process: 4207 ExecStop=/etc/init.d/dcm4chee stop (code=exited, status=0/SUCCESS)
  Process: 4505 ExecStart=/etc/init.d/dcm4chee start (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/dcm4chee.service
           |-4506 /bin/sh /opt/dcm4chee/bin/run.sh -b 0.0.0.0
           `-4532 java -Dprogram.name=run.sh -server -Xms512m -Xmx2048m -XX:MaxPermSize=256m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.messaging.ServerPeerID=0 -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl -Djava.awt.headless=true -Dapp.name=dcm4chee -Djava.net.preferIPv4Stack=true -Djava.library.path=/opt/dcm4chee/bin/native -Djava.endorsed.dirs=/opt/dcm4chee/lib/endorsed -classpath /opt/dcm4chee/bin/run.jar org.jboss.Main -b 0.0.0.0 -b 0.0.0.0

gustavo.fernandez@linux-csi0:~> /opt/dcm4chee/server/default/data # service dcm4chee stop
gustavo.fernandez@linux-csi0:~> /opt/dcm4chee/server/default/data # service dcm4chee start

AND VOILÁ