"service appdcontroller start" fails

Open
#27 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
shell
Domain
devops

Research direction

Start by reproducing service appdcontroller start and service appdcontroller status on the stated CentOS 7.2.1511 environment, then inspect the appdcontroller service entry point and its startup output. Done means the controller and listed services start successfully and status no longer reports an unknown HA type or passive state.

Written by the indexing model from the issue text.

Description

Hi,
HA toolkit has been installed just for the linux service part, no HA at all.
Controller is running under root.

Controller 4.2.5.2
CentOS Linux release 7.2.1511

[root@152101lmd5 Controller]# service appdcontroller start
awk: cmd. line:1: '/^\s_EVENTS_HEAP_SETTINGS=/ { print }'
awk: cmd. line:1: ^ invalid char ''' in expression
[INFO] Path to mysql is not defined in system environment (MYSQL_BIN). Using mysql from /opt/AppDynamics/Controller/db/bin
[INFO] Mysql configuration file is not defined in system environment (AD_DB_CNF). Using mysql configuration file: /opt/AppDynamics/Controller/db/db.cnf
[INFO] Mysql datadir is /opt/AppDynamics/Controller/db/data
Starting controller database on port 3388
Waiting for Controller database to start on port 3388.......
*_*** Controller database started on port 3388 *****
skipping appserver start - HA passive
watchdog disabled

[root@152101lmd5 Controller]# service appdcontroller status
db running as root - passive
unknown HA type
watchdog not running
assassin not running
controller not running
events service not running
reporting service not running
machine-agent service not running

Dominant language
Shell
Stars
13
Forks
11
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Appdynamics/HA-toolkit

All issues in Appdynamics/HA-toolkit

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.