I have 4 WSE servers (at 4.9.2.6) and each one after the update happens, the WSE Engine Manager service won’t stay “running” under Windows Services. So the management WSE site, you cannot log in at all. When I try to start the service and it starts, but will not stay on. Nothing in the logs at all. Any ideas?
Anyone else having this type of problem?
Here is what i get now in the manager logs.
| 2025-04-16 | 08:31:34 | EDT | server | - | WARN | server | Cache miss for REQUEST dispatch to ‘/enginemanager/Home.htm’ (previous null). Performing MatchableHandlerMapping lookup. This is logged once only at WARN level, and every time at TRACE. |
|---|---|---|---|---|---|---|---|
| 2025-04-16 | 08:31:34 | EDT | server | - | INFO | server | WowzaHttpSessionListener.sessionCreated: F5282A5975EC2F7388564E2573B8E90B |
| 2025-04-16 | 08:31:34 | EDT | server | - | INFO | server | WowzaSecurityTokenGlobalAttrInterceptor.preHandle: CSRF insert for session [F5282A5975EC2F7388564E2573B8E90B]: 4C836E84207A80F3EDF970F438313C896D7B9F2976ACD6B3 |
| 2025-04-16 | 08:31:34 | EDT | http://localhost:8087 | anonymousUser | INFO | server | SesssionTimeoutFilter.doFilter: Session new [F5282A5975EC2F7388564E2573B8E90B] |
| 2025-04-16 | 08:31:40 | EDT | server | - | INFO | server | REST API: ConfigBase: init |
| 2025-04-16 | 08:31:40 | EDT | server | - | INFO | server | REST API: Authentication: Successful login for:admin |
| 2025-04-16 | 08:31:42 | EDT | http://localhost:8087 | admin | WARN | server | Exception in processing: org.restlet.resource.ResourceException: Unauthorized (401) - The request requires user authentication |
Hello @Andy_Gillette
This is being worked on within support ticket: 22675239334
The 401 warn might be a red herring as the service does not stay on. The update logs located in [install-dir]/updates/4.9.3 folder might have further details on what the issue could be with the manager service.
Looking forward to work with you within the ticket.
-Jason