From: Serge L. <fi...@in...> - 2009-08-24 04:49:51
|
Hello, I'm still not sure, but it seems to be correlated: if syslog-ng starts before an attempt to login (ssh or console - it doesn't matter) the login process is getting stuck. As a workaround you can add "--no-caps" to the daemon parameters. I'm trying to update syslog-ng to 3.0.4 and verify if the problem goes away. Sincerely, Serge |
From: Heiko Z. <he...@zu...> - 2009-08-24 11:42:36
|
Quoting Serge Leschinsky <fi...@in...>: > Hello, > > I'm still not sure, but it seems to be correlated: if syslog-ng > starts before an > attempt to login (ssh or console - it doesn't matter) the login process is > getting stuck. > > As a workaround you can add "--no-caps" to the daemon parameters. > > I'm trying to update syslog-ng to 3.0.4 and verify if the problem goes away. This is interesting, I never saw this behavior before.... Could it have something to do with a kernel update or another program we recently updated? -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Heiko Z. <he...@zu...> - 2009-08-24 21:07:27
|
Quoting Serge Leschinsky <fi...@in...>: > Hello, > > I'm still not sure, but it seems to be correlated: if syslog-ng > starts before an > attempt to login (ssh or console - it doesn't matter) the login process is > getting stuck. > > As a workaround you can add "--no-caps" to the daemon parameters. > > I'm trying to update syslog-ng to 3.0.4 and verify if the problem goes away. Syslog-ng is not happy in the current DL CVS version, it's complaining a lot about the config file. It may be worth sticking with the old version for now. What do you think? -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Serge L. <fi...@in...> - 2009-08-25 02:45:38
|
Heiko Zuerker wrote: > Quoting Serge Leschinsky <fi...@in...>: > >> Hello, >> >> I'm still not sure, but it seems to be correlated: if syslog-ng >> starts before an >> attempt to login (ssh or console - it doesn't matter) the login process is >> getting stuck. >> >> As a workaround you can add "--no-caps" to the daemon parameters. >> >> I'm trying to update syslog-ng to 3.0.4 and verify if the problem goes away. > > Syslog-ng is not happy in the current DL CVS version, it's complaining > a lot about the config file. Heiko, are you sure it's new config file? I modified it for new syslog and it's OK ( at least on my system ). It should be like the following: root@gw:~ # cat /etc/syslog-ng/syslog-ng.conf @version: 3.0 ##################################################################### # define options for syslog ##################################################################### options { long_hostnames(on); flush_lines(0); time_reopen(60); use_dns (no); }; ##################################################################### # define the source pipe for all local messages ##################################################################### source src { file("/proc/kmsg" program_override("kernel: ")); unix-stream("/dev/log" max-connections(1000)); internal(); }; .... > It may be worth sticking with the old version for now. What do you think? > 3.0.4 working correctly. I'm quite limited in testing options, but with 3.0.4 everything looks fine. So, I'd suggest moving forward... The changes will be committed tonight (PST). Sincerely, Serge |
From: Heiko Z. <he...@zu...> - 2009-08-27 18:43:47
|
Quoting Serge Leschinsky <fi...@in...>: > Heiko Zuerker wrote: >> Quoting Serge Leschinsky <fi...@in...>: >> >>> Hello, >>> >>> I'm still not sure, but it seems to be correlated: if syslog-ng >>> starts before an >>> attempt to login (ssh or console - it doesn't matter) the login process is >>> getting stuck. >>> >>> As a workaround you can add "--no-caps" to the daemon parameters. >>> >>> I'm trying to update syslog-ng to 3.0.4 and verify if the problem >>> goes away. >> >> Syslog-ng is not happy in the current DL CVS version, it's complaining >> a lot about the config file. > Heiko, are you sure it's new config file? I modified it for new > syslog and it's > OK ( at least on my system ). > > It should be like the following: > > root@gw:~ # cat /etc/syslog-ng/syslog-ng.conf > @version: 3.0 > > ##################################################################### > # define options for syslog > ##################################################################### > options { long_hostnames(on); flush_lines(0); time_reopen(60); > use_dns (no); }; > > ##################################################################### > # define the source pipe for all local messages > ##################################################################### > source src { file("/proc/kmsg" program_override("kernel: ")); > unix-stream("/dev/log" max-connections(1000)); internal(); }; > .... Syslog-ng works fine with the default config, but not if you upgrade an older system. Can we add something simple to upgrade-config to make the upgrade life easier? -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Serge L. <fi...@in...> - 2009-08-28 03:24:59
|
Heiko Zuerker wrote: > Syslog-ng works fine with the default config, but not if you upgrade > an older system. > Can we add something simple to upgrade-config to make the upgrade life easier? > Hmm... Probably we can try to apply the diff for syslog-ng config, I think on most systems the diff should apply, because the changes affect only main options. Serge |
From: Bruce S. <bw...@re...> - 2009-08-28 11:39:38
|
>> Syslog-ng works fine with the default config, but not if you upgrade >> an older system. >> Can we add something simple to upgrade-config to make the upgrade life easier? > > Hmm... Probably we can try to apply the diff for syslog-ng config, I think on > most systems the diff should apply, because the changes affect only main options. It shouldn't be a problem unless they customized their syslog-ng config. And if they customized it, there is a really good chance a patch would fail. I'm not sure of the best solution for this. - BS |
From: Heiko Z. <he...@zu...> - 2009-08-28 11:52:00
|
Quoting Bruce Smith <bw...@re...>: >>> Syslog-ng works fine with the default config, but not if you upgrade >>> an older system. >>> Can we add something simple to upgrade-config to make the upgrade >>> life easier? >> >> Hmm... Probably we can try to apply the diff for syslog-ng config, >> I think on >> most systems the diff should apply, because the changes affect only >> main options. > > It shouldn't be a problem unless they customized their syslog-ng config. > And if they customized it, there is a really good chance a patch would fail. > > I'm not sure of the best solution for this. There's not too much we can do if folks change their config files, but I think we should be able to modify those specific lines if they're not changed. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Bruce S. <bw...@re...> - 2009-08-28 12:54:51
|
>>>> Syslog-ng works fine with the default config, but not if you upgrade >>>> an older system. >>>> Can we add something simple to upgrade-config to make the upgrade >>>> life easier? >>> >>> Hmm... Probably we can try to apply the diff for syslog-ng config, >>> I think on >>> most systems the diff should apply, because the changes affect only >>> main options. >> >> It shouldn't be a problem unless they customized their syslog-ng config. >> And if they customized it, there is a really good chance a patch would fail. >> >> I'm not sure of the best solution for this. > > There's not too much we can do if folks change their config files, but > I think we should be able to modify those specific lines if they're > not changed. If the config file hasn't changed, it should update to the new version by default. Isn't that the way it works? - BS |
From: Heiko Z. <he...@zu...> - 2009-08-28 13:17:55
|
Quoting Bruce Smith <bw...@re...>: >>>>> Syslog-ng works fine with the default config, but not if you upgrade >>>>> an older system. >>>>> Can we add something simple to upgrade-config to make the upgrade >>>>> life easier? >>>> >>>> Hmm... Probably we can try to apply the diff for syslog-ng config, >>>> I think on >>>> most systems the diff should apply, because the changes affect only >>>> main options. >>> >>> It shouldn't be a problem unless they customized their syslog-ng config. >>> And if they customized it, there is a really good chance a patch >>> would fail. >>> >>> I'm not sure of the best solution for this. >> >> There's not too much we can do if folks change their config files, but >> I think we should be able to modify those specific lines if they're >> not changed. > > If the config file hasn't changed, it should update to the new version > by default. Isn't that the way it works? That is correct. But isn't it highly likely that somebody added lines for i.e. a remote log? At least I have all my servers set up this way. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Bruce S. <bw...@re...> - 2009-08-28 13:51:15
|
>>>>>> Syslog-ng works fine with the default config, but not if you upgrade >>>>>> an older system. >>>>>> Can we add something simple to upgrade-config to make the upgrade >>>>>> life easier? >>>>> >>>>> Hmm... Probably we can try to apply the diff for syslog-ng config, >>>>> I think on >>>>> most systems the diff should apply, because the changes affect only >>>>> main options. >>>> >>>> It shouldn't be a problem unless they customized their syslog-ng config. >>>> And if they customized it, there is a really good chance a patch >>>> would fail. >>>> >>>> I'm not sure of the best solution for this. >>> >>> There's not too much we can do if folks change their config files, but >>> I think we should be able to modify those specific lines if they're >>> not changed. >> >> If the config file hasn't changed, it should update to the new version >> by default. Isn't that the way it works? > > That is correct. > But isn't it highly likely that somebody added lines for i.e. a remote > log? At least I have all my servers set up this way. It seems like the last time I looked, those lines are already in the config file commented out, so all you have to do is uncomment them. And I don't think a patch will work on a line that has changed at all. Even just a "#" removed. - BS |
From: Heiko Z. <he...@zu...> - 2009-08-28 13:59:55
|
Quoting Bruce Smith <bw...@re...>: >>>>>>> Syslog-ng works fine with the default config, but not if you upgrade >>>>>>> an older system. >>>>>>> Can we add something simple to upgrade-config to make the upgrade >>>>>>> life easier? >>>>>> >>>>>> Hmm... Probably we can try to apply the diff for syslog-ng config, >>>>>> I think on >>>>>> most systems the diff should apply, because the changes affect only >>>>>> main options. >>>>> >>>>> It shouldn't be a problem unless they customized their syslog-ng config. >>>>> And if they customized it, there is a really good chance a patch >>>>> would fail. >>>>> >>>>> I'm not sure of the best solution for this. >>>> >>>> There's not too much we can do if folks change their config files, but >>>> I think we should be able to modify those specific lines if they're >>>> not changed. >>> >>> If the config file hasn't changed, it should update to the new version >>> by default. Isn't that the way it works? >> >> That is correct. >> But isn't it highly likely that somebody added lines for i.e. a remote >> log? At least I have all my servers set up this way. > > It seems like the last time I looked, those lines are already in the > config file commented out, so all you have to do is uncomment them. > > And I don't think a patch will work on a line that has changed at all. > Even just a "#" removed. Another options would be using sed and just replacing the lines in question. -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
From: Bruce S. <bw...@re...> - 2009-08-28 14:03:56
|
>>>>>>>> Syslog-ng works fine with the default config, but not if you upgrade >>>>>>>> an older system. >>>>>>>> Can we add something simple to upgrade-config to make the upgrade >>>>>>>> life easier? >>>>>>> >>>>>>> Hmm... Probably we can try to apply the diff for syslog-ng config, >>>>>>> I think on >>>>>>> most systems the diff should apply, because the changes affect only >>>>>>> main options. >>>>>> >>>>>> It shouldn't be a problem unless they customized their syslog-ng config. >>>>>> And if they customized it, there is a really good chance a patch >>>>>> would fail. >>>>>> >>>>>> I'm not sure of the best solution for this. >>>>> >>>>> There's not too much we can do if folks change their config files, but >>>>> I think we should be able to modify those specific lines if they're >>>>> not changed. >>>> >>>> If the config file hasn't changed, it should update to the new version >>>> by default. Isn't that the way it works? >>> >>> That is correct. >>> But isn't it highly likely that somebody added lines for i.e. a remote >>> log? At least I have all my servers set up this way. >> >> It seems like the last time I looked, those lines are already in the >> config file commented out, so all you have to do is uncomment them. >> >> And I don't think a patch will work on a line that has changed at all. >> Even just a "#" removed. > > Another options would be using sed and just replacing the lines in question. That would stand a much better chance of working (IMO). - BS |