Start/Restart Of Weblogic Services fails via JCS UI (Nodemanager does not start automatically on JCS start/restart)

(Doc ID 2350152.1)

Last updated on JANUARY 24, 2018

Applies to:

Java Cloud Service - Version 14.1 to 14.1
Information in this document applies to any platform.


Start up operation via UI succeeds. 
JCS VM comes up. But still weblogic services does not come up(Process does not show when checked in putty).

Node Manager don't starts on JCS start/restart from UI.

In Chef.log

See the following error:
[2018-01-10T08:38:01+00:00] DEBUG: Re-raising exception: Mixlib::ShellOut::ShellCommandFailed - bash[start_nm_on_vm_reboot] (wlss::initial line 29) had an error: Mixlib::ShellOut::ShellCommandFailed: Expected process to exit with [0], but received '1'
---- Begin output of "bash" "/tmp/chef-script20180110-3273-1m8wvaq" ----
STDERR: sudo: sorry, you must have a tty to run sudo
---- End output of "bash" "/tmp/chef-script20180110-3273-1m8wvaq" ----

The issue can be reproduced with the following steps:
1. Try starting services from backend, it starts.
2. Restart from JCS UI succeeds in activity but no processes started at backend.




Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms