Improve Loop-Server logging for troubleshooting

VERIFIED FIXED

Status

VERIFIED FIXED
4 years ago
4 years ago

People

(Reporter: tarek, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa+])

(Reporter)

Description

4 years ago
Today we had to debug a server stack alive to understand why it was not working.

We had three configuration problems related to:

- CORS
- fakeTokbox
- https

We need to get better at troubleshooting this kind of issue by using :

- the information displayed at / and /__heartbeat__
- the errors found in the logs
I was just about to open a bug like this - thanks for saving me the effort!...
Whiteboard: [qa+]
OS: Mac OS X → All
Hardware: x86 → All
Summary: Improve logging for troubleshooting → Improve Loop-Server logging for troubleshooting
I guess this is related to bug 984325, we need to check log errors are effectively captured.
Tarek, what do you have in mind specifically about having better loggin here? (it seems that the errors I found in the sentry deployment for stage is enough?).
Flags: needinfo?(tarek)
(Reporter)

Comment 4

4 years ago
Are those logs enough to detect the issues we had ? Would you have been able to troubleshoot them with no ssh access ?
Flags: needinfo?(tarek)
That was useful for the problems we had so far.

However, I need to double check if what I found in the stdout of the process (collected by circus) was also sent to sentry, and if not, fix it.
Logs there seem to be enough. Closing.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
I agree.
/var/log/circus.log
/var/log/loop_err.log
/var/log/loop_out.log
/var/log/hekad/loop.stdout.log
/var/log/hekad/loop.stderr.log
/var/log/nginx/access.log
/var/log/nginx/error.log
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.