while I add a class in puppet GUI, it showing me connection error. I checked the puppet dashboard production log, i guess it is throwing
Connecting to database specified by database.yml
Problem loading console auth middleware: cannot load such file -- console_auth_middleware
Problem with loading console: cannot load such file -- console_middleware
Problem with loading console auth: cannot load such file -- console_auth_app_middleware
Problem with loading event inspector: cannot load such file -- event_inspector_middleware
Problem with loading live management: cannot load such file -- live_management
error for this. How can i fix it.
Related
I am getting an error code in my dev tools.
Error handling response: Error: Failed to construct 'WebSocket': The URL 'ws/ws' is invalid.
at init (chrome-extension://fiegdmejfepffgpnejdinekhfieaogmj/reload.js:22:18)
at chrome-extension://fiegdmejfepffgpnejdinekhfieaogmj/reload.js:65:13
What does this mean and how do I fix it?
I had the same problem and like Aleksey Razbakov said, it's probably from one of your extensions. In my case I had to disabled : Live Server Web Extension. And now this error is gone.
I have setup a sails project from production to local machine ( window). We are using sails-cassandra. Now when i am running **node app.js*. I am getting following error
> error: A hook (`orm`) failed to load!
error: Error: There was an error
> attempting to load `sails-cassandra`. (Sails attempted to load this
> adapter because it is referenced by a datastore
> (`someCassandraServer`) in this app's configuration) Please ensure
> that `sails-cassandra` is a valid Sails/Waterline adapter, and that it
> is installed in this app.
Anybody have an idea what i am missing. My Cassandra database is setup on external server, i am able to ping that server.
I am having issues with node-red and can no longer run any flows, i am not sure what to do anymore.
i get the following error
Imported unrecognised type: mqtt-env-broker
Flows stopped due to missing node types. Check logs for details.
Tried to remove this module from the palette but get the following error, i am also unable to disable it
Failed to remove: node-red-contrib-mqtt-env
Error: Type in use: mqtt-env-broker
Check the log for more information
I have installed the node-red-admin and tried to remove it from command line, so i issued the following command
sudo node-red-admin remove node-red-contrib-mqtt-env/mqtt-env
i get the following error
404: Cannot DELETE /nodes/node-red-contrib-mqtt-env/mqtt-env
this is what i get when i ran the following command
node-red-admin list
Nodes Types State
node-red-contrib-mqtt-env/mqtt-env mqtt-env in error
mqtt-env out
mqtt-env-broker
node-red-dashboard/ui_audio ui_audio enabled
...
...
node-red/mqtt mqtt in error
mqtt out
mqtt-broker
The flows are stopped because they are trying to use a node type you have not got installed - or in this instance, it appears, is hitting an error when it tries to start
The runtime won't let you remove the node because it is referenced in your flow.
To fix this you need to delete any of the nodes referenced by this module from your flow. The name mqtt-env-broker suggests it is a configuration node rather than a regular flow node. Open the Configuration Nodes sidebar panel (from the drop-down menu) and look for any unknown config nodes. Double click on them and delete them. Once you've removed them, hit deploy and things should start working again.
You should then be able to delete the node module from your runtime.
i am using liferay 6.2 ga6 after installation when i am trying to create a new portlet it shows below error
BUILD FAILED
E:\liferay-basic-ga6\plugins\portlets\build.xml:5: The following error occurred while executing this line:
E:\liferay-basic-ga6\plugins\build-common-plugins.xml:5: The following error occurred while executing this line:
E:\liferay-basic-ga6\plugins\build-common.xml:60: The following error occurred while executing this line:
E:\liferay-basic-ga6\plugins\build-common-ivy.xml:130: The following error occurred while executing this line:
E:\liferay-basic-ga6\plugins\build-common-ivy.xml:81: HTTP Authorization failure
then i referred below blog
https://web.liferay.com/community/forums/-/message_boards/message/74382032
and made below changes
ivy.jar.url=https://repository.liferay.com/nexus/content/repositories/liferay-public-snapshots/com/liferay/org.apache.ivy/${ivy.version}/org.apache.ivy-${ivy.version}.jar
i m getting the below error:
Buildfile: M:\xxx\plugins\liferay-plugins-sdk-6.2\portlets\build.xml
[ivy:resolve] :: Apache Ivy 2.4.0 - 20130110142753 :: http://ant.apache.org/ivy/ ::
[ivy:resolve] :: loading settings :: file = M:\xxx\plugins\liferay-plugins-sdk-6.2\ivy-settings.xml
and finally error which is shown in image please check here
please help me resolve this issue .it would be great help.
If you're unable to access this URL,you seem to be behind a proxy server.
Try this Post and ivy proxy settings to set your proxy settings.
In essence you need to proxy details to allow ivy to connect to repository for fetching artifacts,in your ivy settings xml file
<setproxy proxyhost="${proxy.host}"
proxyport="${proxy.port}"
nonproxyhosts="xyz.svn.com"/>
I'm trying to host and distribute xbmc addon on my site. I've made a repository which points to the directory where the addon zip file is. At the same folder I have an xml which describes the addon and so the addon name and description are being recognized by xbmc.
However when trying to install the addon it shows 0% downloading progress and then the progress disappears - resulting in the following error inside xbmc.log file:
ERROR: CCurlFile::FillBuffer - Failed: HTTP response code said error(22)
according to curl errors page, this happens when -
CURLE_HTTP_RETURNED_ERROR (22)
This is returned if CURLOPT_FAILONERROR is set TRUE and the HTTP
server returns an error code that is >= 400.
by that I assume the error may be caused by a misconfigured access permissions (perhaps I need to change some htaccess configuration?).
please help
I solved this on my own eventually. Apparently, the file structure was wrong - I needed to follow the file structure as mentioned in section 4.3 here in order for it to work