Integration Server starting problem in Linux platform

2004-06-21 14:54:07 EDT [ISS.0025.0001C] Integration Server 6.1 Build 132
2004-06-21 14:54:07 EDT [ISS.0025.0006C] License Manager started
2004-06-21 14:54:07 EDT [ISS.0025.0041C] FIPS mode not initialized
2004-06-21 14:54:08 EDT [BAS.0123.0001C] FSData full consistency check is being
performed. Db:WmRepository4\FSD
2004-06-21 14:54:10 EDT [ISS.0025.0017C] Repository Manager started
2004-06-21 14:54:28 EDT [ISS.0025.0024C] JDBC Connection Manager started
2004-06-21 14:54:33 EDT [ISS.0025.0023C] Audit Log Manager started
com.wm.util.coder.InvalidDatatypeException: [ISC.0076.9009] Root element is null

Does it stuck there and not moving further?

Also is your IS61 abruptly killed session before your restart sever?

Thanks rmg for looking into it.
Yes, it is stuck there and not moving further. I m trying first time to start intgration server after installation. There were no earlier sessions.

Are you starting IS via command line?

HTH,
RMG

I m using Putty to run the Integration Server and using command ‘nohup ./server.sh &’.
And then I m seeing AuditLogManager errors on server.log

-Shiva

Please check this similar error below and esp Resolution part from Empower site:

Description:

Original Article Number : 0 : after a disk full problem, we cannot restart an IS the log generated when launching the IS is com.wm.util.coder.InvalidDatatypeException: [ISC.0076.9009] Root element is null at com.wm.util.coder.XMLCoder.decode(XMLCoder.java:280) at com.wm.util.coder.Coder.readFromFile(Coder.java:143) at com.wm.app.b2b.server.PackageManager.getManifest(PackageManager.java:2308) at com.wm.app.b2b.server.PackageManager.getManifest(PackageManager.java:2274) at com.wm.app.b2b.server.PackageManager.getAllManifests(PackageManager.java:2254) at com.wm.app.b2b.server.PackageManager.loadPackages(PackageManager.java:333) at com.wm.app.b2b.server.PackageManager.init(PackageManager.java:255) at com.wm.app.b2b.server.Server.run(Server.java:411) [HR][/HR]Resolution:

After system runned out of disk space, some manifest.v3 files got corrupted. The command “find ./ -name manifest.v3 | xargs ls -l” showed some zero size files. Restoring them with manifest.bak solved the issue.

HTH,
RMG

Thanks RMG,
This problem resolved a after restoring [COLOR=#333333]manifest.v3

I m trying to start a new Thread (Post) for new topic. I went through following document [/color]http://catb.org/~esr/faqs/smart-questions.html but No related topic.

Actually when I m clicking on New Post a lot of new posts came on the same page. Thanks in advance.