search

theforeman / foreman_cockpit

:rocket: Display console and journal of Cockpit-enabled hosts in Foreman - now replaced by Remote Execution's cockpit integration
GNU General Public License v3.0
18 stars 13 forks source link

Cockpit is no show anything on foreman katello 3.1 #10

Open mgamboa opened 8 years ago

mgamboa commented 8 years ago

Enviroment Katello 3.1 Foreman 1.12.2 Cockpit tfm-rubygem-foreman_cockpit-2.0.2-1.fm1_12.el7.noarch

i just try to look into the system or any other part of cockpit option on production.log show was ok but is no show anything.

but debugging the jscript "Handler function threw an exception: TypeError: this.transport is null Stack: DSC_send@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/main.js:1391:5 NEA_addSecurityInfo@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/webconsole.js:2136:5 NetworkResponseListener.prototype._getSecurityInfo<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/webconsole/network-monitor.js:266:5 exports.makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/ThreadSafeDevToolsUtils.js:101:14 NetworkResponseListener.prototype.onStartRequest@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/webconsole/network-monitor.js:215:5 Line: 1391, column: 5"ThreadSafeDevToolsUtils.js:80 Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel() Strict-Transport-Security: The connection to the site is untrustworthy, so the specified header was ignored.[Learn More]system Blocked loading mixed active content "about:neterror?e=netTimeout&u=https%3A//oradb01.dev.loc%3A9090/cockpit/%40localhost/system/index.html&c=UTF-8&f=regular&d=The%20server%20at%20oradb01.dev.nbg6.sh.loc%20is%20taking%20too%20long%20to%20respond."[Learn More]oradb01.dev.nbg6.sh.loc Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel()Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel() Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel() Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel() Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel() Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel() Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel()

I don't know what could be the issue because from the katello server i can connect to the cockpit server with curl https://ip:9090 -k and i get response

Dizziex commented 7 years ago

I also seem to have issues getting the cockpit feature to work in Katello 3.1 (Foreman 1.12.4). I cannot install the cockpit feature with foreman-installer (option not available, the option is available on a stand-alone foreman 1.12.4 instance though). Installed it by installing the rpm from the foreman plugins 1.12 repo. Installs fine, but no option when opening a host. (manually connecting to the host opens cockpit fine). Only entry in logging specific about cockpit is this: 2016-11-11 13:02:02 [app] [I] Started GET "/assets/foreman_cockpit/load_partial-6e55161e03a2c7f54effe6d906a227b878d6a8367fc9755ba68f7dbf41715c40.js" for 192.168.151.94 at 2016-11-11 13:02:02 +0100 The same entry appears when I open a host page where cockpit isn't running (no error that the plugin cannot connect).