Topic
  • 7 replies
  • Latest Post - ‏2013-09-25T16:19:37Z by Stan
ChiFeng
ChiFeng
6 Posts

Pinned topic Start Instance SWS error

‏2013-09-23T05:56:09Z |

I follow the Installation video to install the Streams 3.1 on CentOS 6.4

after I start a instance and got sws error

it shows the following msg 

-----------------------------

# streamsdev.localdomain: ###########################################
# streamsdev.localdomain: Successfully started daemons: aas,srm,sch,sam
# streamsdev.localdomain: FAILED daemon startup: sws
# streamsdev.localdomain: ===========================================
# streamsdev.localdomain: sws startup msgs:
# streamsdev.localdomain: ++ exporting trace level error
# streamsdev.localdomain: Using java: /opt/ibm/InfoSphereStreams/java/bin/java

...

# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtil.createPrintWriterFor(LibertyUtil.java:120)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtilUpdate.doIt(LibertyUtilUpdate.java:176)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtilPreStart.doIt(LibertyUtilPreStart.java:528)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtilPreStart.main(LibertyUtilPreStart.java:1303)
# streamsdev.localdomain: Caused by: java.io.FileNotFoundException: /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env (Permission denied)
# streamsdev.localdomain:     at java.io.FileOutputStream.open(Native Method)
# streamsdev.localdomain:     at java.io.FileOutputStream.<init>(FileOutputStream.java:191)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtil.createPrintWriterFor(LibertyUtil.java:117)
# streamsdev.localdomain:     ... 3 more
# streamsdev.localdomain: [9/23/13 1:39:07 PM] ERROR:  [LibertyUtilPreStart] (main()) LibertyUtilPreStart.main(): Caught DFEException: Unable to open file </home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env> for writing. [java.lang.Thread.getStackTraceImpl(Thread.java:unavailable)]
# streamsdev.localdomain: com.ibm.distillery.dfe.util.DFEException: Unable to open file </home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env> for writing.
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtil.createPrintWriterFor(LibertyUtil.java:120)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtilUpdate.doIt(LibertyUtilUpdate.java:176)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtilPreStart.doIt(LibertyUtilPreStart.java:528)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtilPreStart.main(LibertyUtilPreStart.java:1303)
# streamsdev.localdomain: Caused by: java.io.FileNotFoundException: /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env (Permission denied)
# streamsdev.localdomain:     at java.io.FileOutputStream.open(Native Method)
# streamsdev.localdomain:     at java.io.FileOutputStream.<init>(FileOutputStream.java:191)
# streamsdev.localdomain:     at com.ibm.streams.sws.liberty.LibertyUtil.createPrintWriterFor(LibertyUtil.java:117)
# streamsdev.localdomain:     ... 3 more
# streamsdev.localdomain: /opt/ibm/InfoSphereStreams/system/impl/bin/sws-start.pl: system() failed with code 1 ()
# streamsdev.localdomain: ===========================================
# streamsdev.localdomain: sws log tail(100):
# streamsdev.localdomain: ###########################################
streamsdev.localdomain failed
Error:  CDISC5173E The system could not process the following number of hosts: 1. See the previous error messages.


CDISC0062I The system is cleaning up after an instance did not start.
CDISC0063I The system is stopping the runtime services of the DefaultInst@CentOS instance.
CDISC0026I The system is stopping the runtime services of the instance immediately.
CDISC0027I The system is stopping the runtime services of the instance. Any failures to stop the services will be ignored.
CDISC0068I The system is stopping in parallel the runtime services of 1 hosts.
CDISC0054I The system is stopping in parallel the distributed name services of the following 1 hosts:
        streamsdev.localdomain
CDISC0055I The system is resetting the NameServiceUrl property of the instance.
Error:  CDISC5181E The instance did not start. The system shut down and cleaned up the instance services.
1
The DefaultInst instance cannot be started.

-------------------------------------------

 

anyone can help me to fix this error?

thanks.

 

  • WarrenAcker
    WarrenAcker
    47 Posts
    ACCEPTED ANSWER

    Re: Start Instance SWS error

    ‏2013-09-24T15:08:13Z  
    • ChiFeng
    • ‏2013-09-24T01:04:54Z

    Hello Warren,

    the user was the same.

    here is the pemissions set

    -------------------------------------------------

    drwxrwxr-x. 3 CentOS CentOS 4096 Sep 16 22:43 apps
    drwxrwxr-x. 2 CentOS CentOS 4096 Sep 16 22:43 dropins
    -rw-rw-r--. 1 CentOS CentOS   51 Sep 23 13:45 jvm.options
    -rw-rw-r--. 1 CentOS CentOS   56 Sep 16 22:43 server.env
    -rw-rw-r--. 1 CentOS CentOS  304 Sep 16 22:43 server.xml
    drwxrwxr-x. 2 CentOS CentOS 4096 Sep 16 22:43 workarea

    --------------------------------------------------

    Thanks,

    ChiFeng

     

    Hi ChiFeng,

    I noticed that you are running SELinux in enforcing mode, and I'm guessing that this is an issue with CentOS and how InfoSphere Streams is doing SELinux labelling there.  To prove this, I need two things.  First, run "ls -Z" in the directory you checked permissions in, and copy the results here.  Secondly, please attach the audit.log file from the /var/log/audit directory.  This should show us if something is wrong with how the security was set up for the files.

    To work around this for now if possible, you can try to run with SELinux set to permissive.

    Thanks,

    Warren

  • Stan
    Stan
    76 Posts

    Re: Start Instance SWS error

    ‏2013-09-23T14:22:24Z  

    The errors indicate permisison problems in the /home/CetnOS directory tree.  Are you starting the instance as the user CentOS?  If so please check that the direcotries in the tree are all owned by the user CentOS.

      # streamsdev.localdomain: Caused by: java.io.FileNotFoundException: /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env (Permission denied)

    If that is not the problem please

    1) post the full sws.0.log (in /hone/CentOS/.streams/logs/sws

    2) And the output from dependency_checker.sh $STREAMS_INSTALL/bin

  • WarrenAcker
    WarrenAcker
    47 Posts

    Re: Start Instance SWS error

    ‏2013-09-23T14:24:21Z  

    Hi ChiFeng,

    Was the same user account used for the mkinstance and startinstance commands?  Only the instance owner can start the instances they created. 

    If the same user was used, please post the permissions set for the /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver directory.  Also, if the /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/jvm.options and /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env files already exist, please post the permissions for those files.

    Thanks,

    Warren

  • ChiFeng
    ChiFeng
    6 Posts

    Re: Start Instance SWS error

    ‏2013-09-24T01:04:54Z  

    Hi ChiFeng,

    Was the same user account used for the mkinstance and startinstance commands?  Only the instance owner can start the instances they created. 

    If the same user was used, please post the permissions set for the /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver directory.  Also, if the /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/jvm.options and /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env files already exist, please post the permissions for those files.

    Thanks,

    Warren

    Hello Warren,

    the user was the same.

    here is the pemissions set

    -------------------------------------------------

    drwxrwxr-x. 3 CentOS CentOS 4096 Sep 16 22:43 apps
    drwxrwxr-x. 2 CentOS CentOS 4096 Sep 16 22:43 dropins
    -rw-rw-r--. 1 CentOS CentOS   51 Sep 23 13:45 jvm.options
    -rw-rw-r--. 1 CentOS CentOS   56 Sep 16 22:43 server.env
    -rw-rw-r--. 1 CentOS CentOS  304 Sep 16 22:43 server.xml
    drwxrwxr-x. 2 CentOS CentOS 4096 Sep 16 22:43 workarea

    --------------------------------------------------

    Thanks,

    ChiFeng

     

  • ChiFeng
    ChiFeng
    6 Posts

    Re: Start Instance SWS error

    ‏2013-09-24T01:39:52Z  
    • Stan
    • ‏2013-09-23T14:22:24Z

    The errors indicate permisison problems in the /home/CetnOS directory tree.  Are you starting the instance as the user CentOS?  If so please check that the direcotries in the tree are all owned by the user CentOS.

      # streamsdev.localdomain: Caused by: java.io.FileNotFoundException: /home/CentOS/.streams/instances/DefaultInst@CentOS/sws/usr/servers/swsserver/server.env (Permission denied)

    If that is not the problem please

    1) post the full sws.0.log (in /hone/CentOS/.streams/logs/sws

    2) And the output from dependency_checker.sh $STREAMS_INSTALL/bin

    Hi Stan,

    1) sws.0.log file is empty

    -rw-rw-r--. 1 CentOS CentOS 0 Sep 16 22:43 sws.0.log

    2)

    IBM InfoSphere Streams 3.1.0.0 Trial Dependency Checker
    Date:  Tue Sep 24 09:25:31 CST 2013

    === System Information ===
    * Hostname:  streamsdev.localdomain
    * IP address:  172.16.20.132
    * Operating system:  CentOS release 6.4 (Final)
    * System architecture:  x86_64
    * Security-Enhanced Linux setting:  Enforcing
    * Default Java:   
      * Java vendor:  IBM Corporation
      * Java version:  1.6.0
      * Java VM version:  2.4
      * Java runtime version:  pxa6460sr13fp1-20130325_01 (SR13 FP1)
      * Java full version:  JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr13-20130114_134867 (JIT enabled, AOT enabled)
    J9VM - 20130114_134867
    JIT  - r9_20130108_31100
    GC   - 20121212_AA
      * Java system encoding:  UTF-8
    * Java Home:  /opt/ibm/InfoSphereStreams/java
      * Java vendor:  IBM Corporation
      * Java version:  1.6.0
      * Java VM version:  2.4
      * Java runtime version:  pxa6460sr13fp1-20130325_01 (SR13 FP1)
      * Java full version:  JRE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460sr13-20130114_134867 (JIT enabled, AOT enabled)
    J9VM - 20130114_134867
    JIT  - r9_20130108_31100
    GC   - 20121212_AA
      * Java system encoding:  UTF-8
    * Encoding:  UTF-8

    === System Configuration Check ===
    * Status:  PASS - Check:  Hostname and IP address check
    * Status:  PASS - Check:  Operating system version check
    * Status:  PASS - Check:  Architecture check
    * Status:  PASS - Check:  Encoding check

    === Software Dependency Package Check ===
    * Status:  CORRECT VERSION - Package:  bash, System Version:  4.1.2-15.el6_4
    * Status:  CORRECT VERSION - Package:  bind-utils, System Version:  9.8.2-0.17.rc1.el6_4.6
    * Status:  CORRECT VERSION - Package:  bzip2-libs, System Version:  1.0.5-7.el6_0
    * Status:  CORRECT VERSION - Package:  coreutils, System Version:  8.4-19.el6_4.2
    * Status:  CORRECT VERSION - Package:  diffutils, System Version:  2.8.1-28.el6
    * Status:  CORRECT VERSION - Package:  findutils, System Version:  4.4.2-6.el6
    * Status:  CORRECT VERSION - Package:  gawk, System Version:  3.1.7-10.el6
    * Status:  CORRECT VERSION - Package:  gcc, System Version:  4.4.7-3.el6
    * Status:  CORRECT VERSION - Package:  gcc-c++, System Version:  4.4.7-3.el6
    * Status:  CORRECT VERSION - Package:  glibc-common, System Version:  2.12-1.107.el6_4.4
    * Status:  CORRECT VERSION - Package:  grep, System Version:  2.6.3-3.el6
    * Status:  CORRECT VERSION - Package:  iproute, System Version:  2.6.32-23.el6
    * Status:  CORRECT VERSION - Package:  libcurl-devel, System Version:  7.19.7-37.el6_4
    * Status:  CORRECT VERSION - Package:  libselinux-utils, System Version:  2.0.94-5.3.el6_4.1
    * Status:  CORRECT VERSION - Package:  libstdc++, System Version:  4.4.7-3.el6
    * Status:  CORRECT VERSION - Package:  libxslt, System Version:  1.1.26-2.el6_3.1
    * Status:  CORRECT VERSION - Package:  make, System Version:  3.81-20.el6
    * Status:  CORRECT VERSION - Package:  net-tools, System Version:  1.60-110.el6_2
    * Status:  CORRECT VERSION - Package:  openssh-clients, System Version:  5.3p1-84.1.el6
    * Status:  CORRECT VERSION - Package:  openssl, System Version:  1.0.0-27.el6_4.2
    * Status:  CORRECT VERSION - Package:  pam, System Version:  1.1.1-13.el6
    * Status:  CORRECT VERSION - Package:  perl, System Version:  5.10.1-131.el6_4
    * Status:  CORRECT VERSION - Package:  perl-Time-HiRes, System Version:  1.9721-131.el6_4
    * Status:  CORRECT VERSION - Package:  perl-XML-Simple, System Version:  2.18-6.el6
    * Status:  CORRECT VERSION - Package:  policycoreutils, System Version:  2.0.83-19.30.el6
    * Status:  CORRECT VERSION - Package:  policycoreutils-python, System Version:  2.0.83-19.30.el6
    * Status:  CORRECT VERSION - Package:  procps, System Version:  3.2.8-25.el6
    * Status:  CORRECT VERSION - Package:  rpm, System Version:  4.8.0-32.el6
    * Status:  CORRECT VERSION - Package:  sed, System Version:  4.2.1-10.el6
    * Status:  CORRECT VERSION - Package:  selinux-policy, System Version:  3.7.19-195.el6_4.12
    * Status:  CORRECT VERSION - Package:  selinux-policy-targeted, System Version:  3.7.19-195.el6_4.12
    * Status:  CORRECT VERSION - Package:  tar, System Version:  1.23-11.el6
    * Status:  CORRECT VERSION - Package:  unzip, System Version:  6.0-1.el6
    * Status:  CORRECT VERSION - Package:  util-linux-ng, System Version:  2.17.2-12.9.el6_4.3
    * Status:  CORRECT VERSION - Package:  which, System Version:  2.19-6.el6
    * Status:  CORRECT VERSION - Package:  xdg-utils, System Version:  1.0.2-17.20091016cvs.el6
    * Status:  CORRECT VERSION - Package:  zip, System Version:  3.0-1.el6

    === Summary of Errors and Warnings ===

    CDISI0003I The dependency checker evaluated the system and did not find errors or warnings.

    --------

    Thanks,

    ChiFeng.

  • WarrenAcker
    WarrenAcker
    47 Posts

    Re: Start Instance SWS error

    ‏2013-09-24T15:08:13Z  
    • ChiFeng
    • ‏2013-09-24T01:04:54Z

    Hello Warren,

    the user was the same.

    here is the pemissions set

    -------------------------------------------------

    drwxrwxr-x. 3 CentOS CentOS 4096 Sep 16 22:43 apps
    drwxrwxr-x. 2 CentOS CentOS 4096 Sep 16 22:43 dropins
    -rw-rw-r--. 1 CentOS CentOS   51 Sep 23 13:45 jvm.options
    -rw-rw-r--. 1 CentOS CentOS   56 Sep 16 22:43 server.env
    -rw-rw-r--. 1 CentOS CentOS  304 Sep 16 22:43 server.xml
    drwxrwxr-x. 2 CentOS CentOS 4096 Sep 16 22:43 workarea

    --------------------------------------------------

    Thanks,

    ChiFeng

     

    Hi ChiFeng,

    I noticed that you are running SELinux in enforcing mode, and I'm guessing that this is an issue with CentOS and how InfoSphere Streams is doing SELinux labelling there.  To prove this, I need two things.  First, run "ls -Z" in the directory you checked permissions in, and copy the results here.  Secondly, please attach the audit.log file from the /var/log/audit directory.  This should show us if something is wrong with how the security was set up for the files.

    To work around this for now if possible, you can try to run with SELinux set to permissive.

    Thanks,

    Warren

  • ChiFeng
    ChiFeng
    6 Posts

    Re: Start Instance SWS error

    ‏2013-09-25T02:19:43Z  

    Hi ChiFeng,

    I noticed that you are running SELinux in enforcing mode, and I'm guessing that this is an issue with CentOS and how InfoSphere Streams is doing SELinux labelling there.  To prove this, I need two things.  First, run "ls -Z" in the directory you checked permissions in, and copy the results here.  Secondly, please attach the audit.log file from the /var/log/audit directory.  This should show us if something is wrong with how the security was set up for the files.

    To work around this for now if possible, you can try to run with SELinux set to permissive.

    Thanks,

    Warren

    Hi Warren,

    after I set the SELinux to pemissive and the instance started successfully!!

    Thanks a lots for your help,

    ChiFeng

    ------------------------------

    First)

    drwxrwxr-x. CentOS CentOS system_u:object_r:user_home_dir_t:s0 apps
    drwxrwxr-x. CentOS CentOS system_u:object_r:user_home_dir_t:s0 dropins
    -rw-rw-r--. CentOS CentOS unconfined_u:object_r:user_home_t:s0 jvm.options
    -rw-rw-r--. CentOS CentOS system_u:object_r:user_home_dir_t:s0 server.env
    -rw-rw-r--. CentOS CentOS system_u:object_r:user_home_dir_t:s0 server.xml
    drwxrwxr-x. CentOS CentOS system_u:object_r:user_home_dir_t:s0 workarea

     

    Secondly)

    there is no audit.log file in the directory

  • Stan
    Stan
    76 Posts

    Re: Start Instance SWS error

    ‏2013-09-25T16:19:37Z  
    • ChiFeng
    • ‏2013-09-25T02:19:43Z

    Hi Warren,

    after I set the SELinux to pemissive and the instance started successfully!!

    Thanks a lots for your help,

    ChiFeng

    ------------------------------

    First)

    drwxrwxr-x. CentOS CentOS system_u:object_r:user_home_dir_t:s0 apps
    drwxrwxr-x. CentOS CentOS system_u:object_r:user_home_dir_t:s0 dropins
    -rw-rw-r--. CentOS CentOS unconfined_u:object_r:user_home_t:s0 jvm.options
    -rw-rw-r--. CentOS CentOS system_u:object_r:user_home_dir_t:s0 server.env
    -rw-rw-r--. CentOS CentOS system_u:object_r:user_home_dir_t:s0 server.xml
    drwxrwxr-x. CentOS CentOS system_u:object_r:user_home_dir_t:s0 workarea

     

    Secondly)

    there is no audit.log file in the directory

    An alternate location is /var/log/messages - would you check there for the audit.log

    For more information on Selinux and CentOS - including the excerpt below, see http://wiki.centos.org/HowTos/SELinux#head-02c04b0b030dd3c3d58bb7acbbcff033505dd3af

    To troubleshoot any issue, the log files are key and SELinux is no different. By default SELinux log messages are written to /var/log/audit/audit.log via the Linux Auditing System auditd, which is started by default. If the auditd daemon is not running, then messages are written to /var/log/messages . SELinux log messages are labeled with the "AVC" keyword so that they might be easily filtered from other messages, as with grep.