Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

LinuxDiagnostic-3.0.111: Problem(s) detected in generated mdsd configuration.

See original GitHub issue

I have enabled the diagnostic settings on two new VMs, a Ubuntu 16.04 and Centos 7.3 Marketplace image and I am getting the following error in the log, any suggestion ?

2018/03/07 00:25:46 ERROR:CalledProcessError.  Command string was SSL_CERT_FILE=/etc/pki/tls/cert.pem SSL_CERT_DIR=/etc/pki/tls/certs /usr/local/lad/bin/mdsd -v -c /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlC
fg.xml
2018/03/07 00:25:47 [Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111] Problem(s) detected in generated mdsd configuration. Can't enable, although this install/enable operation is reported as successful so the VM can complete successful startup. Linux Diagnostic Extension will exit. Config validation message: 2018-03-07T00:25:46.8564990Z: Not all GCS env vars are defined. Missing 5: MONITORING_GCS_ENVIRONMENT MONITORING_GCS_ACCOUNT MONITORING_GCS_REGION MONITORING_GC
S_CERT_CERTFILE MONITORING_GCS_CERT_KEYFILE. GCS won't be used.
2018/03/07 00:25:47 [Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111] Daemon,success,0,Problem(s) detected in generated mdsd configuration. Can't enable, although this install/enable operation is reported as successful so the VM can
complete successful startup. Linux Diagnostic Extension will exit. Config validation message: 2018-03-07T00:25:46.8564990Z: Not all GCS env vars are defined. Missing 5: MONITORING_GCS_ENVIRONMENT MONITORING_GCS_ACCOUNT MONITORING_GCS_REG
ION MONITORING_GCS_CERT_CERTFILE MONITORING_GCS_CERT_KEYFILE. GCS won't be used.
..
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: <DerivedEvent> does not define subelement <LADQuery>
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: No default credentials were defined
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: <DerivedEvent> does not define subelement <LADQuery>
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: No default credentials were defined
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: <DerivedEvent> does not define subelement <LADQuery>
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: No default credentials were defined
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: <DerivedEvent> does not define subelement <LADQuery>
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: No default credentials were defined
2018/03/07 00:25:47 /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.111/xmlCfg.xml(97) Error: <DerivedEvent> does not define subelement <LADQuery>

Issue Analytics

State:
Created 6 years ago
Comments:14 (4 by maintainers)

Top GitHub Comments

3reactions

benc-ukcommented, Apr 3, 2018

Isn’t this just supposed to work? Enabling diagnostics from the portal or CLI is a standard admin task and shouldn’t require such arcane knowledge of the inner workings of this extension and the WALinuxAgent

0reactions

abhijeetgaihacommented, May 9, 2018

Duplicate of #577