Its all OK now :) On Fri, Jul 24, 2015 at 9:14 AM, frex popo <frexpo...@gmail.com> wrote:
> Now I am getting this :) > sudo /sbin/service tideway stop > Stopping local ADDM application services > Waiting for other service operations to complete ... > > So going through the logs to see what's what > > On Fri, Jul 24, 2015 at 8:54 AM, frex popo <frexpo...@gmail.com> wrote: > >> indeed and since this is production its difficult to keep trying things >> not knowing what to expect. BMC never got back to me on this. Will send >> them the solution anyway and hope they will create a KB#for it in case >> someone else find themselves in the same mess :) >> >> On Thu, Jul 23, 2015 at 7:36 PM, jortega999 . <jortega9...@gmail.com> >> wrote: >> >>> ** >>> >>> Ah yes, now I remember that I did the same thing. After I rebooted the >>> appliance, all scans were stopped. When I started discovery scans, the >>> cancelled discovery finished. I guess that they cannot stop unless the scan >>> engine is running. Strange indeed. >>> On Jul 23, 2015 9:36 AM, "frex popo" <frexpo...@gmail.com> wrote: >>> >>>> ** >>>> Resolved it!! :) >>>> I had all scans STOPPED for the upgrade, now I restarted all SCANS and >>>> I sopped them again. >>>> It now says there are no current runs to show! >>>> >>>> Thanks >>>> >>>> On Thu, Jul 23, 2015 at 4:31 PM, frex popo <frexpo...@gmail.com> wrote: >>>> >>>>> Well no luck, :( >>>>> >>>>> In the Discovery tab, in the "Currently Processing Runs" the two job >>>>> still show (on hold) in red and the first column still says Cancelling... >>>>> >>>>> Anyone had this problem before >>>>> >>>>> On Thu, Jul 23, 2015 at 4:26 PM, frex popo <frexpo...@gmail.com> >>>>> wrote: >>>>> >>>>>> funy enough I just rebooted the appliance and thought I will check my >>>>>> account when I found your message :) >>>>>> Its still in the process of rebooting so hope that resolves it!! >>>>>> Many thanks anyway >>>>>> >>>>>> On Thu, Jul 23, 2015 at 3:33 PM, jortega999 . <jortega9...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> ** >>>>>>> >>>>>>> I think that you need to reboot the appliance. That happened to me >>>>>>> once an I believe that is how I resolved it. >>>>>>> On Jul 23, 2015 7:43 AM, "frex popo" <frexpo...@gmail.com> wrote: >>>>>>> >>>>>>>> ** >>>>>>>> Hi all, >>>>>>>> >>>>>>>> Need to upgrade addm however can not cancel come job (on HOLD).. >>>>>>>> the console says Cancelling... but this has been going for hours. >>>>>>>> >>>>>>>> Restarted the appliance services but can not get to cancel the runs. >>>>>>>> >>>>>>>> Any thoughts will be very much appreciated >>>>>>>> frex >>>>>>>> >>>>>>>> These queries are written to the model.log continously >>>>>>>> ________________________________________ >>>>>>>> >>>>>>>> 72293971712: 2015-07-23 13:59:47,316: model.search.servants: INFO: >>>>>>>> Completed search 127: SEARCH DiscoveryRun WHERE __inprogress IS >>>>>>>> DEFINED AND >>>>>>>> _consolidation_source IS NOT DEFINED ORDER BY starttime SHOW cancelled, >>>>>>>> done, key, label, processing, scan_level, scan_type, starttime, total, >>>>>>>> user, valid_ranges, #id, >>>>>>>> #DiscoveryRun:EndpointRange:EndpointRange:IPRange.repeat >>>>>>>> >>>>>>>> 139672293971712: 2015-07-23 13:59:47,317: model.search.servants: >>>>>>>> INFO: Search 128 (system): SEARCH DiscoveryRun WHERE __inprogress IS >>>>>>>> DEFINED AND _consolidation_source IS DEFINED ORDER BY starttime, >>>>>>>> discovery_starttime SHOW cancelled, consolidation_cancelled, >>>>>>>> consolidation_done_count, done, key, label, scan_level, scan_type, >>>>>>>> starttime, total, user, valid_ranges, _consolidation_source_name, >>>>>>>> __remote_inprogress, #id >>>>>>>> >>>>>>>> 139672293971712: 2015-07-23 13:59:47,318: model.search.servants: >>>>>>>> INFO: Completed search 128: SEARCH DiscoveryRun WHERE __inprogress IS >>>>>>>> DEFINED AND _consolidation_source IS DEFINED ORDER BY starttime, >>>>>>>> discovery_starttime SHOW cancelled, consolidation_cancelled, >>>>>>>> consolidation_done_count, done, key, label, scan_level, scan_type, >>>>>>>> starttime, total, user, valid_ranges, _consolidation_source_name, >>>>>>>> __remote_inprogress, #id >>>>>>>> >>>>>>>> 139672199563008: 2015-07-23 13:59:49,346: model.search.servants: >>>>>>>> INFO: Search 129 (system): SEARCH DiscoveryRun WHERE __inprogress IS >>>>>>>> DEFINED AND _consolidation_source IS NOT DEFINED ORDER BY starttime >>>>>>>> SHOW >>>>>>>> cancelled, done, key, label, processing, scan_level, scan_type, >>>>>>>> starttime, >>>>>>>> total, user, valid_ranges, #id, >>>>>>>> #DiscoveryRun:EndpointRange:EndpointRange:IPRange.repeat >>>>>>>> >>>>>>>> 139672199563008: 2015-07-23 13:59:49,347: model.search.servants: >>>>>>>> INFO: Completed search 129: SEARCH DiscoveryRun WHERE __inprogress IS >>>>>>>> DEFINED AND _consolidation_source IS NOT DEFINED ORDER BY starttime >>>>>>>> SHOW >>>>>>>> cancelled, done, key, label, processing, scan_level, scan_type, >>>>>>>> starttime, >>>>>>>> total, user, valid_ranges, #id, >>>>>>>> #DiscoveryRun:EndpointRange:EndpointRange:IPRange.repeat >>>>>>>> >>>>>>>> 139672293971712: 2015-07-23 13:59:49,349: model.search.servants: >>>>>>>> INFO: Search 130 (system): SEARCH DiscoveryRun WHERE __inprogress IS >>>>>>>> DEFINED AND _consolidation_source IS DEFINED ORDER BY starttime, >>>>>>>> discovery_starttime SHOW cancelled, consolidation_cancelled, >>>>>>>> consolidation_done_count, done, key, label, scan_level, scan_type, >>>>>>>> starttime, total, user, valid_ranges, _consolidation_source_name, >>>>>>>> __remote_inprogress, #id >>>>>>>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>>>>>> >>>>>>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>>>>> >>>>>> >>>>>> >>>>> >>>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> >>> _ARSlist: "Where the Answers Are" and have been for 20 years_ >>> >> >> > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
