Re: [rsyslog] Unable to use foreach
The foreach assuming json_object shouldn't be a problem, because it checks for the same before invoking the loop. All I can commit to is I can re-look at it once I have some time at hand. Which version of json-c are you using? On Fri, Jun 12, 2015 at 1:28 AM, David Lang wrote: > Just a note that there is definantly something wrong with the variable > handling right now. I've got a hard to reproduce bug that I've been fighting > for the last month where messages from just a couple sources seem to trigger > corruption when sending messages out with an action that has it's own queue > and a custom template (output prior to the point is fine, but the message > send and output after shows corrupt data, occasionally a double free or > other corruption message) > > Some of the cleanup in the clang support branch seems to help some of it, > but the one box that I tested it on hasn't let me reproduce the problem > since, even with older versions :-( > > David Lang > > > > ___ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of > sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T > LIKE THAT. -- Regards, Janmejay http://codehunk.wordpress.com ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
2015-06-12 16:26 GMT+02:00 Rainer Gerhards : > Sent from phone, thus brief. > Am 12.06.2015 16:11 schrieb "David Lang" : > > > > On Fri, 12 Jun 2015, Rainer Gerhards wrote: > > > >> 2015-06-11 23:06 GMT+02:00 Brian Knox : > >>> > >>> Florian - plan will probably depend on what we decide we're deploying. > >>> Andre has set up an account already ( Rainer may have the details as > well > >>> ). We gave them access to the beta for the team account features - so > it > >>> should already be set up as a team account. We should make sure any > >>> infrastructure we set up is provisioned from that account since we (DO) > >>> have applied quite a bit of credit to it. > >>> > >>> If we're just working together on how we'd like to automate package > >>> building I'd suggest a small server to start with and if we grow out of > it > >>> we can bump it up.. maybe the 2GB ram / 2 core / 40GB ssd option to > >>> prototype on? Hard to know until we nail down exactly what we're > trying to > >>> stand up. > Sounds fine to me. Even with virtual machines I usually work with a similar setup. I assume it will be sufficient at first. > >> > >> > >> OK, I think I'll simply provision such a machine (so I finally get my > >> hands on your interface as well ;)). Does the NYC datacenter sound > >> good given our collaborator base? > > > > > > I don't think the collaborator base needs to drive the datacenter, we'll > be working via git/ssh/etc anyway. > > Lol, you know I am an old fashioned guy ;) but I was more thinking on > internet closeness ... But agreed that's also yesteryears ;) > At first I thought the same, but really today locations on a global scale are mostly irrelevant for such work. Florian > > Rainer > > > > David Lang > > > >> What do you think makes most sense from a file system structure point > >> of view? I have something along this on my mind: > >> > >> /home/... > >> pkgproject - packaging project user (also for cron jobs) > >> rainer > >> brian > >> andre > >> florian > >> > >> > >> under pkgproject, I'd create subdirs for each git repository. > >> > >> Once done, I'd see that I can migrate my current daily build > >> environment to that machine. That will probably raise questions, it's > >> currently tied to the result of testbench runs. Maybe issues to > >> discuss... Let's assume this works then we can begin to modify it in a > >> way that suits us better. > >> > >> It would probably good to describe the environment I use. I could do a > >> Hangout on that, but I am not sure if I have sufficient time the next > >> days and enough advance notice timeframe to make it fully interactive. > >> > >> Comments? > >> > >> Rainer > >> ___ > >> rsyslog mailing list > >> http://lists.adiscon.net/mailman/listinfo/rsyslog > >> http://www.rsyslog.com/professional-services/ > >> What's up with rsyslog? Follow https://twitter.com/rgerhards > >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > >> > > ___ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com/professional-services/ > > What's up with rsyslog? Follow https://twitter.com/rgerhards > > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > ___ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] (no subject)
Thanks you for the answer!
Below is the exact config for official rsyslog-8.10.0.ad1-2.el7.x86_64 from
my test CentOS 7 machine
# grep -v '^#\|^$' /etc/rsyslog.conf
$ModLoad imuxsock # provides support for local system logging (e.g. via
logger command)
$ModLoad imklog # reads kernel messages (the same are read from journald)
$WorkDirectory /var/lib/rsyslog
$ActionFileDefaultTemplate RSYSLOG_TraditionalFileFormat
$IncludeConfig /etc/rsyslog.d/*.conf
*.info;mail.none;authpriv.none;cron.none/var/log/messages
authpriv.* /var/log/secure
mail.* -/var/log/maillog
cron.* /var/log/cron
*.emerg :omusrmsg:*
uucp,news.crit /var/log/spooler
local7.*/var/log/boot.log
# ls /etc/rsyslog.d/
00-server.conf 50-client.conf listen.conf
# cat /etc/rsyslog.d/00-server.conf
$ModLoad imrelp
$InputRELPServerRun 2514
$template DynHostMessages,
"/var/log/HOSTS/%HOSTNAME%/messages-%$YEAR%%$MONTH%%$DAY%"
if $inputname == 'imrelp' then {
*.* -?DynHostMessages
stop
}
# cat /etc/rsyslog.d/50-client.conf
$ModLoad omrelp
*.* :omrelp:127.0.0.1:2514
# cat /etc/rsyslog.d/listen.conf
$SystemLogSocketName /run/systemd/journal/syslog
On every restart Rsyslog process hangs without eating any resources.
There is no loops because of config files order and immediately stopping
everything received from imrelp as shown above.
I believe the problem is in RELP module because there is not problems then
I switch to TCP module as shown below.
# cat /etc/rsyslog.d/00-server.conf
$ModLoad imtcp
$InputTCPServerRun 514
$template DynHostMessages,
"/var/log/HOSTS/%HOSTNAME%/messages-%$YEAR%%$MONTH%%$DAY%"
if $inputname == 'imtcp' then {
*.* -?DynHostMessages
stop
}
# cat /etc/rsyslog.d/50-client.conf
$ModLoad omrelp
*.* @@127.0.0.1:514
Regards
Aleksey
On Fri, Jun 12, 2015 at 5:09 PM, David Lang wrote:
> What else in is the config?
>
> when you say it hangs on a restart, is it eating CPU, doing a lot of I/O
> or just sitting doing nothing?
>
> I don't see a good reason to send to yourself over relp, and if your
> server is doing that, you are trying very hard to create a loop.
>
> David lang
>
>
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
[rsyslog] Rsyslog Remote Logging Timestamp Consistency
Hi, I'm logging from several machines to a centralised location. In both the server and the clients I've set the configuration as below, $ActionFileDefaultTemplate RSYSLOG_FileFormat for more accurate timestamp. But on the server I see that the timestamp is accurate only upto seconds. But on the clients I see the logs are more accurate. Please help me in resolving this issue? Thanks. ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
Sent from phone, thus brief. Am 12.06.2015 16:11 schrieb "David Lang" : > > On Fri, 12 Jun 2015, Rainer Gerhards wrote: > >> 2015-06-11 23:06 GMT+02:00 Brian Knox : >>> >>> Florian - plan will probably depend on what we decide we're deploying. >>> Andre has set up an account already ( Rainer may have the details as well >>> ). We gave them access to the beta for the team account features - so it >>> should already be set up as a team account. We should make sure any >>> infrastructure we set up is provisioned from that account since we (DO) >>> have applied quite a bit of credit to it. >>> >>> If we're just working together on how we'd like to automate package >>> building I'd suggest a small server to start with and if we grow out of it >>> we can bump it up.. maybe the 2GB ram / 2 core / 40GB ssd option to >>> prototype on? Hard to know until we nail down exactly what we're trying to >>> stand up. >> >> >> OK, I think I'll simply provision such a machine (so I finally get my >> hands on your interface as well ;)). Does the NYC datacenter sound >> good given our collaborator base? > > > I don't think the collaborator base needs to drive the datacenter, we'll be working via git/ssh/etc anyway. Lol, you know I am an old fashioned guy ;) but I was more thinking on internet closeness ... But agreed that's also yesteryears ;) Rainer > > David Lang > >> What do you think makes most sense from a file system structure point >> of view? I have something along this on my mind: >> >> /home/... >> pkgproject - packaging project user (also for cron jobs) >> rainer >> brian >> andre >> florian >> >> >> under pkgproject, I'd create subdirs for each git repository. >> >> Once done, I'd see that I can migrate my current daily build >> environment to that machine. That will probably raise questions, it's >> currently tied to the result of testbench runs. Maybe issues to >> discuss... Let's assume this works then we can begin to modify it in a >> way that suits us better. >> >> It would probably good to describe the environment I use. I could do a >> Hangout on that, but I am not sure if I have sufficient time the next >> days and enough advance notice timeframe to make it fully interactive. >> >> Comments? >> >> Rainer >> ___ >> rsyslog mailing list >> http://lists.adiscon.net/mailman/listinfo/rsyslog >> http://www.rsyslog.com/professional-services/ >> What's up with rsyslog? Follow https://twitter.com/rgerhards >> NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. >> > ___ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
On Fri, 12 Jun 2015, Rainer Gerhards wrote: 2015-06-11 20:59 GMT+02:00 David Lang : If the package is built from the master git tree, it should be signed by a common project key. I guess that includes packages build from the v8-stable branches. I ask because from master we usually build only the daily builds. Right. Anything built from any branch of the rsyslog git repository is a project package, anything built from a person't repository is a personal testing branch. David Lang ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
On Fri, 12 Jun 2015, Rainer Gerhards wrote: 2015-06-11 23:06 GMT+02:00 Brian Knox : Florian - plan will probably depend on what we decide we're deploying. Andre has set up an account already ( Rainer may have the details as well ). We gave them access to the beta for the team account features - so it should already be set up as a team account. We should make sure any infrastructure we set up is provisioned from that account since we (DO) have applied quite a bit of credit to it. If we're just working together on how we'd like to automate package building I'd suggest a small server to start with and if we grow out of it we can bump it up.. maybe the 2GB ram / 2 core / 40GB ssd option to prototype on? Hard to know until we nail down exactly what we're trying to stand up. OK, I think I'll simply provision such a machine (so I finally get my hands on your interface as well ;)). Does the NYC datacenter sound good given our collaborator base? I don't think the collaborator base needs to drive the datacenter, we'll be working via git/ssh/etc anyway. David Lang What do you think makes most sense from a file system structure point of view? I have something along this on my mind: /home/... pkgproject - packaging project user (also for cron jobs) rainer brian andre florian under pkgproject, I'd create subdirs for each git repository. Once done, I'd see that I can migrate my current daily build environment to that machine. That will probably raise questions, it's currently tied to the result of testbench runs. Maybe issues to discuss... Let's assume this works then we can begin to modify it in a way that suits us better. It would probably good to describe the environment I use. I could do a Hangout on that, but I am not sure if I have sufficient time the next days and enough advance notice timeframe to make it fully interactive. Comments? Rainer ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] (no subject)
What else in is the config?
when you say it hangs on a restart, is it eating CPU, doing a lot of I/O or just
sitting doing nothing?
I don't see a good reason to send to yourself over relp, and if your server is
doing that, you are trying very hard to create a loop.
David lang
On Fri, 12 Jun 2015, Aleksey Chudov wrote:
Date: Fri, 12 Jun 2015 12:24:19 +0300
From: Aleksey Chudov
Reply-To: rsyslog-users
To: rsyslog@lists.adiscon.com
Subject: [rsyslog] (no subject)
Hello,
I have configured Rsyslog central server and created the same RELP client
configuration for all Rsyslog clients and Rsyslog server itself.
My test configuration below
1. Server only
# cat /etc/rsyslog.d/00-server.conf
$ModLoad imrelp
$InputRELPServerRun 2514
$template DynHostMessages,
"/var/log/HOSTS/%HOSTNAME%/messages-%$YEAR%%$MONTH%%$DAY%"
if $inputname == 'imrelp' then {
*.* -?DynHostMessages
stop
}
2. Clients and server
# cat /etc/rsyslog.d/50-client.conf
$ModLoad omrelp
*.* :omrelp:127.0.0.1:2514
While using the above configuration Rsyslog server process hungs on every
restart and needs to be killed by SIGKILL. There's no problem with
delivery of messages.
This configuration may looks strange. Why server should send messages to
themselves over relp? Just to simplify the configuration and standardize
log files location for all hosts without creating custom rules for the
server.
I have tested official packages
rsyslog 7.6.7-1.el7
rsyslog-relp 7.6.7-1.el7
and
rsyslog 8.10.0.ad1-2.el7
rsyslog-relp 8.10.0.ad1-2.el7
Is it a bug?
Regards,
Aleksey
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
Let's do it "around the (my) corner" in Frankfurt ;) Sent from phone, thus brief. Am 12.06.2015 14:39 schrieb "Brian Knox" : > Rainer - truth be told the best datacenter we currently have is Frankfurt > :) It just opened recently, and the hypervisors in Germany are on the new > (v2) version of our hardware platform, have 40gbit nics, etc. > > If you wanted to do it in NYC instead, I'd suggest NYC3. > > Brian > > > > On Fri, Jun 12, 2015 at 8:25 AM, Rainer Gerhards > > wrote: > > > 2015-06-11 23:06 GMT+02:00 Brian Knox : > > > Florian - plan will probably depend on what we decide we're deploying. > > > Andre has set up an account already ( Rainer may have the details as > well > > > ). We gave them access to the beta for the team account features - so > it > > > should already be set up as a team account. We should make sure any > > > infrastructure we set up is provisioned from that account since we (DO) > > > have applied quite a bit of credit to it. > > > > > > If we're just working together on how we'd like to automate package > > > building I'd suggest a small server to start with and if we grow out of > > it > > > we can bump it up.. maybe the 2GB ram / 2 core / 40GB ssd option to > > > prototype on? Hard to know until we nail down exactly what we're > trying > > to > > > stand up. > > > > OK, I think I'll simply provision such a machine (so I finally get my > > hands on your interface as well ;)). Does the NYC datacenter sound > > good given our collaborator base? > > > > What do you think makes most sense from a file system structure point > > of view? I have something along this on my mind: > > > > /home/... > > pkgproject - packaging project user (also for cron jobs) > > rainer > > brian > > andre > > florian > > > > > > under pkgproject, I'd create subdirs for each git repository. > > > > Once done, I'd see that I can migrate my current daily build > > environment to that machine. That will probably raise questions, it's > > currently tied to the result of testbench runs. Maybe issues to > > discuss... Let's assume this works then we can begin to modify it in a > > way that suits us better. > > > > It would probably good to describe the environment I use. I could do a > > Hangout on that, but I am not sure if I have sufficient time the next > > days and enough advance notice timeframe to make it fully interactive. > > > > Comments? > > > > Rainer > > ___ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com/professional-services/ > > What's up with rsyslog? Follow https://twitter.com/rgerhards > > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > > DON'T LIKE THAT. > > > ___ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
Rainer - truth be told the best datacenter we currently have is Frankfurt :) It just opened recently, and the hypervisors in Germany are on the new (v2) version of our hardware platform, have 40gbit nics, etc. If you wanted to do it in NYC instead, I'd suggest NYC3. Brian On Fri, Jun 12, 2015 at 8:25 AM, Rainer Gerhards wrote: > 2015-06-11 23:06 GMT+02:00 Brian Knox : > > Florian - plan will probably depend on what we decide we're deploying. > > Andre has set up an account already ( Rainer may have the details as well > > ). We gave them access to the beta for the team account features - so it > > should already be set up as a team account. We should make sure any > > infrastructure we set up is provisioned from that account since we (DO) > > have applied quite a bit of credit to it. > > > > If we're just working together on how we'd like to automate package > > building I'd suggest a small server to start with and if we grow out of > it > > we can bump it up.. maybe the 2GB ram / 2 core / 40GB ssd option to > > prototype on? Hard to know until we nail down exactly what we're trying > to > > stand up. > > OK, I think I'll simply provision such a machine (so I finally get my > hands on your interface as well ;)). Does the NYC datacenter sound > good given our collaborator base? > > What do you think makes most sense from a file system structure point > of view? I have something along this on my mind: > > /home/... > pkgproject - packaging project user (also for cron jobs) > rainer > brian > andre > florian > > > under pkgproject, I'd create subdirs for each git repository. > > Once done, I'd see that I can migrate my current daily build > environment to that machine. That will probably raise questions, it's > currently tied to the result of testbench runs. Maybe issues to > discuss... Let's assume this works then we can begin to modify it in a > way that suits us better. > > It would probably good to describe the environment I use. I could do a > Hangout on that, but I am not sure if I have sufficient time the next > days and enough advance notice timeframe to make it fully interactive. > > Comments? > > Rainer > ___ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
2015-06-11 23:06 GMT+02:00 Brian Knox : > Florian - plan will probably depend on what we decide we're deploying. > Andre has set up an account already ( Rainer may have the details as well > ). We gave them access to the beta for the team account features - so it > should already be set up as a team account. We should make sure any > infrastructure we set up is provisioned from that account since we (DO) > have applied quite a bit of credit to it. > > If we're just working together on how we'd like to automate package > building I'd suggest a small server to start with and if we grow out of it > we can bump it up.. maybe the 2GB ram / 2 core / 40GB ssd option to > prototype on? Hard to know until we nail down exactly what we're trying to > stand up. OK, I think I'll simply provision such a machine (so I finally get my hands on your interface as well ;)). Does the NYC datacenter sound good given our collaborator base? What do you think makes most sense from a file system structure point of view? I have something along this on my mind: /home/... pkgproject - packaging project user (also for cron jobs) rainer brian andre florian under pkgproject, I'd create subdirs for each git repository. Once done, I'd see that I can migrate my current daily build environment to that machine. That will probably raise questions, it's currently tied to the result of testbench runs. Maybe issues to discuss... Let's assume this works then we can begin to modify it in a way that suits us better. It would probably good to describe the environment I use. I could do a Hangout on that, but I am not sure if I have sufficient time the next days and enough advance notice timeframe to make it fully interactive. Comments? Rainer ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] packaging project mission statement
Excellent! I'll start in on the omczmq and imczmq packages when I get a little time! Cheers, Brian On Fri, Jun 12, 2015 at 8:17 AM, Rainer Gerhards wrote: > Hi all, > > I have amended the README.md with a mission statement plus some more > details: > > https://github.com/rsyslog/rsyslog-pkg-ubuntu/blob/master/README.md > > Please have a look and act accordingly. > > Thx, > Rainer > ___ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com/professional-services/ > What's up with rsyslog? Follow https://twitter.com/rgerhards > NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad > of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you > DON'T LIKE THAT. > ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
Re: [rsyslog] rsyslog packaging project - was: rsyslog adiscon packages
2015-06-11 20:59 GMT+02:00 David Lang : > If the package is built from the master git tree, it should be signed by a > common project key. I guess that includes packages build from the v8-stable branches. I ask because from master we usually build only the daily builds. Rainer ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
[rsyslog] packaging project mission statement
Hi all, I have amended the README.md with a mission statement plus some more details: https://github.com/rsyslog/rsyslog-pkg-ubuntu/blob/master/README.md Please have a look and act accordingly. Thx, Rainer ___ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
[rsyslog] (no subject)
Hello,
I have configured Rsyslog central server and created the same RELP client
configuration for all Rsyslog clients and Rsyslog server itself.
My test configuration below
1. Server only
# cat /etc/rsyslog.d/00-server.conf
$ModLoad imrelp
$InputRELPServerRun 2514
$template DynHostMessages,
"/var/log/HOSTS/%HOSTNAME%/messages-%$YEAR%%$MONTH%%$DAY%"
if $inputname == 'imrelp' then {
*.* -?DynHostMessages
stop
}
2. Clients and server
# cat /etc/rsyslog.d/50-client.conf
$ModLoad omrelp
*.* :omrelp:127.0.0.1:2514
While using the above configuration Rsyslog server process hungs on every
restart and needs to be killed by SIGKILL. There's no problem with
delivery of messages.
This configuration may looks strange. Why server should send messages to
themselves over relp? Just to simplify the configuration and standardize
log files location for all hosts without creating custom rules for the
server.
I have tested official packages
rsyslog 7.6.7-1.el7
rsyslog-relp 7.6.7-1.el7
and
rsyslog 8.10.0.ad1-2.el7
rsyslog-relp 8.10.0.ad1-2.el7
Is it a bug?
Regards,
Aleksey
___
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
