cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3353
Views
5
Helpful
7
Replies

Job Shows Still Running

acdixon9201
Level 1
Level 1

Hello. In our vsom environment we have a job that appears to still be running, but shows an end time (back in 10/2014). I cannot seem to find a way to clear the indicator. We recently updated to 7.6 and the job stayed through the update. Does anyone have an idea on how to clear this?


Thanks,

Chris D.

 

1 Accepted Solution

Accepted Solutions

Hi,

My name is Jayesh from the Physical Security team. This is happened when the jobs is freezes in the VSOM and its not completing from the server. 

To clear the stuck job, log in to the VSOM server's CLI as 'localadmin' and run these two commands: 

** Resolution:
 

$  sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-file=/usr/BWhttpd/vsom_be/db/db.cnf VSOM -e "update subjobstatus set STATUS = 'COMPLETED', ENDTIME=now() where status = 'INPROGRESS';"

$  sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-file=/usr/BWhttpd/vsom_be/db/db.cnf VSOM -e "update jobstatus set RUNNINGSUBJOBS = 0,EXPECTEDSUBJOBS = 1 where runningsubjobs > 0;"

Hope this help and clear your old running jobs.

 

Regards,

Jayesh

View solution in original post

7 Replies 7

Scott Olsen
Level 6
Level 6

Interesting.  Sounds like a database inconsistency bug to me.  My recommendation is to open a Cisco TAC case to have it evaluated.  I'll offer a prediction though;

TAC will probably want to perform an interactive WebEX session.  They'll likely then perform some direct manipulation of the mysql DB tables to remove this anomalous record and then consider the case resolved.  I suppose whether you'd consider this an appropriate 'fix' is subjective. (I'm of the opinion that anything which requires in a manual corrective update/change to a backend database record is absolutely a bug)

I'd also recommend you ask for a root cause analysis of how/why something like this occurred, as well as a bugID covering the behaviour.  

All the best.  Cheers!

 

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com

Hi,

My name is Jayesh from the Physical Security team. This is happened when the jobs is freezes in the VSOM and its not completing from the server. 

To clear the stuck job, log in to the VSOM server's CLI as 'localadmin' and run these two commands: 

** Resolution:
 

$  sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-file=/usr/BWhttpd/vsom_be/db/db.cnf VSOM -e "update subjobstatus set STATUS = 'COMPLETED', ENDTIME=now() where status = 'INPROGRESS';"

$  sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-file=/usr/BWhttpd/vsom_be/db/db.cnf VSOM -e "update jobstatus set RUNNINGSUBJOBS = 0,EXPECTEDSUBJOBS = 1 where runningsubjobs > 0;"

Hope this help and clear your old running jobs.

 

Regards,

Jayesh

Hello Chris,

 

we have the same issue and about to come crazy. 7.6 is crazy buggy version.

Hi Anil, 

    I used the commands that Jayesh posted and it cleared the job. They were in the system a while before we updated to 7.6, so I'm not sure if it is worth trying to figure out why. 

Our jobs cleared by it self after 3-4 days later but our customer very stressed these kind of bugs. We have another case now, when we tried to register the cameras in admin state to the vsom they are not joining and than we try to change the passworda after that we cant. It's turned to a cycle the cameras are junk now.

Hi Anil,

Nice to see you again. As this is not actually a bug for this version, it just that the jobs is completed in the VSOM and stuck while processing it. Most of the time this jobs will run whenever the server reboots to update the server if any changes reports in them, in the same time you perform some other operation in VSOM which cause sometimes to stuck the running jobs in VSOM and which is not getting clear by itself. 

So, keep this command handy to clear any such instances in future.

There is no issues in using this command, it will affect any other operations in VSOM.

And if you face any issues, we (TAC) is always there to help you. :)

While I still absolutely consider this a bug, I'd like to offer the following additional step to ensure no jobs persist (even those marked 'COMPLETE') with a *zero* ENDTIME value, as apparently this is used in application logic on some levels elsewhere.

$  sudo /usr/BWhttpd/vsom_be/db/mysql/bin/mysql --defaults-file=/usr/BWhttpd/vsom_be/db/db.cnf VSOM -e "update jobstatus set endtime = unix_timestamp(now())*1000 where endtime=0;"

Otherwise, it appears the server may still indicate to other components that there are jobs in progress...

Scott Olsen Solutions Specialist Bulletproof Solutions Inc. Web: www.bulletproofsi.com
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: