Fehlerprotokolle nach dem Upgrade leer

Unterstützung
1

Version 3.1.0.beta3, alle vorherigen Log-Einträge fehlen, neue Ereignisse werden nicht protokolliert.

Gleiches Problem auf zwei aktualisierten Instanzen.

2

Ich habe meinen Test-Site heute Morgen auf 3.1.0.beta3 aktualisiert und meine /logs-Historie scheint noch intakt zu sein? Ich glaube, ich habe auch einige Deprecation Warnings nach dem Upgrade.

Schaue ich an der richtigen Stelle nach?

3

Ich habe viele wiederkehrende Konsolenfehler auf der Seite /logs (keine Fehler auf der Hauptforenseite).

       GET https://forum.domain.name/logs/messages.json?filter=2_3_4_5 404
(anonymous) @ client-app.js:177
(anonymous) @ vendor.js:3856
e @ vendor.js:3856
l @ client-app.js:172
load @ client-app.js:209
reload @ client-app.js:212
setupController @ client-app.js:257
n @ vendor.js:1829
s.setup @ vendor.js:1352
s @ vendor.js:3769
n.routeEnteredOrUpdated @ vendor.js:3770
n.setupContexts @ vendor.js:3767
n.finalizeTransition @ vendor.js:3759
(anonymous) @ vendor.js:3752
y @ vendor.js:3835
g @ vendor.js:3833
t.invoke @ vendor.js:3368
t.flush @ vendor.js:3360
t.flush @ vendor.js:3374
n._end @ vendor.js:3437
_boundAutorunEnd @ vendor.js:3388
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._ensureInstance @ vendor.js:3449
n.schedule @ vendor.js:3409
e.schedule @ vendor.js:2266
waitForDOMReady @ vendor.js:2026
init @ vendor.js:2025
n @ vendor.js:1829
v @ vendor.js:1733
e.create @ vendor.js:1746
(anonymous) @ client-app.js:297
forum.domain.name/:1 
        
       Uncaught (in promise) XMLHttpRequest {readyState: 4, timeout: 0, withCredentials: false, upload: XMLHttpRequestUpload, onreadystatechange: ƒ, …}
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._end @ vendor.js:3438
_boundAutorunEnd @ vendor.js:3388
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._end @ vendor.js:3438
_boundAutorunEnd @ vendor.js:3388
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._end @ vendor.js:3438
_boundAutorunEnd @ vendor.js:3388
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._end @ vendor.js:3438
_boundAutorunEnd @ vendor.js:3388
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._end @ vendor.js:3438
_boundAutorunEnd @ vendor.js:3388
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._ensureInstance @ vendor.js:3449
n.schedule @ vendor.js:3409
(anonymous) @ vendor.js:1586
m @ vendor.js:3831
(anonymous) @ vendor.js:3856
Ember.RSVP.Promise.o.onreadystatechange @ client-app.js:177
XMLHttpRequest.send (async)
(anonymous) @ client-app.js:177
(anonymous) @ vendor.js:3856
e @ vendor.js:3856
l @ client-app.js:172
load @ client-app.js:209
reload @ client-app.js:212
setupController @ client-app.js:257
n @ vendor.js:1829
s.setup @ vendor.js:1352
s @ vendor.js:3769
n.routeEnteredOrUpdated @ vendor.js:3770
n.setupContexts @ vendor.js:3767
n.finalizeTransition @ vendor.js:3759
(anonymous) @ vendor.js:3752
y @ vendor.js:3835
g @ vendor.js:3833
t.invoke @ vendor.js:3368
t.flush @ vendor.js:3360
t.flush @ vendor.js:3374
n._end @ vendor.js:3437
_boundAutorunEnd @ vendor.js:3388
Promise.then (async)
r @ vendor.js:3344
flush @ vendor.js:2274
n._scheduleAutorun @ vendor.js:3451
n._ensureInstance @ vendor.js:3449
n.schedule @ vendor.js:3409
e.schedule @ vendor.js:2266
waitForDOMReady @ vendor.js:2026
init @ vendor.js:2025
n @ vendor.js:1829
v @ vendor.js:1733
e.create @ vendor.js:1746
(anonymous) @ client-app.js:297
client-app.js:177

Bitte helfen Sie mir, es zu beheben.

4

Können Sie bitte versuchen, Ihren Browser vollständig zu beenden und dann wieder zu öffnen? Ich glaube, es ist wahrscheinlich, dass Sie eine zwischengespeicherte Version des /logs-JavaScript haben.

5 „Gefällt mir“
5

Das war’s, danke. Das erneute Öffnen des Browsers hat nicht funktioniert, aber ein Hard Refresh schon (und das Leeren des Chrome-Caches auf Android).

5 „Gefällt mir“
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.