Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rsyslog.conf parsing failed in Ubuntu 16 with Rainerscript #142

Open
klaurean opened this issue May 4, 2016 · 3 comments
Open

Rsyslog.conf parsing failed in Ubuntu 16 with Rainerscript #142

klaurean opened this issue May 4, 2016 · 3 comments

Comments

@klaurean
Copy link

klaurean commented May 4, 2016

Having issues with Ubuntu 16.04 which has rsyslog.conf in RainerScript format.
We are puppetizing deployments for Ubuntu 16.04 OSes and we need to have it run successfully with this new format.
When running the rsyslog.lns on the file, we get the error below:
Error: /Stage[main]/Entos_syslog_config/Syslog[kern_info]: Could not evaluate: Augeas didn't load /etc/rsyslog.conf with Rsyslog.lns: Get did not match entire input (line:13, character:0)
Error: /Stage[main]/Entos_syslog_config/Syslog[all_info]: Could not evaluate: Augeas didn't load /etc/rsyslog.conf with Rsyslog.lns: Get did not match entire input (line:13, character:0)
...etc...

Using augtool, I found that it is the following two lines that are in rainerscript format instead of legacy (if commented out and replaced with legacy format, augtool runs fine on rsyslog.conf on this OS).

"rainerscript"
module(load="imuxsock") # provides support for local system logging
module(load="imklog") # provides kernel logging support

"legacy"
$ModLoad imuxsock # provides support for local system logging
$ModLoad imklog # provides kernel logging support

Rsyslog reference
http://www.rsyslog.com/doc/v8-stable/configuration/basic_structure.html#configuration-file

Thanks!

@klaurean
Copy link
Author

klaurean commented May 5, 2016

Hi @domcleal please let me know if you are the right person for this. This is my first issue submission so I am still learning the procedure!

@telnoratti
Copy link

I can confirm I see this issue as well on 16.04.

@telnoratti
Copy link

e00c7a815cb6c3e63aa3eec7329126fd2eccbf79 fixes this issue for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants