debug-log on windows clouds not tailing

Bug #1654266 reported by Matthew Williams
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Invalid
Medium
Unassigned

Bug Description

Running juju debug-log from a linux client to a windows server on azure doesn't appear to always tail the log properly.

For example I run juju debug-log and wait. Last output is

unit-mssql-express-2: 12:25:11 DEBUG juju.worker.logger logger setup

Then I Ctrl+C and run juju debug-log again and now I see updated log messages:
unit-mssql-express-2: 13:00:54 ERROR unit.mssql-express/2.juju-log Error while running C:\Juju\lib\juju\agents\unit-mssql-express-2\charm\hooks\install.ps1
unit-mssql-express-2: 13:00:54 ERROR unit.mssql-express/2.juju-log MSSQL Express 2014 failed to install
unit-mssql-express-2: 13:00:54 ERROR unit.mssql-express/2.juju-log At C:\Juju\lib\juju\agents\unit-mssql-express-2\charm\lib\Modules\MSSQLExpressHooks\MSSQLExpressHooks.psm1:157 char:9

Changed in juju:
status: New → Triaged
importance: Undecided → Medium
tags: added: debug-log windows
Revision history for this message
Jordan Barrett (barrettj12) wrote :

Juju no longer supports Windows machines, so marking as invalid.

Changed in juju:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.