jujud panic output does not appear in log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Using Juju 2.2.6, when I kill the machine 0 machine agent with -QUIT, I do not see any panic output in /var/log/
If confirmed, this is a significant issue because sometimes the panic stack trace can be the only thing that allows us to diagnose an issue.
The script that starts jujud (/var/lib/
#!/usr/bin/env bash
# Set up logging.
touch '/var/log/
chown syslog:syslog '/var/log/
chmod 0600 '/var/log/
exec >> '/var/log/
exec 2>&1
# Run the script.
'/var/
Since jujud no longer prints its logging output to stdout, but instead opens and writes the machine-0.log file itself, I wonder if there is some raciness between that output and the stderr output which is going to the same file but using a different file descriptor.
Changed in juju: | |
status: | Incomplete → New |
I did a quick test, bootstrapping juju 2.2.6 on lxd, and I can't reproduce this. com/juju/ juju/worker/ catacomb. (*Catacomb) .add.func2( 0xc420a9f4a0, 0x7ff97c6216d0, 0xc4208b1320, 0xc4208b13e0)
/tmp/tmpwONtpt /juju-core_ 2.2.6/src/ github. com/juju/ juju/worker/ catacomb/ catacomb. go:181 +0x152 com/juju/ juju/worker/ catacomb. (*Catacomb) .add
/tmp/tmpwONtpt /juju-core_ 2.2.6/src/ github. com/juju/ juju/worker/ catacomb/ catacomb. go:187 +0xe1
I see the traceback in the machine-0.log file as expected
...
goroutine 3501 [select, 1 minutes]:
github.
created by github.
Is it possible you passed -QUIT to the wrong process?
I killed the 'jujud' process, rather than the "exec-start.sh" process.