I will verify tomorrow if inotify is installed on the system. Running
CentOS7.2 and foreman 1.13.1.
Thanks in advance,
Christian
···
Am Donnerstag, 3. November 2016 13:52:08 UTC+1 schrieb Lukas Zapletal:
>
> On Thu, Nov 3, 2016 at 9:52 AM, Christian Froestl > <christia...@gmail.com > wrote:
> > webfrontend of smart-proxy dhcp
>
> What's that? Do you mean DHCP browser plugin?
>
> Anyway, we introduced some ISC DHCP optimizations via inotify, this
> might be regression. Symtoms are very similar.
>
> http://projects.theforeman.org/issues/16099
>
> What OS are you running on? Can you tell if inotify is available on your
> system?
>
> Dmitri, is it possible to turn off inotify listener and fallback to
> the legacy mode in configuration? I cannot find anything like that.
>
>
> --
> Later,
> Lukas @lzap Zapletal
>
The foreman-proxy service should be colocated with the DHCP daemon and
lease file, not remote.
···
On 03/11/16 12:51, Lukas Zapletal wrote:
> On Thu, Nov 3, 2016 at 9:52 AM, Christian Froestl > wrote:
>> webfrontend of smart-proxy dhcp
>
> What's that? Do you mean DHCP browser plugin?
>
> Anyway, we introduced some ISC DHCP optimizations via inotify, this
> might be regression. Symtoms are very similar.
>
> http://projects.theforeman.org/issues/16099
>
> What OS are you running on? Can you tell if inotify is available on your system?
It should be, if that's normal install from RPMs. And CentOS 7 has
kernel inotify for sure (unless you disabled it). Strange. Any errors
during proxy startup?
···
On Thu, Nov 3, 2016 at 3:42 PM, Christian Froestl wrote:
> Hi,
>
> I will verify tomorrow if inotify is installed on the system. Running
> CentOS7.2 and foreman 1.13.1.
>
> Thanks in advance,
> Christian
>
> Am Donnerstag, 3. November 2016 13:52:08 UTC+1 schrieb Lukas Zapletal:
>>
>> On Thu, Nov 3, 2016 at 9:52 AM, Christian Froestl >> wrote:
>> > webfrontend of smart-proxy dhcp
>>
>> What's that? Do you mean DHCP browser plugin?
>>
>> Anyway, we introduced some ISC DHCP optimizations via inotify, this
>> might be regression. Symtoms are very similar.
>>
>> http://projects.theforeman.org/issues/16099
>>
>> What OS are you running on? Can you tell if inotify is available on your
>> system?
>>
>> Dmitri, is it possible to turn off inotify listener and fallback to
>> the legacy mode in configuration? I cannot find anything like that.
>>
>>
>> --
>> Later,
>> Lukas @lzap Zapletal
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscribe@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
I was wondering, if it is possible to detect such a scenario. During
plugin initialization, proxy could touch the file after inotify is
active and if no event is fired, we can sent out an error.
Anyway, thanks for the heads up!
···
On Thu, Nov 3, 2016 at 5:33 PM, Dominic Cleal wrote:
> Per Christian's other thread
> (https://groups.google.com/forum/#!topic/foreman-users/xEITFFe9uE8), the
> leases file appears to be accessed over NFS instead of being local to
> foreman-proxy, which will not work with inotify.
>
> The foreman-proxy service should be colocated with the DHCP daemon and
> lease file, not remote.
