UNABLE TO STOP BOOMI ATOM

We were updating Java version using Atmosphere UI and tried to restart the atoms from terminal. All atoms were successfully restarted except one atom. We were getting timeout error while running ./atom stop command. We could see following error message on cluster status page of atmosphere UI.

EW_ID_MISMATCH There are differing view IDs in the various view snapshot files. Severe
These nodes are reporting the issue:
Node 1 10_x_x_x Found different view id [10_x_x_x|90] in "node.10_x_x_x.dat"
Node 2 10_x_x_x Found different view id [10_x_x_x|101] in "node.10_x_x_x.dat"

We analyzed atom logs but could not find the reason for timeout. We killed the process and removed above dat files from $MOLECULE_HOME/bin/views directory. But we got again same problem, we couldn’t stop the atom. So, to troubleshoot further, captured system calls using strace by attaching to running process. Following lines were repeating in the trace log.

open("/tmp/i4jdaemon__data_boomi_Boomi_AtomSphere_Molecule_Molecule_boomi_dev_vmw_molecule_bin_atom", O_RDONLY) = 6 <0.000014>
81678 01:23:42 fstat(6, {st_mode=S_IFREG|0664, st_size=45, …}) = 0 <0.000008>
81678 01:23:42 fstat(6, {st_mode=S_IFREG|0664, st_size=45, …}) = 0 <0.000008>
81678 01:23:42 fcntl(6, F_SETLK, {l_type=F_RDLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = -1 EAGAIN (Resource temporarily unavailable)

From above output, we can conclude that boomi stop script was trying to acquire some sort of lock on /tmp/i4jdaemon__data_boomi_Boomi_AtomSphere_Molecule_Molecule_boomi_dev_vmw_molecule_bin_atom file but it was not succeeding. So, killed the boomi process using kill -9 <pid> command and removed the file starting with i4jdaemon in /tmp directory. After this, we were able to stop and stop atom without any problem.

Comments

Post a Comment

Popular posts from this blog

HOW WE REDUCED SOA OSB PROVISIONING FROM 4 DAYS TO 4 HOURS

 In our organization, we’ve undertaken the task of upgrading both SOA and OSB from version 12.2.1.3 to 12.2.1.4. This involves an out-of-place migration approach, wherein we create a new environment and switch traffic during the cutover. As you know, this process typically requires several days we opt for manual provisioing. A very significant amount of automation work was previously accomplished for 12.2.1.3 by our predecessors. Despite these efforts, the process still used to take lot of time due to following factors: Bugs in existing automation. For example, SOA composite deployments is not stable which warrants lot of manual work Import of 10s of TLS Certificates into KSS Manual retiring and shutting down of services Monitoring setup Miscellaneous: Increasing Log file count, enabling GC logging, changing heap parameters, bash profile changes While our current automation initiatives have yielded substantial savings, we aimed to capitalize on this upgrade activity to enable end-t...
Read more

NOT ABLE TO START RABBITMQ CLUSTER: CANNOT DECLARE A QUEUE ‘~S’ ON NODE ‘~S’: ~255P

We have 7 node rabbitmq cluster and we are using sharding queues. We have shutdown all non prod rabbitmq nodes as part of VM patching. As it was non prod, we thought of shutting down all together instead of rolling patching. We couldn’t start the any of the rabbitmq post patching. All of nodes were failing to start with the below error: 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> “Cannot declare a queue ‘~s’ on node ‘~s’: ~255p”, 2022-06-23 05:13:10.104845-07:00 [error] <0.647.0> [“queue ‘sharding: shard.my.queue – rabbit@rabbit1’ in vhost ‘my_vhost'” This is a known issue in some old versions of rabbitmq. rabbitmq node fails to come up with above error. Work around for this is to disable sharding policy for the problematic sharding queue. It can be done either from command line or from rabbitmq admin page. It requires to connect a running node. But as all the nodes were down, we could not disable sharding policy. Luckily, rabbitmq allows disabling sharding pulgi...
Read more

SOA SUITE 12.2.1.4 INSTALLATION: GOT EXCEPTION WHEN AUTO CONFIGURING THE SCHEMA COMPONENT(S) WITH DATA OBTAINED FROM SHADOW TABLE

  We planned to do out of place upgrade from soa suite 12.2.1.3 to 12.2.1.4. As part of this, we planned to automate end to end provisioning. While executing domain configuration using ansible and python scripts, we got following error in domain creation step. Got exception when auto configuring the schema component(s) with data obtained from shadow table. Failed to build JDBC Connection object: com.oracle.cie.domain.script.jython.CommandExceptionHandler. exception. Quick internet search gave few solutions like deleting domain-registry.xml file, verifying dehydration store password supplied to script etc. But none of them helped. After trying several options, I thought I might have done some stupid error prior to domain creation step. To track down the issue, though of checking what getDatabaseDefaults actually doing. I tried to grep for the getDatabaseDefaults function call inside oracle home. But couldn’t find the source code for the python function. As a final resort, thought of...
Read more