[jira] [Updated] (TC-499) Traffic Portal logging should be consistent with other TC applications
[
https://issues.apache.org/jira/browse/TC-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Neuman updated TC-499:
Issue Type: Improvement (was: Bug)
> Traffic Portal logging should be consistent with other TC applications
> --
>
> Key: TC-499
> URL: https://issues.apache.org/jira/browse/TC-499
> Project: Traffic Control
> Issue Type: Improvement
> Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: David Neuman
>
> Currently, Traffic Portal's logging is different from other TC components.
> It does not contain a log level or a timestamp. We should make the logging
> consistent with other TC components so that users can easily discern what is
> going on and when it happened.
> Example of the current logging (these messages were over several hours):
> {quote}
> Error: ENOENT: no such file or directory, open '/etc/pki/tls/private/ca.crt'
> at Error (native)
> at Object.fs.openSync (fs.js:641:18)
> at Object.fs.readFileSync (fs.js:509:33)
> at Object. (/opt/traffic_portal/server.js:148:29)
> at Module._compile (module.js:570:32)
> at Object.Module._extensions..js (module.js:579:10)
> at Module.load (module.js:487:32)
> at tryModuleLoad (module.js:446:12)
> at Function.Module._load (module.js:438:3)
> at Module.runMain (module.js:604:10)
> error: Forever detected script exited with code: 1
> error: Script restart attempt #116
> Traffic Portal Port : 80
> Traffic Portal SSL Port : 443
> error: Forever detected script was killed by signal: SIGKILL
> Traffic Portal Port : 80
> Traffic Portal SSL Port : 443
> error: Forever detected script was killed by signal: SIGKILL
> Traffic Portal Port : 80
> Traffic Portal SSL Port : 443
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (TC-499) Traffic Portal logging should be consistent with other TC applications
[
https://issues.apache.org/jira/browse/TC-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hank Beatty updated TC-499:
---
Affects Version/s: 2.1.0
> Traffic Portal logging should be consistent with other TC applications
> --
>
> Key: TC-499
> URL: https://issues.apache.org/jira/browse/TC-499
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Portal
>Affects Versions: 2.1.0
>Reporter: David Neuman
>
> Currently, Traffic Portal's logging is different from other TC components.
> It does not contain a log level or a timestamp. We should make the logging
> consistent with other TC components so that users can easily discern what is
> going on and when it happened.
> Example of the current logging (these messages were over several hours):
> {quote}
> Error: ENOENT: no such file or directory, open '/etc/pki/tls/private/ca.crt'
> at Error (native)
> at Object.fs.openSync (fs.js:641:18)
> at Object.fs.readFileSync (fs.js:509:33)
> at Object. (/opt/traffic_portal/server.js:148:29)
> at Module._compile (module.js:570:32)
> at Object.Module._extensions..js (module.js:579:10)
> at Module.load (module.js:487:32)
> at tryModuleLoad (module.js:446:12)
> at Function.Module._load (module.js:438:3)
> at Module.runMain (module.js:604:10)
> error: Forever detected script exited with code: 1
> error: Script restart attempt #116
> Traffic Portal Port : 80
> Traffic Portal SSL Port : 443
> error: Forever detected script was killed by signal: SIGKILL
> Traffic Portal Port : 80
> Traffic Portal SSL Port : 443
> error: Forever detected script was killed by signal: SIGKILL
> Traffic Portal Port : 80
> Traffic Portal SSL Port : 443
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
