Product: PowerShell Universal
Version: 4.0.10
Hi all, we added a second PSU node recently (both Windows Server) and job output is no longer working correctly in the admin console:
TypeError: Cannot read properties of undefined (reading 'log')
at v (https://webaddress/admin/static/js/36.94cfc862.chunk.js:1:16258)
at div
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:1017995
at k (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:112809)
at div
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:3035540
at T (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:112579)
at n (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:3135592)
at Suspense
at u (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:9343)
at m (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:112075)
at g (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:112253)
at U (https://webaddress/admin/static/js/24.c26844df.chunk.js:1:10683)
at d (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:388526)
at p (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:388854)
at p
at d (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:388526)
at p (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:388854)
at n (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:3135592)
at Suspense
at u (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:9343)
at main
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:923119
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:922950
at section
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:923354
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:922950
at div
at div
at t (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:2905562)
at Oe (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:164766)
at section
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:923354
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:922950
at section
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:923354
at https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:922950
at Wt (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:187467)
at d (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:388526)
at p (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:388854)
at h (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:388591)
at u (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:376639)
at n (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:3135592)
at Suspense
at u (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:9343)
at m (https://webaddress/admin/static/js/main.31a3a517.chunk.js:1:154850)
at s (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:954224)
at c (https://webaddress/admin/static/js/18.c249edd3.chunk.js:2:679331)
at ya
Output seems to be there for only the most recent jobs, and appear as JSON strings [{“…”}] before they eventually go missing and start throwing the above stacktrace.
Tried changing the logging targets around, currently we only target the database, which is Azure SQL with the PSU service account being an owner. Any ideas?