What is the reason of syslog-ng error: "destination plugin http not found"? - syslog-ng

Here is part of my syslog-ng.conf file (with some exclusions):
destination d_elastic_docker {
http(url("http://192.168.122.79:9200/_bulk")
method("POST")
);
};
I've got the following message from syslog-ng -v:
Error parsing destination, destination plugin http not found in /etc/syslog-ng/conf.d/docker-journal-elastic.conf at line 31, column 5:
included from /etc/syslog-ng/syslog-ng.conf line 162, column 1
http(url("http://192.168.122.79:9200/_bulk")
^^^^
Where is my problem?

The http() plugin is missing. Make sure you installed the appropriate package (for example, on Debian/Ubuntu: syslog-ng-mod-http), or use the --enable-http configure option if you compiled syslog-ng from source.

Related

Unable to find package 'Swashbuckle.AspNetCore.SwaggerUI.6.2.3'

I'm using swagger, but I have this problem according to the documentation. The nuget package has not been downloaded successfully. What should I do?
This is the error message:
Severity Code Description Project File Line Suppression State Error
The feed'nuget.org [https://api.nuget.org/v3/index.json]' lists
package'Swashbuckle.AspNetCore.SwaggerUI.6.2.3' but multiple attempts
to download the nupkg have failed. The feed is either invalid or
required packages were removed while the current operation was in
progress. Verify the package exists on the feed and try again. Unable
to find package'Swashbuckle.AspNetCore.SwaggerUI.6.2.3'.
Update:
I try to use the command:Install-Package Swashbuckle.AspNetCore -Version 6.2.3
Error:
Maybe a problem on your internet connection? Package seems exist (https://www.nuget.org/packages/Swashbuckle.AspNetCore.SwaggerUI/6.2.3).

Flow generates many errors for new project

Flow seems to generate a lot of errors on a new project. What am I doing wrong ?
What I did:
Created a new React Native project using react-native init FlowProject
Followed the set-up for Flow with yarn and Babel
yarn add --dev babel-cli babel-preset-flow
yarn add --dev flow-bin
Ran yarn run flow (.flowconfig was generated by the init)
Here is the error I get:
.flowconfig:53 Unsupported option specified! (unsafe.enable_getters_and_setters)
error Command failed with exit code 8.
Now if I remove the specified line (and version number), I get a bunch of these two errors:
Error: node_modules/react-native/Libraries/Inspector/Inspector.js:104
104: clearTimeout(_hideWait);
^^^^^^^^^ null. This type is incompatible with the expected param type of
733: declare function clearTimeout(timeoutId?: TimeoutID): void;
^^^^^^^^^ TimeoutID. See lib: /private/tmp/flow/flowlib_171966cc/core.js:733
Error: node_modules/react-native/Libraries/Lists/VirtualizedList.js:1094
1094: this.props.onEndReachedThreshold * visibleLength / 2;
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ undefined. The operand of an arithmetic operation must be a number.
Found 19 errors
error Command failed with exit code 2.
If I delete the generated .flowconfig file (see at the end), recreate it with yarn run flow init, and run yarn run flow again, I get the following errors (I'm just showing those 5, most of them were similar to each other):
Error: node_modules/react-native/Libraries/Animated/src/AnimatedEvent.js:101
101: if (__DEV__) {
^^^^^^^ __DEV__. Could not resolve name
Error: node_modules/react-native/Libraries/Inspector/Inspector.js:104
104: clearTimeout(_hideWait);
^^^^^^^^^ null. This type is incompatible with the expected param type of
733: declare function clearTimeout(timeoutId?: TimeoutID): void;
^^^^^^^^^ TimeoutID. See lib: /private/tmp/flow/flowlib_15451c3f/core.js:733
Error: node_modules/react-native/Libraries/Interaction/InteractionManager.js:107
107: return promise.done(...args);
^^^^^^^^^^^^^^^^^^^^^ call of method `done`. Function cannot be called on
107: return promise.done(...args);
^^^^^^^^^^^^^^^^^^^^^ property `done` of unknown type
Error: node_modules/react-native/Libraries/Interaction/TaskQueue.js:165
165: .done();
^^^^ property `done`. Property not found in
v---------
152: task.gen()
153: .then(() => {
154: DEBUG && infoLog(
...:
164: })
-^ Promise
Error: node_modules/react-native/Libraries/Lists/VirtualizedList.js:1016
1016: distanceFromEnd < onEndReachedThreshold * visibleLength &&
^^^^^^^^^^^^^^^^^^^^^ undefined. The operand of an arithmetic operation must be a number.
... 16 more errors (only 50 out of 66 errors displayed)
To see all errors, re-run Flow with --show-all-errors
error Command failed with exit code 2.
Now I know that I can tell flow to ignore certain files, but first, it seems weird to me that flow gives me these errors for code that I have not produced. I've also seen on a github issue that we shouldn't tell flow to ignore the node_modules. So is the solution to ignore every single file that this first flow analysis gives us ?
Here's a list of the files concerned:
Error node_modules/react-native/Libraries/Inspector/Inspector.js:
Error node_modules/react-native/Libraries/Interaction/InteractionManager.js
Error node_modules/react-native/Libraries/Lists/FlatList.js
Error node_modules/react-native/Libraries/Lists/ViewabilityHelper.js
Error node_modules/react-native/Libraries/Lists/VirtualizedList.js
Error node_modules/react-native/Libraries/Lists/VirtualizedSectionList.js
Error node_modules/react-native/Libraries/StyleSheet/flattenStyle.js
Generated .flowconfig file
[ignore]
; We fork some components by platform
.*/*[.]android.js
; Ignore "BUCK" generated dirs
<PROJECT_ROOT>/\.buckd/
; Ignore unexpected extra "#providesModule"
.*/node_modules/.*/node_modules/fbjs/.*
; Ignore duplicate module providers
; For RN Apps installed via npm, "Libraries" folder is inside
; "node_modules/react-native" but in the source repo it is in the root
.*/Libraries/react-native/React.js
; Ignore polyfills
.*/Libraries/polyfills/.*
; Ignore metro
.*/node_modules/metro/.*
[include]
[libs]
node_modules/react-native/Libraries/react-native/react-native-interface.js
node_modules/react-native/flow/
node_modules/react-native/flow-github/
[options]
emoji=true
module.system=haste
munge_underscores=true
module.name_mapper='^[./a-zA-Z0-9$_-]+\.\(bmp\|gif\|jpg\|jpeg\|png\|psd\|svg\|webp\|m4v\|mov\|mp4\|mpeg\|mpg\|webm\|aac\|aiff\|caf\|m4a\|mp3\|wav\|html\|pdf\)$' -> 'RelativeImageStub'
module.file_ext=.js
module.file_ext=.jsx
module.file_ext=.json
module.file_ext=.native.js
suppress_type=$FlowIssue
suppress_type=$FlowFixMe
suppress_type=$FlowFixMeProps
suppress_type=$FlowFixMeState
suppress_comment=\\(.\\|\n\\)*\\$FlowFixMe\\($\\|[^(]\\|(\\(<VERSION>\\)? *\\(site=[a-z,_]*react_native[a-z,_]*\\)?)\\)
suppress_comment=\\(.\\|\n\\)*\\$FlowIssue\\((\\(<VERSION>\\)? *\\(site=[a-z,_]*react_native[a-z,_]*\\)?)\\)?:? #[0-9]+
suppress_comment=\\(.\\|\n\\)*\\$FlowFixedInNextDeploy
suppress_comment=\\(.\\|\n\\)*\\$FlowExpectedError
unsafe.enable_getters_and_setters=true
[version]
^0.61.0
You cannot delete the React Native .flowconfig, because it defines a lot of custom configuration required for the project to typecheck cleanly.
Let's instead look at the initial error:
.flowconfig:53 Unsupported option specified! (unsafe.enable_getters_and_setters)
error Command failed with exit code 8.
This is caused by the version of Flow you installed with yarn add flow-bin no longer supporting this option (It was removed in 0.62). You'll need to install the exact version of Flow defined on the last line of your .flowconfig
[version]
^0.61.0
You can do this with:
yarn add flow-bin#0.61
Now the project should type check correctly.
Note that in the future, if you upgrade your project template with react-native upgrade and you accept the changes to .flowconfig, you may need to manually upgrade your flow-bin dependency to match.
Found this semi-related issue which recommended updating the flowconfig to use the latest version from create-react-native-app. Seems to have worked for me.
Go to .flowconfig file in your root project folder.
Delete this lines:
esproposal.optional_chaining=enable
esproposal.nullish_coalescing=enable
Done!

Error when calling request binary, system exit code: 126, text output, Error when calling response binary, system exit code: 126, text output:

I'm using a prestashop version 1.6.1.1 for my site and im using "tggatos SIPS/ATOS" module for payements.
After migrating my site to a new server i got some errors because of which the payment module is not working :
Error when calling request binary, system exit code: 126, text output:
Error when calling response binary, system exit code: 126, text output:
I would be very grateful for any advice or suggestion on how to fix this issue.
To resolve this issue you have to make sure, that those files are actually binaries. If you've transferred them i.e. by filezilla ftp client then transfer is not in binary mode by default.
Unpack them directly from archive on server or change transfer settings should resolve that issue.

ejabberd hook execution error while trying building a message receipts module

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.

Where to find documentation of apache2-mod-xsendfile version 9.2?

I have this version installed and I'm unable to correctly configure the module due to a lack of documentation. In particular the option XSendFilePath is not recognized:
Invalid command 'XSendFilePath', perhaps misspelled or defined by a module not included in the server configuration
If I remove the XSendFilePath directive I get the error:
The given path was above the root path: xsendfile: unable to find file: