Sles 11 SP 4
syslog-ng-2.0.9-27.34.39.2 - does threaded() even work on this version?
I'm trying to enable multithreading but running into a syntax error when adding the threaded() into the options {} stanza .. Line 16 is the threaded() .. I've tried a few things but nothing is working. Any advice would help? Thank You ~ Sean
=========== syslog-ng.conf ==================
options {
create_dirs(yes);
keep_hostname(yes);
log_fetch_limit(100);
flush_lines(100);
use_dns(no);
threaded(yes);
};
============== error ==============
Error parsing main, syntax error, unexpected LL_IDENTIFIER, expecting '}' in /opt/syslog-ng/etc/syslog-ng.conf at line 16, column 2:
threaded();
^^^^^^^^
Your syslog-ng version is too old, multithreading was introduced around version 3.3. You can find a list of newer packages at the syslog-ng website, and detailed instructions on how to install recent syslog-ng version on SLES.
Regards,
Robert
Related
We have:
Ubuntu 20.04 and Puppet 7.
We faced the issue with modules:
puppet-datadog-agent (both versions 3.1.0 and 3.15.0) and puppetlabs-concat (both versions 2.2.1 and 7.1.1) throw this error :
2022-07-05 11:15:56 +0000 Puppet (err): no parameter named 'target' (file: ../modules/concat/manifests/fragment.pp, line: 50) on Concat_fragment[datadog header] (file: ../modules/concat/manifests/fragment.pp, line: 50) on node [DNS](http://DNS)
We had a working puppet before updated datadog and concat modules, and now even rollback doesn't help us :(
Any ideas, dear experts?
Have recently installed PowerMTA server on CentOS 6, but unable to start pmta service and getting this error in logs.
service pmta restart
Stopping PowerMTA: [ OK ]
Starting PowerMTA: [FAILED]
/usr/sbin/pmtad --debug
2018-05-26 20:41:27 WARNING (line 15 of /etc/pmta/config): deprecated syntax for max-message-size; use file size syntax (such as in "100K") or "unlimited" instead.
2018-05-26 20:41:27 WARNING (line 82 of /etc/pmta/virtualhost.txt): "auto-cold-virtual-mta" deprecated; use explicitly defined cold Virtual MTAs instead.
2018-05-26 20:41:27 Startup error: Error in line 51 of /etc/pmta/config: Error in line 82 of /etc/pmta/virtualhost.txt: not a valid local IP address
I installed PMTA 4.5 on 5 different VPS and only this one not starting dunno what is wrong.
pmta/virtualhost.txt checked and ip is right.I know thease questions are stupid but i`m new with linux, thanks for help!
The IP in line 82 is a public IP, try to change it to a private one like 192.168...
I followed this guide:
https://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/
I stayed with the Active/Passive DRBD file system sharing. I had to reboot my cluster and now I am getting the following error:
Current DC: rbx-1 (version 1.1.16-12.el7_4.4-94ff4df) - partition with quorum
Last updated: Tue Nov 28 17:01:14 2017
Last change: Tue Nov 28 16:40:09 2017 by root via cibadmin on rbx-1
2 nodes configured
5 resources configured
Node rbx-2: UNCLEAN (offline)
Online: [ rbx-1 ]
Full list of resources:
ClusterIP (ocf::heartbeat:IPaddr2): Started rbx-1
WebSite (ocf::heartbeat:apache): Stopped
Master/Slave Set: WebDataClone [WebData]
WebData (ocf::linbit:drbd): FAILED rbx-1 (blocked)
Stopped: [ rbx-2 ]
WebFS (ocf::heartbeat:Filesystem): Stopped
Failed Actions:
* WebData_stop_0 on rbx-1 'invalid parameter' (2): call=20, status=complete, exitreason='none',
last-rc-change='Tue Nov 28 16:27:58 2017', queued=0ms, exec=3ms
Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled
Any ideas?
Also does anyone have any recommended guides for submitting jobs?
This post is relatively old at this point but I'll leave this here for others to find if they stumble upon the same issue.
This problem has to do with an issue with the DRBD integration script that pacemaker uses. If it's broken, missing, has incorrect permissions, etc. you can get an error like this. In CentOS 7 that script is located at /usr/lib/ocf/resource.d/drbd
Note: This is specifically for the guide mentioned by OP but may help you:
Section 7.1 has a big "IMPORTANT" block that talks about replacing the Pacemaker integration script due to a bug. If you use the command it tells you to there, you actually replace the script with a 404 Error page which obviously doesn't work, causing the error. You can fix this issue by replacing the script with the original, either by reinstalling DRBD...
yum remove -y kmod-drbd84 drbd84-utils
yum install -y kmod-drbd84 drbd84-utils
...or finding just the drbd script elsewhere and adding/replacing it to /usr/lib/ocf/resource.d/drbd. Make sure its permissions are correct and that it is set as executable.
Hope that helps!
After adding Owasp crs rules for Modsecurity and restarting apache I am getting this error in REQUEST-941-APPLICATION-ATTACK-XSS.conf file.
AH00526: Syntax error on line 56 of /etc/apache2/modsecurity.d/rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf:
Error creating rule: Failed to resolve operator: detectXSS
Action 'configtest' failed.
The Apache error log may have more information.
Please help me to fix this issue
DetectXSS was only added in ModSecurity 2.8: https://github.com/SpiderLabs/ModSecurity/wiki/Reference-Manual#detectXSS
You must be running a previous version. Possibly because you are using a packaged version and they are terrible about keeping these up to date except for security patches. Centos/RHEL for example only has ModSecurity 2.7.3 in the standard repo for example.
You should upgrade to the latest version.
when I try to install the linux-nagios-agent on my linux server I get the error below:
/home/lost+found/linux-nrpe-agent # ./fullinstall
/etc/os-release: line 2: syntax error near unexpected token `('
Below is the content of the os-release
# cat /etc/os-release
NAME=openSUSE
VERSION = 12.1 (Asparagus)
VERSION_ID="12.1"
PRETTY_NAME="openSUSE 12.1 (Asparagus) (x86_64)"
ID=opensuse
Any idea what is causing the problem?
Try to double quote the VERSION string, here's how it looks in a newer version:
# cat /etc/os-release
NAME=openSUSE
VERSION="13.2 (Harlequin)"
VERSION_ID="13.2"
PRETTY_NAME="openSUSE 13.2 (Harlequin) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.2"
BUG_REPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://opensuse.org/"
ID_LIKE="suse"