I'm trying to upgrade the sensu-puppet module and im getting an error when i run puppet now: the error is:
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Invalid parameter prefetch on Sensurabbitmqconfig[<(hostname
is here, removed for this post on ask puppet)>] at
/etc/puppet/environments/staging/modules/sensu/manifests/rabbitmq/config.pp:123
Warning: Not using cache on failed catalog Error: Could not retrieve
catalog; skipping run
I have no idea what's going wrong or how to fix it. I looked in the pathway at the rabbitmq config and found this:
prefetch => $sensu::rabbitmq_prefetch
But I'm not sure what the issue is. Anyone know what might be causing this?
Where did you get the puppet module and what way?
Did you use puppet module install or a git pull?
Make sure sure that the parameter you want to use is in
modules/sensu/lib/puppet/provider/sensu_rabbitmq_config/json.rb
and also
modules/sensu/lib/puppet/type/sensu_rabbitmq_config.rb
Related
I'm new to using cloudflare and wrangler. I've a project that I've been working on, and I'm now trying to deploy it using wrangler publish, but I keep running into issues. My product is coded in node.js, and I'm using version 2 of wrangler. When I execute wrangler publish I get:
Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2Basic JavaScript project found. Skipping unnecessary build!
Error: Something went wrong with the request to Cloudflare...
Uncaught SyntaxError: Cannot use import statement outside a module
at worker.js:2
I've searched for a solution, and one of them that I found said to change module in wrangler.toml from type="javascript"to type="webpack" however that gives me a bunch of errors:
./node_modules/destroy/index.js
Module not found: Error: Can't resolve 'fs' ... Parsed request is a module...resolve as module
/Users/Desktop/APIs/cpiCalculator2/node_modules/destroy/node_modules doesn't exist or is not a directory
...
Error: webpack returned an error. You may be able to resolve this issue by running npm install.
I've tried reinstalling npm as it suggests and then wrangler publish again, but that just gives me the same error message.
I'm really not sure what the issue is, and I would really appreciate any help or advice on how to resolve this issue. Thank you!
Also, just a note, I'm not sure if this is affecting it, but I do have two other js documents in the main area of my project (where my index.js file is).
I done all steps to install orocommerce on azure CentOS and nginx.
So now i got the following error after
$ ./bin/console oro:install --env=prod --timeout=900
"In ParameterBag.php line 102:
You have requested a non-existent parameter "web_backend_prefix".
Have anybody an idea?
How exactly did you get the source code (if GitHub - what repository, tag/branch, if download - what website and version)? Based on the error text it seems like it might be OroPlatform or OroCRM application, not OroCommerce.
I am getting this error When i have Started the apache server
Starting httpd: /usr/sbin/httpd: symbol lookup error: /usr/sbin/httpd:
undefined symbol: apr_bucket_alloc_aligned_floor
Please help me on this.
i got this error too this morning, it was a module conflict.
Removed the conflicting module, then ran easyapache 4 and reprovisioned the profile in WHM.
The conflicting module was:
Error: Multilib version problems found. This often means that the root
cause is something else and multilib version checking is just
pointing out that there is a problem. Eg.:
1. You have an upgrade for ea-apache24-mod_cloudflare which is missing some
dependency that another package requires. Yum is trying to
solve this by installing an older version of ea-apache24-mod_cloudflare of the
different architecture. If you exclude the bad architecture
yum will tell you what the root cause is (which package
requires what). You can try redoing the upgrade with
--exclude ea-apache24-mod_cloudflare.otherarch ... this should give you an error
message showing the root cause of the problem.
2. You have multiple architectures of ea-apache24-mod_cloudflare installed, but
yum can only see an upgrade for one of those arcitectures.
If you don't want/need both architectures anymore then you
can remove the one with the missing update and everything
will work.
3. You have duplicate versions of ea-apache24-mod_cloudflare installed already.
You can use "yum check" to get yum show these errors.
...you can also use --setopt=protected_multilib=false to remove
this checking, however this is almost never the correct thing to
do as something else is very likely to go wrong (often causing
much more problems).
Protected multilib versions: ea-apache24-mod_cloudflare-1.2.0-.5.47.x86_64 != ea-apache24-mod_cloudflare-1.2.0-.5.37.i686
Run yum update to see the error, or what ever command your OS has to check for updates.
Regards,
Tommy
If dealing with cPanel, check for updates via yum. In my case, updates were needed, so updated all yum packages.
I then found PHP scripts were not being parsed. Check that the PHP handler is set to whatever your handler should be. In my case, the handler was set to "None".
I hope this helps!
I need help understanding an error why I'm seeing an error.
The feature api is already enabled with the correct ApiListener object, and Api logs are being updated in /var/lib/icinga2/api/log/current .
But I'm getting this error when I restart icinga2:
Error: Error while evaluating expression: The type 'ApiUser' is unknown: in /etc/icinga2/conf.d/api-users.conf: 1:0-1:20
I'm running version r2.3.10-1 of Icinga2 on Ubuntu.
Can someone explain what the problem is?
You are probably mixing the current snapshot packages with the released stable versions. The 'ApiUser' object is part of the upcoming Icinga 2 v2.4 release and only available in git master (and therefore snapshot packages as well as docs). The stable 2.3.x tree does not have that kind of configuration object type and therefore bails out with an error.
Remove that file or its content, you don't need it for 2.3.x.
I am getting an error while trying to return a receipt message from server to acknowledge message received at server for which I am using a non official module (mod_stanza_ack) and ejabberd 15.07.
I have compiled and configured it successfully too, but it's giving the following error during ejabberd hook execution:
#ejabberd_hooks:run_fold1:371 {undef,[{mod_send_receipt,on_user_send_packet,[{xmlel,<<"message">>,[{<<"id">>,<<"6uAAO-218">>}.....
undef means the function mod_send_receipt:on_user_send_packet.
I see possible reason for this:
source file is not compiled (due to syntax error for example)
or the resulting .beam file is not in your Erlang VM code path
or the function is actually not defined in your module
You need to fix your module accordingly or put the .beam file in the right place.