05-23-2018 07:28 AM - edited 03-01-2019 06:36 PM
Hello, Everyone.
I'm having problems with my ACS 5.5
After boot, the ACS does not start the processes 'management' and because of that, other process don't start as well.
acs2/admin# show application status acs
ACS role: SECONDARY
Process 'database' running
Process 'management' Execution failed
Process 'runtime' initializing
Process 'adclient' running
Process 'ntpd' running
Process 'view-database' Execution failed
Process 'view-jobmanager' initializing
Process 'view-alertmanager' initializing
Process 'view-collector' initializing
Process 'view-logprocessor' initializing
The web interface is not working and when I login in CLI interface, the following message apears:
Error: Could not open main par file for writing
*** Error in creating main par file ***
My ACS is currently in the version 5.5 as below:
Cisco Application Deployment Engine OS Release: 2.1
ADE-OS Build Version: 2.1.1.129
ADE-OS System Architecture: i386
Copyright (c) 2005-2013 by Cisco Systems, Inc.
All rights reserved.
Hostname: acs2
Version information of installed applications
---------------------------------------------
Cisco ACS VERSION INFORMATION
-----------------------------
Version : 5.5.0.46.10
Internal Build ID : B.723
Patches :
5-5-0-46-10
Any ideas ?
Thanks in advance.
Bruno Fraga
05-24-2018 04:58 AM
It seems to me a hardware problem... I have two disks on this ACS appliance and maybe one of the disks is corrupted although my show commands don't indicated problems of this kind...
acs2/admin# sh disks
disk repository: 1% used (92136 of 65539868)
Internal filesystems:
/ : 4% used ( 286716 of 8063408)
/storedconfig : 2% used ( 17784 of 1004052)
/var : 5% used ( 408648 of 10095152)
/altroot : 4% used ( 34092 of 1032088)
/usr : 13% used ( 958216 of 8063408)
/opt : 21% used ( 70157916 of 362854908)
/recovery : 4% used ( 34092 of 1032088)
/home : 4% used ( 34352 of 1032088)
/storeddata : 28% used ( 1303096 of 5063712)
/tmp : 1% used ( 51460 of 8063408)
/boot : 52% used ( 49661 of 101086)
/dev/shm : 0% used ( 0 of 2009460)
all internal filesystems have sufficient free space
acs2/admin# sh inventory
NAME: "CSACS-1121-K9 chassis", DESCR: "CSACS-1121-K9 chassis"
PID: CSACS-1121-K9 , VID: V01 , SN: KQ84KHC
Total RAM Memory: 4018920 kB
CPU Core Count: 4
CPU 0: Model Info: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
CPU 1: Model Info: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
CPU 2: Model Info: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
CPU 3: Model Info: Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
Hard Disk Count(*): 2
Disk 0: Device Name: /dev/sda
Disk 0: Capacity: 250.00 GB
Disk 0: Geometry: 255 heads 63 sectors/track 30401 cylinders
Disk 1: Device Name: /dev/sdb
Disk 1: Capacity: 250.00 GB
Disk 1: Geometry: 255 heads 63 sectors/track 30401 cylinders
NIC Count: 4
NIC 0: Device Name: eth0
NIC 0: HW Address:
NIC 0: Driver Descr: Broadcom Tigon3 ethernet driver
NIC 1: Device Name: eth1
NIC 1: HW Address:
NIC 1: Driver Descr: Broadcom Tigon3 ethernet driver
NIC 2: Device Name: eth2
NIC 2: HW Address:
NIC 2: Driver Descr: Intel(R) PRO/1000 Network Driver
NIC 3: Device Name: eth3
NIC 3: HW Address:
NIC 3: Driver Descr: Intel(R) PRO/1000 Network Driver
(*) Hard Disk Count may be Logical.
At the same time, the monitor screen, where the appliance is, indicates to me the following:
EXT3-fs error (device dm-4): ext3_free_blocks_sb: bit already cleared for block 30899244
ext3_abort called.
EXT3-fs error (device dm-4): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-f error (device dm-4) in ext3_free_blocks_sb: Journal has aborted
EXT3-f error (device dm-4) in ext3_free_blocks_sb: Journal has aborted
EXT3-f error (device dm-4) in ext3_free_blocks_sb: Journal has aborted
EXT3-f error (device dm-4) in ext3_reserve_inode_write: Journal has aborted
EXT3-f error (device dm-4) in ext3_truncate: Journal has aborted
EXT3-f error (device dm-4) in ext3_reserve_inode_write: Journal has aborted
EXT3-f error (device dm-4) in ext3_orphan_del: Journal has aborted
EXT3-f error (device dm-4) in ext3_reserve_inode_write: Journal has aborted
Any solution different from reinstalling all the system changing the HD SATA Disks ??
Is it possible to replace the disks, one at the time, without reinstalling the system ??
I mean... is there any kind of commands to force ACS migrate all data to just one disk (setting the other one corrupted free) ??
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide