After deploying new plugin, 500 when logginh in to WMS Manager

[Andrew_O_Hara]

We run the Wowza Streaming Engine and Manager with our own custom engine plugin. We hadn’t deployed to this particular instance in a long time, and ran into issues during deployment, relating to the media cache attempting to use a missing ephemeral volume. We’ve fixed the engine issues, but now we get a 500 when we try to log in to the manager.

If we remove our plugin jar, then restart the engine and manager, we can log in to the manager. I’ve pulled these logs from the manager which contain the startup output followed by the exception from an attempted login to the manager. None of it is very helpful. Does anyone have any ideas on how we can diagnose this login issue?

#Version: 1.0
#Start-Date: 2020-03-17 18:24:45 UTC
#Software: Wowza Streaming Engine Manager 4.7.7.01 build20190222144406
#Date: 2020-03-17
#Fields: date   time    tz      x-server        x-user  x-severity      x-category      x-comment
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      OS Name: Linux: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      OS Version: 4.4.23-31.54.amzn1.x86_64: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      OS Architecture: amd64: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Name: Java HotSpot(TM) 64-Bit Server VM: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Vendor: Oracle Corporation: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Version: 1.8.0_25: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java VM Version: 25.25-b02: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Spec Version: 1.8: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Home: /usr/local/WowzaStreamingEngine-4.2.0/jre1.8.0_25: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Max Heap Size: 7152MB: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Architecture: 64: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Locale[user.language]: en: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Locale[user.country]: US: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Locale[file.encoding]: UTF-8: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Timezone[user.timezone]: Universal: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Args[0]: -Dcom.wowza.wms.ConfigURL="": 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Args[1]: -Dcom.wowza.wms.ConfigHome=/usr/local/WowzaStreamingEngine/manager: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Args[2]: -Djava.io.tmpdir=/usr/local/WowzaStreamingEngine/manager/temp: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Args[3]: -Dlog4j.configuration=file:///usr/local/WowzaStreamingEngine/manager/conf/winstone-log4j.properties: 
2020-03-17      18:24:45        UTC                     INFO    com.wowza.wms.logging.Log4jStartupListener      Java Args[4]: -Djava.net.preferIPv4Stack=true: 
2020-03-17      18:24:46        UTC                     INFO    org.hibernate.validator.util.Version    Hibernate Validator null
2020-03-17      18:24:47        UTC                     INFO    com.wowza.wms.server.ManagerConfiguration       Loading configuration from /usr/local/WowzaStreamingEngine/manager/conf/Manager.xml: 
2020-03-17      18:24:47        UTC                     INFO    com.wowza.wms.server.ManagerConfiguration       Loading configuration from /usr/local/WowzaStreamingEngine/manager/conf/Manager.xml: 
2020-03-17      18:24:47        UTC                     INFO    com.wowza.wms.webapp.RequestLoggingFilter       RequestLoggingFilter disabled, no HTTP requests will be logged: 
2020-03-17      18:25:07        UTC                     ERROR   rest    WowzaAuthenticationProvider:Authentication:  : Internal Server Error (500) - An exception occured writing the response entity|at org.restlet.resource.ClientResource.doError(ClientResource.java:599)|at org.restlet.resource.ClientResource.handleInbound(ClientResource.java:1165)|at org.restlet.resource.ClientResource.handle(ClientResource.java:1060)|at org.restlet.resource.ClientResource.handle(ClientResource.java:1035)|at org.restlet.resource.ClientResource.handle(ClientResource.java:937)|

[Rose_Power-Wowza_Com]

Due to the fact you are using a custom module and we are not sure how this has been integrated, we will need a support ticket. Tech support does not debug in forums as they require full zipped files and logs. You can submit one here:

https://www.wowza.com/support/open-ticket

We will need to run some tests to determine what has changed since you last ran it successfully. Thank you.