oozie not starting,giving below alert

[#1]

while starting oozie service getting below error:

oozie server status:Execution of 'source /usr/hdp/current/oozie-server/conf/oozie-env.sh ; oozie admin -oozie http://master1:11000/oozie -status' returned 255. Connection exception has occurred [ java.net.ConnectException Connection refused (Connection refused) ]. Trying after 1 sec. Retry count = 1 Connection exception has occurred [ java.net.ConnectException Connection refused (Connection refused) ].

oozie server web ui:Connection failed to master1:11000/oozie/?user.name=oozie (<urlopen error [Errno 111] Connection refused>)

oozie log:

Jun 03, 2019 8:34:40 PM org.apache.coyote.http11.Http11Protocol pause

INFO: Pausing Coyote HTTP/1.1 on http-11000

Jun 03, 2019 8:34:41 PM org.apache.catalina.core.StandardService stop

INFO: Stopping service Catalina

Jun 03, 2019 8:34:41 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc

SEVERE: The web application [/oozie] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

Jun 03, 2019 8:34:41 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads

SEVERE: The web application [/oozie] appears to have started a thread named [FileWatchdog] but has failed to stop it. This is very likely to create a memory leak.

[#2 · Accepted solution]

@John

It looks like it is complaining about the JDBC driver. So can you please try this:

SEVERE: The web application [/oozie] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

It can happen if the Oozie Server was not stopped properly, So please try to Kill the Oozie process properly and then restart it freshly.

Also can you please check what is the "mysql" jdbc driver version present here "/usr/hdp/current/oozie-server/oozie-server/webapps/oozie/WEB-INF/lib/"

May be you can try tp updated the jdbc driver jar inside "/usr/hdp/current/oozie-server/libext/" and fthen prepare new war file.

1. Stop oozie server

2. Run below command

# /usr/hdp/current/oozie-server/bin/oozie-setup.sh prepare-war

3. Start Oozie server.

.

Still if it fails then can you please share the full log

[#3]

@John
Are you still getting the same error? Did it resolve the issue?